diff --git a/.github/actions-scripts/create-enterprise-issue.js b/.github/actions-scripts/create-enterprise-issue.js index 72e36a0dd3..4ae065133c 100755 --- a/.github/actions-scripts/create-enterprise-issue.js +++ b/.github/actions-scripts/create-enterprise-issue.js @@ -86,7 +86,9 @@ async function run() { 'utf8' ) const issueLabels = - milestone === 'release' ? ['enterprise release'] : ['enterprise deprecation', 'priority-4', 'batch', 'time sensitive'] + milestone === 'release' + ? ['enterprise release'] + : ['enterprise deprecation', 'priority-4', 'batch', 'time sensitive'] const issueTitle = `[${nextMilestoneDate}] Enterprise Server ${versionNumber} ${milestone} (technical steps)` const issueBody = `GHES ${versionNumber} ${milestone} occurs on ${nextMilestoneDate}. diff --git a/.github/actions-scripts/enable-automerge.js b/.github/actions-scripts/enable-automerge.js index 1d3885a623..649a0e5052 100644 --- a/.github/actions-scripts/enable-automerge.js +++ b/.github/actions-scripts/enable-automerge.js @@ -1,12 +1,23 @@ import { getOctokit } from '@actions/github' -const token = process.env.GITHUB_TOKEN -const prNumber = process.env.AUTOMERGE_PR_NUMBER -const github = getOctokit(token) main() async function main() { - const pull = await github.pulls.get({ - ...context.repo, + const [org, repo] = process.env.GITHUB_REPOSITORY.split('/') + if (!org || !repo) { + throw new Error('GITHUB_REPOSITORY environment variable not set') + } + const prNumber = process.env.AUTOMERGE_PR_NUMBER + if (!prNumber) { + throw new Error(`AUTOMERGE_PR_NUMBER environment variable not set`) + } + const token = process.env.GITHUB_TOKEN + if (!token) { + throw new Error(`GITHUB_TOKEN environment variable not set`) + } + const github = getOctokit(token) + const pull = await github.rest.pulls.get({ + owner: org, + repo: repo, pull_number: parseInt(prNumber), }) diff --git a/.github/actions-scripts/update-merge-queue-branch.js b/.github/actions-scripts/update-merge-queue-branch.js new file mode 100644 index 0000000000..8c8c061532 --- /dev/null +++ b/.github/actions-scripts/update-merge-queue-branch.js @@ -0,0 +1,135 @@ +#!/usr/bin/env node + +import { getOctokit } from '@actions/github' +const token = process.env.GITHUB_TOKEN +const github = getOctokit(token) + +// Mergeable status documentation here: +// https://docs.github.com/en/graphql/reference/enums#mergestatestatus +// https://docs.github.com/en/graphql/reference/enums#mergeablestate + +/* + This script gets a list of automerge-enabled PRs and sorts them + by priority. The PRs with the skip-to-front-of-merge-queue label + are prioritized first. The rest of the PRs are sorted by the date + they were updated. This is basically a FIFO queue, while allowing + writers the ability to skip the line when high-priority ships are + needed but a freeze isn't necessary. +*/ + +main() + +async function main() { + const [org, repo] = process.env.GITHUB_REPOSITORY.split('/') + if (!org || !repo) { + throw new Error('GITHUB_REPOSITORY environment variable not set') + } + // Get a list of open PRs and order them from oldest to newest + const query = `query ($first: Int, $after: String, $firstLabels: Int, $repo: String!, $org: String!) { + organization(login: $org) { + repository(name: $repo) { + pullRequests(first: $first, after: $after, states: OPEN, orderBy: {field: UPDATED_AT, direction: ASC}) { + edges{ + node { + number + url + updatedAt + mergeable + mergeStateStatus + autoMergeRequest { + enabledBy { + login + } + enabledAt + } + labels (first:$firstLabels){ + nodes { + name + } + } + } + } + pageInfo { + hasNextPage + endCursor + } + } + } + } + }` + + const queryVariables = { + repo, + org, + first: 100, + after: null, // when pagination in null it will get first page + firstLabels: 100, + headers: { + // required for the mergeStateStatus enum + accept: 'application/vnd.github.merge-info-preview+json', + }, + } + let hasNextPage = true + const autoMergeEnabledPRs = [] + + // we need to get all the paginated results in the case that + // there are more than 100 PRs + while (hasNextPage) { + const graph = await github.graphql(query, queryVariables) + const dataRoot = graph.organization.repository.pullRequests + const pullRequests = dataRoot.edges + // update pagination variables + hasNextPage = dataRoot.pageInfo.hasNextPage + // the endCursor is the start cursor for the next page + queryVariables.after = dataRoot.pageInfo.endCursor + + const filteredPrs = pullRequests + // this simplifies the format received from the graphql query to + // remove the unnecessary nested objects + .map((pr) => { + // make the labels object just an array of the label names + const labelArray = pr.node.labels.nodes.map((label) => label.name) + pr.node.labels = labelArray + // return the pr object and ✂️ the node property + return pr.node + }) + .filter((pr) => pr.autoMergeRequest !== null) + .filter((pr) => pr.mergeable === 'MERGEABLE') + // filter out prs that don't have a calculated mergeable state yet + .filter((pr) => pr.mergeStateStatus !== 'UNKNOWN') + // filter out prs that still need a review, have merge conflicts, + // or have failing ci tests + .filter((pr) => pr.mergeStateStatus !== 'BLOCKED') + // **NOTE**: In the future we may want to send slack message to initiators + // of PRs with the following merge states because these can happen after + // a PR is green and the automerge is enabled + .filter((pr) => pr.mergeStateStatus !== 'DIRTY') + .filter((pr) => pr.mergeStateStatus !== 'UNSTABLE') + + autoMergeEnabledPRs.push(...filteredPrs) + } + + // Get the list of prs with the skip label so they can + // be put at the beginning of the list + const prioritizedPrList = autoMergeEnabledPRs.sort( + (a, b) => + Number(b.labels.includes('skip-to-front-of-merge-queue')) - + Number(a.labels.includes('skip-to-front-of-merge-queue')) + ) + + if (prioritizedPrList.length) { + const nextInQueue = prioritizedPrList.shift() + // Update the branch for the next PR in the merge queue + github.rest.pulls.updateBranch({ + owner: org, + repo, + pull_number: nextInQueue.number, + }) + console.log(`⏱ Total PRs in the merge queue: ${prioritizedPrList.length + 1}`) + console.log(`🚂 Updated branch for PR #${JSON.stringify(nextInQueue, null, 2)}`) + } + + prioritizedPrList.length + ? console.log(`🚏 Next up in the queue: \n ${JSON.stringify(prioritizedPrList, null, 2)}`) + : console.log(`⚡ The merge queue is empty`) +} diff --git a/.github/allowed-actions.js b/.github/allowed-actions.js index 210021ab13..bb0d4a7904 100644 --- a/.github/allowed-actions.js +++ b/.github/allowed-actions.js @@ -17,7 +17,6 @@ export default [ 'cschleiden/actions-linter@caffd707beda4fc6083926a3dff48444bc7c24aa', // uses github-actions-parser v0.23.0 'dawidd6/action-delete-branch@47743101a121ad657031e6704086271ca81b1911', // v3.0.2 'dawidd6/action-download-artifact@af92a8455a59214b7b932932f2662fdefbd78126', // v2.15.0 - 'docker://chinthakagodawita/autoupdate-action:v1', 'dorny/paths-filter@eb75a1edc117d3756a18ef89958ee59f9500ba58', 'trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b', // v1.2.4 'github/codeql-action/analyze@v1', diff --git a/.github/workflows/autoupdate-branch.yml b/.github/workflows/autoupdate-branch.yml index ced565ca53..1dc89b56ca 100644 --- a/.github/workflows/autoupdate-branch.yml +++ b/.github/workflows/autoupdate-branch.yml @@ -1,20 +1,22 @@ name: Autoupdate branch -# **What it does**: Any pull requests with automerge will get main branch updates. -# **Why we have it**: So we don't have to watch pull requests and click update branch 100x. +# **What it does**: The next pull request in the merge queue will get its +# branch updated with main. Only updating one branch ensures that pull requests +# in the queue are merged sequentially. +# **Why we have it**: So we don't have to watch pull requests and click +# update branch 1000x. # **Who does it impact**: Our health. - # -# This workflow checks all open PRs targeting `main` as their base branch and -# will attempt to update them if they have automerge. -# It is triggered when a `push` event occurs ON the `main` branch (e.g. a PR -# was merged or a force-push was done). +# The merge queue consists of any pull requests with automerge enabled and +# are mergeable. There is a label that can be used to skip to the front of +# the queue (`skip-to-front-of-merge-queue`). # -# It should work on all PRs created from source branches within the repo itself -# but is unlikely to work for PRs created from forked repos. +# This workflow is triggered when a `push` event occurs ON the `main` branch +# (e.g. a PR was merged or a force-push was done). # -# It is still worthwhile to leave it enabled for the `docs` open source repo as -# it should at least be running on `repo-sync` branch PRs. +# This workflow runs on all PRs created from source branches within the +# public and private docs repos but is won't work for PRs created from +# forked repos. # on: @@ -28,8 +30,19 @@ jobs: name: autoupdate runs-on: ubuntu-latest steps: - - uses: docker://chinthakagodawita/autoupdate-action:v1 + - name: Check out repo content + uses: actions/checkout@1e204e9a9253d643386038d443f96446fa156a97 + + - name: Setup Node + uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c + with: + node-version: 16.13.x + cache: npm + + - name: Install dependencies + run: npm ci + + - name: Update next PR in queue env: - GITHUB_TOKEN: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }} - PR_FILTER: auto_merge - MERGE_MSG: "Branch was updated using the 'autoupdate branch' Actions workflow." + GITHUB_TOKEN: ${{ secrets.DOCUBOT_REPO_PAT }} + run: node .github/actions-scripts/update-merge-queue-branch.js diff --git a/.github/workflows/create-translation-batch-pr.yml b/.github/workflows/create-translation-batch-pr.yml new file mode 100644 index 0000000000..6154870d67 --- /dev/null +++ b/.github/workflows/create-translation-batch-pr.yml @@ -0,0 +1,170 @@ +name: Create translation Batch Pull Request + +# **What it does**: +# - Creates one pull request per language after running a series of automated checks, +# removing translations that are broken in any known way +# **Why we have it**: +# - To deploy translations +# **Who does it impact**: It automates what would otherwise be manual work, +# helping docs engineering focus on higher value work + +on: + workflow_dispatch: + schedule: + - cron: '33 18 * * *' # every day at 18:33 UTC at least until automerge is working + +jobs: + create-translation-batch: + name: Create translation batch + runs-on: ubuntu-latest + # A sync's average run time is ~3.2 hours. + # This sets a maximum execution time of 300 minutes (5 hours) to prevent the workflow from running longer than necessary. + timeout-minutes: 300 + strategy: + fail-fast: false + max-parallel: 1 + matrix: + include: + - language: pt-BR + language_code: pt + # - language: zh-CN + # language_code: cn + # - language: ja-JP + # language_code: ja + # - language: es-ES + # language_code: es + steps: + - name: Set branch name + id: set-branch + run: | + echo "::set-output name=BRANCH_NAME::translation-batch-${{ matrix.language }}-$(date +%Y-%m-%d__%H-%M)" + + - run: git config --global user.name "docubot" + - run: git config --global user.email "67483024+docubot@users.noreply.github.com" + + - name: Checkout + uses: actions/checkout@1e204e9a9253d643386038d443f96446fa156a97 + with: + fetch-depth: 0 + lfs: true + + - run: git checkout -b ${{ steps.set-branch.outputs.BRANCH_NAME }} + + - name: Remove unwanted git hooks + run: rm .git/hooks/post-checkout + + - name: Install Crowdin CLI + run: | + wget https://artifacts.crowdin.com/repo/deb/crowdin3.deb -O /tmp/crowdin.deb + sudo dpkg -i /tmp/crowdin.deb + + - name: Upload files to crowdin + run: crowdin upload sources --no-progress --no-colors --verbose --debug '--branch=main' '--config=crowdin.yml' + env: + # This is a numeric id, not to be confused with Crowdin API v1 "project identifier" string + # See "API v2" on https://crowdin.com/project//settings#api + CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }} + + # A personal access token, not to be confused with Crowdin API v1 "API key" + # See https://crowdin.com/settings#api-key to generate a token + # This token was created by logging into Crowdin with the octoglot user + CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }} + + - name: Remove all language translations + run: | + git rm -rf --quiet translations/${{ matrix.language }}/content + git rm -rf --quiet translations/${{ matrix.language }}/data + + - name: Download crowdin translations + run: crowdin download --no-progress --no-colors --verbose --debug '--branch=main' '--config=crowdin.yml' --language=${{ matrix.language }} + env: + # This is a numeric id, not to be confused with Crowdin API v1 "project identifier" string + # See "API v2" on https://crowdin.com/project//settings#api + CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }} + + # A personal access token, not to be confused with Crowdin API v1 "API key" + # See https://crowdin.com/settings#api-key to generate a token + # This token was created by logging into Crowdin with the octoglot user + CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }} + + - name: Commit crowdin sync + run: | + git add . + git commit -m "Add crowdin translations" || echo "Nothing to commit" + + - name: 'Setup node' + uses: actions/setup-node@270253e841af726300e85d718a5f606959b2903c + with: + node-version: '16' + + - run: npm ci + + - name: Reset files with broken liquid tags + run: | + node script/i18n/reset-files-with-broken-liquid-tags.js --language=${{ matrix.language_code }} + git add . && git commit -m "run script/i18n/reset-files-with-broken-liquid-tags.js --language=${{ matrix.language_code }}" || echo "Nothing to commit" + + # step 5 in docs-engineering/crowdin.md using script from docs-internal#22709 + - name: Reset known broken files + run: | + node script/i18n/reset-known-broken-translation-files.js + git add . && git commit -m "run script/i18n/reset-known-broken-translation-files.js" || echo "Nothing to commit" + env: + GITHUB_TOKEN: ${{ secrets.DOCUBOT_REPO_PAT }} + + # step 6 in docs-engineering/crowdin.md + - name: Homogenize frontmatter + run: | + node script/i18n/homogenize-frontmatter.js + git add . && git commit -m "Run script/i18n/homogenize-frontmatter.js" || echo "Nothing to commit" + + # step 7 in docs-engineering/crowdin.md + - name: Fix translation errors + run: | + node script/i18n/fix-translation-errors.js + git add . && git commit -m "Run script/i18n/fix-translation-errors.js" || echo "Nothing to commit" + + # step 8a in docs-engineering/crowdin.md + - name: Check parsing + run: | + node script/i18n/lint-translation-files.js --check parsing + git add . && git commit -m "Run script/i18n/lint-translation-files.js --check parsing" || echo "Nothing to commit" + + # step 8b in docs-engineering/crowdin.md + - name: Check rendering + run: | + node script/i18n/lint-translation-files.js --check rendering + git add . && git commit -m "Run script/i18n/lint-translation-files.js --check rendering" || echo "Nothing to commit" + + - name: Create Pull Request + env: + GITHUB_TOKEN: ${{ secrets.DOCUBOT_REPO_PAT }} + # We'll try to create the pull request based on the changes we pushed up in the branch. + # If there are actually no differences between the branch and `main`, we'll delete it. + run: | + git push origin ${{ steps.set-branch.outputs.BRANCH_NAME }} + gh pr create -t "New translation batch for ${{ matrix.language }}" \ + --base=main \ + --head=${{ steps.set-branch.outputs.BRANCH_NAME }} \ + -b "New batch for ${{ matrix.language }} created by [this workflow]($GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID)" || git push origin :${{ steps.set-branch.outputs.BRANCH_NAME }} + + # When the maximum execution time is reached for this job, Actions cancels the workflow run. + # This emits a notification for the first responder to triage. + - name: Send Slack notification if workflow is cancelled + uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 + if: cancelled() + with: + channel: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }} + bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} + color: failure + text: 'The new translation batch for ${{ matrix.language }} was cancelled.' + + # Emit a notification for the first responder to triage if the workflow failed. + - name: Send Slack notification if workflow failed + uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 + if: failure() + with: + channel: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }} + bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} + color: failure + text: 'The new translation batch for ${{ matrix.language }} failed.' diff --git a/.github/workflows/repo-sync.yml b/.github/workflows/repo-sync.yml index c687fb6785..fba131f3ff 100644 --- a/.github/workflows/repo-sync.yml +++ b/.github/workflows/repo-sync.yml @@ -128,6 +128,9 @@ jobs: pr_body: "This is an automated pull request to sync changes between the public and private repos.\n\n:robot: This pull request should be merged (not squashed) to preserve continuity across repos, so please let a bot do the merging!" pr_label: automated-reposync-pr github_token: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }} + # This will exit 0 if there's no difference between `repo-sync` + # and `main`. And if so, no PR will be created. + pr_allow_empty: false - name: Find pull request uses: juliangruber/find-pull-request-action@db875662766249c049b2dcd85293892d61cb0b51 diff --git a/.github/workflows/site-policy-sync.yml b/.github/workflows/site-policy-sync.yml index 4ee14f2c61..84e4442605 100644 --- a/.github/workflows/site-policy-sync.yml +++ b/.github/workflows/site-policy-sync.yml @@ -19,9 +19,7 @@ on: jobs: sync: name: Get the latest docs - if: >- - github.event.pull_request.merged == true && - github.repository == 'github/docs-internal' + if: github.event_name == 'workflow_dispatch' || (github.event.pull_request.merged == true && github.repository == 'github/docs-internal') runs-on: ubuntu-latest permissions: contents: write @@ -49,6 +47,7 @@ jobs: git checkout -b automated-sync-$GITHUB_RUN_ID git add . PR_TITLE=${{ github.event.pull_request.title }} + echo PR_TITLE: $PR_TITLE [[ ! -z $PR_TITLE ]] && DESCRIPTION="${PR_TITLE}" || DESCRIPTION="Update manually triggered by workflow" echo "DESCRIPTION=$DESCRIPTION" >> $GITHUB_ENV git commit -m "$(echo $DESCRIPTION)" diff --git a/.github/workflows/staging-build-pr.yml b/.github/workflows/staging-build-pr.yml index 50f050f9cc..5233e85ffe 100644 --- a/.github/workflows/staging-build-pr.yml +++ b/.github/workflows/staging-build-pr.yml @@ -34,9 +34,10 @@ jobs: runs-on: ubuntu-latest steps: - name: Dump full context for debugging - env: - GITHUB_CONTEXT: ${{ toJSON(github) }} - run: echo "$GITHUB_CONTEXT" + run: | + cat << EOF + ${{ toJSON(github) }} + EOF build-pr: if: ${{ github.repository == 'github/docs-internal' || github.repository == 'github/docs' }} diff --git a/.github/workflows/transfer-to-localization-repo.yml b/.github/workflows/transfer-to-localization-repo.yml index 6294106178..0e34e61a3c 100644 --- a/.github/workflows/transfer-to-localization-repo.yml +++ b/.github/workflows/transfer-to-localization-repo.yml @@ -60,7 +60,7 @@ jobs: OLD_ISSUE: ${{ github.event.issue.html_url }} - name: Comment on the old issue - run: gh issue comment $OLD_ISSUE --body "Thank you for opening this issue! Updates to translated content must be made internally. I have copied your issue to an internal issue, so I will close this issue." + run: gh issue comment $OLD_ISSUE --body "Thanks for opening this issue! Unfortunately, we are not able to accept issues for translated content. Our translation process involves an integration with an external service at crowdin.com, where all translation activity happens. We hope to eventually open up the translation process to the open-source community, but we're not there yet.See https://github.com/github/docs/blob/main/contributing/types-of-contributions.md#earth_asia-translations for more information." env: GITHUB_TOKEN: ${{secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES}} OLD_ISSUE: ${{ github.event.issue.html_url }} diff --git a/README.md b/README.md index bb4cebe892..c57336af62 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ That's how you can easily become a member of the GitHub Documentation community. ## READMEs In addition to the README you're reading right now, this repo includes other READMEs that describe the purpose of each subdirectory in more detail: -YOu can go through among them for specified details regarding the topics listed below. +You can go through among them for specified details regarding the topics listed below. - [content/README.md](content/README.md) - [content/graphql/README.md](content/graphql/README.md) diff --git a/assets/images/enterprise/custom-footer/add-footer-links.png b/assets/images/enterprise/custom-footer/add-footer-links.png new file mode 100644 index 0000000000..07a049d508 Binary files /dev/null and b/assets/images/enterprise/custom-footer/add-footer-links.png differ diff --git a/assets/images/enterprise/custom-footer/custom-footer-section.png b/assets/images/enterprise/custom-footer/custom-footer-section.png new file mode 100644 index 0000000000..867852d54d Binary files /dev/null and b/assets/images/enterprise/custom-footer/custom-footer-section.png differ diff --git a/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png b/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png new file mode 100644 index 0000000000..7b840da753 Binary files /dev/null and b/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png differ diff --git a/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png b/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png new file mode 100644 index 0000000000..d1e5bcb6f2 Binary files /dev/null and b/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png differ diff --git a/assets/images/enterprise/custom-footer/octodemo-footer.png b/assets/images/enterprise/custom-footer/octodemo-footer.png new file mode 100644 index 0000000000..d7dee2115e Binary files /dev/null and b/assets/images/enterprise/custom-footer/octodemo-footer.png differ diff --git a/assets/images/enterprise/custom-footer/update-custom-footer.png b/assets/images/enterprise/custom-footer/update-custom-footer.png new file mode 100644 index 0000000000..5777dc0d60 Binary files /dev/null and b/assets/images/enterprise/custom-footer/update-custom-footer.png differ diff --git a/assets/images/help/images/actions-enterprise-overview.png b/assets/images/help/images/actions-enterprise-overview.png new file mode 100644 index 0000000000..4bf00365dc Binary files /dev/null and b/assets/images/help/images/actions-enterprise-overview.png differ diff --git a/assets/images/help/images/actions-policies-overview.png b/assets/images/help/images/actions-policies-overview.png new file mode 100644 index 0000000000..154d00902f Binary files /dev/null and b/assets/images/help/images/actions-policies-overview.png differ diff --git a/assets/images/help/repository/PR-bypass-requirements.png b/assets/images/help/repository/PR-bypass-requirements.png new file mode 100644 index 0000000000..635fa7c23a Binary files /dev/null and b/assets/images/help/repository/PR-bypass-requirements.png differ diff --git a/assets/images/help/settings/actions-access-settings.png b/assets/images/help/settings/actions-access-settings.png index e59acac5ad..82499feebc 100644 Binary files a/assets/images/help/settings/actions-access-settings.png and b/assets/images/help/settings/actions-access-settings.png differ diff --git a/components/Search.tsx b/components/Search.tsx index 9e63eba825..5c5ca25035 100644 --- a/components/Search.tsx +++ b/components/Search.tsx @@ -2,16 +2,17 @@ import React, { useState, useEffect, useRef, ReactNode, RefObject } from 'react' import { useRouter } from 'next/router' import useSWR from 'swr' import cx from 'classnames' +import { ActionList, Label, Overlay } from '@primer/components' import { useTranslation } from 'components/hooks/useTranslation' import { sendEvent, EventType } from 'components/lib/events' import { useMainContext } from './context/MainContext' import { useVersion } from 'components/hooks/useVersion' import { useQuery } from 'components/hooks/useQuery' +import { Link } from 'components/Link' import { useLanguages } from './context/LanguagesContext' import styles from './Search.module.scss' -import { ActionList, Label, Link, Overlay } from '@primer/components' type SearchResult = { url: string diff --git a/components/article/ArticlePage.tsx b/components/article/ArticlePage.tsx index 2f0406d098..2daf9b26c1 100644 --- a/components/article/ArticlePage.tsx +++ b/components/article/ArticlePage.tsx @@ -46,7 +46,7 @@ export const ArticlePage = () => { const renderTocItem = (item: MiniTocItem) => { return ( { return ( -
+
{title && (

{sectionLink ? ( diff --git a/components/page-header/Breadcrumbs.module.scss b/components/page-header/Breadcrumbs.module.scss index 3e82493512..ba389ad73f 100644 --- a/components/page-header/Breadcrumbs.module.scss +++ b/components/page-header/Breadcrumbs.module.scss @@ -1,3 +1,3 @@ .breadcrumbs { - clip-path: inset(-5px -5px -5px 0px); + clip-path: inset(-0.5rem -0.5rem -0.5rem 0); } diff --git a/components/playground/content/building-and-testing/nodejs.tsx b/components/playground/content/building-and-testing/nodejs.tsx index 88cd2ec794..0686d0feca 100644 --- a/components/playground/content/building-and-testing/nodejs.tsx +++ b/components/playground/content/building-and-testing/nodejs.tsx @@ -180,7 +180,11 @@ const article: PlaygroundArticleT = { type: 'sub-section', title: 'Example caching dependencies', content: dedent` - When using GitHub-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the \`cache\` action. For more information, see [Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows) and the [\`cache\` action](https://github.com/marketplace/actions/cache). + + When using GitHub-hosted runners, you can cache and restore the dependencies using the [\`setup-node\` action](https://github.com/actions/setup-node). To cache dependencies with the \`setup-node\` action, you must have a \`package-lock.json\`, \`yarn.lock\`, or \`pnpm-lock.yaml\` file in the root of the repository. + + If you have a custom requirement or need finer controls for caching, you can use the [\`cache\` action](https://github.com/marketplace/actions/cache). For more information, see [Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows) and the [\`cache\` action](https://github.com/marketplace/actions/cache). + `, }, { @@ -493,15 +497,7 @@ const article: PlaygroundArticleT = { uses: actions/setup-node@v1 with: node-version: '12.x' - - name: Cache Node.js modules - uses: actions/cache@v2 - with: - # npm cache files are stored in \`~/.npm\` on Linux/macOS - path: ~/.npm - key: \${{ runner.OS }}-node-\${{ hashFiles('**/package-lock.json') }} - restore-keys: | - \${{ runner.OS }}-node- - \${{ runner.OS }}- + cache: 'npm' - name: Install dependencies run: npm ci `, diff --git a/components/playground/content/building-and-testing/python.tsx b/components/playground/content/building-and-testing/python.tsx index c39e9931fa..e64f2ccfc4 100644 --- a/components/playground/content/building-and-testing/python.tsx +++ b/components/playground/content/building-and-testing/python.tsx @@ -136,11 +136,11 @@ const article: PlaygroundArticleT = { }, title: 'Caching Dependencies', content: dedent` - When using GitHub-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [\`cache\`](https://github.com/marketplace/actions/cache) action. For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." - Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example shown depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip). + When using GitHub-hosted runners, you can cache and restore the dependencies using the [\`setup-python\` action](https://github.com/actions/setup-python). By default, the \`setup-python\` action searches for the dependency file (\`requirements.txt\` for pip or \`Pipfile.lock\` for pipenv) in the whole repository. + + If you have a custom requirement or need finer controls for caching, you can use the [\`cache\` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example shown here, depending on the operating system you use. For more information, see [Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows) and the [\`cache\` action](https://github.com/marketplace/actions/cache). - **Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how pip installs cached dependencies. The performance varies from project to project. `, }, { @@ -392,16 +392,7 @@ const article: PlaygroundArticleT = { uses: actions/setup-python@v2 with: python-version: '3.x' - - name: Cache pip - uses: actions/cache@v2 - with: - # This path is specific to Ubuntu - path: ~/.cache/pip - # Look to see if there is a cache hit for the corresponding requirements file - key: \${{ runner.os }}-pip-\${{ hashFiles('requirements.txt') }} - restore-keys: | - \${{ runner.os }}-pip- - \${{ runner.os }}- + cache: 'pip' - name: Install dependencies run: pip install -r requirements.txt `, diff --git a/components/sidebar/SidebarHomepage.tsx b/components/sidebar/SidebarHomepage.tsx index a6d1d9e2d7..93c78600d8 100644 --- a/components/sidebar/SidebarHomepage.tsx +++ b/components/sidebar/SidebarHomepage.tsx @@ -1,5 +1,6 @@ import { useRouter } from 'next/router' import { LinkExternalIcon } from '@primer/octicons-react' +import { ActionList } from '@primer/components' import { useVersion } from 'components/hooks/useVersion' import { useMainContext } from 'components/context/MainContext' @@ -11,43 +12,53 @@ export const SidebarHomepage = () => { const router = useRouter() const { currentVersion } = useVersion() const { activeProducts, isFPT } = useMainContext() + const navItems = [] + + for (let i = 0; i < activeProducts.length; i++) { + const product = activeProducts[i] + + if (!isFPT && !product.versions?.includes(currentVersion) && !product.external) { + continue + } + + const href = `${!product.external ? `/${router.locale}` : ''}${ + product.versions?.includes(currentVersion) && !isFPT + ? `/${currentVersion}/${product.id}` + : product.href + }` + + navItems.push({ + renderItem: () => ( + + + {product.name} + {product.external && ( + + + + )} + + + ), + }) + } return (
    {!isFPT && } - - {activeProducts.map((product) => { - if (!isFPT && !product.versions?.includes(currentVersion) && !product.external) { - return null - } - - const href = `${!product.external ? `/${router.locale}` : ''}${ - product.versions?.includes(currentVersion) && !isFPT - ? `/${currentVersion}/${product.id}` - : product.href - }` - - return ( -
  • - - {product.name} - {product.external && ( - - - - )} - -
    • - ) - })} +
  • + +
) } diff --git a/components/sidebar/SidebarProduct.module.scss b/components/sidebar/SidebarProduct.module.scss index e46a56783f..5696dd2568 100644 --- a/components/sidebar/SidebarProduct.module.scss +++ b/components/sidebar/SidebarProduct.module.scss @@ -1,7 +1,7 @@ .sidebarArticle::before { content: ""; position: absolute; - left: 26px; + left: calc(1.5rem + 2px); height: 100%; border-left: 1px solid var(--color-fg-default); width: 1px; diff --git a/components/sidebar/SidebarProduct.tsx b/components/sidebar/SidebarProduct.tsx index 4a533e3c34..09488cd96c 100644 --- a/components/sidebar/SidebarProduct.tsx +++ b/components/sidebar/SidebarProduct.tsx @@ -2,6 +2,7 @@ import { useRouter } from 'next/router' import cx from 'classnames' import { useState, useEffect, SyntheticEvent } from 'react' import { ChevronDownIcon } from '@primer/octicons-react' +import { ActionList } from '@primer/components' import { Link } from 'components/Link' import { ProductTreeNode, useMainContext } from 'components/context/MainContext' @@ -114,28 +115,37 @@ const CollapsibleSection = (props: SectionProps) => { const title = page.renderedShortTitle || page.renderedFullTitle const isCurrent = routePath === page.href - return ( -
  • - ( + - {title} - -
    • - ) + + {title} + + + ), + } } return ( @@ -172,19 +182,23 @@ const CollapsibleSection = (props: SectionProps) => {
    {childTitle}
     -
      - {childPage.childPages.map(renderTerminalPageLink)} -
    +
    + { + return renderTerminalPageLink(cp) + })} + > +
    ) })} ) : page.childPages[0]?.page.documentType === 'article' ? ( -
      - {/* */} - {page.childPages.map(renderTerminalPageLink)} -
    +
    + +
    ) : null} } diff --git a/components/ui/MarkdownContent/MarkdownContent.module.scss b/components/ui/MarkdownContent/MarkdownContent.module.scss index a36d8a21c0..859941a877 100644 --- a/components/ui/MarkdownContent/MarkdownContent.module.scss +++ b/components/ui/MarkdownContent/MarkdownContent.module.scss @@ -14,8 +14,8 @@ h5, h6 { display: inline-block; - margin-top: 10px; - margin-bottom: 10px; + margin-top: 0.5rem; + margin-bottom: 0.5rem; p { margin: 0; @@ -36,8 +36,8 @@ } } & > a[class~="doctocat-link"] { - padding: 8px; - margin-left: -32px; + padding: 0.5rem; + margin-left: -2rem; color: var(--color-fg-muted); &:active, &:focus { diff --git a/components/ui/MarkdownContent/stylesheets/code.scss b/components/ui/MarkdownContent/stylesheets/code.scss index e3b1a7a32f..8c440c47c8 100644 --- a/components/ui/MarkdownContent/stylesheets/code.scss +++ b/components/ui/MarkdownContent/stylesheets/code.scss @@ -1,16 +1,16 @@ .markdownBody { [class~="highlight"] pre, pre { - margin-top: 10px; + margin-top: 0.5rem; } [class~="height-constrained-code-block"] pre { - max-height: 500px; + max-height: 32rem; overflow: auto; } [class~="code-extra"] { - margin-top: 24px; + margin-top: 1.5rem; pre { margin-top: 0 !important; @@ -22,24 +22,24 @@ } } + // on graphql/overview/resource-limitations + pre [class~="redbox"], + pre [class~="greenbox"], + pre [class~="bluebox"] { + color: var(--color-fg-on-emphasis); + padding: 0 0.25rem; + border-radius: 4px; // primer rounded-1 + } + pre [class~="redbox"] { - border: 2px solid var(--color-danger-emphasis); - padding: 2px; - border-radius: 2px; - margin-right: 2px; + background-color: var(--color-danger-emphasis); } pre [class~="greenbox"] { - border: 2px solid var(--color-success-emphasis); - padding: 2px; - border-radius: 2px; - margin-right: 2px; + background-color: var(--color-success-emphasis); } pre [class~="bluebox"] { - border: 2px solid var(--color-accent-emphasis); - padding: 2px; - border-radius: 2px; - margin-right: 2px; + background-color: var(--color-accent-emphasis); } } diff --git a/components/ui/MarkdownContent/stylesheets/lists.scss b/components/ui/MarkdownContent/stylesheets/lists.scss index fdfb43ff6c..e4e626eca6 100644 --- a/components/ui/MarkdownContent/stylesheets/lists.scss +++ b/components/ui/MarkdownContent/stylesheets/lists.scss @@ -3,20 +3,20 @@ counter-reset: li; list-style: none; position: relative; - padding-bottom: 10px; + padding-bottom: 0.5rem; padding-left: 0; > li { - padding: 8px 0 8px 40px; + padding: 0.5rem 0 0.5rem 2.5rem; border: 0; position: relative; - margin-bottom: 5px; + margin-bottom: 0.25rem; &:before { - width: 22px; - height: 22px; - font-size: 14px; - margin: 1px 0 0 8px; + width: calc(1.5rem - 2px); + height: calc(1.5rem - 2px); + font-size: calc(1rem - 2px); + margin: 1px 0 0 0.5rem; content: counter(li); counter-increment: li; position: absolute; @@ -46,11 +46,11 @@ } p:not(:first-child) { - margin-top: 15px; + margin-top: 1rem; } [class~="extended-markdown"] { - margin-top: 15px; + margin-top: 1rem; } } @@ -63,8 +63,8 @@ ul ol, ol ol, ol ul { - margin-top: 15px; - margin-bottom: 15px; + margin-top: 1rem; + margin-bottom: 1rem; } } diff --git a/components/ui/MarkdownContent/stylesheets/table.scss b/components/ui/MarkdownContent/stylesheets/table.scss index 0738f4bcac..33cc0148b4 100644 --- a/components/ui/MarkdownContent/stylesheets/table.scss +++ b/components/ui/MarkdownContent/stylesheets/table.scss @@ -16,7 +16,7 @@ font-size: 85%; padding: 0.2em 0.4em; background-color: var(--color-canvas-subtle); - border-radius: 6px; + border-radius: 6px; // primer rounded-2 } pre > code { @@ -37,8 +37,8 @@ top: 0; background: var(--color-canvas-default); box-shadow: 0 3px 0 0 var(--color-canvas-subtle); - padding: 12px 8px; - border: 0px; + padding: 0.75rem 0.5rem; + border: 0; } th[align="center"] { @@ -55,8 +55,8 @@ } td { - padding: 10px 8px; - border: 0px; + padding: 0.75rem 0.5rem; + border: 0; vertical-align: top; } diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 4bb83fdf0a..ff77342e3d 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -22,7 +22,7 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% note %} -**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." +**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} diff --git a/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index fe7548a156..603f7c540d 100644 --- a/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -23,11 +23,34 @@ Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a c To cache dependencies for a job, you'll need to use {% data variables.product.prodname_dotcom %}'s `cache` action. The action retrieves a cache identified by a unique key. For more information, see [`actions/cache`](https://github.com/actions/cache). -If you are caching Ruby gems, instead consider using the Ruby maintained action, which can cache bundle installs on initiation. For more information, see [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically). +If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use. -To cache and restore dependencies for npm, Yarn, or pnpm, you can use the [`actions/setup-node` action](https://github.com/actions/setup-node). - -Gradle and Maven caching is available with [`actions/setup-java` action](https://github.com/actions/setup-java). + + + + + + + + + + + + + + + + + + + + + + + + + +
    Package managerssetup-* action for caching
    npm, yarn, pnpmsetup-node
    pip, pipenvsetup-python
    gradle, mavensetup-java
    ruby gemssetup-ruby
    {% warning %} @@ -209,4 +232,4 @@ For example, if a pull request contains a `feature` branch (the current scope) a ## Usage limits and eviction policy -{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 5 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 5 GB. +{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB. diff --git a/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index e816c5b1f1..0715e07423 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -288,7 +288,7 @@ steps: - run: pnpm test ``` -To cache dependencies, you must have a `package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml` file in the root of the repository. If you need more flexible customization, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "Caching dependencies to speed up workflows". +If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "Caching dependencies to speed up workflows". ## Building and testing your code diff --git a/content/actions/automating-builds-and-tests/building-and-testing-python.md b/content/actions/automating-builds-and-tests/building-and-testing-python.md index 2d1608fcb0..9b0b916538 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -241,38 +241,24 @@ steps: ### Caching Dependencies -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "Caching dependencies to speed up workflows." +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python). -Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example below depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip). +The following example caches dependencies for pip. -{% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 -- name: Setup Python - uses: actions/setup-python@v2 +- uses: actions/setup-python@v2 with: - python-version: '3.x' -- name: Cache pip - uses: actions/cache@v2 - with: - # This path is specific to Ubuntu - path: ~/.cache/pip - # Look to see if there is a cache hit for the corresponding requirements file - key: ${{ runner.os }}-pip-${{ hashFiles('requirements.txt') }} - restore-keys: | - ${{ runner.os }}-pip- - ${{ runner.os }}- -- name: Install dependencies - run: pip install -r requirements.txt + python-version: '3.9' + cache: 'pip' +- run: pip install -r requirements.txt +- run: pip test ``` -{% endraw %} -{% note %} +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "Caching packages dependencies" in the `setup-python` actions README. -**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how pip installs cached dependencies. The performance varies from project to project. - -{% endnote %} +If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository. ## Testing your code diff --git a/content/actions/guides.md b/content/actions/guides.md index 9c6031f5bb..7ac00d9b29 100644 --- a/content/actions/guides.md +++ b/content/actions/guides.md @@ -13,6 +13,7 @@ learningTracks: - continuous_integration - continuous_deployment - deploy_to_the_cloud + - '{% ifversion ghec or ghes or ghae %}adopting_github_actions_for_your_enterprise{% endif %}' - hosting_your_own_runners - create_actions includeGuides: diff --git a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 92e41df413..40d2652bc4 100644 --- a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -128,6 +128,8 @@ Some extra configuration might be required to use actions from {% data variables The self-hosted runner polls {% data variables.product.product_name %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs. +{% data reusables.actions.self-hosted-runner-ports-protocols %} + {% ifversion ghae %} You must ensure that the self-hosted runner has appropriate network access to communicate with the {% data variables.product.prodname_ghe_managed %} URL and its subdomains. For example, if your instance name is `octoghae`, then you will need to allow the self-hosted runner to access `octoghae.githubenterprise.com`, `api.octoghae.githubenterprise.com`, and `codeload.octoghae.githubenterprise.com`. @@ -187,7 +189,7 @@ If you use an IP address allow list for your {% data variables.product.prodname_ {% else %} -You must ensure that the machine has the appropriate network access to communicate with {% data variables.product.product_location %}. +You must ensure that the machine has the appropriate network access to communicate with {% data variables.product.product_location %}.{% ifversion ghes %} Self-hosted runners connect directly to {% data variables.product.product_location %} and do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.product.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.product.product_location %}, with no need for traffic to traverse a public network.{% endif %} {% endif %} diff --git a/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 7bec46029b..9028179143 100644 --- a/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -37,6 +37,8 @@ The proxy environment variables are read when the self-hosted runner application On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example `https_proxy` and `HTTPS_PROXY`, the self-hosted runner application uses the lowercase environment variable. +{% data reusables.actions.self-hosted-runner-ports-protocols %} + ## Using a .env file to set the proxy configuration If setting environment variables is not practical, you can set the proxy configuration variables in a file named _.env_ in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in _.env_ for the proxy configuration. diff --git a/content/actions/learn-github-actions/understanding-github-actions.md b/content/actions/learn-github-actions/understanding-github-actions.md index 1f478ee5c9..9613ae2f2f 100644 --- a/content/actions/learn-github-actions/understanding-github-actions.md +++ b/content/actions/learn-github-actions/understanding-github-actions.md @@ -23,7 +23,7 @@ topics: ## Overview -{% data variables.product.prodname_actions %} help you automate tasks within your software development life cycle. {% data variables.product.prodname_actions %} are event-driven, meaning that you can run a series of commands after a specified event has occurred. For example, every time someone creates a pull request for a repository, you can automatically run a command that executes a software testing script. +{% data reusables.actions.about-actions %} {% data variables.product.prodname_actions %} are event-driven, meaning that you can run a series of commands after a specified event has occurred. For example, every time someone creates a pull request for a repository, you can automatically run a command that executes a software testing script. This diagram demonstrates how you can use {% data variables.product.prodname_actions %} to automatically run your software testing scripts. An event automatically triggers the _workflow_, which contains a _job_. The job then uses _steps_ to control the order in which _actions_ are run. These actions are the commands that automate your software testing. @@ -59,7 +59,7 @@ _Actions_ are standalone commands that are combined into _steps_ to create a _jo {% ifversion ghae %}A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. For {% data variables.product.prodname_ghe_managed %}, you can use the security hardened {% data variables.actions.hosted_runner %}s which are bundled with your instance in the cloud. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.actions.hosted_runner %}s run each workflow job in a fresh virtual environment. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." {% else %} -A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS, and each job in a workflow runs in a fresh virtual environment. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." +{% data reusables.actions.about-runners %} A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS, and each job in a workflow runs in a fresh virtual environment. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." {% endif %} ## Create an example workflow diff --git a/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md index c8426dd9c7..2700c6ee2e 100644 --- a/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md +++ b/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -46,7 +46,7 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e {% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. * {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. * {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. * {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. * {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. diff --git a/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md new file mode 100644 index 0000000000..c334869985 --- /dev/null +++ b/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md @@ -0,0 +1,38 @@ +--- +title: Configuring custom footers +intro: 'You can give users easy access to enterprise-specific links by adding custom footers to {% data variables.product.product_name %}.' +versions: + ghec: '*' + ghes: '>=3.4' +type: how_to +topics: + - Enterprise + - Fundamentals +shortTitle: Configure custom footers +--- +Enterprise owners can configure {% data variables.product.product_name %} to show custom footers with up to five additional links. + +![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png) + +The custom footer is displayed above the {% data variables.product.prodname_dotcom %} footer {% ifversion ghes or ghae %}to all users, on all pages of {% data variables.product.product_name %}{% else %}to all enterprise members and collaborators, on all repository and organization pages for repositories and organizations that belong to the enterprise{% endif %}. + +## Configuring custom footers for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} + +1. Under "Settings", click **Profile**. +{%- ifversion ghec %} +![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png) +{%- else %} +![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png) +{%- endif %} + +1. At the top of the Profile section, click **Custom footer**. +![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png) + +1. Add up to five links in the fields shown. +![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png) + +1. Click **Update custom footer** to save the content and display the custom footer. +![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png) diff --git a/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md index 1ad518dd0f..d5d41ee13a 100644 --- a/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md +++ b/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Configuring GitHub Pages for your enterprise -intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise and choose whether to make sites publicly accessible.' +intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.' redirect_from: - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/ - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/ @@ -18,9 +18,12 @@ topics: - Pages shortTitle: Configure GitHub Pages --- + +{% ifversion ghes %} + ## Enabling public sites for {% data variables.product.prodname_pages %} -{% ifversion ghes %}If private mode is enabled on your enterprise, the {% else %}The {% endif %}public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites. +If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites. {% warning %} @@ -28,42 +31,35 @@ shortTitle: Configure GitHub Pages {% endwarning %} -{% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} 4. Select **Public Pages**. ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} -{% elsif ghae %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.pages-tab %} -5. Under "Pages policies", select **Public {% data variables.product.prodname_pages %}**. - ![Checkbox to enable public {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/public-github-pages-checkbox.png) -{% data reusables.enterprise-accounts.pages-policies-save %} -{% endif %} ## Disabling {% data variables.product.prodname_pages %} for your enterprise -{% ifversion ghes %} If subdomain isolation is disabled for your enterprise, you should also disable {% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. For more information, see "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)." -{% endif %} -{% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} 4. Unselect **Enable Pages**. ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) {% data reusables.enterprise_management_console.save-settings %} -{% elsif ghae %} + +{% endif %} + +{% ifversion ghae %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.pages-tab %} 5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**. ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} + {% endif %} {% ifversion ghes %} diff --git a/content/admin/configuration/configuring-your-enterprise/index.md b/content/admin/configuration/configuring-your-enterprise/index.md index b760e58eb7..d92f270477 100644 --- a/content/admin/configuration/configuring-your-enterprise/index.md +++ b/content/admin/configuration/configuring-your-enterprise/index.md @@ -34,6 +34,7 @@ children: - /restricting-network-traffic-to-your-enterprise - /configuring-github-pages-for-your-enterprise - /configuring-the-referrer-policy-for-your-enterprise + - /configuring-custom-footers shortTitle: Configure your enterprise --- diff --git a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md index b95f09ee96..412d68ed18 100644 --- a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md +++ b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -25,7 +25,9 @@ topics: When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. -Users will not be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. Users can only search private repositories you've enabled {% data variables.product.prodname_unified_search %} for and that they have access to in the connected {% data variables.product.prodname_ghe_cloud %} organizations. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." +After you enable unified search for {% data variables.product.product_location %}, individual users must also connect their user accounts on {% data variables.product.product_name %} with their user accounts on {% data variables.product.prodname_dotcom_the_website %} in order to see search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +Users will not be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. Users can only search private repositories you've enabled {% data variables.product.prodname_unified_search %} for and that they have access to in the connected {% data variables.product.prodname_ghe_cloud %} organizations. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)." Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported. diff --git a/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index f56219578b..ee0f477635 100644 --- a/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -6,7 +6,6 @@ versions: topics: - Enterprise children: - - /getting-started-with-github-actions-for-github-enterprise-server - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage diff --git a/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md similarity index 62% rename from content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md rename to content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md index 36295127e8..6b94aa303c 100644 --- a/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md @@ -1,7 +1,7 @@ --- title: Getting started with GitHub Actions for GitHub AE -shortTitle: Getting started with GitHub Actions -intro: 'Learn configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' +shortTitle: Get started +intro: 'Learn about configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghae: '*' @@ -11,12 +11,21 @@ topics: - Enterprise redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae + - /admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae --- {% data reusables.actions.ae-beta %} +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %} + This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}. +{% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_managed %} by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you need to manage access permissions for {% data variables.product.prodname_actions %} and add runners to run workflows. + +{% data reusables.actions.introducing-enterprise %} + +{% data reusables.actions.migrating-enterprise %} + ## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." @@ -31,7 +40,4 @@ You can use policies to manage access to {% data variables.product.prodname_acti To run {% data variables.product.prodname_actions %} workflows, you need to add runners. You can add runners at the enterprise, organization, or repository levels. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." - -## General security hardening for {% data variables.product.prodname_actions %} - -If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." +{% data reusables.actions.general-security-hardening %} \ No newline at end of file diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md new file mode 100644 index 0000000000..8680be8654 --- /dev/null +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md @@ -0,0 +1,34 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Cloud +shortTitle: Get started +intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}.' +permissions: 'Enterprise owners can configure {% data variables.product.prodname_actions %}.' +versions: + ghec: '*' +type: how_to +topics: + - Actions + - Enterprise +--- + +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %} + +{% data variables.product.prodname_actions %} is enabled for your enterprise by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you can manage the policies that control how enterprise members use {% data variables.product.prodname_actions %} and optionally add self-hosted runners to run workflows. + +{% data reusables.actions.introducing-enterprise %} + +{% data reusables.actions.migrating-enterprise %} + +## Managing policies for {% data variables.product.prodname_actions %} + +You can use policies to control how enterprise members use {% data variables.product.prodname_actions %}. For example, you can restrict which actions are allowed and configure artifact and log retention. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +## Adding runners + +To run {% data variables.product.prodname_actions %} workflows, you need to use runners. {% data reusables.actions.about-runners %} If you use {% data variables.product.company_short %}-hosted runners, you will be be billed based on consumption after exhausting the minutes included in {% data variables.product.product_name %}, while self-hosted runners are free. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." + +For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." + +If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" + +{% data reusables.actions.general-security-hardening %} \ No newline at end of file diff --git a/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md similarity index 88% rename from content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md rename to content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 8d6dc084a3..cdddcb3c87 100644 --- a/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -1,12 +1,13 @@ --- title: Getting started with GitHub Actions for GitHub Enterprise Server -shortTitle: Getting started with GitHub Actions +shortTitle: Get started intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' redirect_from: - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage - /admin/github-actions/enabling-github-actions-and-configuring-storage - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server versions: ghes: '*' type: how_to @@ -18,11 +19,15 @@ topics: {% data reusables.actions.enterprise-github-hosted-runners %} -{% ifversion ghes %} +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} -This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. -{% endif %} +{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. + +{% data reusables.actions.introducing-enterprise %} + +{% data reusables.actions.migrating-enterprise %} ## Review hardware considerations @@ -137,9 +142,7 @@ You can control which actions your users are allowed to use in your enterprise. For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." -## General security hardening for {% data variables.product.prodname_actions %} - -If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." +{% data reusables.actions.general-security-hardening %} {% endif %} diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md new file mode 100644 index 0000000000..7a7069a145 --- /dev/null +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md @@ -0,0 +1,19 @@ +--- +title: Getting started with GitHub Actions for your enterprise +intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise." +versions: + ghec: '*' + ghes: '*' + ghae: '*' +topics: + - Enterprise + - Actions +children: + - /introducing-github-actions-to-your-enterprise + - /migrating-your-enterprise-to-github-actions + - /getting-started-with-github-actions-for-github-enterprise-cloud + - /getting-started-with-github-actions-for-github-enterprise-server + - /getting-started-with-github-actions-for-github-ae +shortTitle: Get started +--- + diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md new file mode 100644 index 0000000000..85a750a3f9 --- /dev/null +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -0,0 +1,124 @@ +--- +title: Introducing GitHub Actions to your enterprise +shortTitle: Introduce Actions +intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise." +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise +--- + +## About {% data variables.product.prodname_actions %} for enterprises + +{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)." + +![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png) + +Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs. + +## Governance and compliance + +Your should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations. + +Determine which actions your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)." + +Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions that were not created by {% data variables.product.company_short %}. You can configure the actions that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions, you can limit allowed actions to those created by verified creators or a list of specific actions. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)." + +![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png) + +{% ifversion ghec or ghae-issue-4757-and-5856 %} +Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." +{% endif %} + +You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %} + +![Audit log entries](/assets/images/help/repository/audit-log-entries.png) + +## Security + +You should plan your approach to security hardening for {% data variables.product.prodname_actions %}. + +### Security hardening individual workflows and repositories + +Make a plan to enforce good security practices for people using {% data variables.product.prodname_actions %} features within your enterprise. For more information about these practices, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)." + +You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "[Innersourcing](#innersourcing)." + +### Securing access to secrets and deployment resources + +You should plan where you'll store your secrets. We recommend storing secrets in {% data variables.product.prodname_dotcom %}, but you might choose to store secrets in a cloud provider. + +In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +![Screenshot of a list of secrets](/assets/images/help/settings/actions-org-secrets-list.png) + +You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see "[Using environments for deployments](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." + +### Security considerations for third-party actions + +There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that enourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)." + +## Innersourcing + +Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource workflows. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources. + +{% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %} +With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + +To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)." + +## Managing resources + +You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}. + +### Runners + +{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %} + +{% ifversion ghec %}If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers.{% else %}Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners.{% endif %} Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container. + +You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." + +{% ifversion ghec or ghes > 3.2 %} +You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." +{% endif %} + +Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)." + +### Storage + +{% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)." + +![Screenshot of artifact](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) + +{% ifversion ghes %} +You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." +{% endif %} + +{% data reusables.github-actions.artifact-log-retention-statement %} + +If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data. + +{% ifversion ghec %} +Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." +{% endif %} + +## Tracking usage + +You should consider making a plan to track your enterprise's usage of {% data variables.product.prodname_actions %}, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows. + +{% ifversion ghec %} +You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)." + +For more detailed usage data, you{% else %}You{% endif %} can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)." + +Make a plan for how your enterprise can pass the information from these webhooks into a data archiving system. You can consider using "CEDAR.GitHub.Collector", an open source tool that collects and processes webhook data from {% data variables.product.prodname_dotcom %}. For more information, see the [`Microsoft/CEDAR.GitHub.Collector` repository](https://github.com/microsoft/CEDAR.GitHub.Collector/). + +You should also plan how you'll enable your teams to get the data they need from your archiving system. \ No newline at end of file diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md new file mode 100644 index 0000000000..2936f4d27f --- /dev/null +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md @@ -0,0 +1,87 @@ +--- +title: Migrating your enterprise to GitHub Actions +shortTitle: Migrate to Actions +intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider." +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise +--- + +## About enterprise migrations to {% data variables.product.prodname_actions %} + +To migrate your enterprise to {% data variables.product.prodname_actions %} from an existing system, you can plan the migration, complete the migration, and retire existing systems. + +This guide addresses specific considerations for migrations. For additional information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)." + +## Planning your migration + +Before you begin migrating your enterprise to {% data variables.product.prodname_actions %}, you should identify which workflows will be migrated and how those migrations will affect your teams, then plan how and when you will complete the migrations. + +### Leveraging migration specialists + +{% data variables.product.company_short %} can help with your migration, and you may also benefit from purchasing {% data variables.product.prodname_professional_services %}. For more information, contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}. + +### Identifying and inventorying migration targets + +Before you can migrate to {% data variables.product.prodname_actions %}, you need to have a complete understanding of the workflows being used by your enterprise in your existing system. + +First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind. + +Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)." + +With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}. + +### Determine team impacts from migrations + +When you change the tools being used within your enterprise, you influence how your team works. You'll need to consider how moving a workflow from your existing systems to {% data variables.product.prodname_actions %} will affect your developers' day-to-day work. + +Identify any processes, integrations, and third-party tools that will be affected by your migration, and make a plan for any updates you'll need to make. + +Consider how the migration may affect your compliance concerns. For example, will your existing credential scanning and security analysis tools work with {% data variables.product.prodname_actions %}, or will you need to use new tools? + +Identify the gates and checks in your existing system and verify that you can implement them with {% data variables.product.prodname_actions %}. + +### Identifying and validating migration tools + +Automated migration tools can translate your enterprise's workflows from the existing system's syntax to the syntax required by {% data variables.product.prodname_actions %}. Identify third-party tooling or contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %} to ask about tools that {% data variables.product.company_short %} can provide. + +After you've identified a tool to automate your migrations, validate the tool by running the tool on some test workflows and verifying that the results are as expected. + +Automated tooling should be able to migrate the majority of your workflows, but you'll likely need to manually rewrite at least a small percentage. Estimate the amount of manual work you'll need to complete. + +### Deciding on a migration approach + +Determine the migration approach that will work best for your enterprise. Smaller teams may be able to migrate all their workflows at once, with a "rip-and-replace" approach. For larger enterprises, an iterative approach may be more realistic. You can choose to have a central body manage the entire migration or you can ask individual teams to self serve by migrating their own workflows. + +We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too. + +Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. + +Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable. + +### Defining your migration schedule + +After you decide on a migration approach, build a schedule that outlines when each of your teams will migrate their workflows to {% data variables.product.prodname_actions %}. + +First, decide the date you'd like your migration to be complete. For example, you can plan to complete your migration by the time your contract with your current provider ends. + +Then, work with your teams to create a schedule that meets your deadline without sacrificing their team goals. Look at your business's cadence and the workload of each individual team you're asking to migrate. Coordinate with each team to understand their delivery schedules and create a plan that allows the team to migrate their workflows at a time that won't impact their ability to deliver. + +## Migrating to {% data variables.product.prodname_actions %} + +When you're ready to start your migration, translate your existing workflows to {% data variables.product.prodname_actions %} using the automated tooling and manual rewriting you planned for above. + +You may also want to maintain old build artifacts from your existing system, perhaps by writing a scripted process to archive the artifacts. + +## Retiring existing systems + +After your migration is complete, you can think about retiring your existing system. + +You may want to run both systems side-by-side for some period of time, while you verify that your {% data variables.product.prodname_actions %} configuration is stable, with no degradation of experience for developers. + +Eventually, decommission and shut off the old systems, and ensure that no one within your enterprise can turn the old systems back on. diff --git a/content/admin/github-actions/index.md b/content/admin/github-actions/index.md index 324514e3af..808fdae5b0 100644 --- a/content/admin/github-actions/index.md +++ b/content/admin/github-actions/index.md @@ -4,11 +4,13 @@ intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion gha redirect_from: - /enterprise/admin/github-actions versions: + ghec: '*' ghes: '*' ghae: '*' topics: - Enterprise children: + - /getting-started-with-github-actions-for-your-enterprise - /using-github-actions-in-github-ae - /enabling-github-actions-for-github-enterprise-server - /managing-access-to-actions-from-githubcom diff --git a/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 42282a53e2..c04ba00eea 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -26,7 +26,7 @@ shortTitle: Add actions in your enterprise ## Official actions bundled with your enterprise instance -Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. +{% data reusables.actions.actions-bundled-with-ghes %} The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. @@ -40,7 +40,7 @@ Each action is a repository in the `actions` organization, and each action repos ## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} -If users in your enterprise need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options. +{% data reusables.actions.access-actions-on-dotcom %} The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 39d6182e98..3470da6098 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -19,10 +19,14 @@ shortTitle: Use GitHub Connect for actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +## About automatic access to {% data variables.product.prodname_dotcom_the_website %} actions + By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." +To use actions from {% data variables.product.prodname_dotcom_the_website %}, your self-hosted runners must be able to download public actions from `api.github.com`. + ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions {% data reusables.actions.enterprise-github-connect-warning %} diff --git a/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/content/admin/github-actions/using-github-actions-in-github-ae/index.md index e5077235ba..ed67e364c7 100644 --- a/content/admin/github-actions/using-github-actions-in-github-ae/index.md +++ b/content/admin/github-actions/using-github-actions-in-github-ae/index.md @@ -4,7 +4,6 @@ intro: 'Learn how to configure {% data variables.product.prodname_actions %} on versions: ghae: '*' children: - - /getting-started-with-github-actions-for-github-ae - /using-actions-in-github-ae shortTitle: Use Actions in GitHub AE --- diff --git a/content/admin/guides.md b/content/admin/guides.md index 469d2d8844..6eee293a97 100644 --- a/content/admin/guides.md +++ b/content/admin/guides.md @@ -9,14 +9,15 @@ versions: ghes: '*' ghae: '*' learningTracks: + - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' - '{% ifversion ghae %}get_started_with_github_ae{% endif %}' - '{% ifversion ghes %}deploy_an_instance{% endif %}' - '{% ifversion ghes %}upgrade_your_instance{% endif %}' + - adopting_github_actions_for_your_enterprise - '{% ifversion ghes %}increase_fault_tolerance{% endif %}' - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}' - - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' includeGuides: - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - /admin/authentication/changing-authentication-methods diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index f4f336c243..6c2bd6b7ce 100644 --- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -54,7 +54,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} 1. Under **Policies**, select **Allow select actions** and add your required actions to the list. - {%- ifversion ghes or ghae-issue-5094 %} + {%- ifversion ghes > 3.0 or ghae-issue-5094 %} ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) diff --git a/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md b/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md index 51734f096d..6d6bfc2f50 100644 --- a/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md +++ b/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md @@ -24,7 +24,7 @@ In future releases of {% data variables.product.prodname_ghe_server %}, we will To prepare for these changes, if you have private mode enabled, you can run a migration on your instance to convert public repositories to internal. This migration is currently optional, to allow you to test the changes on a non-production instance. The migration will become mandatory in the future. -When you run the migration, all public repositories owned by organizations on your instance will become internal repositories. If any of those repositories have forks, the forks will be detached from their parent and become private. Private repositories will remain private. +When you run the migration, all public repositories owned by organizations on your instance will become internal repositories. If any of those repositories have forks, the forks will become private. Private repositories will remain private. All public repositories owned by user accounts on your instance will become private repositories. If any of those repositories have forks, the forks will also become private. The owner of each fork will be given read permissions to the fork's parent. diff --git a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index fcd90269b5..9056bc0961 100644 --- a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -50,7 +50,7 @@ To replace all text listed in `passwords.txt` wherever it can be found in your r $ bfg --replace-text passwords.txt ``` -After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on. ```shell $ git push --force @@ -124,7 +124,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil > 1 files changed, 1 insertions(+), 0 deletions(-) ``` 6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out. -7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, as well as all the branches you've pushed up: +7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history. ```shell $ git push origin --force --all > Counting objects: 1074, done. diff --git a/content/authentication/managing-commit-signature-verification/signing-commits.md b/content/authentication/managing-commit-signature-verification/signing-commits.md index 235fdd82fa..ad03fae2b2 100644 --- a/content/authentication/managing-commit-signature-verification/signing-commits.md +++ b/content/authentication/managing-commit-signature-verification/signing-commits.md @@ -36,7 +36,7 @@ If you have multiple keys or are attempting to sign commits or tags with a key t 1. When committing changes in your local branch, add the -S flag to the git commit command: ```shell - $ git commit -S -m your commit message + $ git commit -S -m "your commit message" # Creates a signed commit ``` 2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key). diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index df5c0646bc..8d71a5fd2e 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -169,11 +169,13 @@ codeql database analyze <database> --format=<format> \ | `` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `//codeql/qlpacks/codeql-/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. | `--format` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)." | `--output` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -| `--sarif-category` | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% if codeql-packs %} +| `--sarif-category` | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %} +| `--sarif-add-query-help` | | Optional. Use if you want to include any available markdown-rendered query help for custom queries used in your analysis. Any query help for custom queries included in the SARIF output will be displayed in the code scanning UI if the relevant query generates an alert. For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/#including-query-help-for-custom-codeql-queries-in-sarif-files) in the documentation for the {% data variables.product.prodname_codeql_cli %}.{% endif %}{% if codeql-packs %} | `` | | Optional. Use if you have downloaded CodeQL query packs and want to run the default queries or query suites specified in the packs. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} packs](#downloading-and-using-codeql-query-packs)."{% endif %} | `--threads` | | Optional. Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`. | `--verbose` | | Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae or ghec %} and diagnostic data from the database creation process{% endif %}. + For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. ### Basic example diff --git a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 365eee209c..e4cde2b237 100644 --- a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -82,12 +82,8 @@ After your pattern is created, {% data variables.product.prodname_secret_scannin ## Defining a custom pattern for an enterprise account -{% ifversion fpt or ghec or ghes %} - Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." -{% endif %} - {% note %} **Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. @@ -98,12 +94,12 @@ Before defining a custom pattern, you must ensure that you enable secret scannin {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.advanced-security-policies %} {% data reusables.enterprise-accounts.advanced-security-security-features %} -1. Under "Secret scanning custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}. +1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghes > 3.2 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Editing a custom pattern When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern. @@ -120,7 +116,7 @@ When you save a change to a custom pattern, this closes all the {% data variable * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above. * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 or ghae %} 1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. 1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern. 1. Click **Yes, delete this pattern**. diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index fa4504e80c..b62275e4e3 100644 --- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -179,14 +179,14 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" # The following properties are now available: - # - steps.metadata.outputs.dependency-names - # - steps.metadata.outputs.dependency-type - # - steps.metadata.outputs.update-type + # - steps.dependabot-metadata.outputs.dependency-names + # - steps.dependabot-metadata.outputs.dependency-type + # - steps.dependabot-metadata.outputs.update-type ``` {% endraw %} @@ -214,12 +214,12 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Add a label for all production dependencies - if: ${{ steps.metadata.outputs.dependency-type == 'direct:production' }} + if: ${{ steps.dependabot-metadata.outputs.dependency-type == 'direct:production' }} run: gh pr edit "$PR_URL" --add-label "production" env: PR_URL: ${{github.event.pull_request.html_url}} @@ -244,7 +244,7 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" @@ -277,12 +277,12 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Enable auto-merge for Dependabot PRs - if: ${{contains(steps.metadata.outputs.dependency-names, 'my-dependency') && steps.metadata.outputs.update-type == 'version-update:semver-patch'}} + if: ${{contains(steps.dependabot-metadata.outputs.dependency-names, 'my-dependency') && steps.dependabot-metadata.outputs.update-type == 'version-update:semver-patch'}} run: gh pr merge --auto --merge "$PR_URL" env: PR_URL: ${{github.event.pull_request.html_url}} diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index 1c4848c31c..10088f39bd 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -18,7 +18,7 @@ redirect_from: - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces --- -By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. +By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." diff --git a/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/content/get-started/using-git/getting-changes-from-a-remote-repository.md index 0f6a6df2b4..209c0beb0e 100644 --- a/content/get-started/using-git/getting-changes-from-a-remote-repository.md +++ b/content/get-started/using-git/getting-changes-from-a-remote-repository.md @@ -77,7 +77,7 @@ $ git pull remotename branchname Because `pull` performs a merge on the retrieved changes, you should ensure that your local work is committed before running the `pull` command. If you run into -[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line +[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line) you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort` to take the branch back to where it was in before you pulled. diff --git a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index fd5e5db29b..4b2252d181 100644 --- a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -52,7 +52,7 @@ You can disable all workflows for an organization or set a policy that configure {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} 1. Under **Policies**, select **Allow select actions** and add your required actions to the list. - {%- ifversion ghes %} + {%- ifversion ghes > 3.0 %} ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) {%- else %} ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 6531ae0ad6..04002cc4a8 100644 --- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -21,7 +21,7 @@ topics: **Note:** When working with pull requests, keep the following in mind: * If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes. -* When pushing commits to a pull request, don't force push. Force pushing can corrupt your pull request. +* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} diff --git a/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md index 4495c57188..613caee543 100644 --- a/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md +++ b/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md @@ -84,7 +84,7 @@ $ git fetch upstream recover-B ## Avoid force pushes -Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. +Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests. ## Further reading diff --git a/content/repositories/archiving-a-github-repository/archiving-repositories.md b/content/repositories/archiving-a-github-repository/archiving-repositories.md index e1fafe49e4..b8d5a45fc7 100644 --- a/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -31,7 +31,7 @@ topics: Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project. -When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, and comments become read-only. To make changes in an archived repository, you must unarchive the repository first. +When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first. You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)." diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index b36d6296c0..6353932fb4 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -157,7 +157,7 @@ You can only give push access to a protected branch to users, teams, or installe ### Allow force pushes -By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests. Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index ea779e9ec2..af1d2efaca 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -67,6 +67,10 @@ When you create a branch rule, the branch you specify doesn't have to exist yet ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) +{% ifversion fpt or ghec %} + - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. + ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) +{% endif %} - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) 1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." @@ -100,7 +104,7 @@ When you create a branch rule, the branch you specify doesn't have to exist yet ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png) - Search for and select the people, teams, or apps who will have permission to push to the protected branch. ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png) -1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. +2. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)." ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png) 1. Optionally, select **Allow deletions**. ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png) 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 4948034d55..651ec1b4dd 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,8 @@ Prerequisites for repository transfers: - When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %} - To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization. - The target account must not have a repository with the same name, or a fork in the same network. -- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact. +- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %} +- Internal repositories can't be transferred.{% endif %} - Private forks can't be transferred. {% ifversion fpt or ghec %}If you transfer a private repository to a {% data variables.product.prodname_free_user %} user or organization account, the repository will lose access to features like protected branches and {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %} diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 36462de836..cb0ef50a07 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -57,7 +57,7 @@ You can disable all workflows for a repository or set a policy that configures w {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} 1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. - {%- ifversion ghes %} + {%- ifversion ghes > 3.0 %} ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) {%- else %} ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) @@ -122,8 +122,8 @@ To configure whether workflows in an internal repository can be accessed from ou 1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png) * **Not accessible** - Workflows in other repositories can't use workflows in this repository. - * **Accessible by any repository in the organization** - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization. - * **Accessible by any repository in the enterprise** - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. + * **Accessible from repositories in the '<organization name>' organization** - Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal. + * **Accessible from repositories in the '<enterprise name>' enterprise** - Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal. 1. Click **Save** to apply the settings. {% endif %} diff --git a/content/rest/overview/api-previews.md b/content/rest/overview/api-previews.md index d1ec6f2b9d..54bb112651 100644 --- a/content/rest/overview/api-previews.md +++ b/content/rest/overview/api-previews.md @@ -190,7 +190,7 @@ You can now provide more information in GitHub for URLs that link to registered **Custom media types:** `corsair-preview` **Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) -{% ifversion ghes < 3.3 %} +{% ifversion ghae or ghes < 3.3 %} ## Enable and disable Pages diff --git a/content/rest/reference/permissions-required-for-github-apps.md b/content/rest/reference/permissions-required-for-github-apps.md index 4237a0432d..a8142804dc 100644 --- a/content/rest/reference/permissions-required-for-github-apps.md +++ b/content/rest/reference/permissions-required-for-github-apps.md @@ -147,6 +147,11 @@ _Search_ - [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) - [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) - [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository) (:write) {% ifversion fpt or ghes -%} - [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) - [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write) @@ -903,6 +908,11 @@ _Teams_ - [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) - [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) - [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization) (:write) +- [`PUT /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (:write) {% endif %} ### Permission on "single file" diff --git a/content/rest/reference/search.md b/content/rest/reference/search.md index 85173ec75a..99d4a14e4f 100644 --- a/content/rest/reference/search.md +++ b/content/rest/reference/search.md @@ -83,7 +83,7 @@ More results might have been found, but also might not. ### Access errors or missing search results -You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessible Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}. +You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}. When your search query requests multiple resources, the response will only contain the resources that you have access to and will **not** provide an error message listing the resources that were not returned. diff --git a/content/rest/reference/secret-scanning.md b/content/rest/reference/secret-scanning.md index eacaef323d..d3fd555101 100644 --- a/content/rest/reference/secret-scanning.md +++ b/content/rest/reference/secret-scanning.md @@ -11,6 +11,12 @@ miniTocMaxHeadingLevel: 3 {% data reusables.secret-scanning.api-beta %} -The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For more information on secret scanning, see "[About secret scanning](/code-security/secret-security/about-secret-scanning)." +The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}: + +- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. +- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below. +{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %} + +For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." {% include rest_operations_at_current_path %} diff --git a/data/learning-tracks/actions.yml b/data/learning-tracks/actions.yml index bd481b61ff..f4b36da2cf 100644 --- a/data/learning-tracks/actions.yml +++ b/data/learning-tracks/actions.yml @@ -36,6 +36,17 @@ deploy_to_the_cloud: - /actions/deployment/deploying-to-amazon-elastic-container-service - /actions/deployment/deploying-to-azure-app-service - /actions/deployment/deploying-to-google-kubernetes-engine +adopting_github_actions_for_your_enterprise: + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.' + guides: + - /actions/learn-github-actions/understanding-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae + - /actions/security-guides/security-hardening-for-github-actions hosting_your_own_runners: title: 'Host your own runners' description: 'You can create self-hosted runners to run workflows in a highly customizable environment.' diff --git a/data/learning-tracks/admin.yml b/data/learning-tracks/admin.yml index 7e18b0de17..b918b1009b 100644 --- a/data/learning-tracks/admin.yml +++ b/data/learning-tracks/admin.yml @@ -1,6 +1,9 @@ get_started_with_github_ae: title: 'Get started with {% data variables.product.prodname_ghe_managed %}' description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.' + featured_track: true + versions: + ghae: '*' guides: - /admin/overview/about-github-ae - /admin/overview/about-data-residency @@ -12,6 +15,8 @@ deploy_an_instance: title: 'Deploy an instance' description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.' featured_track: true + versions: + ghes: '*' guides: - /admin/overview/system-overview - /admin/installation @@ -23,6 +28,8 @@ deploy_an_instance: upgrade_your_instance: title: 'Upgrade your instance' description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.' + versions: + ghes: '*' guides: - /admin/enterprise-management/enabling-automatic-update-checks - /admin/installation/setting-up-a-staging-instance @@ -31,9 +38,23 @@ upgrade_your_instance: - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/enterprise-management/upgrading-github-enterprise-server +adopting_github_actions_for_your_enterprise: + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.' + guides: + - /actions/learn-github-actions/understanding-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae + - /actions/security-guides/security-hardening-for-github-actions + increase_fault_tolerance: title: 'Increase the fault tolerance of your instance' description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment." + versions: + ghes: '*' guides: - /admin/configuration/accessing-the-administrative-shell-ssh - /admin/configuration/configuring-backups-on-your-appliance @@ -44,6 +65,8 @@ increase_fault_tolerance: improve_security_of_your_instance: title: 'Improve the security of your instance' description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data." + versions: + ghes: '*' guides: - /admin/configuration/enabling-private-mode - /admin/guides/installation/configuring-tls @@ -58,6 +81,8 @@ improve_security_of_your_instance: configure_github_actions: title: 'Configure {% data variables.product.prodname_actions %}' description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.' + versions: + ghes: '*' guides: - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise @@ -69,6 +94,8 @@ configure_github_actions: configure_github_advanced_security: title: 'Configure {% data variables.product.prodname_GH_advanced_security %}' description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}." + versions: + ghes: '*' guides: - /admin/advanced-security/about-licensing-for-github-advanced-security - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise @@ -79,6 +106,9 @@ configure_github_advanced_security: get_started_with_your_enterprise_account: title: 'Get started with your enterprise account' description: 'Get started with your enterprise account to centrally manage multiple organizations on {% data variables.product.product_name %}.' + versions: + ghes: '*' + ghec: '*' guides: - /admin/overview/about-enterprise-accounts - /billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise diff --git a/data/release-notes/enterprise-server/3-0/16.yml b/data/release-notes/enterprise-server/3-0/16.yml index b4b1e79088..c8c0de3aa3 100644 --- a/data/release-notes/enterprise-server/3-0/16.yml +++ b/data/release-notes/enterprise-server/3-0/16.yml @@ -7,6 +7,7 @@ sections: - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. - Custom firewall rules are removed during the upgrade process. diff --git a/data/release-notes/enterprise-server/3-0/20.yml b/data/release-notes/enterprise-server/3-0/20.yml new file mode 100644 index 0000000000..b83329aaf4 --- /dev/null +++ b/data/release-notes/enterprise-server/3-0/20.yml @@ -0,0 +1,21 @@ +date: '2021-11-23' +sections: + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - Pre-receive hooks would fail due to undefined `PATH`. + - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. + - Some critical services may not have been available on backend nodes in GHES Cluster. + changes: + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. + - Upgraded collectd to version 5.12.0. + - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/12.yml b/data/release-notes/enterprise-server/3-1/12.yml new file mode 100644 index 0000000000..fb6b8860bc --- /dev/null +++ b/data/release-notes/enterprise-server/3-1/12.yml @@ -0,0 +1,24 @@ +date: '2021-11-23' +sections: + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. + - Pre-receive hooks would fail due to undefined `PATH`. + - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' + - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. + - Some critical services may not have been available on backend nodes in GHES Cluster. + changes: + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. + - Upgraded collectd to version 5.12.0. + - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + known_issues: + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/8.yml b/data/release-notes/enterprise-server/3-1/8.yml index 84dc8d4e2b..8f2e886f89 100644 --- a/data/release-notes/enterprise-server/3-1/8.yml +++ b/data/release-notes/enterprise-server/3-1/8.yml @@ -8,6 +8,7 @@ sections: - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' known_issues: - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. diff --git a/data/release-notes/enterprise-server/3-2/4.yml b/data/release-notes/enterprise-server/3-2/4.yml new file mode 100644 index 0000000000..2fa7bd8a0a --- /dev/null +++ b/data/release-notes/enterprise-server/3-2/4.yml @@ -0,0 +1,28 @@ +date: '2021-11-23' +sections: + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. + - Pre-receive hooks would fail due to undefined `PATH`. + - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' + - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' + - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. + - Some critical services may not have been available on backend nodes in GHES Cluster. + - The repository permissions to the user returned by the `/repos` API would not return the full list. + - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. + - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. + - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. + changes: + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. + - Upgraded collectd to version 5.12.0. + - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/reusables/actions/about-actions.md b/data/reusables/actions/about-actions.md new file mode 100644 index 0000000000..04b25d13f2 --- /dev/null +++ b/data/reusables/actions/about-actions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} helps you automate tasks within your software development life cycle. diff --git a/data/reusables/actions/about-runners.md b/data/reusables/actions/about-runners.md new file mode 100644 index 0000000000..c39fcf6ebb --- /dev/null +++ b/data/reusables/actions/about-runners.md @@ -0,0 +1 @@ +A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. \ No newline at end of file diff --git a/data/reusables/actions/access-actions-on-dotcom.md b/data/reusables/actions/access-actions-on-dotcom.md new file mode 100644 index 0000000000..b9ea810c36 --- /dev/null +++ b/data/reusables/actions/access-actions-on-dotcom.md @@ -0,0 +1 @@ +If users in your enterprise need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options. diff --git a/data/reusables/actions/actions-bundled-with-ghes.md b/data/reusables/actions/actions-bundled-with-ghes.md new file mode 100644 index 0000000000..4f4fbbeeac --- /dev/null +++ b/data/reusables/actions/actions-bundled-with-ghes.md @@ -0,0 +1 @@ +Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. \ No newline at end of file diff --git a/data/reusables/actions/general-security-hardening.md b/data/reusables/actions/general-security-hardening.md new file mode 100644 index 0000000000..30435d7ab4 --- /dev/null +++ b/data/reusables/actions/general-security-hardening.md @@ -0,0 +1,3 @@ +## General security hardening for {% data variables.product.prodname_actions %} + +If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." \ No newline at end of file diff --git a/data/reusables/actions/introducing-enterprise.md b/data/reusables/actions/introducing-enterprise.md new file mode 100644 index 0000000000..b7e8b0856c --- /dev/null +++ b/data/reusables/actions/introducing-enterprise.md @@ -0,0 +1 @@ +Before you get started, you should make a plan for how you'll introduce {% data variables.product.prodname_actions %} to your enterprise. For more information, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)." \ No newline at end of file diff --git a/data/reusables/actions/migrating-enterprise.md b/data/reusables/actions/migrating-enterprise.md new file mode 100644 index 0000000000..9876b13360 --- /dev/null +++ b/data/reusables/actions/migrating-enterprise.md @@ -0,0 +1 @@ +If you're migrating your enterprise to {% data variables.product.prodname_actions %} from another provider, there are additional considerations. For more information, see "[Migrating your enterprise to {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions)." \ No newline at end of file diff --git a/data/reusables/actions/self-hosted-runner-ports-protocols.md b/data/reusables/actions/self-hosted-runner-ports-protocols.md new file mode 100644 index 0000000000..486bb3838a --- /dev/null +++ b/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -0,0 +1,3 @@ +{% ifversion ghes or ghae %} +The connection between self-hosted runners and {% data variables.product.product_name %} is over HTTP (port 80) and HTTPS (port 443). +{% endif %} \ No newline at end of file diff --git a/data/reusables/secret-scanning/api-beta.md b/data/reusables/secret-scanning/api-beta.md index d109ab3f8e..fa4bfc814a 100644 --- a/data/reusables/secret-scanning/api-beta.md +++ b/data/reusables/secret-scanning/api-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghes > 3.0 %} +{% ifversion ghes > 3.0 or ghae-next %} {% note %} diff --git a/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 148734d46e..72c2d40a41 100644 --- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -187,6 +187,10 @@ Shopify | Shopify Private App Password | shopify_private_app_password Slack | Slack API Token | slack_api_token Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url +{%- ifversion fpt or ghec or ghes > 3.3 %} +Square | Square Production Application Secret | square_production_application_secret{% endif %} +{%- ifversion fpt or ghec or ghes > 3.3 %} +Square | Square Sandbox Application Secret | square_sandbox_application_secret{% endif %} SSLMate | SSLMate API Key | sslmate_api_key SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret Stripe | Stripe API Key | stripe_api_key diff --git a/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 194b263a77..87d68a1614 100644 --- a/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -75,6 +75,8 @@ RubyGems | RubyGems API Key Samsara | Samsara API Token Samsara | Samsara OAuth Access Token SendGrid | SendGrid API Key +Sendinblue | Sendinblue API Key +Sendinblue | Sendinblue SMTP Key Shopify | Shopify App Shared Secret Shopify | Shopify Access Token Shopify | Shopify Custom App Access Token @@ -91,4 +93,5 @@ Stripe | Stripe Test API Restricted Key Tencent Cloud | Tencent Cloud Secret ID Twilio | Twilio Account String Identifier Twilio | Twilio API Key +Typeform | Typeform Personal Access Token Valour | Valour Access Token diff --git a/lib/excluded-links.js b/lib/excluded-links.js index 88bf7ca0c4..d676989446 100644 --- a/lib/excluded-links.js +++ b/lib/excluded-links.js @@ -19,5 +19,5 @@ export default [ 'https://en.liberapay.com/', 'https://nbviewer.jupyter.org/github/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb', 'https://www.vmware.com/products/esxi-and-esx.html', - 'https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5' + 'https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5', ] diff --git a/lib/languages.js b/lib/languages.js index 2da5833067..5488a89a6f 100644 --- a/lib/languages.js +++ b/lib/languages.js @@ -41,7 +41,7 @@ const languages = { hreflang: 'pt', dir: 'translations/pt-BR', wip: false, - } + }, } if (process.env.ENABLED_LANGUAGES) { diff --git a/lib/liquid-tags/liquid-tag.js b/lib/liquid-tags/liquid-tag.js deleted file mode 100644 index cb4071ad6b..0000000000 --- a/lib/liquid-tags/liquid-tag.js +++ /dev/null @@ -1,33 +0,0 @@ -import { fileURLToPath } from 'url' -import path from 'path' -import readFileAsync from '../readfile-async.js' -import Liquid from 'liquid' -import { paramCase } from 'change-case' -const __dirname = path.dirname(fileURLToPath(import.meta.url)) - -export default class LiquidTag extends Liquid.Tag { - constructor(template, tagName, param) { - super() - this.param = param - this.tagName = tagName - this.templatePath = path.join( - __dirname, - `../../includes/liquid-tags/${paramCase(this.constructor.name)}.html` - ) - this.template = null - return this - } - - async render(context) { - return this.parseTemplate(context) - } - - async getTemplate() { - if (!this.template) { - this.template = await readFileAsync(this.templatePath, 'utf8') - this.template = this.template.replace(/\r/g, '') - } - - return this.template - } -} diff --git a/lib/render-content/plugins/rewrite-local-links.js b/lib/render-content/plugins/rewrite-local-links.js index f4ee823ba9..cdcbf0a9bc 100644 --- a/lib/render-content/plugins/rewrite-local-links.js +++ b/lib/render-content/plugins/rewrite-local-links.js @@ -10,7 +10,7 @@ import removeFPTFromPath from '../../remove-fpt-from-path.js' import readJsonFile from '../../read-json-file.js' const supportedVersions = Object.keys(allVersions) const supportedPlans = Object.values(allVersions).map((v) => v.plan) -const externalRedirects = Object.keys(readJsonFile('./lib/redirects/external-sites.json')) +const externalRedirects = readJsonFile('./lib/redirects/external-sites.json') // Matches any tags with an href that starts with `/` const matcher = (node) => @@ -41,7 +41,7 @@ function getNewHref(node, languageCode, version) { // Exceptions to link rewriting if (href.startsWith('/assets')) return if (href.startsWith('/public')) return - if (externalRedirects.includes(href)) return + if (href in externalRedirects) return let newHref = href // If the link has a hardcoded plan or version in it, do not update other than adding a language code diff --git a/lib/render-content/renderContent.js b/lib/render-content/renderContent.js index 125d71eeac..a5db3a2ddb 100644 --- a/lib/render-content/renderContent.js +++ b/lib/render-content/renderContent.js @@ -17,6 +17,9 @@ const inlineTagRegex = new RegExp(`\n?(?)\n?`, 'gm') // parse multiple times because some templates contain more templates. :] async function renderContent(template = '', context = {}, options = {}) { + // If called with a falsy template, it can't ever become something + // when rendered. We can exit early to save some pointless work. + if (!template) return template try { // remove any newlines that precede html comments, then remove the comments if (template) { diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index fa38d8fd90..23d9d8ca3c 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -6530,8 +6530,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -6593,8 +6593,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -9129,6 +9129,514 @@ "bodyParameters": [], "descriptionHTML": "

    Forces the removal of a self-hosted runner from an enterprise. You can use this endpoint to completely remove the runner when the machine you were using no longer exists.

    \n

    You must authenticate using an access token with the manage_runners:enterprise scope to use this endpoint.

    " }, + { + "verb": "get", + "requestPath": "/enterprises/{enterprise}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The slug version of the enterprise name. You can also substitute this value with the enterprise id.

    " + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels", + "html": "
    curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n enterprise: 'enterprise',\n runner_id: 42\n})", + "html": "
    await octokit.request('GET /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n  enterprise: 'enterprise',\n  runner_id: 42\n})\n
    " + } + ], + "summary": "List labels for a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nLists all labels for a self-hosted runner configured in an enterprise.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/list-labels-for-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise" + }, + "x-github": { + "enabledForGitHubApps": false, + "githubCloudOnly": false, + "category": "enterprise-admin", + "subcategory": "actions" + }, + "slug": "list-labels-for-a-self-hosted-runner-for-an-enterprise", + "category": "enterprise-admin", + "categoryLabel": "Enterprise admin", + "subcategory": "actions", + "subcategoryLabel": "Actions", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Lists all labels for a self-hosted runner configured in an enterprise.

    \n

    You must authenticate using an access token with the manage_runners:enterprise scope to use this endpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, + { + "verb": "post", + "requestPath": "/enterprises/{enterprise}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The slug version of the enterprise name. You can also substitute this value with the enterprise id.

    " + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X POST \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels \\\n -d '{\"labels\":[\"labels\"]}'", + "html": "
    curl \\\n  -X POST \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels \\\n  -d '{\"labels\":[\"labels\"]}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('POST /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n enterprise: 'enterprise',\n runner_id: 42,\n labels: [\n 'labels'\n ]\n})", + "html": "
    await octokit.request('POST /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n  enterprise: 'enterprise',\n  runner_id: 42,\n  labels: [\n    'labels'\n  ]\n})\n
    " + } + ], + "summary": "Add custom labels to a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nAdd custom labels to a self-hosted runner configured in an enterprise.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/add-custom-labels-to-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#add-custom-labels-to-a-self-hosted-runner-for-an-enterprise" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array of strings", + "minItems": 1, + "description": "

    Required. The names of the custom labels to add to the runner.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to add to the runner.", + "childParamsGroups": [] + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "actions" + }, + "slug": "add-custom-labels-to-a-self-hosted-runner-for-an-enterprise", + "category": "enterprise-admin", + "categoryLabel": "Enterprise admin", + "subcategory": "actions", + "subcategoryLabel": "Actions", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Add custom labels to a self-hosted runner configured in an enterprise.

    \n

    You must authenticate using an access token with the manage_runners:enterprise scope to use this endpoint.

    ", + "bodyParameters": [ + { + "type": "array of strings", + "minItems": 1, + "description": "

    Required. The names of the custom labels to add to the runner.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to add to the runner.", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "put", + "requestPath": "/enterprises/{enterprise}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The slug version of the enterprise name. You can also substitute this value with the enterprise id.

    " + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels \\\n -d '{\"labels\":[\"labels\"]}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels \\\n  -d '{\"labels\":[\"labels\"]}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('PUT /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n enterprise: 'enterprise',\n runner_id: 42,\n labels: [\n 'labels'\n ]\n})", + "html": "
    await octokit.request('PUT /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n  enterprise: 'enterprise',\n  runner_id: 42,\n  labels: [\n    'labels'\n  ]\n})\n
    " + } + ], + "summary": "Set custom labels for a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in an enterprise.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/set-custom-labels-for-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#set-custom-labels-for-a-self-hosted-runner-for-an-enterprise" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array of strings", + "minItems": 0, + "description": "

    Required. The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "childParamsGroups": [] + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "actions" + }, + "slug": "set-custom-labels-for-a-self-hosted-runner-for-an-enterprise", + "category": "enterprise-admin", + "categoryLabel": "Enterprise admin", + "subcategory": "actions", + "subcategoryLabel": "Actions", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in an enterprise.

    \n

    You must authenticate using an access token with the manage_runners:enterprise scope to use this endpoint.

    ", + "bodyParameters": [ + { + "type": "array of strings", + "minItems": 0, + "description": "

    Required. The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "delete", + "requestPath": "/enterprises/{enterprise}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The slug version of the enterprise name. You can also substitute this value with the enterprise id.

    " + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n enterprise: 'enterprise',\n runner_id: 42\n})", + "html": "
    await octokit.request('DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels', {\n  enterprise: 'enterprise',\n  runner_id: 42\n})\n
    " + } + ], + "summary": "Remove all custom labels from a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all custom labels from a self-hosted runner configured in an\nenterprise. Returns the remaining read-only labels from the runner.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/remove-all-custom-labels-from-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "actions" + }, + "slug": "remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise", + "category": "enterprise-admin", + "categoryLabel": "Enterprise admin", + "subcategory": "actions", + "subcategoryLabel": "Actions", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove all custom labels from a self-hosted runner configured in an\nenterprise. Returns the remaining read-only labels from the runner.

    \n

    You must authenticate using an access token with the manage_runners:enterprise scope to use this endpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 3,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "delete", + "requestPath": "/enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The slug version of the enterprise name. You can also substitute this value with the enterprise id.

    " + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + }, + { + "name": "name", + "description": "The name of a self-hosted runner's custom label.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The name of a self-hosted runner's custom label.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels/NAME", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/enterprises/ENTERPRISE/actions/runners/42/labels/NAME
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}', {\n enterprise: 'enterprise',\n runner_id: 42,\n name: 'name'\n})", + "html": "
    await octokit.request('DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}', {\n  enterprise: 'enterprise',\n  runner_id: 42,\n  name: 'name'\n})\n
    " + } + ], + "summary": "Remove a custom label from a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove a custom label from a self-hosted runner configured\nin an enterprise. Returns the remaining labels from the runner.\n\nThis endpoint returns a `404 Not Found` status if the custom label is not\npresent on the runner.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/remove-custom-label-from-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove a custom label from a self-hosted runner configured\nin an enterprise. Returns the remaining labels from the runner.

    \n

    This endpoint returns a 404 Not Found status if the custom label is not\npresent on the runner.

    \n

    You must authenticate using an access token with the manage_runners:enterprise scope to use this endpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, { "verb": "get", "requestPath": "/enterprises/{enterprise}/audit-log", @@ -10209,8 +10717,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10491,6 +10999,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -10513,8 +11022,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10586,8 +11094,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10787,8 +11295,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10988,6 +11496,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -11010,8 +11519,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11081,8 +11589,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -11175,8 +11683,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -11328,6 +11836,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -11350,8 +11859,7 @@ "description": "Not Found if gist is not starred" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -11474,6 +11982,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -11496,8 +12005,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11556,8 +12064,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -12107,8 +12615,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -12170,8 +12678,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -12282,6 +12790,7 @@ "categoryLabel": "Markdown", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -12294,7 +12803,6 @@ "description": "Not modified" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The Markdown text to render in HTML.

    ", @@ -13069,6 +13577,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -13096,8 +13605,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -13405,8 +13913,8 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -13481,6 +13989,7 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "205", @@ -13498,8 +14007,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -16923,6 +17431,504 @@ "bodyParameters": [], "descriptionHTML": "

    Forces the removal of a self-hosted runner from an organization. You can use this endpoint to completely remove the runner when the machine you were using no longer exists.

    \n

    You must authenticate using an access token with the admin:org scope to use this endpoint.

    " }, + { + "verb": "get", + "requestPath": "/orgs/{org}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/orgs/ORG/actions/runners/42/labels", + "html": "
    curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/actions/runners/42/labels
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /orgs/{org}/actions/runners/{runner_id}/labels', {\n org: 'org',\n runner_id: 42\n})", + "html": "
    await octokit.request('GET /orgs/{org}/actions/runners/{runner_id}/labels', {\n  org: 'org',\n  runner_id: 42\n})\n
    " + } + ], + "summary": "List labels for a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nLists all labels for a self-hosted runner configured in an organization.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/list-labels-for-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "list-labels-for-a-self-hosted-runner-for-an-organization", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Lists all labels for a self-hosted runner configured in an organization.

    \n

    You must authenticate using an access token with the admin:org scope to use this endpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, + { + "verb": "post", + "requestPath": "/orgs/{org}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X POST \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/orgs/ORG/actions/runners/42/labels \\\n -d '{\"labels\":[\"labels\"]}'", + "html": "
    curl \\\n  -X POST \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/actions/runners/42/labels \\\n  -d '{\"labels\":[\"labels\"]}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('POST /orgs/{org}/actions/runners/{runner_id}/labels', {\n org: 'org',\n runner_id: 42,\n labels: [\n 'labels'\n ]\n})", + "html": "
    await octokit.request('POST /orgs/{org}/actions/runners/{runner_id}/labels', {\n  org: 'org',\n  runner_id: 42,\n  labels: [\n    'labels'\n  ]\n})\n
    " + } + ], + "summary": "Add custom labels to a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nAdd custom labels to a self-hosted runner configured in an organization.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/add-custom-labels-to-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array of strings", + "minItems": 1, + "description": "

    Required. The names of the custom labels to add to the runner.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to add to the runner.", + "childParamsGroups": [] + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "add-custom-labels-to-a-self-hosted-runner-for-an-organization", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Add custom labels to a self-hosted runner configured in an organization.

    \n

    You must authenticate using an access token with the admin:org scope to use this endpoint.

    ", + "bodyParameters": [ + { + "type": "array of strings", + "minItems": 1, + "description": "

    Required. The names of the custom labels to add to the runner.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to add to the runner.", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "put", + "requestPath": "/orgs/{org}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/orgs/ORG/actions/runners/42/labels \\\n -d '{\"labels\":[\"labels\"]}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/actions/runners/42/labels \\\n  -d '{\"labels\":[\"labels\"]}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('PUT /orgs/{org}/actions/runners/{runner_id}/labels', {\n org: 'org',\n runner_id: 42,\n labels: [\n 'labels'\n ]\n})", + "html": "
    await octokit.request('PUT /orgs/{org}/actions/runners/{runner_id}/labels', {\n  org: 'org',\n  runner_id: 42,\n  labels: [\n    'labels'\n  ]\n})\n
    " + } + ], + "summary": "Set custom labels for a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in an organization.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/set-custom-labels-for-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array of strings", + "minItems": 0, + "description": "

    Required. The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "childParamsGroups": [] + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "set-custom-labels-for-a-self-hosted-runner-for-an-organization", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in an organization.

    \n

    You must authenticate using an access token with the admin:org scope to use this endpoint.

    ", + "bodyParameters": [ + { + "type": "array of strings", + "minItems": 0, + "description": "

    Required. The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "delete", + "requestPath": "/orgs/{org}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/orgs/ORG/actions/runners/42/labels", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/actions/runners/42/labels
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /orgs/{org}/actions/runners/{runner_id}/labels', {\n org: 'org',\n runner_id: 42\n})", + "html": "
    await octokit.request('DELETE /orgs/{org}/actions/runners/{runner_id}/labels', {\n  org: 'org',\n  runner_id: 42\n})\n
    " + } + ], + "summary": "Remove all custom labels from a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all custom labels from a self-hosted runner configured in an\norganization. Returns the remaining read-only labels from the runner.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-all-custom-labels-from-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove all custom labels from a self-hosted runner configured in an\norganization. Returns the remaining read-only labels from the runner.

    \n

    You must authenticate using an access token with the admin:org scope to use this endpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 3,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, + { + "verb": "delete", + "requestPath": "/orgs/{org}/actions/runners/{runner_id}/labels/{name}", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + }, + { + "name": "name", + "description": "The name of a self-hosted runner's custom label.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The name of a self-hosted runner's custom label.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/orgs/ORG/actions/runners/42/labels/NAME", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/actions/runners/42/labels/NAME
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /orgs/{org}/actions/runners/{runner_id}/labels/{name}', {\n org: 'org',\n runner_id: 42,\n name: 'name'\n})", + "html": "
    await octokit.request('DELETE /orgs/{org}/actions/runners/{runner_id}/labels/{name}', {\n  org: 'org',\n  runner_id: 42,\n  name: 'name'\n})\n
    " + } + ], + "summary": "Remove a custom label from a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove a custom label from a self-hosted runner configured\nin an organization. Returns the remaining labels from the runner.\n\nThis endpoint returns a `404 Not Found` status if the custom label is not\npresent on the runner.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-custom-label-from-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "remove-a-custom-label-from-a-self-hosted-runner-for-an-organization", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove a custom label from a self-hosted runner configured\nin an organization. Returns the remaining labels from the runner.

    \n

    This endpoint returns a 404 Not Found status if the custom label is not\npresent on the runner.

    \n

    You must authenticate using an access token with the admin:org scope to use this endpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, { "verb": "get", "requestPath": "/orgs/{org}/actions/secrets", @@ -18013,6 +19019,7 @@ "subcategory": "blocking", "subcategoryLabel": "Blocking", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -18025,8 +19032,7 @@ "description": "If the user is not blocked:" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -18086,6 +19092,7 @@ "subcategory": "blocking", "subcategoryLabel": "Blocking", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -18098,8 +19105,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -18159,6 +19165,7 @@ "subcategory": "blocking", "subcategoryLabel": "Blocking", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -18166,8 +19173,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -18367,6 +19373,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -18374,8 +19381,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -18689,8 +19695,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -19716,6 +20722,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -19728,8 +20735,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -24126,6 +25132,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -24138,8 +25145,7 @@ "description": "Not Found if user is not a public member" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -24272,6 +25278,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -24279,8 +25286,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -29699,8 +30705,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29922,6 +30928,7 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -29949,8 +30956,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -30039,6 +31045,7 @@ "subcategoryLabel": "Cards", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30071,7 +31078,6 @@ "description": "Response" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the card in a column. Can be one of: top, bottom, or after:<card_id> to place after the specified card.

    ", @@ -30146,8 +31152,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30340,6 +31346,7 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -30362,8 +31369,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -30451,8 +31457,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30752,6 +31758,7 @@ "subcategoryLabel": "Columns", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30779,7 +31786,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the column in a project. Can be one of: first, last, or after:<column_id> to place after the specified column.

    ", @@ -31678,8 +32684,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -34343,6 +35349,549 @@ "bodyParameters": [], "descriptionHTML": "

    Forces the removal of a self-hosted runner from a repository. You can use this endpoint to completely remove the runner when the machine you were using no longer exists.

    \n

    You must authenticate using an access token with the repo\nscope to use this endpoint.

    " }, + { + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels", + "html": "
    curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n owner: 'octocat',\n repo: 'hello-world',\n runner_id: 42\n})", + "html": "
    await octokit.request('GET /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  runner_id: 42\n})\n
    " + } + ], + "summary": "List labels for a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nLists all labels for a self-hosted runner configured in a repository.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/list-labels-for-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "list-labels-for-a-self-hosted-runner-for-a-repository", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Lists all labels for a self-hosted runner configured in a repository.

    \n

    You must authenticate using an access token with the repo scope to use this\nendpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, + { + "verb": "post", + "requestPath": "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X POST \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels \\\n -d '{\"labels\":[\"labels\"]}'", + "html": "
    curl \\\n  -X POST \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels \\\n  -d '{\"labels\":[\"labels\"]}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('POST /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n owner: 'octocat',\n repo: 'hello-world',\n runner_id: 42,\n labels: [\n 'labels'\n ]\n})", + "html": "
    await octokit.request('POST /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  runner_id: 42,\n  labels: [\n    'labels'\n  ]\n})\n
    " + } + ], + "summary": "Add custom labels to a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nAdd custom labels to a self-hosted runner configured in a repository.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/add-custom-labels-to-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array of strings", + "minItems": 1, + "description": "

    Required. The names of the custom labels to add to the runner.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to add to the runner.", + "childParamsGroups": [] + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "add-custom-labels-to-a-self-hosted-runner-for-a-repository", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Add custom labels to a self-hosted runner configured in a repository.

    \n

    You must authenticate using an access token with the repo scope to use this\nendpoint.

    ", + "bodyParameters": [ + { + "type": "array of strings", + "minItems": 1, + "description": "

    Required. The names of the custom labels to add to the runner.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to add to the runner.", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "put", + "requestPath": "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels \\\n -d '{\"labels\":[\"labels\"]}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels \\\n  -d '{\"labels\":[\"labels\"]}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('PUT /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n owner: 'octocat',\n repo: 'hello-world',\n runner_id: 42,\n labels: [\n 'labels'\n ]\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  runner_id: 42,\n  labels: [\n    'labels'\n  ]\n})\n
    " + } + ], + "summary": "Set custom labels for a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in a repository.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/set-custom-labels-for-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array of strings", + "minItems": 0, + "description": "

    Required. The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "childParamsGroups": [] + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "set-custom-labels-for-a-self-hosted-runner-for-a-repository", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in a repository.

    \n

    You must authenticate using an access token with the repo scope to use this\nendpoint.

    ", + "bodyParameters": [ + { + "type": "array of strings", + "minItems": 0, + "description": "

    Required. The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.

    ", + "items": { + "type": "string" + }, + "name": "labels", + "in": "body", + "rawType": "array", + "rawDescription": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, + { + "verb": "delete", + "requestPath": "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n owner: 'octocat',\n repo: 'hello-world',\n runner_id: 42\n})", + "html": "
    await octokit.request('DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  runner_id: 42\n})\n
    " + } + ], + "summary": "Remove all custom labels from a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all custom labels from a self-hosted runner configured in a\nrepository. Returns the remaining read-only labels from the runner.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-all-custom-labels-from-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove all custom labels from a self-hosted runner configured in a\nrepository. Returns the remaining read-only labels from the runner.

    \n

    You must authenticate using an access token with the repo scope to use this\nendpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 3,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, + { + "verb": "delete", + "requestPath": "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Unique identifier of the self-hosted runner.

    " + }, + { + "name": "name", + "description": "The name of a self-hosted runner's custom label.", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    The name of a self-hosted runner's custom label.

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels/NAME", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/actions/runners/42/labels/NAME
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}', {\n owner: 'octocat',\n repo: 'hello-world',\n runner_id: 42,\n name: 'name'\n})", + "html": "
    await octokit.request('DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  runner_id: 42,\n  name: 'name'\n})\n
    " + } + ], + "summary": "Remove a custom label from a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove a custom label from a self-hosted runner configured\nin a repository. Returns the remaining labels from the runner.\n\nThis endpoint returns a `404 Not Found` status if the custom label is not\npresent on the runner.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-custom-label-from-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + }, + "slug": "remove-a-custom-label-from-a-self-hosted-runner-for-a-repository", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "self-hosted-runners", + "subcategoryLabel": "Self hosted runners", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Note: The Actions Runner Labels API endpoints are currently in beta and are subject to change.

    \n

    Remove a custom label from a self-hosted runner configured\nin a repository. Returns the remaining labels from the runner.

    \n

    This endpoint returns a 404 Not Found status if the custom label is not\npresent on the runner.

    \n

    You must authenticate using an access token with the repo scope to use this\nendpoint.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"total_count\": 4,\n  \"labels\": [\n    {\n      \"id\": 5,\n      \"name\": \"self-hosted\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 7,\n      \"name\": \"X64\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 20,\n      \"name\": \"macOS\",\n      \"type\": \"read-only\"\n    },\n    {\n      \"id\": 21,\n      \"name\": \"no-gpu\",\n      \"type\": \"custom\"\n    }\n  ]\n}\n
    " + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Validation failed" + } + ] + }, { "verb": "get", "requestPath": "/repos/{owner}/{repo}/actions/runs", @@ -38004,8 +39553,8 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -38089,6 +39638,7 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -38111,8 +39661,7 @@ "description": "Preview header missing" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -38237,13 +39786,13 @@ "x-codeSamples": [ { "lang": "Shell", - "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", - "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " }, { "lang": "JavaScript", - "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 'app_id'\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", - "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 'app_id'\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " + "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 42\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 42\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " } ], "summary": "Update branch protection", @@ -38305,11 +39854,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38335,11 +39884,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38399,11 +39948,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38429,11 +39978,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38458,11 +40007,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38979,11 +40528,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -39009,11 +40558,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -39073,11 +40622,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -39103,11 +40652,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -39132,11 +40681,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -50108,7 +51657,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -50169,7 +51718,7 @@ "subcategoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\".

    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", + "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

    \n
    Cannot assign {member} permission of {role name}\n
    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", "bodyParameters": [ { "type": "string", @@ -50289,6 +51838,7 @@ "subcategory": "collaborators", "subcategoryLabel": "Collaborators", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -50296,8 +51846,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -50539,8 +52088,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -50745,6 +52294,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -50757,8 +52307,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -54388,8 +55937,8 @@ "subcategory": "deployments", "subcategoryLabel": "Deployments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -54661,7 +56210,7 @@ "properties": { "state": { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -54674,7 +56223,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, "target_url": { @@ -54771,7 +56320,7 @@ "bodyParameters": [ { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -54784,7 +56333,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, { @@ -55783,6 +57332,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -55790,8 +57340,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -55888,8 +57437,8 @@ "subcategory": "forks", "subcategoryLabel": "Forks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -57396,6 +58945,7 @@ "subcategory": "refs", "subcategoryLabel": "Refs", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -57408,8 +58958,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -58428,8 +59977,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -59591,6 +61140,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -59603,8 +61153,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -61941,6 +63490,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -61948,8 +63498,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -62687,8 +64236,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62893,6 +64442,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -62900,8 +64450,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -63334,8 +64883,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63417,8 +64966,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64492,8 +66041,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64596,8 +66145,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65048,6 +66597,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -65060,8 +66610,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -65834,6 +67383,7 @@ "subcategory": "timeline", "subcategoryLabel": "Timeline", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -65851,8 +67401,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -65932,8 +67481,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66161,8 +67710,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66333,8 +67882,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66571,8 +68120,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66805,6 +68354,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -66812,8 +68362,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -67502,8 +69051,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67772,8 +69321,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -68039,6 +69588,7 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -68051,8 +69601,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -68142,8 +69691,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -68451,8 +70000,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -69022,6 +70571,7 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -69039,8 +70589,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -69120,8 +70669,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -69258,8 +70807,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -69336,8 +70885,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72186,6 +73735,7 @@ "category": "pulls", "categoryLabel": "Pulls", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -72198,8 +73748,7 @@ "description": "Not Found if pull request has not been merged" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -72489,8 +74038,8 @@ "subcategory": "review-requests", "subcategoryLabel": "Review requests", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72790,6 +74339,7 @@ "subcategoryLabel": "Review requests", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -72802,7 +74352,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "type": "array of strings", @@ -73488,8 +75037,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -73712,8 +75261,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75137,6 +76686,7 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -75144,8 +76694,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -75952,8 +77501,8 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -77448,8 +78997,8 @@ "subcategory": "watching", "subcategoryLabel": "Watching", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -77732,8 +79281,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -77896,8 +79445,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -77983,8 +79532,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -82693,6 +84242,7 @@ "category": "scim", "categoryLabel": "SCIM", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -82715,8 +84265,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -83795,6 +85344,7 @@ "category": "scim", "categoryLabel": "SCIM", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -83817,8 +85367,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -88977,6 +90526,7 @@ "subcategory": "blocking", "subcategoryLabel": "Blocking", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -89004,8 +90554,7 @@ "description": "If the user is not blocked:" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -89056,6 +90605,7 @@ "subcategory": "blocking", "subcategoryLabel": "Blocking", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -89088,8 +90638,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -89140,6 +90689,7 @@ "subcategory": "blocking", "subcategoryLabel": "Blocking", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -89167,8 +90717,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -91716,6 +93265,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -91743,8 +93293,7 @@ "description": "if the person is not followed by the authenticated user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -93659,8 +95208,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -93739,8 +95288,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -96503,6 +98052,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -96530,8 +98080,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -96583,6 +98132,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -96610,8 +98160,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -96787,6 +98336,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -96814,8 +98364,7 @@ "description": "Not Found if this repository is not starred by you" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -96963,6 +98512,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -96990,8 +98540,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -97542,6 +99091,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -97549,8 +99099,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -97770,6 +99319,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -97782,8 +99332,7 @@ "description": "if the user does not follow the target user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -99166,8 +100715,8 @@ "category": "projects", "categoryLabel": "Projects", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -99330,6 +100879,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -99337,8 +100887,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", diff --git a/lib/rest/static/decorated/ghes-3.0.json b/lib/rest/static/decorated/ghes-3.0.json index 0d2fefa149..77b15aa411 100644 --- a/lib/rest/static/decorated/ghes-3.0.json +++ b/lib/rest/static/decorated/ghes-3.0.json @@ -124,8 +124,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -553,8 +553,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -964,6 +964,7 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -971,8 +972,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -1152,8 +1152,8 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1212,6 +1212,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -1219,8 +1220,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "patch", @@ -1869,8 +1869,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2053,8 +2053,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2501,8 +2501,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2776,8 +2776,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -3050,6 +3050,7 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3057,8 +3058,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -3601,6 +3601,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3608,8 +3609,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10171,8 +10171,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10234,8 +10234,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10546,8 +10546,8 @@ "subcategory": "license", "subcategoryLabel": "License", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10596,8 +10596,8 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10646,6 +10646,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10653,8 +10654,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10695,6 +10695,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10702,8 +10703,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10743,6 +10743,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10750,8 +10751,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10792,6 +10792,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10799,8 +10800,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10841,6 +10841,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10848,8 +10849,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10890,6 +10890,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10897,8 +10898,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10939,6 +10939,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10946,8 +10947,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10988,6 +10988,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10995,8 +10996,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11036,6 +11036,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11043,8 +11044,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11085,6 +11085,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11092,8 +11093,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14214,8 +14214,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14496,6 +14496,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -14518,8 +14519,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14591,8 +14591,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14792,8 +14792,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14993,6 +14993,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15015,8 +15016,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15086,8 +15086,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15180,8 +15180,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15333,6 +15333,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15355,8 +15356,7 @@ "description": "Not Found if gist is not starred" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -15479,6 +15479,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15501,8 +15502,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15561,8 +15561,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16133,8 +16133,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16196,8 +16196,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16308,6 +16308,7 @@ "categoryLabel": "Markdown", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16320,7 +16321,6 @@ "description": "Not modified" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The Markdown text to render in HTML.

    ", @@ -16462,8 +16462,8 @@ "category": "meta", "categoryLabel": "Meta", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16556,6 +16556,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16583,8 +16584,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -16892,8 +16892,8 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16968,6 +16968,7 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "205", @@ -16985,8 +16986,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21219,6 +21219,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -21226,8 +21227,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21298,8 +21298,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -22325,6 +22325,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -22337,8 +22338,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -23975,8 +23975,8 @@ "subcategory": "org-pre-receive-hooks", "subcategoryLabel": "Org pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -24586,6 +24586,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -24598,8 +24599,7 @@ "description": "Not Found if user is not a public member" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -24732,6 +24732,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -24739,8 +24740,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -29246,8 +29246,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29485,6 +29485,7 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -29512,8 +29513,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -29610,6 +29610,7 @@ "subcategoryLabel": "Cards", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -29642,7 +29643,6 @@ "description": "Response" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the card in a column. Can be one of: top, bottom, or after:<card_id> to place after the specified card.

    ", @@ -29725,8 +29725,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29935,6 +29935,7 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -29957,8 +29958,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -30054,8 +30054,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30371,6 +30371,7 @@ "subcategoryLabel": "Columns", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30398,7 +30399,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the column in a project. Can be one of: first, last, or after:<column_id> to place after the specified column.

    ", @@ -31358,8 +31358,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -35894,8 +35894,8 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -35979,6 +35979,7 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -36001,8 +36002,7 @@ "description": "Preview header missing" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -36135,13 +36135,13 @@ "x-codeSamples": [ { "lang": "Shell", - "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", - "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " }, { "lang": "JavaScript", - "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 'app_id'\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", - "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 'app_id'\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " + "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 42\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 42\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " } ], "summary": "Update branch protection", @@ -36203,11 +36203,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36233,11 +36233,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36297,11 +36297,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36327,11 +36327,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36356,11 +36356,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36885,11 +36885,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36915,11 +36915,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36979,11 +36979,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37009,11 +37009,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37038,11 +37038,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -47021,7 +47021,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -47082,7 +47082,7 @@ "subcategoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\".

    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", + "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

    \n
    Cannot assign {member} permission of {role name}\n
    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", "bodyParameters": [ { "type": "string", @@ -47202,6 +47202,7 @@ "subcategory": "collaborators", "subcategoryLabel": "Collaborators", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -47209,8 +47210,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -47468,8 +47468,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -47674,6 +47674,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -47686,8 +47687,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -51303,8 +51303,8 @@ "subcategory": "deployments", "subcategoryLabel": "Deployments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -51590,7 +51590,7 @@ "properties": { "state": { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -51603,7 +51603,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.0/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.0/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, "target_url": { @@ -51714,7 +51714,7 @@ "bodyParameters": [ { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -51727,7 +51727,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.0/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.0/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, { @@ -52132,6 +52132,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -52139,8 +52140,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -52237,8 +52237,8 @@ "subcategory": "forks", "subcategoryLabel": "Forks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -53745,6 +53745,7 @@ "subcategory": "refs", "subcategoryLabel": "Refs", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -53757,8 +53758,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -54777,8 +54777,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -55940,6 +55940,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -55952,8 +55953,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -56751,6 +56751,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -56758,8 +56759,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -57532,8 +57532,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -57738,6 +57738,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -57745,8 +57746,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -58208,8 +58208,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -58299,8 +58299,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -59397,8 +59397,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -59501,8 +59501,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -59953,6 +59953,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -59965,8 +59966,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -60774,6 +60774,7 @@ "subcategory": "timeline", "subcategoryLabel": "Timeline", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -60791,8 +60792,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -60872,8 +60872,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61101,8 +61101,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61273,8 +61273,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61511,8 +61511,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61745,6 +61745,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -61752,8 +61753,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -62184,8 +62184,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62454,8 +62454,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62721,6 +62721,7 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -62733,8 +62734,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -62824,8 +62824,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63133,8 +63133,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63720,6 +63720,7 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -63737,8 +63738,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -63818,8 +63818,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63956,8 +63956,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64034,8 +64034,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64248,8 +64248,8 @@ "subcategory": "repo-pre-receive-hooks", "subcategoryLabel": "Repo pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67148,6 +67148,7 @@ "category": "pulls", "categoryLabel": "Pulls", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -67160,8 +67161,7 @@ "description": "Not Found if pull request has not been merged" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -67451,8 +67451,8 @@ "subcategory": "review-requests", "subcategoryLabel": "Review requests", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67752,6 +67752,7 @@ "subcategoryLabel": "Review requests", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -67764,7 +67765,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "type": "array of strings", @@ -68450,8 +68450,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -68674,8 +68674,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -70062,6 +70062,7 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -70069,8 +70070,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -70685,8 +70685,8 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -71640,8 +71640,8 @@ "subcategory": "watching", "subcategoryLabel": "Watching", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -71924,8 +71924,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72088,8 +72088,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72182,8 +72182,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -73978,8 +73978,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -74115,8 +74115,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -78851,6 +78851,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -78878,8 +78879,7 @@ "description": "if the person is not followed by the authenticated user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -80406,8 +80406,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -80486,8 +80486,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -81728,6 +81728,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -81755,8 +81756,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -81808,6 +81808,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -81835,8 +81836,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -82012,6 +82012,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -82039,8 +82040,7 @@ "description": "Not Found if this repository is not starred by you" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -82188,6 +82188,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -82215,8 +82216,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -82767,6 +82767,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -82774,8 +82775,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -82995,6 +82995,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -83007,8 +83008,7 @@ "description": "if the user does not follow the target user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -83584,8 +83584,8 @@ "category": "projects", "categoryLabel": "Projects", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -83748,6 +83748,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -83755,8 +83756,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json index 14f69ee89e..0037393df1 100644 --- a/lib/rest/static/decorated/ghes-3.1.json +++ b/lib/rest/static/decorated/ghes-3.1.json @@ -124,8 +124,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -553,8 +553,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -964,6 +964,7 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -971,8 +972,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -1152,8 +1152,8 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1212,6 +1212,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -1219,8 +1220,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "patch", @@ -1869,8 +1869,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2053,8 +2053,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2501,8 +2501,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2776,8 +2776,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -3050,6 +3050,7 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3057,8 +3058,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -3601,6 +3601,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3608,8 +3609,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10171,8 +10171,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10234,8 +10234,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10546,8 +10546,8 @@ "subcategory": "license", "subcategoryLabel": "License", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10596,8 +10596,8 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10646,6 +10646,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10653,8 +10654,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10695,6 +10695,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10702,8 +10703,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10743,6 +10743,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10750,8 +10751,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10792,6 +10792,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10799,8 +10800,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10841,6 +10841,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10848,8 +10849,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10890,6 +10890,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10897,8 +10898,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10939,6 +10939,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10946,8 +10947,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10988,6 +10988,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10995,8 +10996,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11036,6 +11036,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11043,8 +11044,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11085,6 +11085,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11092,8 +11093,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14214,8 +14214,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14496,6 +14496,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -14518,8 +14519,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14591,8 +14591,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14792,8 +14792,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14993,6 +14993,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15015,8 +15016,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15086,8 +15086,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15180,8 +15180,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15333,6 +15333,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15355,8 +15356,7 @@ "description": "Not Found if gist is not starred" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -15479,6 +15479,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15501,8 +15502,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15561,8 +15561,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16133,8 +16133,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16196,8 +16196,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16308,6 +16308,7 @@ "categoryLabel": "Markdown", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16320,7 +16321,6 @@ "description": "Not modified" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The Markdown text to render in HTML.

    ", @@ -16462,8 +16462,8 @@ "category": "meta", "categoryLabel": "Meta", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16556,6 +16556,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16583,8 +16584,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -16892,8 +16892,8 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16968,6 +16968,7 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "205", @@ -16985,8 +16986,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21341,6 +21341,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -21348,8 +21349,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21420,8 +21420,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -22447,6 +22447,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -22459,8 +22460,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -24097,8 +24097,8 @@ "subcategory": "org-pre-receive-hooks", "subcategoryLabel": "Org pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -24708,6 +24708,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -24720,8 +24721,7 @@ "description": "Not Found if user is not a public member" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -24854,6 +24854,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -24861,8 +24862,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -29368,8 +29368,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29607,6 +29607,7 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -29634,8 +29635,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -29732,6 +29732,7 @@ "subcategoryLabel": "Cards", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -29764,7 +29765,6 @@ "description": "Response" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the card in a column. Can be one of: top, bottom, or after:<card_id> to place after the specified card.

    ", @@ -29847,8 +29847,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30057,6 +30057,7 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -30079,8 +30080,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -30176,8 +30176,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30493,6 +30493,7 @@ "subcategoryLabel": "Columns", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30520,7 +30521,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the column in a project. Can be one of: first, last, or after:<column_id> to place after the specified column.

    ", @@ -31480,8 +31480,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -36016,8 +36016,8 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -36101,6 +36101,7 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -36123,8 +36124,7 @@ "description": "Preview header missing" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -36257,13 +36257,13 @@ "x-codeSamples": [ { "lang": "Shell", - "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", - "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " }, { "lang": "JavaScript", - "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 'app_id'\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", - "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 'app_id'\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " + "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 42\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 42\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " } ], "summary": "Update branch protection", @@ -36325,11 +36325,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36355,11 +36355,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36419,11 +36419,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36449,11 +36449,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -36478,11 +36478,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37007,11 +37007,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37037,11 +37037,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37101,11 +37101,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37131,11 +37131,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37160,11 +37160,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -47690,7 +47690,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -47751,7 +47751,7 @@ "subcategoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\".

    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", + "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

    \n
    Cannot assign {member} permission of {role name}\n
    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", "bodyParameters": [ { "type": "string", @@ -47871,6 +47871,7 @@ "subcategory": "collaborators", "subcategoryLabel": "Collaborators", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -47878,8 +47879,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -48137,8 +48137,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -48343,6 +48343,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -48355,8 +48356,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -51972,8 +51972,8 @@ "subcategory": "deployments", "subcategoryLabel": "Deployments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -52259,7 +52259,7 @@ "properties": { "state": { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -52272,7 +52272,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.1/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.1/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, "target_url": { @@ -52383,7 +52383,7 @@ "bodyParameters": [ { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -52396,7 +52396,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.1/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.1/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, { @@ -52801,6 +52801,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -52808,8 +52809,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -52906,8 +52906,8 @@ "subcategory": "forks", "subcategoryLabel": "Forks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -54414,6 +54414,7 @@ "subcategory": "refs", "subcategoryLabel": "Refs", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -54426,8 +54427,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -55446,8 +55446,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -56609,6 +56609,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -56621,8 +56622,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -57420,6 +57420,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -57427,8 +57428,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -58201,8 +58201,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -58407,6 +58407,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -58414,8 +58415,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -58877,8 +58877,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -58968,8 +58968,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -60066,8 +60066,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -60170,8 +60170,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -60622,6 +60622,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -60634,8 +60635,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -61443,6 +61443,7 @@ "subcategory": "timeline", "subcategoryLabel": "Timeline", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -61460,8 +61461,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -61541,8 +61541,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61770,8 +61770,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61942,8 +61942,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62180,8 +62180,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62414,6 +62414,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -62421,8 +62422,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -62853,8 +62853,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63123,8 +63123,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63390,6 +63390,7 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -63402,8 +63403,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -63493,8 +63493,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63802,8 +63802,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64389,6 +64389,7 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -64406,8 +64407,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -64487,8 +64487,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64625,8 +64625,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64703,8 +64703,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64917,8 +64917,8 @@ "subcategory": "repo-pre-receive-hooks", "subcategoryLabel": "Repo pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67817,6 +67817,7 @@ "category": "pulls", "categoryLabel": "Pulls", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -67829,8 +67830,7 @@ "description": "Not Found if pull request has not been merged" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -68120,8 +68120,8 @@ "subcategory": "review-requests", "subcategoryLabel": "Review requests", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -68421,6 +68421,7 @@ "subcategoryLabel": "Review requests", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -68433,7 +68434,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "type": "array of strings", @@ -69119,8 +69119,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -69343,8 +69343,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -70731,6 +70731,7 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -70738,8 +70739,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -71354,8 +71354,8 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72708,8 +72708,8 @@ "subcategory": "watching", "subcategoryLabel": "Watching", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72992,8 +72992,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -73156,8 +73156,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -73250,8 +73250,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75046,8 +75046,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75183,8 +75183,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -79919,6 +79919,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -79946,8 +79947,7 @@ "description": "if the person is not followed by the authenticated user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -81474,8 +81474,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -81554,8 +81554,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -82796,6 +82796,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -82823,8 +82824,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -82876,6 +82876,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -82903,8 +82904,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -83080,6 +83080,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -83107,8 +83108,7 @@ "description": "Not Found if this repository is not starred by you" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -83256,6 +83256,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -83283,8 +83284,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -83835,6 +83835,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -83842,8 +83843,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -84063,6 +84063,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -84075,8 +84076,7 @@ "description": "if the user does not follow the target user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -84652,8 +84652,8 @@ "category": "projects", "categoryLabel": "Projects", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -84816,6 +84816,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -84823,8 +84824,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index 27f083dec6..fd06dfcd10 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -124,8 +124,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -553,8 +553,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -964,6 +964,7 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -971,8 +972,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -1152,8 +1152,8 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1212,6 +1212,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -1219,8 +1220,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "patch", @@ -1869,8 +1869,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2053,8 +2053,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2501,8 +2501,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2776,8 +2776,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -3050,6 +3050,7 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3057,8 +3058,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -3601,6 +3601,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3608,8 +3609,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10391,8 +10391,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10454,8 +10454,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10766,8 +10766,8 @@ "subcategory": "license", "subcategoryLabel": "License", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10816,8 +10816,8 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10866,6 +10866,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10873,8 +10874,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10915,6 +10915,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10922,8 +10923,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10963,6 +10963,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10970,8 +10971,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11012,6 +11012,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11019,8 +11020,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11061,6 +11061,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11068,8 +11069,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11110,6 +11110,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11117,8 +11118,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11159,6 +11159,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11166,8 +11167,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11208,6 +11208,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11215,8 +11216,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11256,6 +11256,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11263,8 +11264,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11305,6 +11305,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11312,8 +11313,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14434,8 +14434,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14716,6 +14716,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -14738,8 +14739,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14811,8 +14811,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15012,8 +15012,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15213,6 +15213,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15235,8 +15236,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15306,8 +15306,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15400,8 +15400,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15553,6 +15553,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15575,8 +15576,7 @@ "description": "Not Found if gist is not starred" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -15699,6 +15699,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15721,8 +15722,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15781,8 +15781,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16353,8 +16353,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16416,8 +16416,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16528,6 +16528,7 @@ "categoryLabel": "Markdown", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16540,7 +16541,6 @@ "description": "Not modified" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The Markdown text to render in HTML.

    ", @@ -16682,8 +16682,8 @@ "category": "meta", "categoryLabel": "Meta", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16776,6 +16776,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16803,8 +16804,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -17112,8 +17112,8 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -17188,6 +17188,7 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "205", @@ -17205,8 +17206,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21561,6 +21561,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -21568,8 +21569,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21640,8 +21640,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -22667,6 +22667,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -22679,8 +22680,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -24591,8 +24591,8 @@ "subcategory": "org-pre-receive-hooks", "subcategoryLabel": "Org pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -25202,6 +25202,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -25214,8 +25215,7 @@ "description": "Not Found if user is not a public member" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -25348,6 +25348,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -25355,8 +25356,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -29869,8 +29869,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30108,6 +30108,7 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -30135,8 +30136,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -30233,6 +30233,7 @@ "subcategoryLabel": "Cards", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30265,7 +30266,6 @@ "description": "Response" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the card in a column. Can be one of: top, bottom, or after:<card_id> to place after the specified card.

    ", @@ -30348,8 +30348,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30558,6 +30558,7 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -30580,8 +30581,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -30677,8 +30677,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30994,6 +30994,7 @@ "subcategoryLabel": "Columns", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -31021,7 +31022,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the column in a project. Can be one of: first, last, or after:<column_id> to place after the specified column.

    ", @@ -31981,8 +31981,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -37262,8 +37262,8 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -37347,6 +37347,7 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -37369,8 +37370,7 @@ "description": "Preview header missing" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -37503,13 +37503,13 @@ "x-codeSamples": [ { "lang": "Shell", - "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", - "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " }, { "lang": "JavaScript", - "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 'app_id'\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", - "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 'app_id'\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " + "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 42\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 42\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " } ], "summary": "Update branch protection", @@ -37571,11 +37571,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37601,11 +37601,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37665,11 +37665,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37695,11 +37695,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37724,11 +37724,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38253,11 +38253,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38283,11 +38283,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38347,11 +38347,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38377,11 +38377,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38406,11 +38406,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -48936,7 +48936,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -48997,7 +48997,7 @@ "subcategoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\".

    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", + "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

    \n
    Cannot assign {member} permission of {role name}\n
    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", "bodyParameters": [ { "type": "string", @@ -49117,6 +49117,7 @@ "subcategory": "collaborators", "subcategoryLabel": "Collaborators", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -49124,8 +49125,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -49383,8 +49383,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -49589,6 +49589,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -49601,8 +49602,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -53238,8 +53238,8 @@ "subcategory": "deployments", "subcategoryLabel": "Deployments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -53525,7 +53525,7 @@ "properties": { "state": { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -53538,7 +53538,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.2/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.2/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, "target_url": { @@ -53649,7 +53649,7 @@ "bodyParameters": [ { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. Note: To use the inactive state, you must provide the application/vnd.github.ant-man-preview+json custom media type. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -53662,7 +53662,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.2/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.2/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, { @@ -54675,6 +54675,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -54682,8 +54683,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -54780,8 +54780,8 @@ "subcategory": "forks", "subcategoryLabel": "Forks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -56288,6 +56288,7 @@ "subcategory": "refs", "subcategoryLabel": "Refs", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -56300,8 +56301,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -57320,8 +57320,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -58483,6 +58483,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -58495,8 +58496,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -59595,6 +59595,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -59602,8 +59603,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -60376,8 +60376,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -60582,6 +60582,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -60589,8 +60590,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -61052,8 +61052,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61143,8 +61143,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62241,8 +62241,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62345,8 +62345,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62797,6 +62797,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -62809,8 +62810,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -63618,6 +63618,7 @@ "subcategory": "timeline", "subcategoryLabel": "Timeline", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -63635,8 +63636,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -63716,8 +63716,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63945,8 +63945,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64117,8 +64117,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64355,8 +64355,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64589,6 +64589,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -64596,8 +64597,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -65028,8 +65028,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65298,8 +65298,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65565,6 +65565,7 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -65577,8 +65578,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -65668,8 +65668,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65977,8 +65977,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66564,6 +66564,7 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -66581,8 +66582,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -66662,8 +66662,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66800,8 +66800,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66878,8 +66878,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67092,8 +67092,8 @@ "subcategory": "repo-pre-receive-hooks", "subcategoryLabel": "Repo pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -69992,6 +69992,7 @@ "category": "pulls", "categoryLabel": "Pulls", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -70004,8 +70005,7 @@ "description": "Not Found if pull request has not been merged" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -70295,8 +70295,8 @@ "subcategory": "review-requests", "subcategoryLabel": "Review requests", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -70596,6 +70596,7 @@ "subcategoryLabel": "Review requests", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -70608,7 +70609,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "type": "array of strings", @@ -71294,8 +71294,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -71518,8 +71518,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72906,6 +72906,7 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -72913,8 +72914,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -73529,8 +73529,8 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75032,8 +75032,8 @@ "subcategory": "watching", "subcategoryLabel": "Watching", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75316,8 +75316,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75480,8 +75480,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75574,8 +75574,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -77833,8 +77833,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -77970,8 +77970,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -82706,6 +82706,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -82733,8 +82734,7 @@ "description": "if the person is not followed by the authenticated user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -84261,8 +84261,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -84341,8 +84341,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -85592,6 +85592,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -85619,8 +85620,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -85672,6 +85672,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -85699,8 +85700,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -85876,6 +85876,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -85903,8 +85904,7 @@ "description": "Not Found if this repository is not starred by you" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -86052,6 +86052,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -86079,8 +86080,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -86631,6 +86631,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -86638,8 +86639,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -86859,6 +86859,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -86871,8 +86872,7 @@ "description": "if the user does not follow the target user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -87448,8 +87448,8 @@ "category": "projects", "categoryLabel": "Projects", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -87612,6 +87612,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -87619,8 +87620,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json index 543f7f646c..c3b870cfe9 100644 --- a/lib/rest/static/decorated/ghes-3.3.json +++ b/lib/rest/static/decorated/ghes-3.3.json @@ -116,8 +116,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -506,8 +506,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -890,6 +890,7 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -897,8 +898,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -1070,8 +1070,8 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1130,6 +1130,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -1137,8 +1138,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "patch", @@ -1771,8 +1771,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1939,8 +1939,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2347,8 +2347,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2606,8 +2606,8 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2864,6 +2864,7 @@ "subcategory": "pre-receive-hooks", "subcategoryLabel": "Pre receive hooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -2871,8 +2872,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -3415,6 +3415,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -3422,8 +3423,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10205,8 +10205,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10268,8 +10268,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10580,8 +10580,8 @@ "subcategory": "license", "subcategoryLabel": "License", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10630,8 +10630,8 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10680,6 +10680,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10687,8 +10688,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10729,6 +10729,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10736,8 +10737,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10777,6 +10777,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10784,8 +10785,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10826,6 +10826,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10833,8 +10834,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10875,6 +10875,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10882,8 +10883,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10924,6 +10924,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10931,8 +10932,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10973,6 +10973,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -10980,8 +10981,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11022,6 +11022,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11029,8 +11030,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11070,6 +11070,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11077,8 +11078,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -11119,6 +11119,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11126,8 +11127,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14373,8 +14373,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14655,6 +14655,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -14677,8 +14678,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14750,8 +14750,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -14951,8 +14951,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15152,6 +15152,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15174,8 +15175,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15245,8 +15245,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15339,8 +15339,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15492,6 +15492,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15514,8 +15515,7 @@ "description": "Not Found if gist is not starred" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -15638,6 +15638,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15660,8 +15661,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -15720,8 +15720,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16271,8 +16271,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16334,8 +16334,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16446,6 +16446,7 @@ "categoryLabel": "Markdown", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16458,7 +16459,6 @@ "description": "Not modified" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The Markdown text to render in HTML.

    ", @@ -16600,8 +16600,8 @@ "category": "meta", "categoryLabel": "Meta", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -16694,6 +16694,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -16721,8 +16722,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -17030,8 +17030,8 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -17106,6 +17106,7 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "205", @@ -17123,8 +17124,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21465,6 +21465,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -21472,8 +21473,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -21544,8 +21544,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -22571,6 +22571,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -22583,8 +22584,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -24466,8 +24466,8 @@ "subcategory": "org-pre-receive-hooks", "subcategoryLabel": "Org pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -25047,6 +25047,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -25059,8 +25060,7 @@ "description": "Not Found if user is not a public member" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -25193,6 +25193,7 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -25200,8 +25201,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -29688,8 +29688,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29911,6 +29911,7 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -29938,8 +29939,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -30028,6 +30028,7 @@ "subcategoryLabel": "Cards", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30060,7 +30061,6 @@ "description": "Response" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the card in a column. Can be one of: top, bottom, or after:<card_id> to place after the specified card.

    ", @@ -30135,8 +30135,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30329,6 +30329,7 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -30351,8 +30352,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -30440,8 +30440,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -30741,6 +30741,7 @@ "subcategoryLabel": "Columns", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -30768,7 +30769,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the column in a project. Can be one of: first, last, or after:<column_id> to place after the specified column.

    ", @@ -31667,8 +31667,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -37506,8 +37506,8 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -37591,6 +37591,7 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -37613,8 +37614,7 @@ "description": "Preview header missing" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -37739,13 +37739,13 @@ "x-codeSamples": [ { "lang": "Shell", - "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", - "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " }, { "lang": "JavaScript", - "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 'app_id'\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", - "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 'app_id'\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " + "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 42\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 42\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " } ], "summary": "Update branch protection", @@ -37807,11 +37807,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37837,11 +37837,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37901,11 +37901,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37931,11 +37931,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -37960,11 +37960,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38481,11 +38481,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38511,11 +38511,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38575,11 +38575,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38605,11 +38605,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -38634,11 +38634,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -49225,7 +49225,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -49286,7 +49286,7 @@ "subcategoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\".

    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", + "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

    \n
    Cannot assign {member} permission of {role name}\n
    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", "bodyParameters": [ { "type": "string", @@ -49406,6 +49406,7 @@ "subcategory": "collaborators", "subcategoryLabel": "Collaborators", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -49413,8 +49414,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -49656,8 +49656,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -49862,6 +49862,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -49874,8 +49875,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -53436,8 +53436,8 @@ "subcategory": "deployments", "subcategoryLabel": "Deployments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -53709,7 +53709,7 @@ "properties": { "state": { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -53722,7 +53722,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, "target_url": { @@ -53819,7 +53819,7 @@ "bodyParameters": [ { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -53832,7 +53832,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, { @@ -54831,6 +54831,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -54838,8 +54839,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -54936,8 +54936,8 @@ "subcategory": "forks", "subcategoryLabel": "Forks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -56444,6 +56444,7 @@ "subcategory": "refs", "subcategoryLabel": "Refs", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -56456,8 +56457,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -57476,8 +57476,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -58639,6 +58639,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -58651,8 +58652,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -59751,6 +59751,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -59758,8 +59759,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -60497,8 +60497,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -60703,6 +60703,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -60710,8 +60711,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -61144,8 +61144,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61227,8 +61227,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62302,8 +62302,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62406,8 +62406,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62858,6 +62858,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -62870,8 +62871,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -63644,6 +63644,7 @@ "subcategory": "timeline", "subcategoryLabel": "Timeline", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -63661,8 +63662,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -63742,8 +63742,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63971,8 +63971,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64143,8 +64143,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64381,8 +64381,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -64615,6 +64615,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -64622,8 +64623,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -65312,8 +65312,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65582,8 +65582,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65849,6 +65849,7 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -65861,8 +65862,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -65952,8 +65952,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66261,8 +66261,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66832,6 +66832,7 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -66849,8 +66850,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -66930,8 +66930,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67068,8 +67068,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67146,8 +67146,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -67344,8 +67344,8 @@ "subcategory": "repo-pre-receive-hooks", "subcategoryLabel": "Repo pre receive hooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -70135,6 +70135,7 @@ "category": "pulls", "categoryLabel": "Pulls", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -70147,8 +70148,7 @@ "description": "Not Found if pull request has not been merged" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -70438,8 +70438,8 @@ "subcategory": "review-requests", "subcategoryLabel": "Review requests", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -70739,6 +70739,7 @@ "subcategoryLabel": "Review requests", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -70751,7 +70752,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "type": "array of strings", @@ -71437,8 +71437,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -71661,8 +71661,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -73063,6 +73063,7 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -73070,8 +73071,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -73855,8 +73855,8 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75351,8 +75351,8 @@ "subcategory": "watching", "subcategoryLabel": "Watching", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75635,8 +75635,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75799,8 +75799,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75886,8 +75886,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -78102,8 +78102,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -78239,8 +78239,8 @@ "subcategory": "management-console", "subcategoryLabel": "Management console", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -82862,6 +82862,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -82889,8 +82890,7 @@ "description": "if the person is not followed by the authenticated user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -84396,8 +84396,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -84476,8 +84476,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -85720,6 +85720,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -85747,8 +85748,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -85800,6 +85800,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -85827,8 +85828,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -86004,6 +86004,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -86031,8 +86032,7 @@ "description": "Not Found if this repository is not starred by you" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -86180,6 +86180,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -86207,8 +86208,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -86759,6 +86759,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -86766,8 +86767,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -86987,6 +86987,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -86999,8 +87000,7 @@ "description": "if the user does not follow the target user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -87569,8 +87569,8 @@ "category": "projects", "categoryLabel": "Projects", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -87733,6 +87733,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -87740,8 +87741,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index c27d68afe0..46f70826ca 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -116,8 +116,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -506,8 +506,8 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -890,6 +890,7 @@ "subcategory": "global-webhooks", "subcategoryLabel": "Global webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -897,8 +898,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -1070,8 +1070,8 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1130,6 +1130,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -1137,8 +1138,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -1455,8 +1455,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -1623,8 +1623,8 @@ "subcategory": "pre-receive-environments", "subcategoryLabel": "Pre receive environments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -2276,6 +2276,7 @@ "subcategory": "users", "subcategoryLabel": "Users", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -2283,8 +2284,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -5833,8 +5833,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -5896,8 +5896,8 @@ "category": "codes-of-conduct", "categoryLabel": "Codes of conduct", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -6208,8 +6208,8 @@ "subcategory": "license", "subcategoryLabel": "License", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -6258,8 +6258,8 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -6308,6 +6308,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6315,8 +6316,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6357,6 +6357,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6364,8 +6365,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6405,6 +6405,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6412,8 +6413,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6454,6 +6454,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6461,8 +6462,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6503,6 +6503,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6510,8 +6511,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6552,6 +6552,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6559,8 +6560,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6601,6 +6601,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6608,8 +6609,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6650,6 +6650,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6657,8 +6658,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6698,6 +6698,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6705,8 +6706,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -6747,6 +6747,7 @@ "subcategory": "admin-stats", "subcategoryLabel": "Admin stats", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -6754,8 +6755,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -9252,8 +9252,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -9534,6 +9534,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -9556,8 +9557,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -9629,8 +9629,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -9830,8 +9830,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10031,6 +10031,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -10053,8 +10054,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10124,8 +10124,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10218,8 +10218,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -10371,6 +10371,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -10393,8 +10394,7 @@ "description": "Not Found if gist is not starred" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -10517,6 +10517,7 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -10539,8 +10540,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -10599,8 +10599,8 @@ "category": "gists", "categoryLabel": "Gists", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -11150,8 +11150,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -11213,8 +11213,8 @@ "category": "licenses", "categoryLabel": "Licenses", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -11325,6 +11325,7 @@ "categoryLabel": "Markdown", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -11337,7 +11338,6 @@ "description": "Not modified" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The Markdown text to render in HTML.

    ", @@ -11801,8 +11801,8 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -11877,6 +11877,7 @@ "subcategory": "notifications", "subcategoryLabel": "Notifications", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "205", @@ -11894,8 +11895,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -14889,6 +14889,164 @@ "bodyParameters": [], "descriptionHTML": "

    Removes a repository from an organization secret when the visibility for repository access is set to selected. The visibility is set when you Create or update an organization secret. You must authenticate using an access token with the admin:org scope to use this endpoint. GitHub Apps must have the secrets organization permission to use this endpoint.

    " }, + { + "verb": "get", + "requestPath": "/orgs/{org}/external-group/{group_id}", + "serverUrl": "https://{hostname}/api/v3", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "group_id", + "description": "group_id parameter", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    group_id parameter

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/orgs/ORG/external-group/42", + "html": "
    curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/orgs/ORG/external-group/42
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /orgs/{org}/external-group/{group_id}', {\n org: 'org',\n group_id: 42\n})", + "html": "
    await octokit.request('GET /orgs/{org}/external-group/{group_id}', {\n  org: 'org',\n  group_id: 42\n})\n
    " + } + ], + "summary": "Get an external group", + "description": "Displays information about the specific group's usage. Provides a list of the group's external members as well as a list of teams that this group is connected to.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/external-idp-group-info-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#external-idp-group-info-for-an-organization" + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": true, + "category": "teams", + "subcategory": "external-groups" + }, + "slug": "get-an-external-group", + "category": "teams", + "categoryLabel": "Teams", + "subcategory": "external-groups", + "subcategoryLabel": "External groups", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Displays information about the specific group's usage. Provides a list of the group's external members as well as a list of teams that this group is connected to.

    \n

    You can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"GitHub's products\" in the GitHub Help documentation.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"group_id\": \"123\",\n  \"group_name\": \"Octocat admins\",\n  \"updated_at\": \"2021-01-24T11:31:04-06:00\",\n  \"teams\": [\n    {\n      \"team_id\": 1,\n      \"team_name\": \"team-test\"\n    },\n    {\n      \"team_id\": 2,\n      \"team_name\": \"team-test2\"\n    }\n  ],\n  \"members\": [\n    {\n      \"member_id\": 1,\n      \"member_login\": \"mona-lisa_eocsaxrs\",\n      \"member_name\": \"Mona Lisa\",\n      \"member_email\": \"mona_lisa@github.com\"\n    },\n    {\n      \"member_id\": 2,\n      \"member_login\": \"octo-lisa_eocsaxrs\",\n      \"member_name\": \"Octo Lisa\",\n      \"member_email\": \"octo_lisa@github.com\"\n    }\n  ]\n}\n
    " + } + ] + }, + { + "verb": "get", + "requestPath": "/orgs/{org}/external-groups", + "serverUrl": "https://{hostname}/api/v3", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + }, + "descriptionHTML": "

    Results per page (max 100)

    " + }, + { + "name": "page", + "description": "Page token", + "in": "query", + "schema": { + "type": "integer" + }, + "descriptionHTML": "

    Page token

    " + }, + { + "name": "display_name", + "description": "Limits the list to groups containing the text in the group name", + "in": "query", + "schema": { + "type": "string" + }, + "descriptionHTML": "

    Limits the list to groups containing the text in the group name

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/orgs/ORG/external-groups", + "html": "
    curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/orgs/ORG/external-groups
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /orgs/{org}/external-groups', {\n org: 'org'\n})", + "html": "
    await octokit.request('GET /orgs/{org}/external-groups', {\n  org: 'org'\n})\n
    " + } + ], + "summary": "List external groups in an organization", + "description": "Lists external groups available in an organization. You can query the groups using the `display_name` parameter, only groups with a `group_name` containing the text provided in the `display_name` parameter will be returned. You can also limit your page results using the `per_page` parameter. GitHub AE generates a url-encoded `page` token using a cursor value for where the next page begins. For more information on cursor pagination, see \"[Offset and Cursor Pagination explained](https://dev.to/jackmarchant/offset-and-cursor-pagination-explained-b89).\"\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/list-external-idp-groups-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#list-external-idp-groups-for-an-organization" + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": true, + "category": "teams", + "subcategory": "external-groups" + }, + "slug": "list-external-groups-in-an-organization", + "category": "teams", + "categoryLabel": "Teams", + "subcategory": "external-groups", + "subcategoryLabel": "External groups", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

    Lists external groups available in an organization. You can query the groups using the display_name parameter, only groups with a group_name containing the text provided in the display_name parameter will be returned. You can also limit your page results using the per_page parameter. GitHub AE generates a url-encoded page token using a cursor value for where the next page begins. For more information on cursor pagination, see \"Offset and Cursor Pagination explained.\"

    \n

    You can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"GitHub's products\" in the GitHub Help documentation.

    ", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"groups\": [\n    {\n      \"group_id\": \"123\",\n      \"group_name\": \"Octocat admins\",\n      \"updated_at\": \"2021-01-24T11:31:04-06:00\"\n    },\n    {\n      \"group_id\": \"456\",\n      \"group_name\": \"Octocat docs members\",\n      \"updated_at\": \"2021-03-24T11:31:04-06:00\"\n    }\n  ]\n}\n
    " + } + ] + }, { "verb": "get", "requestPath": "/orgs/{org}/hooks", @@ -14958,8 +15116,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -15985,6 +16143,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -15997,8 +16156,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -20898,6 +21056,185 @@ "bodyParameters": [], "descriptionHTML": "

    Note: You can also specify a team or organization with team_id and org_id using the route DELETE /organizations/:org_id/team/:team_id/discussions/:discussion_number/reactions/:reaction_id.

    \n

    Delete a reaction to a team discussion. OAuth access tokens require the write:discussion scope.

    " }, + { + "verb": "patch", + "requestPath": "/orgs/{org}/teams/{team_slug}/external-groups", + "serverUrl": "https://{hostname}/api/v3", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "team_slug", + "description": "team_slug parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    team_slug parameter

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X PATCH \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/orgs/ORG/teams/TEAM_SLUG/external-groups \\\n -d '{\"group_id\":42}'", + "html": "
    curl \\\n  -X PATCH \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/orgs/ORG/teams/TEAM_SLUG/external-groups \\\n  -d '{\"group_id\":42}'
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('PATCH /orgs/{org}/teams/{team_slug}/external-groups', {\n org: 'org',\n team_slug: 'team_slug',\n group_id: 42\n})", + "html": "
    await octokit.request('PATCH /orgs/{org}/teams/{team_slug}/external-groups', {\n  org: 'org',\n  team_slug: 'team_slug',\n  group_id: 42\n})\n
    " + } + ], + "summary": "Update the connection between an external group and a team", + "description": "Creates a connection between a team and an external group. Only one external group can be linked to a team.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/link-external-idp-group-to-team-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#link-external-idp-group-team-connection" + }, + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "properties": { + "group_id": { + "type": "integer", + "description": "

    Required. External Group Id

    ", + "example": 1, + "name": "group_id", + "in": "body", + "rawType": "integer", + "rawDescription": "External Group Id", + "childParamsGroups": [] + } + }, + "required": [ + "group_id" + ] + }, + "example": { + "group_id": 123 + } + } + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": false, + "category": "teams", + "subcategory": "external-groups" + }, + "slug": "update-the-connection-between-an-external-group-and-a-team", + "category": "teams", + "categoryLabel": "Teams", + "subcategory": "external-groups", + "subcategoryLabel": "External groups", + "contentType": "application/json", + "notes": [], + "descriptionHTML": "

    Creates a connection between a team and an external group. Only one external group can be linked to a team.

    \n

    You can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"GitHub's products\" in the GitHub Help documentation.

    ", + "bodyParameters": [ + { + "type": "integer", + "description": "

    Required. External Group Id

    ", + "example": 1, + "name": "group_id", + "in": "body", + "rawType": "integer", + "rawDescription": "External Group Id", + "childParamsGroups": [] + } + ], + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
    {\n  \"group_id\": \"123\",\n  \"group_name\": \"Octocat admins\",\n  \"updated_at\": \"2021-01-24T11:31:04-06:00\",\n  \"teams\": [\n    {\n      \"team_id\": 1,\n      \"team_name\": \"team-test\"\n    },\n    {\n      \"team_id\": 2,\n      \"team_name\": \"team-test2\"\n    }\n  ],\n  \"members\": [\n    {\n      \"member_id\": 1,\n      \"member_login\": \"mona-lisa_eocsaxrs\",\n      \"member_name\": \"Mona Lisa\",\n      \"member_email\": \"mona_lisa@github.com\"\n    },\n    {\n      \"member_id\": 2,\n      \"member_login\": \"octo-lisa_eocsaxrs\",\n      \"member_name\": \"Octo Lisa\",\n      \"member_email\": \"octo_lisa@github.com\"\n    }\n  ]\n}\n
    " + } + ] + }, + { + "verb": "delete", + "requestPath": "/orgs/{org}/teams/{team_slug}/external-groups", + "serverUrl": "https://{hostname}/api/v3", + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "team_slug", + "description": "team_slug parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

    team_slug parameter

    " + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/orgs/ORG/teams/TEAM_SLUG/external-groups", + "html": "
    curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/orgs/ORG/teams/TEAM_SLUG/external-groups
    " + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /orgs/{org}/teams/{team_slug}/external-groups', {\n org: 'org',\n team_slug: 'team_slug'\n})", + "html": "
    await octokit.request('DELETE /orgs/{org}/teams/{team_slug}/external-groups', {\n  org: 'org',\n  team_slug: 'team_slug'\n})\n
    " + } + ], + "summary": "Remove the connection between an external group and a team", + "description": "Deletes a connection between a team and an external group.\n\nYou can manage team membership with your IdP using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/unlink-external-idp-group-from-team-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#unlink-external-idp-group-team-connection" + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": false, + "category": "teams", + "subcategory": "external-groups" + }, + "slug": "remove-the-connection-between-an-external-group-and-a-team", + "category": "teams", + "categoryLabel": "Teams", + "subcategory": "external-groups", + "subcategoryLabel": "External groups", + "notes": [], + "responses": [ + { + "httpStatusCode": "204", + "httpStatusMessage": "No Content", + "description": "Response" + } + ], + "bodyParameters": [], + "descriptionHTML": "

    Deletes a connection between a team and an external group.

    \n

    You can manage team membership with your IdP using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

    " + }, { "verb": "get", "requestPath": "/orgs/{org}/teams/{team_slug}/members", @@ -22213,8 +22550,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -22436,6 +22773,7 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -22463,8 +22801,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -22553,6 +22890,7 @@ "subcategoryLabel": "Cards", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -22585,7 +22923,6 @@ "description": "Response" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the card in a column. Can be one of: top, bottom, or after:<card_id> to place after the specified card.

    ", @@ -22660,8 +22997,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -22854,6 +23191,7 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -22876,8 +23214,7 @@ "description": "Forbidden" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -22965,8 +23302,8 @@ "subcategory": "cards", "subcategoryLabel": "Cards", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -23266,6 +23603,7 @@ "subcategoryLabel": "Columns", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "201", @@ -23293,7 +23631,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "description": "

    Required. The position of the column in a project. Can be one of: first, last, or after:<column_id> to place after the specified column.

    ", @@ -24192,8 +24529,8 @@ "subcategory": "columns", "subcategoryLabel": "Columns", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29274,8 +29611,8 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -29359,6 +29696,7 @@ "subcategory": "branches", "subcategoryLabel": "Branches", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -29381,8 +29719,7 @@ "description": "Preview header missing" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -29507,13 +29844,13 @@ "x-codeSamples": [ { "lang": "Shell", - "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", - "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":\"app_id\"}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'", + "html": "
    curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/repos/octocat/hello-world/branches/BRANCH/protection \\\n  -d '{\"required_status_checks\":{\"strict\":true,\"contexts\":[\"contexts\"],\"checks\":[{\"context\":\"context\",\"app_id\":42}]},\"enforce_admins\":true,\"required_pull_request_reviews\":{\"dismissal_restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"]},\"dismiss_stale_reviews\":true,\"require_code_owner_reviews\":true,\"required_approving_review_count\":42},\"restrictions\":{\"users\":[\"users\"],\"teams\":[\"teams\"],\"apps\":[\"apps\"]}}'
    " }, { "lang": "JavaScript", - "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 'app_id'\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", - "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 'app_id'\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " + "source": "await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n owner: 'octocat',\n repo: 'hello-world',\n branch: 'branch',\n required_status_checks: {\n strict: true,\n contexts: [\n 'contexts'\n ],\n checks: [\n {\n context: 'context',\n app_id: 42\n }\n ]\n },\n enforce_admins: true,\n required_pull_request_reviews: {\n dismissal_restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ]\n },\n dismiss_stale_reviews: true,\n require_code_owner_reviews: true,\n required_approving_review_count: 42\n },\n restrictions: {\n users: [\n 'users'\n ],\n teams: [\n 'teams'\n ],\n apps: [\n 'apps'\n ]\n }\n})", + "html": "
    await octokit.request('PUT /repos/{owner}/{repo}/branches/{branch}/protection', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  branch: 'branch',\n  required_status_checks: {\n    strict: true,\n    contexts: [\n      'contexts'\n    ],\n    checks: [\n      {\n        context: 'context',\n        app_id: 42\n      }\n    ]\n  },\n  enforce_admins: true,\n  required_pull_request_reviews: {\n    dismissal_restrictions: {\n      users: [\n        'users'\n      ],\n      teams: [\n        'teams'\n      ]\n    },\n    dismiss_stale_reviews: true,\n    require_code_owner_reviews: true,\n    required_approving_review_count: 42\n  },\n  restrictions: {\n    users: [\n      'users'\n    ],\n    teams: [\n      'teams'\n    ],\n    apps: [\n      'apps'\n    ]\n  }\n})\n
    " } ], "summary": "Update branch protection", @@ -29575,11 +29912,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -29605,11 +29942,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -29669,11 +30006,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -29699,11 +30036,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -29728,11 +30065,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -30249,11 +30586,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -30279,11 +30616,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -30343,11 +30680,11 @@ "childParamsGroups": [] }, "app_id": { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -30373,11 +30710,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -30402,11 +30739,11 @@ "childParamsGroups": [] }, { - "type": "string", + "type": "integer", "description": "

    The ID of the GitHub App that must provide this check. Set to null to accept the check from any source.

    ", "name": "app_id", "in": "body", - "rawType": "string", + "rawType": "integer", "rawDescription": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source.", "childParamsGroups": [] } @@ -40745,7 +41082,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -40806,7 +41143,7 @@ "subcategoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\".

    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", + "descriptionHTML": "

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

    \n

    For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

    \n
    Cannot assign {member} permission of {role name}\n
    \n

    Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

    \n

    The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

    \n

    Rate limits

    \n

    You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

    ", "bodyParameters": [ { "type": "string", @@ -40926,6 +41263,7 @@ "subcategory": "collaborators", "subcategoryLabel": "Collaborators", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -40933,8 +41271,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -41176,8 +41513,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -41382,6 +41719,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -41394,8 +41732,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -44956,8 +45293,8 @@ "subcategory": "deployments", "subcategoryLabel": "Deployments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -45229,7 +45566,7 @@ "properties": { "state": { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -45242,7 +45579,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, "target_url": { @@ -45339,7 +45676,7 @@ "bodyParameters": [ { "type": "string", - "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", + "description": "

    Required. The state of the status. Can be one of error, failure, inactive, in_progress, queued, pending, or success. When you set a transient deployment to inactive, the deployment will be shown as destroyed in GitHub.

    ", "enum": [ "error", "failure", @@ -45352,7 +45689,7 @@ "name": "state", "in": "body", "rawType": "string", - "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "rawDescription": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "childParamsGroups": [] }, { @@ -45604,6 +45941,7 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -45611,8 +45949,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -45709,8 +46046,8 @@ "subcategory": "forks", "subcategoryLabel": "Forks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -47217,6 +47554,7 @@ "subcategory": "refs", "subcategoryLabel": "Refs", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -47229,8 +47567,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "post", @@ -48249,8 +48586,8 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -49412,6 +49749,7 @@ "subcategory": "webhooks", "subcategoryLabel": "Webhooks", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -49424,8 +49762,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -50524,6 +50861,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -50531,8 +50869,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -51270,8 +51607,8 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -51476,6 +51813,7 @@ "subcategory": "comments", "subcategoryLabel": "Comments", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -51483,8 +51821,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -51917,8 +52254,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -52000,8 +52337,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -53075,8 +53412,8 @@ "subcategory": "events", "subcategoryLabel": "Events", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -53179,8 +53516,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -53631,6 +53968,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -53643,8 +53981,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -54417,6 +54754,7 @@ "subcategory": "timeline", "subcategoryLabel": "Timeline", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -54434,8 +54772,7 @@ "description": "Gone" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -54515,8 +54852,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -54744,8 +55081,8 @@ "subcategory": "keys", "subcategoryLabel": "Keys", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -54916,8 +55253,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -55154,8 +55491,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -55388,6 +55725,7 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -55395,8 +55733,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -56085,8 +56422,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -56355,8 +56692,8 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -56622,6 +56959,7 @@ "subcategory": "milestones", "subcategoryLabel": "Milestones", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -56634,8 +56972,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -56725,8 +57062,8 @@ "subcategory": "labels", "subcategoryLabel": "Labels", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -57034,8 +57371,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -57621,6 +57958,7 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -57638,8 +57976,7 @@ "description": "Validation failed" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -57719,8 +58056,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -57857,8 +58194,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -57935,8 +58272,8 @@ "subcategory": "pages", "subcategoryLabel": "Pages", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -60524,6 +60861,7 @@ "category": "pulls", "categoryLabel": "Pulls", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -60536,8 +60874,7 @@ "description": "Not Found if pull request has not been merged" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -60827,8 +61164,8 @@ "subcategory": "review-requests", "subcategoryLabel": "Review requests", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -61128,6 +61465,7 @@ "subcategoryLabel": "Review requests", "contentType": "application/json", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "200", @@ -61140,7 +61478,6 @@ "description": "Validation failed" } ], - "descriptionHTML": "", "bodyParameters": [ { "type": "array of strings", @@ -61826,8 +62163,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -62050,8 +62387,8 @@ "subcategory": "reviews", "subcategoryLabel": "Reviews", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -63431,6 +63768,7 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -63438,8 +63776,7 @@ "description": "Response" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -64054,8 +64391,8 @@ "subcategory": "releases", "subcategoryLabel": "Releases", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65550,8 +65887,8 @@ "subcategory": "watching", "subcategoryLabel": "Watching", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65834,8 +66171,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -65998,8 +66335,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -66085,8 +66422,8 @@ "category": "repos", "categoryLabel": "Repos", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -72341,6 +72678,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -72368,8 +72706,7 @@ "description": "if the person is not followed by the authenticated user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -73875,8 +74212,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -73955,8 +74292,8 @@ "subcategory": "members", "subcategoryLabel": "Members", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", @@ -75108,6 +75445,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -75135,8 +75473,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "delete", @@ -75188,6 +75525,7 @@ "subcategory": "invitations", "subcategoryLabel": "Invitations", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -75215,8 +75553,7 @@ "description": "Conflict" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -75392,6 +75729,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -75419,8 +75757,7 @@ "description": "Not Found if this repository is not starred by you" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "put", @@ -75568,6 +75905,7 @@ "subcategory": "starring", "subcategoryLabel": "Starring", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -75595,8 +75933,7 @@ "description": "Resource not found" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -76296,6 +76633,7 @@ "subcategory": "followers", "subcategoryLabel": "Followers", "notes": [], + "descriptionHTML": "", "responses": [ { "httpStatusCode": "204", @@ -76308,8 +76646,7 @@ "description": "if the user does not follow the target user" } ], - "bodyParameters": [], - "descriptionHTML": "" + "bodyParameters": [] }, { "verb": "get", @@ -76878,8 +77215,8 @@ "category": "projects", "categoryLabel": "Projects", "notes": [], - "bodyParameters": [], "descriptionHTML": "", + "bodyParameters": [], "responses": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index e6bb3c9048..0df65fb18b 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -18602,6 +18602,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -18620,7 +18622,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -18985,6 +18990,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -19003,7 +19010,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -21672,6 +21682,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -21690,7 +21702,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -21791,6 +21806,907 @@ } } }, + "/enterprises/{enterprise}/actions/runners/{runner_id}/labels": { + "get": { + "summary": "List labels for a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nLists all labels for a self-hosted runner configured in an enterprise.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/list-labels-for-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise" + }, + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "enabledForGitHubApps": false, + "githubCloudOnly": false, + "category": "enterprise-admin", + "subcategory": "actions" + } + }, + "post": { + "summary": "Add custom labels to a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nAdd custom labels to a self-hosted runner configured in an enterprise.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/add-custom-labels-to-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#add-custom-labels-to-a-self-hosted-runner-for-an-enterprise" + }, + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array", + "minItems": 1, + "description": "The names of the custom labels to add to the runner.", + "items": { + "type": "string" + } + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "actions" + } + }, + "put": { + "summary": "Set custom labels for a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in an enterprise.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/set-custom-labels-for-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#set-custom-labels-for-a-self-hosted-runner-for-an-enterprise" + }, + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array", + "minItems": 0, + "description": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "items": { + "type": "string" + } + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "actions" + } + }, + "delete": { + "summary": "Remove all custom labels from a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all custom labels from a self-hosted runner configured in an\nenterprise. Returns the remaining read-only labels from the runner.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/remove-all-custom-labels-from-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise" + }, + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 3, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "actions" + } + } + }, + "/enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}": { + "delete": { + "summary": "Remove a custom label from a self-hosted runner for an enterprise", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove a custom label from a self-hosted runner configured\nin an enterprise. Returns the remaining labels from the runner.\n\nThis endpoint returns a `404 Not Found` status if the custom label is not\npresent on the runner.\n\nYou must authenticate using an access token with the `manage_runners:enterprise` scope to use this endpoint.", + "tags": [ + "enterprise-admin" + ], + "operationId": "enterprise-admin/remove-custom-label-from-self-hosted-runner-for-enterprise", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/enterprise-admin#remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise" + }, + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "name", + "description": "The name of a self-hosted runner's custom label.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "actions", + "subcategory": "self-hosted-runners" + } + } + }, "/enterprises/{enterprise}/audit-log": { "get": { "summary": "Get the audit log for an enterprise", @@ -56550,6 +57466,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -56568,7 +57486,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -56929,6 +57850,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -56947,7 +57870,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -59612,6 +60538,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -59630,7 +60558,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -59730,6 +60661,872 @@ } } }, + "/orgs/{org}/actions/runners/{runner_id}/labels": { + "get": { + "summary": "List labels for a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nLists all labels for a self-hosted runner configured in an organization.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/list-labels-for-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + }, + "post": { + "summary": "Add custom labels to a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nAdd custom labels to a self-hosted runner configured in an organization.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/add-custom-labels-to-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array", + "minItems": 1, + "description": "The names of the custom labels to add to the runner.", + "items": { + "type": "string" + } + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + }, + "put": { + "summary": "Set custom labels for a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in an organization.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/set-custom-labels-for-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array", + "minItems": 0, + "description": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "items": { + "type": "string" + } + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + }, + "delete": { + "summary": "Remove all custom labels from a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all custom labels from a self-hosted runner configured in an\norganization. Returns the remaining read-only labels from the runner.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-all-custom-labels-from-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 3, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + } + }, + "/orgs/{org}/actions/runners/{runner_id}/labels/{name}": { + "delete": { + "summary": "Remove a custom label from a self-hosted runner for an organization", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove a custom label from a self-hosted runner configured\nin an organization. Returns the remaining labels from the runner.\n\nThis endpoint returns a `404 Not Found` status if the custom label is not\npresent on the runner.\n\nYou must authenticate using an access token with the `admin:org` scope to use this endpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-custom-label-from-self-hosted-runner-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "name", + "description": "The name of a self-hosted runner's custom label.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + } + }, "/orgs/{org}/actions/secrets": { "get": { "summary": "List organization secrets", @@ -126479,6 +128276,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -126497,7 +128296,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -129194,6 +130996,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -129212,7 +131016,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -129320,6 +131127,912 @@ } } }, + "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels": { + "get": { + "summary": "List labels for a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nLists all labels for a self-hosted runner configured in a repository.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/list-labels-for-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + }, + "post": { + "summary": "Add custom labels to a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nAdd custom labels to a self-hosted runner configured in a repository.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/add-custom-labels-to-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array", + "minItems": 1, + "description": "The names of the custom labels to add to the runner.", + "items": { + "type": "string" + } + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + }, + "put": { + "summary": "Set custom labels for a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all previous custom labels and set the new custom labels for a specific\nself-hosted runner configured in a repository.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/set-custom-labels-for-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "labels" + ], + "properties": { + "labels": { + "type": "array", + "minItems": 0, + "description": "The names of the custom labels to set for the runner. You can pass an empty array to remove all custom labels.", + "items": { + "type": "string" + } + } + } + }, + "example": { + "labels": [ + "gpu", + "accelerated" + ] + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + }, + "delete": { + "summary": "Remove all custom labels from a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove all custom labels from a self-hosted runner configured in a\nrepository. Returns the remaining read-only labels from the runner.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-all-custom-labels-from-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 3, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + } + }, + "/repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}": { + "delete": { + "summary": "Remove a custom label from a self-hosted runner for a repository", + "description": "**Note:** The Actions Runner Labels API endpoints are currently in beta and are subject to change.\n\nRemove a custom label from a self-hosted runner configured\nin a repository. Returns the remaining labels from the runner.\n\nThis endpoint returns a `404 Not Found` status if the custom label is not\npresent on the runner.\n\nYou must authenticate using an access token with the `repo` scope to use this\nendpoint.", + "tags": [ + "actions" + ], + "operationId": "actions/remove-custom-label-from-self-hosted-runner-for-repo", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "runner_id", + "description": "Unique identifier of the self-hosted runner.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "name", + "description": "The name of a self-hosted runner's custom label.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "labels" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "labels": { + "type": "array", + "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", + "type": "object", + "properties": { + "id": { + "type": "integer", + "description": "Unique identifier of the label." + }, + "name": { + "type": "string", + "description": "Name of the label." + }, + "type": { + "type": "string", + "description": "The type of label. Read-only labels are applied automatically when the runner is configured.", + "enum": [ + "read-only", + "custom" + ] + } + }, + "required": [ + "name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 4, + "labels": [ + { + "id": 5, + "name": "self-hosted", + "type": "read-only" + }, + { + "id": 7, + "name": "X64", + "type": "read-only" + }, + { + "id": 20, + "name": "macOS", + "type": "read-only" + }, + { + "id": 21, + "name": "no-gpu", + "type": "custom" + } + ] + } + } + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + }, + "422": { + "description": "Validation failed", + "content": { + "application/json": { + "schema": { + "title": "Validation Error Simple", + "description": "Validation Error Simple", + "type": "object", + "required": [ + "message", + "documentation_url" + ], + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "errors": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "actions", + "subcategory": "self-hosted-runners" + } + } + }, "/repos/{owner}/{repo}/actions/runs": { "get": { "summary": "List workflow runs for a repository", @@ -150453,7 +153166,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -151872,7 +154585,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -152782,7 +155495,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -153775,7 +156488,7 @@ "description": "The name of the required check" }, "app_id": { - "type": "string", + "type": "integer", "description": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source." } } @@ -153975,7 +156688,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -156584,7 +159297,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -156758,7 +159471,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -163025,7 +165738,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -189655,7 +192368,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -214923,7 +217636,7 @@ "properties": { "state": { "type": "string", - "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "enum": [ "error", "failure", diff --git a/lib/rest/static/dereferenced/ghes-3.0.deref.json b/lib/rest/static/dereferenced/ghes-3.0.deref.json index 4cff9118fd..4ff23ec80b 100644 --- a/lib/rest/static/dereferenced/ghes-3.0.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.0.deref.json @@ -25713,6 +25713,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -25731,7 +25733,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -26096,6 +26101,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -26114,7 +26121,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -28765,6 +28775,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -28783,7 +28795,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -60501,6 +60516,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -60519,7 +60536,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -60880,6 +60900,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -60898,7 +60920,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -63545,6 +63570,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -63563,7 +63590,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -111547,6 +111577,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -111565,7 +111597,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -114244,6 +114279,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -114262,7 +114299,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -128538,7 +128578,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -129957,7 +129997,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -130867,7 +130907,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -131867,7 +131907,7 @@ "description": "The name of the required check" }, "app_id": { - "type": "string", + "type": "integer", "description": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source." } } @@ -132067,7 +132107,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -134718,7 +134758,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -134892,7 +134932,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -157390,7 +157430,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -182192,7 +182232,7 @@ "properties": { "state": { "type": "string", - "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.0/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.0/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "enum": [ "error", "failure", diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json index 5de8dc1ea1..9ebeeb9942 100644 --- a/lib/rest/static/dereferenced/ghes-3.1.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json @@ -25713,6 +25713,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -25731,7 +25733,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -26096,6 +26101,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -26114,7 +26121,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -28765,6 +28775,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -28783,7 +28795,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -60526,6 +60541,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -60544,7 +60561,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -60905,6 +60925,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -60923,7 +60945,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -63570,6 +63595,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -63588,7 +63615,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -111862,6 +111892,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -111880,7 +111912,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -114559,6 +114594,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -114577,7 +114614,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -128853,7 +128893,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -130272,7 +130312,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -131182,7 +131222,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -132182,7 +132222,7 @@ "description": "The name of the required check" }, "app_id": { - "type": "string", + "type": "integer", "description": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source." } } @@ -132382,7 +132422,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -135033,7 +135073,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -135207,7 +135247,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -141474,7 +141514,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -160243,7 +160283,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -185198,7 +185238,7 @@ "properties": { "state": { "type": "string", - "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.1/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.1/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "enum": [ "error", "failure", diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json index 38398ff96d..f491e22f07 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -26612,6 +26612,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -26630,7 +26632,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -26995,6 +27000,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -27013,7 +27020,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -29692,6 +29702,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -29710,7 +29722,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -61529,6 +61544,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -61547,7 +61564,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -61908,6 +61928,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -61926,7 +61948,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -64601,6 +64626,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -64619,7 +64646,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -114009,6 +114039,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -114027,7 +114059,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -116734,6 +116769,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -116752,7 +116789,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -132470,7 +132510,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -133889,7 +133929,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -134799,7 +134839,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -135799,7 +135839,7 @@ "description": "The name of the required check" }, "app_id": { - "type": "string", + "type": "integer", "description": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source." } } @@ -135999,7 +136039,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -138650,7 +138690,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -138824,7 +138864,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -145091,7 +145131,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -163930,7 +163970,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -188950,7 +188990,7 @@ "properties": { "state": { "type": "string", - "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.2/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. **Note:** To use the `inactive` state, you must provide the [`application/vnd.github.ant-man-preview+json`](https://docs.github.com/enterprise-server@3.2/rest/overview/api-previews#enhanced-deployments) custom media type. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "enum": [ "error", "failure", diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json index baba972dc4..64405deb7a 100644 --- a/lib/rest/static/dereferenced/ghes-3.3.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json @@ -26447,6 +26447,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -26465,7 +26467,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -26830,6 +26835,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -26848,7 +26855,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -29527,6 +29537,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -29545,7 +29557,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -61730,6 +61745,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -61748,7 +61765,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -62109,6 +62129,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -62127,7 +62149,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -64802,6 +64827,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -64820,7 +64847,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -116029,6 +116059,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -116047,7 +116079,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -118754,6 +118789,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -118772,7 +118809,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -139365,7 +139405,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -140784,7 +140824,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -141694,7 +141734,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -142687,7 +142727,7 @@ "description": "The name of the required check" }, "app_id": { - "type": "string", + "type": "integer", "description": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source." } } @@ -142887,7 +142927,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -145496,7 +145536,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -145670,7 +145710,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -151937,7 +151977,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -170911,7 +170951,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -195840,7 +195880,7 @@ "properties": { "state": { "type": "string", - "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "enum": [ "error", "failure", diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json index eb53effa3c..04bc65d710 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -15957,6 +15957,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -15975,7 +15977,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -16340,6 +16345,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -16358,7 +16365,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -16524,6 +16534,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -16542,7 +16554,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -42277,6 +42292,335 @@ } } }, + "/orgs/{org}/external-group/{group_id}": { + "get": { + "summary": "Get an external group", + "description": "Displays information about the specific group's usage. Provides a list of the group's external members as well as a list of teams that this group is connected to.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/external-idp-group-info-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#external-idp-group-info-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "group_id", + "description": "group_id parameter", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "title": "ExternalGroup", + "description": "Information about an external group's usage and its members", + "type": "object", + "required": [ + "group_id", + "group_name", + "teams", + "members" + ], + "properties": { + "group_id": { + "description": "The internal ID of the group", + "example": 1, + "type": "integer" + }, + "group_name": { + "description": "The display name for the group", + "example": "group-azuread-test", + "type": "string" + }, + "updated_at": { + "description": "The date when the group was last updated_at", + "example": "2021-01-03 22:27:15:000 -700", + "type": "string" + }, + "teams": { + "description": "An array of teams linked to this group", + "example": [ + { + "team_id": 1, + "team_name": "team-test" + }, + { + "team_id": 2, + "team_name": "team-test2" + } + ], + "type": "array", + "items": { + "type": "object", + "required": [ + "team_id", + "team_name" + ], + "properties": { + "team_id": { + "description": "The id for a team", + "example": 1, + "type": "integer" + }, + "team_name": { + "description": "The name of the team", + "example": "team-test", + "type": "string" + } + } + } + }, + "members": { + "description": "An array of external members linked to this group", + "example": [ + { + "member_id": 1, + "member_login": "mona-lisa_eocsaxrs", + "member_name": "Mona Lisa", + "member_email": "mona_lisa@github.com" + }, + { + "member_id": 2, + "member_login": "octo-lisa_eocsaxrs", + "member_name": "Octo Lisa", + "member_email": "octo_lisa@github.com" + } + ], + "type": "array", + "items": { + "type": "object", + "required": [ + "member_id", + "member_login", + "member_name", + "member_email" + ], + "properties": { + "member_id": { + "description": "The internal user ID of the identity", + "example": 1, + "type": "integer" + }, + "member_login": { + "description": "The handle/login for the user", + "example": "mona-lisa_eocsaxrs", + "type": "string" + }, + "member_name": { + "description": "The user display name/profile name", + "example": "Mona Lisa", + "type": "string" + }, + "member_email": { + "description": "An email attached to a user", + "example": "mona_lisa@github.com", + "type": "string" + } + } + } + } + } + }, + "examples": { + "default": { + "value": { + "group_id": "123", + "group_name": "Octocat admins", + "updated_at": "2021-01-24T11:31:04-06:00", + "teams": [ + { + "team_id": 1, + "team_name": "team-test" + }, + { + "team_id": 2, + "team_name": "team-test2" + } + ], + "members": [ + { + "member_id": 1, + "member_login": "mona-lisa_eocsaxrs", + "member_name": "Mona Lisa", + "member_email": "mona_lisa@github.com" + }, + { + "member_id": 2, + "member_login": "octo-lisa_eocsaxrs", + "member_name": "Octo Lisa", + "member_email": "octo_lisa@github.com" + } + ] + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": true, + "category": "teams", + "subcategory": "external-groups" + } + } + }, + "/orgs/{org}/external-groups": { + "get": { + "summary": "List external groups in an organization", + "description": "Lists external groups available in an organization. You can query the groups using the `display_name` parameter, only groups with a `group_name` containing the text provided in the `display_name` parameter will be returned. You can also limit your page results using the `per_page` parameter. GitHub AE generates a url-encoded `page` token using a cursor value for where the next page begins. For more information on cursor pagination, see \"[Offset and Cursor Pagination explained](https://dev.to/jackmarchant/offset-and-cursor-pagination-explained-b89).\"\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/list-external-idp-groups-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#list-external-idp-groups-for-an-organization" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + } + }, + { + "name": "page", + "description": "Page token", + "in": "query", + "schema": { + "type": "integer" + } + }, + { + "name": "display_name", + "description": "Limits the list to groups containing the text in the group name", + "in": "query", + "schema": { + "type": "string" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "title": "ExternalGroups", + "description": "A list of external groups available to be connected to a team", + "type": "object", + "properties": { + "groups": { + "description": "An array of external groups available to be mapped to a team", + "example": [ + { + "group_id": 1, + "group_name": "group-azuread-test", + "updated_at": "2021-01-03 22:27:15:000 -700" + }, + { + "group_id": 2, + "group_name": "group-azuread-test2", + "updated_at": "2021-06-03 22:27:15:000 -700" + } + ], + "type": "array", + "items": { + "type": "object", + "required": [ + "group_id", + "group_name", + "updated_at" + ], + "properties": { + "group_id": { + "description": "The internal ID of the group", + "example": 1, + "type": "integer" + }, + "group_name": { + "description": "The display name of the group", + "example": "group-azuread-test", + "type": "string" + }, + "updated_at": { + "description": "The time of the last update for this group", + "example": "2019-06-03 22:27:15:000 -700", + "type": "string" + } + } + } + } + } + }, + "examples": { + "default": { + "value": { + "groups": [ + { + "group_id": "123", + "group_name": "Octocat admins", + "updated_at": "2021-01-24T11:31:04-06:00" + }, + { + "group_id": "456", + "group_name": "Octocat docs members", + "updated_at": "2021-03-24T11:31:04-06:00" + } + ] + } + } + } + } + }, + "headers": { + "Link": { + "example": "; rel=\"next\"", + "schema": { + "type": "string" + } + } + } + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": true, + "category": "teams", + "subcategory": "external-groups" + } + } + }, "/orgs/{org}/hooks": { "get": { "summary": "List organization webhooks", @@ -61634,6 +61978,262 @@ } } }, + "/orgs/{org}/teams/{team_slug}/external-groups": { + "patch": { + "summary": "Update the connection between an external group and a team", + "description": "Creates a connection between a team and an external group. Only one external group can be linked to a team.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/link-external-idp-group-to-team-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#link-external-idp-group-team-connection" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "team_slug", + "description": "team_slug parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "properties": { + "group_id": { + "type": "integer", + "description": "External Group Id", + "example": 1 + } + }, + "required": [ + "group_id" + ] + }, + "example": { + "group_id": 123 + } + } + } + }, + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "title": "ExternalGroup", + "description": "Information about an external group's usage and its members", + "type": "object", + "required": [ + "group_id", + "group_name", + "teams", + "members" + ], + "properties": { + "group_id": { + "description": "The internal ID of the group", + "example": 1, + "type": "integer" + }, + "group_name": { + "description": "The display name for the group", + "example": "group-azuread-test", + "type": "string" + }, + "updated_at": { + "description": "The date when the group was last updated_at", + "example": "2021-01-03 22:27:15:000 -700", + "type": "string" + }, + "teams": { + "description": "An array of teams linked to this group", + "example": [ + { + "team_id": 1, + "team_name": "team-test" + }, + { + "team_id": 2, + "team_name": "team-test2" + } + ], + "type": "array", + "items": { + "type": "object", + "required": [ + "team_id", + "team_name" + ], + "properties": { + "team_id": { + "description": "The id for a team", + "example": 1, + "type": "integer" + }, + "team_name": { + "description": "The name of the team", + "example": "team-test", + "type": "string" + } + } + } + }, + "members": { + "description": "An array of external members linked to this group", + "example": [ + { + "member_id": 1, + "member_login": "mona-lisa_eocsaxrs", + "member_name": "Mona Lisa", + "member_email": "mona_lisa@github.com" + }, + { + "member_id": 2, + "member_login": "octo-lisa_eocsaxrs", + "member_name": "Octo Lisa", + "member_email": "octo_lisa@github.com" + } + ], + "type": "array", + "items": { + "type": "object", + "required": [ + "member_id", + "member_login", + "member_name", + "member_email" + ], + "properties": { + "member_id": { + "description": "The internal user ID of the identity", + "example": 1, + "type": "integer" + }, + "member_login": { + "description": "The handle/login for the user", + "example": "mona-lisa_eocsaxrs", + "type": "string" + }, + "member_name": { + "description": "The user display name/profile name", + "example": "Mona Lisa", + "type": "string" + }, + "member_email": { + "description": "An email attached to a user", + "example": "mona_lisa@github.com", + "type": "string" + } + } + } + } + } + }, + "examples": { + "default": { + "value": { + "group_id": "123", + "group_name": "Octocat admins", + "updated_at": "2021-01-24T11:31:04-06:00", + "teams": [ + { + "team_id": 1, + "team_name": "team-test" + }, + { + "team_id": 2, + "team_name": "team-test2" + } + ], + "members": [ + { + "member_id": 1, + "member_login": "mona-lisa_eocsaxrs", + "member_name": "Mona Lisa", + "member_email": "mona_lisa@github.com" + }, + { + "member_id": 2, + "member_login": "octo-lisa_eocsaxrs", + "member_name": "Octo Lisa", + "member_email": "octo_lisa@github.com" + } + ] + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": false, + "category": "teams", + "subcategory": "external-groups" + } + }, + "delete": { + "summary": "Remove the connection between an external group and a team", + "description": "Deletes a connection between a team and an external group.\n\nYou can manage team membership with your IdP using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "tags": [ + "teams" + ], + "operationId": "teams/unlink-external-idp-group-from-team-for-org", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#unlink-external-idp-group-team-connection" + }, + "parameters": [ + { + "name": "org", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "team_slug", + "description": "team_slug parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "204": { + "description": "Response" + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": false, + "category": "teams", + "subcategory": "external-groups" + } + } + }, "/orgs/{org}/teams/{team_slug}/members": { "get": { "summary": "List team members", @@ -83905,6 +84505,8 @@ "labels": { "type": "array", "items": { + "title": "Self hosted runner label", + "description": "A label for a self hosted runner", "type": "object", "properties": { "id": { @@ -83923,7 +84525,10 @@ "custom" ] } - } + }, + "required": [ + "name" + ] } } }, @@ -103586,7 +104191,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -105005,7 +105610,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -105915,7 +106520,7 @@ "type": "string" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } }, @@ -106908,7 +107513,7 @@ "description": "The name of the required check" }, "app_id": { - "type": "string", + "type": "integer", "description": "The ID of the GitHub App that must provide this check. Set to `null` to accept the check from any source." } } @@ -107108,7 +107713,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -109717,7 +110322,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -109891,7 +110496,7 @@ "example": "continuous-integration/travis-ci" }, "app_id": { - "type": "string", + "type": "integer", "nullable": true } } @@ -133287,7 +133892,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -158216,7 +158821,7 @@ "properties": { "state": { "type": "string", - "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued` `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", + "description": "The state of the status. Can be one of `error`, `failure`, `inactive`, `in_progress`, `queued`, `pending`, or `success`. When you set a transient deployment to `inactive`, the deployment will be shown as `destroyed` in GitHub.", "enum": [ "error", "failure", diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br index c74b00152f..f81f327633 100644 --- a/lib/search/indexes/github-docs-3.0-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8257f6b49f9bfd27242d5c9b93f0ad0b2b1aa02c6d5e176eb2413f68482814cc -size 617208 +oid sha256:7ba96d3aa0615a44d7ff3ba36805c9db4474b7cad9c799c1bcf76ba77226b0d5 +size 640635 diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br index 07f85f9a23..95701b297d 100644 --- a/lib/search/indexes/github-docs-3.0-cn.json.br +++ b/lib/search/indexes/github-docs-3.0-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:66c37b6e68b2d91d695ff7af8ec238b7b0f3ae25b4153a935802e1a117567e04 -size 1057671 +oid sha256:7f7f80def1bace9c4e6d7d2d57f3807756c6d27c8cc196cb0c39b518f7fbbdec +size 1109309 diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br index 11bd99f904..0871b5ea69 100644 --- a/lib/search/indexes/github-docs-3.0-en-records.json.br +++ b/lib/search/indexes/github-docs-3.0-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a4ec88836717ffd36327311347de9876d8d3434a8b10d3e6c6f1fc71336b9d2d -size 940606 +oid sha256:349afe95d2533a945c9e3f28df08589b17ba533947be99273ea5319e261f8b8d +size 945236 diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br index 6031eb2bdd..8fdb94016a 100644 --- a/lib/search/indexes/github-docs-3.0-en.json.br +++ b/lib/search/indexes/github-docs-3.0-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cf5a0db21c9f4353a80d3366bad034baaf5cd3f9fc7d64edac8aab224fa873d3 -size 3842456 +oid sha256:a3123cb8c31dfecef09cbeed3373322c5293fe376eb8e6e437bf6ff576672b11 +size 3859529 diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br index e004dac4a2..2d58aa5406 100644 --- a/lib/search/indexes/github-docs-3.0-es-records.json.br +++ b/lib/search/indexes/github-docs-3.0-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1b1844f983496eb0bb5d5312337d40ab034aadd09b63ea153dc7f30fc5c30780 -size 545691 +oid sha256:6f24df755ce8e21087e3f7534cb19059b5e08afcadb680f2a07b6e92e3e2b7a0 +size 544953 diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br index eae62227a5..5802a6b960 100644 --- a/lib/search/indexes/github-docs-3.0-es.json.br +++ b/lib/search/indexes/github-docs-3.0-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1e3b719c4de2205474bc668d0122f2a11f4d75eecf928a84229070891e273fae -size 2163516 +oid sha256:1d5ba69b8bab32e10d3bf830a4ed2f468faa6c75e1514fafe00d3288590ca08b +size 2163462 diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br index fc66a21eae..99ead6cd05 100644 --- a/lib/search/indexes/github-docs-3.0-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6848774934e4f422f53824d4a5aa20f6972b8f70790f1ab41e40544df83ef0e1 -size 638376 +oid sha256:2c6598865db61619bb0ab32865d69fe00a9179c4376d5c45a47f597f3bf939c3 +size 666443 diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br index e45c05d498..894560e1e3 100644 --- a/lib/search/indexes/github-docs-3.0-ja.json.br +++ b/lib/search/indexes/github-docs-3.0-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06845612b23746ac0e8eae3c68c1e1d0eb5d4c5db5a6cb9efb855a3956f2ec98 -size 3281200 +oid sha256:083ffe1bcf987a73999fe58ff5cc21a0a8030dedec341b79f946428a09b72827 +size 3449867 diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br index 9edd2bf7db..9ef2f492d2 100644 --- a/lib/search/indexes/github-docs-3.0-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bfd83204d41311c0d6f390df41ebc9cdac7df1767288c306faaebdc795a382aa -size 543425 +oid sha256:9fb33a2f1fdd823a69446f097d4af097ed888a1e6a4ba2743caaaf7f8e3fe675 +size 572889 diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br index 8a280fd68d..9cb9d1e4ea 100644 --- a/lib/search/indexes/github-docs-3.0-pt.json.br +++ b/lib/search/indexes/github-docs-3.0-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06b5b3f15fc62d312b493aaf19038d6ea858c1c64343493987fea9912a05e159 -size 2187010 +oid sha256:2366394aa9a836c021c74086a025b12649cb316247dc73dd5d1fd3588391f504 +size 2322287 diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index 3e49fd970c..c1eff9bc27 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:efe8aa12be7b76a4901d068fd37472a236deb39c1c489fa3162cdf679622c2e4 -size 631529 +oid sha256:8776134ebc1e7fc0c9fab46e6b4a34d50c7df42c6d26719c7dd7d9cdf120ff44 +size 654962 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index 639e813bce..87f899b737 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bf7e13af4275629591fb1d2aea69a93b61eaabc740100f0d2549af5056535d1c -size 1089094 +oid sha256:773c13c0c4164097cdb8e7cf93e2f6eaf0dc95d0158b9c8de0722d82ef2a926c +size 1141273 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index 73a319f221..20f9adc6dc 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1cdbf888c16cdf9ab7a8ef34fc193a4b423dce2ec978d70e8afe0ae12f15fe86 -size 964308 +oid sha256:a9bb3ecbbcebfbbfbfcae9125ba748d829b0dee347743f3b9f22a957da11628d +size 969683 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index f92ebcd284..e61ca31df9 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:adea30dcf0753b3b5f677ce4e08687eb66b27ef60de2c38e5cfeb683370760fb -size 3932712 +oid sha256:6a46b7d412daea65b191d1e8f90bc742da17969045661c3fb092c0d9946a3e98 +size 3949506 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index 57d91b77b0..00bf6c101c 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fc87e6d9e3f6cfc6182741677def689718fa3dd322d87bdd29fc5360a786648e -size 556869 +oid sha256:7a5bb34f244d12f313bfd7e3aee6bc08fb67464d44596ba3c8ce86b673af0ae2 +size 556215 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index fa00bc4615..293d735986 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a896e381d9a0a2b59f0b68e70b383e5c0fab0d83bd572100adee1cf0db18aef6 -size 2215404 +oid sha256:7d19c3b9652e5afe3f45b2ecfddf785ab1508374ef22ce12a2dfd27e67d905a9 +size 2214108 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index 67825c7aa7..57b6f39960 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e0fefb9d18172c747ceedb239a2866bf1932fabdfbd2daa72da4a42f5a15a3f6 -size 652550 +oid sha256:5f68f1cff05da4075d801aad122eac0dfe2dfaa21b536babfd0e98fd24867ff1 +size 681113 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index 85b05891f8..df19011105 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9a51674ed417e9cc8a539504d345c82970402671b73adebb68e28a9c4adb5ea7 -size 3361992 +oid sha256:567c7239befac798fec2ec02ddae9b8b9948416c58a158382fcf0d7a8631c55d +size 3532267 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index 8d380fc21c..ed5cb1b333 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a70236207492d07ee0303a438a1686873331f16f96e015f47d1d62913ebed63c -size 554746 +oid sha256:4aab77de835739e908f319499996b40e3ff8bd28018335f416b858dfa0956ef5 +size 584762 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index c5856c5f3c..a02c62379e 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:56f2e00bf6b47f26ad8b9b39de2298d40da925f6925abaedbd68ff92f01bcd3a -size 2236322 +oid sha256:1f6260ad7db93e7434a316dc71b7ea8f8dc9c13eedce65ef47feb3f57aebecb9 +size 2375525 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 4a027eaf71..aae89c5cf2 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:39198c904a8fc3f0b5ecc85c98f9a12c95b01934619b49ed9565d56ca375b263 -size 642897 +oid sha256:c3c7e63b166869336442fa0076b553dbeb41913bc5e59f7c3c445d3a6ab6ad66 +size 668265 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 80abad3c4b..0cedbcf866 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:87470ae96e55c9390aa015aa75bb1403c1a97680f6f4de565678f586b143865e -size 1111632 +oid sha256:76abb1fe7c9f8d8ef5fd344d0c09ad61b4a413469b2c27d3f2d9e0a9af5df827 +size 1166061 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 32d40c4452..b4f56fba94 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7a7c24159d80421ed4013df5aed62c6f7c051192e9b81292068d9c81d4602b1a -size 995504 +oid sha256:c752f1bc2190598612b6f9da28f92919356b443d83b089072de00d93fa490228 +size 1000607 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 2bd9ad0a99..6d19eb53d2 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b9f61183d5740e2d281bc448a5aa503c6b0af857ba3687f1cfe2739bf6cf7eae -size 4053521 +oid sha256:80cf44e836e4c9006dc343f6f0a98308980106e07b6277f889706cc6948f6da6 +size 4071021 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 8885335862..4f2823a862 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:49b259354e3a130088320f9cc3053a72f48598759d2bd564c5a8157152721fef -size 566104 +oid sha256:4caca67346b273550f8fd4bf50d363ce448c54cd35922a2e67787eb3da976d0f +size 565519 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index 9895d61b8b..71c320e704 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a8e2e752aaea5cc0f7049066d8972aca713b6340dc8d6f3887f516f41212392a -size 2253218 +oid sha256:07d81c033125703f108dc857d80bf381f38b3602f6debf729f32b69332d7cec6 +size 2251930 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index e559eed7f6..57b63c0e6b 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ccfcd76424a779be5f8176eca414ef3a99432a9f7fc987ce3f73dbc33f371fc9 -size 663777 +oid sha256:62d1026987f34e199d2ed37bca4b5593202f594b44c8d97a369f1075a0de9913 +size 693377 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index c8206fd416..91f7fbcd5a 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2be7219b30f04d71c117963b08cbaa20f8a9977a49e2d83be91d8835db0468c8 -size 3421195 +oid sha256:76d7371f4d8babbd0e0e074b47eb9b1b9cdca9e744a3d221feecfb60af541992 +size 3604053 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index d71925b92b..372a4f4a40 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e4283db5b65996692bd88a23566480e165b85a82091e91a1f1791a304a6e8d7e -size 564069 +oid sha256:7dc21c299548df15ec371bb088c4a8dd1b2b940649d866f526b13dcf87341fc7 +size 595267 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index bdd92e2fb0..711e679ae9 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:864bc7c595611e23f293464c49b8f978e4ebd3cdd61ac0e7ff694bd430ffcded -size 2274541 +oid sha256:13add1aee54d3d4970de15338e5d5b72882fae575d8598eeb9e8d233cfe1a45f +size 2418427 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 812151fb90..04fc36977a 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:46cfd5b7c547ee6393401b5a88b6a42a17ea6c714352ae7db6dc2936a9379452 -size 645720 +oid sha256:91880c4325a916df56f4d4d54a51854156e5e1b53d1aa4d557984ad2bdd00e42 +size 690945 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index eb305753dd..b2e876a192 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:abb804d758765c170906ec1c0d23d7ecd1a03be1b38a5bdafaff7be8a3901ea3 -size 1123322 +oid sha256:f7500dadaab38bfb991b4e1fea78ab55511cad0ec46abef402d14d0b912ad711 +size 1224667 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 000fd5fbb5..618232be4f 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6f978502129bda7e85ca94d9dc5d63cd90966247f7929a6614c86958fd79073f -size 1028579 +oid sha256:90f4bd88bcb00167cba913786e3be437c27e2a95ad32b8b434d3a0063a52f91d +size 1033787 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index b0982c90ce..e44c2b9ce9 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:560d886d28d6ec05933b264a8c29071ef81fab1602bee78b61d07225b3c165d8 -size 4148638 +oid sha256:63b8df778528b95a72abdbabe05c90fd59c4b3ca3cf381ace1c9f74449d87926 +size 4164123 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 118bbc920d..20865556ad 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ce70d91c384a795f3c7e7b6c9804c599dc7356f5df13243fb551c077ce429844 -size 569100 +oid sha256:b0149cd8267c8814790f6f7a5b2a318afec377a54bfa961dc01be0ce4762c3ca +size 568494 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 67dc39f81e..ad9c3d0eee 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:20e31250522c5804a0c8302f05d4d6e32483ea6f43962fa412a162c6a19eb07f -size 2266112 +oid sha256:1afd2bf1137220938f3fd28cd23e798fb15796d9830716776373fd8b576d0de5 +size 2264103 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index bfb3a0ff24..0e374254e7 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:52a0707ac92ec55128cc220cd089769aa3660b409150a13bb72fda6d9f11f15c -size 666298 +oid sha256:4f72b9b3dbd0b14ca7d20d9599d15faf110f9147938d8f592805e87c2443caab +size 716286 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index eb9a0d879c..2bf5b2231a 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dc4250f7f711da2a30194d2a91945a098feae7a37c524fc0565f753d60dc1ea5 -size 3437333 +oid sha256:5ccb3f407eb49ebda3a45f7a07b67bc5ba55575cae025427c53005cae85fbbe4 +size 3732181 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index 1a69e54482..b8049eda50 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3a4d2de7c21719eb48a257ecd162ada6d25944ab091c9534bd856858d1658e9d -size 566618 +oid sha256:68f8d556f5e5fa0f02979a5c6912f0c5b3602d4b20f7a7fdb050fee95b26a516 +size 614005 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index 6ae49abb28..e1011eed5b 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:82bc866bb7661a9cbbf1c902029013f9159f8d3c7aae4357a6d2ef9e4b0478e4 -size 2285086 +oid sha256:62ba2598504741826d3933daae6e3136e569d54304b56c3232d3d7d951b8f46f +size 2500031 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 26728d5c09..e60f66aa2d 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ff3bf1c9ca20a373039222706a4cc8eb505a72e7d7069629bcd5eefc69749d0c -size 869035 +oid sha256:4d34ebae68d56a8015eee534ce138b77a31ad22e55986d90e3ac44f35d927c3d +size 904543 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 859433faa1..9e523db612 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6389767070419dabebc8958ea1ce922702bdda38d7b633c111515286da660c64 -size 1360867 +oid sha256:58cb65096a480c75233da8306f78c156c0248466481768f26c78de852c610213 +size 1446597 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 41db0544d5..fe7d041db0 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2a0cf9b5557881a7a8f611806729810e1cb78d0237ea861ec4f45d4f2df65595 -size 1326664 +oid sha256:31ab363fe17e182d8648777745fcb5303cd31622a4d1241b611ae366ca07a45e +size 1330817 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 7f68e97028..1df42ebda6 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f0de89bf3e3a19f1c0926c89d116edf39b2b92fb3b62bf8a93731732be5d1208 -size 5062798 +oid sha256:7e2736628a9abab713b66cc72f4e4cb5e9c261f4266d4d7d468aa5494e16bf7d +size 5080540 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index 09a0dbcd81..d1eaf7dc00 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:07f53107faa44813662da5aeafc2a17a098ba6995a026f216e5a60ba5f4c1204 -size 754187 +oid sha256:b33644d6570b5dc285508f80c77ffe2fc577e8317a977709d9b97aba39e8d2e6 +size 754431 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 7973c8e6ae..325b459f90 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f5531def883058ecfc4e72e9536068295e5c0ac1db9ab6f8fe5fdf230cf43dbe -size 2890039 +oid sha256:ff187e85662bbfcf9639d546445481e4bfac2e056c27db07e6ee0d925c4337b3 +size 2892624 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index 88c756b61d..5355232e9a 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b8035c3eeba39274e0c4ed904ea0c0963be8ab319a580318f81b60171d2710f8 -size 889675 +oid sha256:9fd3aba32b7cab0757c24188b1e8346de8a60849b5147312db2692a6e2e10e39 +size 930539 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index d035e27242..573aee3ce9 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0b8bd63e8688bc6e09658255ba408bbccdfb755c4a98653b6645dd717c5b20fe -size 4447374 +oid sha256:91f4ff555059cd17439ef023260831d8769166e5daa4f35d2951ef7c9261cf24 +size 4690544 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index fd012c202d..74ceeeb9b7 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0a63920d7b87d8f3af07ba5473c5dd4909eb5a2309d83b41a69aaf49a42edefd -size 755356 +oid sha256:c4a714b9802a4ea21004b313355141714faf1e8695cf66d6b7b83166dbed7e9d +size 796130 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index f382431c57..f29533a0c3 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bd144b14670434b122239d66f6813fcfa27b55ce5a71ce7734a2e5e75734bd76 -size 2935342 +oid sha256:9f30db0eefa5a4ec56ce3733624ac1644611e525dbfa544c67b2e369a3f91b87 +size 3116203 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index a7ac2a2c55..26ebc9d682 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9066469b73737ed84420ba9a734603a9c50a5c350105397605fd5dd371e01371 -size 493445 +oid sha256:f891a0a1fbb3cd4751522131f7870890e4055df42f22352c506ee4b06e4f520c +size 518487 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index a3300a5f95..26728d4a21 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2097dfc76eeda3c23c2793ff59afe477f8a310d4ba7e7c282808babd33e08366 -size 828981 +oid sha256:c979baee854974bbe9232780126d2521b9d6cd95d9a0f81ac6fd9964cdb2cc0e +size 877305 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index e8f083dbce..523d771f2f 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bf8ed4908cef5a08623641b96d1fccd457f8a6bb75d7b8b8e4c3550f782691de -size 795441 +oid sha256:0f80d84bdec590e8a7ba7c843575690ce9586863bc6385f9e119126b1917148e +size 800461 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 9d78e92999..55db85dc4b 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:640e293b1d19a83eeef36a0ad52dd5475626012b55a310f4dc4caac05125c3f5 -size 3196139 +oid sha256:39cc8971095192646356e6b1704daca6565eee0cd34d9732cb9b609794b44606 +size 3212265 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index a60e9337ae..c06f8c9fa6 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e063efcd8ff5d928cfdb598ef9463c7945a9ba0e8319523f92c44b59f17aca50 -size 434991 +oid sha256:8e71e0540df666ae295a9324e3206dcfbacb32a1d992a17d72b7326c34ff979b +size 435132 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 4a688ace53..eb3b5ac4a9 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:031f6bff1f973e13763ef1e41b94184c092dab473edce6d119fb7fdbcee60cd0 -size 1660400 +oid sha256:9c5864b12dac112b6e4eb15f7d2290c1a88a2fdf892774f85c9093bdda77fb1e +size 1661071 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index dcb912efb6..60ccc96d4b 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7056f5a88bb29f4f8b3de47fcd1698c220f0fcf931867e78c55d54e86d95b639 -size 509247 +oid sha256:b5891c0ff8cf03ef7a6f08c33c21ef8f83ee50b0e83f167b4a8663053d414296 +size 538823 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index d632d1057a..2411546122 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:348277fc15f1557f36132ebb5b0aa1af2f48c26a82623b171632f18bde7a5014 -size 2519400 +oid sha256:00fc9d7135361c700912e03cebc323dcce70a271ca5581f1a34eb9c99d5eaae9 +size 2693044 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 7e252ac08a..dcbebcbeab 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:12eb8f304b1f6710c3cbba5ff1af309d01e98b0f23d2d1cb1b7eaf78ce4d1682 -size 434372 +oid sha256:19dd6942fa3b1b293b67399a5c6999f3d992b6875926a018ec78746af364886a +size 465491 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index c955df8fda..68f148fbd2 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:207f7c8ccb25dfbc18cfaffe433b99487b2d6c1c98d28cae3c1dfc8850b188bc -size 1677411 +oid sha256:62c3609f614ce4174ef27200c244d8643bbc7da6b0dad0827acc6bd70cf5f3f3 +size 1816503 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index c70ad58101..3f993921b8 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4f2460f768218f873946cf76a1dbba39272b21fe6019314089bf4b83dda5f359 -size 763279 +oid sha256:a11dfa5ae40bedf3e6b427f1ffdfce94436a5ce5312c51981ba0966c935c19d9 +size 802901 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index a4c1b49421..ee909305af 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cfe9eb6e900f4e684f84055d7ef30219133888978438a450ca35896d89e0ed75 -size 1349504 +oid sha256:6d0e08f1f0a8bd5c3bdbc5799d3fbfa7ac4227a9f51bf6f0f9bb3e09e029acae +size 1448424 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index 94b7271742..472da0a33f 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:670729c3b36a69441538ef5980d766a9d2c7cd4637fd30b587804ff7988fb67b -size 1169605 +oid sha256:613f934d87ce4c47e1e49e705a53f1e42d9ccca4da6aac31d822b58b3eae27f3 +size 1178315 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index a21e2b7dc7..45bbe12a7f 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:47dbdd48b4928a0b61c3382086870fd3ed24d044c9c916fc13b2b3ec2a231655 -size 4719307 +oid sha256:5bc601e942856d4ae49e3dcda449ad146db740404c8df9b869960eea33d0e608 +size 4753618 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index 782be268f3..cbeb03317a 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f257f85a1ec316221d8624f4b239ad12a3cde076136e49c60b8d82b7efe37ff7 -size 687762 +oid sha256:2b0fbbc2d288ca3e8af42ba4ddbfe77811ef0b0a84d0d87ede3e71d455e544ca +size 688022 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index e208f82a0f..1043845cba 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4b44277648a8b919fb0b274479dad3d5ae41540654814ffc6504149a5944b441 -size 2766943 +oid sha256:6f56e5b6df99b70a7ca7195cec7455521fa73e2ff0925000645c43d46d0fd73b +size 2770284 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 5d4162a113..234e5b6489 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7caff9eaec4e458059ee44af1f39b3ae92c49bbfa199ef3aeb2fb743b00e00a6 -size 788808 +oid sha256:35d292d1724c224f2721c74c4c4588c4d5b4c83570bad98ede32079511e2258d +size 832241 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 25dfb830f4..f2d7514ca5 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e2ff154a1dc5e0a87b046cbaa5be20dcb23586f55bfe807f3046d10c479700df -size 4140990 +oid sha256:f5e83fb66b03fc207be0683580766800b17992b5e094c4c375095553430b62db +size 4400962 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index f7b47837a3..5cd37fe863 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ace2d84394aaaab7aa7a0a8af7c6c85aec3d9d225ba85ba5cdee69a303eeda97 -size 686485 +oid sha256:4d27df740742b92356cea1749527eb47c4496bde3945c8a0728e16a55f01d5a4 +size 728775 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index c67d8e8e60..9487794557 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5889ed8314377df96ad5f9e2cb437abbdb0599416cff8687ac56226d76b862da -size 2794108 +oid sha256:afbbccd8914ce4ce46aa5e60924ad15927f09937b2dde93b25397f6f204093ee +size 2989264 diff --git a/middleware/abort.js b/middleware/abort.js index 9df940993a..442ed224b0 100644 --- a/middleware/abort.js +++ b/middleware/abort.js @@ -1,3 +1,5 @@ +import statsd from '../lib/statsd.js' + export default function abort(req, res, next) { // If the client aborts the connection, send an error req.once('aborted', () => { @@ -7,6 +9,18 @@ export default function abort(req, res, next) { } // NOTE: Node.js will also automatically set `req.aborted = true` + const incrementTags = [] + // Be careful with depending on attributes set on the `req` because + // under certain conditions the contextualizers might not yet have + // had a chance to run. + if (req.pagePath) { + incrementTags.push(`path:${req.pagePath}`) + } + if (req.context?.currentCategory) { + incrementTags.push(`product:${req.context.currentCategory}`) + } + statsd.increment('middleware.abort', 1, incrementTags) + const abortError = new Error('Client closed request') abortError.statusCode = 499 abortError.code = 'ECONNRESET' diff --git a/middleware/render-page.js b/middleware/render-page.js index 1fe891d68c..a082920d6a 100644 --- a/middleware/render-page.js +++ b/middleware/render-page.js @@ -34,7 +34,10 @@ export default async function renderPage(req, res, next) { // Updating the Last-Modified header for substantive changes on a page for engineering // Docs Engineering Issue #945 - if (context.page.effectiveDate !== '') { + if (context.page.effectiveDate) { + // Note that if a page has an invalidate `effectiveDate` string value, + // it would be caught prior to this usage and ultimately lead to + // 500 error. res.setHeader('Last-Modified', new Date(context.page.effectiveDate).toUTCString()) } diff --git a/middleware/robots.js b/middleware/robots.js index ac89bee965..53fa6f8abc 100644 --- a/middleware/robots.js +++ b/middleware/robots.js @@ -8,14 +8,10 @@ export default function robots(req, res, next) { res.type('text/plain') - // remove subdomain from host - // docs-internal-12345--branch-name.herokuapp.com -> herokuapp.com - const rootDomain = req.hostname.split('.').slice(1).join('.') - - // prevent crawlers from indexing staging apps - if (rootDomain === 'herokuapp.com') { - return res.send(disallowAll) + // only include robots.txt when it's our production domain and adding localhost for robots-txt.js test + if (req.hostname === 'docs.github.com' || req.hostname === '127.0.0.1') { + return res.send(defaultResponse) } - return res.send(defaultResponse) + return res.send(disallowAll) } diff --git a/middleware/timeout.js b/middleware/timeout.js index 0764576330..fc54c608d8 100644 --- a/middleware/timeout.js +++ b/middleware/timeout.js @@ -1,5 +1,7 @@ import timeout from 'express-timeout-handler' +import statsd from '../lib/statsd.js' + // Heroku router requests timeout after 30 seconds. We should stop them earlier! const maxRequestTimeout = parseInt(process.env.REQUEST_TIMEOUT, 10) || 10000 @@ -14,6 +16,18 @@ export default timeout.handler({ disable: [], onTimeout: function (req, res, next) { + const incrementTags = [] + // Be careful with depending on attributes set on the `req` because + // under certain conditions the contextualizers might not yet have + // had a chance to run. + if (req.pagePath) { + incrementTags.push(`path:${req.pagePath}`) + } + if (req.context?.currentCategory) { + incrementTags.push(`product:${req.context.currentCategory}`) + } + statsd.increment('middleware.timeout', 1, incrementTags) + // Create a custom timeout error const timeoutError = new Error('Request timed out') timeoutError.statusCode = 503 diff --git a/package-lock.json b/package-lock.json index 83ea943afd..5fe905c020 100644 --- a/package-lock.json +++ b/package-lock.json @@ -7,19 +7,16 @@ "name": "docs.github.com", "license": "(MIT AND CC-BY-4.0)", "dependencies": { - "@alex_neo/jest-expect-message": "^1.0.5", "@github/failbot": "0.7.0", "@hapi/accept": "^5.0.2", "@primer/components": "^31.1.0", "@primer/css": "^18.2.0", "@primer/octicons": "^16.1.1", "@primer/octicons-react": "^16.1.1", + "@react-aria/ssr": "^3.1.0", "accept-language-parser": "^1.5.0", "ajv": "^8.7.1", "ajv-formats": "^2.1.1", - "bottleneck": "^2.19.5", - "browser-date-formatter": "^3.0.3", - "change-case": "^4.1.2", "cheerio": "^1.0.0-rc.10", "classnames": "^2.3.1", "compression": "^1.7.4", @@ -31,7 +28,6 @@ "dayjs": "^1.10.7", "dotenv": "^10.0.0", "express": "^4.17.1", - "express-basic-auth": "^1.2.0", "express-rate-limit": "^5.5.1", "express-timeout-handler": "^2.2.2", "flat": "^5.0.2", @@ -66,11 +62,9 @@ "rate-limit-redis": "^2.1.0", "react": "^17.0.2", "react-dom": "^17.0.2", - "react-is": "^17.0.2", "react-markdown": "^7.1.0", "react-syntax-highlighter": "^15.4.4", "redis": "^3.1.2", - "redis-mock": "^0.56.3", "rehype-autolink-headings": "^6.1.0", "rehype-highlight": "^5.0.0", "rehype-raw": "^6.1.0", @@ -100,6 +94,7 @@ "devDependencies": { "@actions/core": "^1.6.0", "@actions/github": "^5.0.0", + "@alex_neo/jest-expect-message": "^1.0.5", "@babel/core": "^7.16.0", "@babel/eslint-parser": "^7.16.3", "@babel/plugin-syntax-top-level-await": "^7.14.5", @@ -124,7 +119,9 @@ "babel-loader": "^8.2.3", "babel-plugin-styled-components": "^1.13.3", "babel-preset-env": "^1.7.0", + "bottleneck": "^2.19.5", "chalk": "^4.1.2", + "change-case": "^4.1.2", "commander": "^8.3.0", "count-array-values": "^1.2.1", "cross-env": "^7.0.3", @@ -222,7 +219,8 @@ "node_modules/@alex_neo/jest-expect-message": { "version": "1.0.5", "resolved": "https://registry.npmjs.org/@alex_neo/jest-expect-message/-/jest-expect-message-1.0.5.tgz", - "integrity": "sha512-1eBykZCd0pPGl5qKtV6Z5ARA6yuhXzHsVN2h5GH5/H6svYa37Jr7vMio5OFpiw1LBHtscrZs7amSkZkcwm0cvQ==" + "integrity": "sha512-1eBykZCd0pPGl5qKtV6Z5ARA6yuhXzHsVN2h5GH5/H6svYa37Jr7vMio5OFpiw1LBHtscrZs7amSkZkcwm0cvQ==", + "dev": true }, "node_modules/@babel/code-frame": { "version": "7.16.0", @@ -4502,6 +4500,7 @@ "version": "7.4.1", "resolved": "https://registry.npmjs.org/acorn/-/acorn-7.4.1.tgz", "integrity": "sha512-nQyp0o1/mNdbTO1PO6kHkwSrmgZ0MT/jCCpNiwbUjGoRN4dlBhqJtoQuCnEOKzgTVwg0ZWiCoQy6SxMebQVh8A==", + "dev": true, "bin": { "acorn": "bin/acorn" }, @@ -6076,7 +6075,8 @@ "node_modules/bottleneck": { "version": "2.19.5", "resolved": "https://registry.npmjs.org/bottleneck/-/bottleneck-2.19.5.tgz", - "integrity": "sha512-VHiNCbI1lKdl44tGrhNfU3lup0Tj/ZBMJB5/2ZbNXRCPuRCO7ed2mgcK4r17y+KB2EfuYuRaVlwNbAeaWGSpbw==" + "integrity": "sha512-VHiNCbI1lKdl44tGrhNfU3lup0Tj/ZBMJB5/2ZbNXRCPuRCO7ed2mgcK4r17y+KB2EfuYuRaVlwNbAeaWGSpbw==", + "dev": true }, "node_modules/boxen": { "version": "5.1.2", @@ -6144,37 +6144,11 @@ "node": ">=8" } }, - "node_modules/brfs": { - "version": "1.6.1", - "resolved": "https://registry.npmjs.org/brfs/-/brfs-1.6.1.tgz", - "integrity": "sha512-OfZpABRQQf+Xsmju8XE9bDjs+uU4vLREGolP7bDgcpsI17QREyZ4Bl+2KLxxx1kCgA0fAIhKQBaBYh+PEcCqYQ==", - "dependencies": { - "quote-stream": "^1.0.1", - "resolve": "^1.1.5", - "static-module": "^2.2.0", - "through2": "^2.0.0" - }, - "bin": { - "brfs": "bin/cmd.js" - } - }, "node_modules/brorand": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/brorand/-/brorand-1.1.0.tgz", "integrity": "sha1-EsJe/kCkXjwyPrhnWgoM5XsiNx8=" }, - "node_modules/browser-date-formatter": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/browser-date-formatter/-/browser-date-formatter-3.0.3.tgz", - "integrity": "sha512-crNsaki/mQRce8SgvRIwpI+lXttxu4HZazMzloziiA57p6LX2d4FPxOg2JTqrW5KIzBQbcSHqfFa485liPvaAw==", - "dependencies": { - "brfs": "^1.4.3", - "dateutil": "^0.1.0", - "domready": "^1.0.8", - "relative-date": "^1.1.3", - "strftime": "^0.10.0" - } - }, "node_modules/browser-process-hrtime": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/browser-process-hrtime/-/browser-process-hrtime-1.0.0.tgz", @@ -6335,6 +6309,7 @@ "version": "0.0.1", "resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-0.0.1.tgz", "integrity": "sha1-kbx0sR6kBbyRa8aqkI+q+ltKrEs=", + "optional": true, "engines": { "node": ">=0.4.0" } @@ -6342,7 +6317,8 @@ "node_modules/buffer-from": { "version": "1.1.2", "resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz", - "integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==" + "integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==", + "devOptional": true }, "node_modules/buffer-xor": { "version": "1.0.3", @@ -6412,6 +6388,7 @@ "version": "4.1.2", "resolved": "https://registry.npmjs.org/camel-case/-/camel-case-4.1.2.tgz", "integrity": "sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==", + "dev": true, "dependencies": { "pascal-case": "^3.1.2", "tslib": "^2.0.3" @@ -6470,6 +6447,7 @@ "version": "1.0.4", "resolved": "https://registry.npmjs.org/capital-case/-/capital-case-1.0.4.tgz", "integrity": "sha512-ds37W8CytHgwnhGGTi88pcPyR15qoNkOpYwmMMfnWqqWgESapLqvDx6huFjQ5vqWSn2Z06173XNA7LtMOeUh1A==", + "dev": true, "dependencies": { "no-case": "^3.0.4", "tslib": "^2.0.3", @@ -6525,6 +6503,7 @@ "version": "4.1.2", "resolved": "https://registry.npmjs.org/change-case/-/change-case-4.1.2.tgz", "integrity": "sha512-bSxY2ws9OtviILG1EiY5K7NNxkqg/JnRnFxLtKQ96JaviiIxi7djMrSd0ECT9AC+lttClmYwKw53BWpOMblo7A==", + "dev": true, "dependencies": { "camel-case": "^4.1.2", "capital-case": "^1.0.4", @@ -6976,6 +6955,7 @@ "engines": [ "node >= 0.8" ], + "optional": true, "dependencies": { "buffer-from": "^1.0.0", "inherits": "^2.0.3", @@ -6986,12 +6966,14 @@ "node_modules/concat-stream/node_modules/isarray": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" + "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=", + "optional": true }, "node_modules/concat-stream/node_modules/readable-stream": { "version": "2.3.7", "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", + "optional": true, "dependencies": { "core-util-is": "~1.0.0", "inherits": "~2.0.3", @@ -7006,6 +6988,7 @@ "version": "1.1.1", "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", + "optional": true, "dependencies": { "safe-buffer": "~5.1.0" } @@ -7066,6 +7049,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/constant-case/-/constant-case-3.0.4.tgz", "integrity": "sha512-I2hSBi7Vvs7BEuJDr5dDHfzb/Ruj3FyvFyh7KLilAjNQw3Be+xgqUBA2W6scVEcL0hL1dwPRtIqEPVUCKkSsyQ==", + "dev": true, "dependencies": { "no-case": "^3.0.4", "tslib": "^2.0.3", @@ -7529,14 +7513,6 @@ "node": ">=10" } }, - "node_modules/dateutil": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/dateutil/-/dateutil-0.1.0.tgz", - "integrity": "sha1-9MAkKeA/knwcnh4hu+KzeDNHfrA=", - "engines": { - "node": "*" - } - }, "node_modules/dayjs": { "version": "1.10.7", "resolved": "https://registry.npmjs.org/dayjs/-/dayjs-1.10.7.tgz", @@ -7896,11 +7872,6 @@ "url": "https://github.com/fb55/domhandler?sponsor=1" } }, - "node_modules/domready": { - "version": "1.0.8", - "resolved": "https://registry.npmjs.org/domready/-/domready-1.0.8.tgz", - "integrity": "sha1-kfJS5Ze2Wvd+dFriTdAYXV4m1Yw=" - }, "node_modules/domutils": { "version": "2.8.0", "resolved": "https://registry.npmjs.org/domutils/-/domutils-2.8.0.tgz", @@ -8019,6 +7990,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/dot-case/-/dot-case-3.0.4.tgz", "integrity": "sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==", + "dev": true, "dependencies": { "no-case": "^3.0.4", "tslib": "^2.0.3" @@ -8059,41 +8031,6 @@ "integrity": "sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==", "dev": true }, - "node_modules/duplexer2": { - "version": "0.1.4", - "resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.1.4.tgz", - "integrity": "sha1-ixLauHjA1p4+eJEFFmKjL8a93ME=", - "dependencies": { - "readable-stream": "^2.0.2" - } - }, - "node_modules/duplexer2/node_modules/isarray": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" - }, - "node_modules/duplexer2/node_modules/readable-stream": { - "version": "2.3.7", - "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", - "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", - "dependencies": { - "core-util-is": "~1.0.0", - "inherits": "~2.0.3", - "isarray": "~1.0.0", - "process-nextick-args": "~2.0.0", - "safe-buffer": "~5.1.1", - "string_decoder": "~1.1.1", - "util-deprecate": "~1.0.1" - } - }, - "node_modules/duplexer2/node_modules/string_decoder": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", - "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", - "dependencies": { - "safe-buffer": "~5.1.0" - } - }, "node_modules/duplexer3": { "version": "0.1.4", "resolved": "https://registry.npmjs.org/duplexer3/-/duplexer3-0.1.4.tgz", @@ -8963,6 +8900,7 @@ "version": "4.3.0", "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz", "integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==", + "devOptional": true, "engines": { "node": ">=4.0" } @@ -8971,6 +8909,7 @@ "version": "2.0.3", "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz", "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==", + "dev": true, "engines": { "node": ">=0.10.0" } @@ -9183,14 +9122,6 @@ "node": ">= 0.10.0" } }, - "node_modules/express-basic-auth": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/express-basic-auth/-/express-basic-auth-1.2.0.tgz", - "integrity": "sha512-iJ0h1Gk6fZRrFmO7tP9nIbxwNgCUJASfNj5fb0Hy15lGtbqqsxpt7609+wq+0XlByZjXmC/rslWQtnuSTVRIcg==", - "dependencies": { - "basic-auth": "^2.0.1" - } - }, "node_modules/express-rate-limit": { "version": "5.5.1", "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-5.5.1.tgz", @@ -9262,20 +9193,6 @@ "node >=0.6.0" ] }, - "node_modules/falafel": { - "version": "2.2.4", - "resolved": "https://registry.npmjs.org/falafel/-/falafel-2.2.4.tgz", - "integrity": "sha512-0HXjo8XASWRmsS0X1EkhwEMZaD3Qvp7FfURwjLKjG1ghfRm/MGZl2r4cWUTv41KdNghTw4OUMmVtdGQp3+H+uQ==", - "dependencies": { - "acorn": "^7.1.1", - "foreach": "^2.0.5", - "isarray": "^2.0.1", - "object-keys": "^1.0.6" - }, - "engines": { - "node": ">=0.4.0" - } - }, "node_modules/fast-deep-equal": { "version": "3.1.3", "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", @@ -9306,7 +9223,8 @@ "node_modules/fast-levenshtein": { "version": "2.0.6", "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz", - "integrity": "sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=" + "integrity": "sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=", + "dev": true }, "node_modules/fast-safe-stringify": { "version": "2.1.1", @@ -10691,6 +10609,7 @@ "version": "2.0.4", "resolved": "https://registry.npmjs.org/header-case/-/header-case-2.0.4.tgz", "integrity": "sha512-H/vuk5TEEVZwrR0lp2zed9OCo1uAILMlx0JEMgC26rzyJJ3N1v6XkwHHXJQdR2doSjcGPM6OKPYoJgf0plJ11Q==", + "dev": true, "dependencies": { "capital-case": "^1.0.4", "tslib": "^2.0.3" @@ -11402,6 +11321,7 @@ "version": "2.8.0", "resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.8.0.tgz", "integrity": "sha512-vd15qHsaqrRL7dtH6QNuy0ndJmRDrS9HAM1CAiSifNUFv4x1a0CCVsj18hJ1mShxIG6T2i1sO78MkP56r0nYRw==", + "dev": true, "dependencies": { "has": "^1.0.3" }, @@ -11791,11 +11711,6 @@ "node": ">=v0.10.0" } }, - "node_modules/isarray": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-2.0.5.tgz", - "integrity": "sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==" - }, "node_modules/isexe": { "version": "2.0.0", "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", @@ -13437,6 +13352,7 @@ "version": "2.0.2", "resolved": "https://registry.npmjs.org/lower-case/-/lower-case-2.0.2.tgz", "integrity": "sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==", + "dev": true, "dependencies": { "tslib": "^2.0.3" } @@ -13491,14 +13407,6 @@ "resolved": "https://registry.npmjs.org/lunr-languages/-/lunr-languages-1.9.0.tgz", "integrity": "sha512-Be5vFuc8NAheOIjviCRms3ZqFFBlzns3u9DXpPSZvALetgnydAN0poV71pVLFn0keYy/s4VblMMkqewTLe+KPg==" }, - "node_modules/magic-string": { - "version": "0.22.5", - "resolved": "https://registry.npmjs.org/magic-string/-/magic-string-0.22.5.tgz", - "integrity": "sha512-oreip9rJZkzvA8Qzk9HFs8fZGF/u7H/gtrE8EN6RjKJ9kh2HlC+yQ2QezifqTZfGyiuAV0dRv5a+y/8gBb1m9w==", - "dependencies": { - "vlq": "^0.2.2" - } - }, "node_modules/make-dir": { "version": "3.1.0", "resolved": "https://registry.npmjs.org/make-dir/-/make-dir-3.1.0.tgz", @@ -13903,14 +13811,6 @@ "resolved": "https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.1.tgz", "integrity": "sha1-sAqqVW3YtEVoFQ7J0blT8/kMu2E=" }, - "node_modules/merge-source-map": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/merge-source-map/-/merge-source-map-1.0.4.tgz", - "integrity": "sha1-pd5GU42uhNQRTMXqArR3KmNGcB8=", - "dependencies": { - "source-map": "^0.5.6" - } - }, "node_modules/merge-stream": { "version": "2.0.0", "resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz", @@ -15277,6 +15177,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/no-case/-/no-case-3.0.4.tgz", "integrity": "sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==", + "dev": true, "dependencies": { "lower-case": "^2.0.2", "tslib": "^2.0.3" @@ -16797,6 +16698,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/param-case/-/param-case-3.0.4.tgz", "integrity": "sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==", + "dev": true, "dependencies": { "dot-case": "^3.0.4", "tslib": "^2.0.3" @@ -16923,6 +16825,7 @@ "version": "3.1.2", "resolved": "https://registry.npmjs.org/pascal-case/-/pascal-case-3.1.2.tgz", "integrity": "sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==", + "dev": true, "dependencies": { "no-case": "^3.0.4", "tslib": "^2.0.3" @@ -16937,6 +16840,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/path-case/-/path-case-3.0.4.tgz", "integrity": "sha512-qO4qCFjXqVTrcbPt/hQfhTQ+VhFsqNKOPtytgNKkKxSoEp3XPUQ8ObFuePylOIok5gjn69ry8XiULxCwot3Wfg==", + "dev": true, "dependencies": { "dot-case": "^3.0.4", "tslib": "^2.0.3" @@ -16972,7 +16876,8 @@ "node_modules/path-parse": { "version": "1.0.7", "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz", - "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==" + "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==", + "dev": true }, "node_modules/path-to-regexp": { "version": "0.1.7", @@ -17624,19 +17529,6 @@ "url": "https://github.com/sponsors/sindresorhus" } }, - "node_modules/quote-stream": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/quote-stream/-/quote-stream-1.0.2.tgz", - "integrity": "sha1-hJY/jJwmuULhU/7rU6rnRlK34LI=", - "dependencies": { - "buffer-equal": "0.0.1", - "minimist": "^1.1.3", - "through2": "^2.0.0" - }, - "bin": { - "quote-stream": "bin/cmd.js" - } - }, "node_modules/random-bytes": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/random-bytes/-/random-bytes-1.0.0.tgz", @@ -18088,14 +17980,6 @@ "node": ">=4" } }, - "node_modules/redis-mock": { - "version": "0.56.3", - "resolved": "https://registry.npmjs.org/redis-mock/-/redis-mock-0.56.3.tgz", - "integrity": "sha512-ynaJhqk0Qf3Qajnwvy4aOjS4Mdf9IBkELWtjd+NYhpiqu4QCNq6Vf3Q7c++XRPGiKiwRj9HWr0crcwy7EiPjYQ==", - "engines": { - "node": ">=6" - } - }, "node_modules/redis-parser": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/redis-parser/-/redis-parser-3.0.0.tgz", @@ -18478,11 +18362,6 @@ "url": "https://opencollective.com/unified" } }, - "node_modules/relative-date": { - "version": "1.1.3", - "resolved": "https://registry.npmjs.org/relative-date/-/relative-date-1.1.3.tgz", - "integrity": "sha1-EgkDBAWI7HpKOZxlR/0B0OPS3GM=" - }, "node_modules/remark-code-extra": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/remark-code-extra/-/remark-code-extra-1.0.1.tgz", @@ -19097,6 +18976,7 @@ "version": "1.20.0", "resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz", "integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==", + "dev": true, "dependencies": { "is-core-module": "^2.2.0", "path-parse": "^1.0.6" @@ -19520,6 +19400,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/sentence-case/-/sentence-case-3.0.4.tgz", "integrity": "sha512-8LS0JInaQMCRoQ7YUytAo/xUu5W2XnQxV2HI/6uM6U7CITS1RqPElr30V6uIqyMKM9lJGRVFy5/4CuzcixNYSg==", + "dev": true, "dependencies": { "no-case": "^3.0.4", "tslib": "^2.0.3", @@ -19635,11 +19516,6 @@ "node": ">=0.10.0" } }, - "node_modules/shallow-copy": { - "version": "0.0.1", - "resolved": "https://registry.npmjs.org/shallow-copy/-/shallow-copy-0.0.1.tgz", - "integrity": "sha1-QV9CcC1z2BAzApLMXuhurhoRoXA=" - }, "node_modules/shallowequal": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/shallowequal/-/shallowequal-1.1.0.tgz", @@ -19751,6 +19627,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/snake-case/-/snake-case-3.0.4.tgz", "integrity": "sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==", + "dev": true, "dependencies": { "dot-case": "^3.0.4", "tslib": "^2.0.3" @@ -20002,215 +19879,6 @@ "url": "https://github.com/sponsors/wooorm" } }, - "node_modules/static-eval": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/static-eval/-/static-eval-2.1.0.tgz", - "integrity": "sha512-agtxZ/kWSsCkI5E4QifRwsaPs0P0JmZV6dkLz6ILYfFYQGn+5plctanRN+IC8dJRiFkyXHrwEE3W9Wmx67uDbw==", - "dependencies": { - "escodegen": "^1.11.1" - } - }, - "node_modules/static-eval/node_modules/escodegen": { - "version": "1.14.3", - "resolved": "https://registry.npmjs.org/escodegen/-/escodegen-1.14.3.tgz", - "integrity": "sha512-qFcX0XJkdg+PB3xjZZG/wKSuT1PnQWx57+TVSjIMmILd2yC/6ByYElPwJnslDsuWuSAp4AwJGumarAAmJch5Kw==", - "dependencies": { - "esprima": "^4.0.1", - "estraverse": "^4.2.0", - "esutils": "^2.0.2", - "optionator": "^0.8.1" - }, - "bin": { - "escodegen": "bin/escodegen.js", - "esgenerate": "bin/esgenerate.js" - }, - "engines": { - "node": ">=4.0" - }, - "optionalDependencies": { - "source-map": "~0.6.1" - } - }, - "node_modules/static-eval/node_modules/levn": { - "version": "0.3.0", - "resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz", - "integrity": "sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=", - "dependencies": { - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-eval/node_modules/optionator": { - "version": "0.8.3", - "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz", - "integrity": "sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==", - "dependencies": { - "deep-is": "~0.1.3", - "fast-levenshtein": "~2.0.6", - "levn": "~0.3.0", - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2", - "word-wrap": "~1.2.3" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-eval/node_modules/prelude-ls": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz", - "integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=", - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-eval/node_modules/type-check": { - "version": "0.3.2", - "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz", - "integrity": "sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=", - "dependencies": { - "prelude-ls": "~1.1.2" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-module": { - "version": "2.2.5", - "resolved": "https://registry.npmjs.org/static-module/-/static-module-2.2.5.tgz", - "integrity": "sha512-D8vv82E/Kpmz3TXHKG8PPsCPg+RAX6cbCOyvjM6x04qZtQ47EtJFVwRsdov3n5d6/6ynrOY9XB4JkaZwB2xoRQ==", - "dependencies": { - "concat-stream": "~1.6.0", - "convert-source-map": "^1.5.1", - "duplexer2": "~0.1.4", - "escodegen": "~1.9.0", - "falafel": "^2.1.0", - "has": "^1.0.1", - "magic-string": "^0.22.4", - "merge-source-map": "1.0.4", - "object-inspect": "~1.4.0", - "quote-stream": "~1.0.2", - "readable-stream": "~2.3.3", - "shallow-copy": "~0.0.1", - "static-eval": "^2.0.0", - "through2": "~2.0.3" - } - }, - "node_modules/static-module/node_modules/escodegen": { - "version": "1.9.1", - "resolved": "https://registry.npmjs.org/escodegen/-/escodegen-1.9.1.tgz", - "integrity": "sha512-6hTjO1NAWkHnDk3OqQ4YrCuwwmGHL9S3nPlzBOUG/R44rda3wLNrfvQ5fkSGjyhHFKM7ALPKcKGrwvCLe0lC7Q==", - "dependencies": { - "esprima": "^3.1.3", - "estraverse": "^4.2.0", - "esutils": "^2.0.2", - "optionator": "^0.8.1" - }, - "bin": { - "escodegen": "bin/escodegen.js", - "esgenerate": "bin/esgenerate.js" - }, - "engines": { - "node": ">=4.0" - }, - "optionalDependencies": { - "source-map": "~0.6.1" - } - }, - "node_modules/static-module/node_modules/esprima": { - "version": "3.1.3", - "resolved": "https://registry.npmjs.org/esprima/-/esprima-3.1.3.tgz", - "integrity": "sha1-/cpRzuYTOJXjyI1TXOSdv/YqRjM=", - "bin": { - "esparse": "bin/esparse.js", - "esvalidate": "bin/esvalidate.js" - }, - "engines": { - "node": ">=4" - } - }, - "node_modules/static-module/node_modules/isarray": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" - }, - "node_modules/static-module/node_modules/levn": { - "version": "0.3.0", - "resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz", - "integrity": "sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=", - "dependencies": { - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-module/node_modules/object-inspect": { - "version": "1.4.1", - "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.4.1.tgz", - "integrity": "sha512-wqdhLpfCUbEsoEwl3FXwGyv8ief1k/1aUdIPCqVnupM6e8l63BEJdiF/0swtn04/8p05tG/T0FrpTlfwvljOdw==" - }, - "node_modules/static-module/node_modules/optionator": { - "version": "0.8.3", - "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz", - "integrity": "sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==", - "dependencies": { - "deep-is": "~0.1.3", - "fast-levenshtein": "~2.0.6", - "levn": "~0.3.0", - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2", - "word-wrap": "~1.2.3" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-module/node_modules/prelude-ls": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz", - "integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=", - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/static-module/node_modules/readable-stream": { - "version": "2.3.7", - "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", - "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", - "dependencies": { - "core-util-is": "~1.0.0", - "inherits": "~2.0.3", - "isarray": "~1.0.0", - "process-nextick-args": "~2.0.0", - "safe-buffer": "~5.1.1", - "string_decoder": "~1.1.1", - "util-deprecate": "~1.0.1" - } - }, - "node_modules/static-module/node_modules/string_decoder": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", - "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", - "dependencies": { - "safe-buffer": "~5.1.0" - } - }, - "node_modules/static-module/node_modules/type-check": { - "version": "0.3.2", - "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz", - "integrity": "sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=", - "dependencies": { - "prelude-ls": "~1.1.2" - }, - "engines": { - "node": ">= 0.8.0" - } - }, "node_modules/statuses": { "version": "1.5.0", "resolved": "https://registry.npmjs.org/statuses/-/statuses-1.5.0.tgz", @@ -20269,14 +19937,6 @@ "resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz", "integrity": "sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=" }, - "node_modules/strftime": { - "version": "0.10.0", - "resolved": "https://registry.npmjs.org/strftime/-/strftime-0.10.0.tgz", - "integrity": "sha1-s/D6QZKVICpaKJ9ta+n0kJphcZM=", - "engines": { - "node": ">=0.2.0" - } - }, "node_modules/string_decoder": { "version": "1.3.0", "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.3.0.tgz", @@ -21051,42 +20711,6 @@ "integrity": "sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=", "devOptional": true }, - "node_modules/through2": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz", - "integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==", - "dependencies": { - "readable-stream": "~2.3.6", - "xtend": "~4.0.1" - } - }, - "node_modules/through2/node_modules/isarray": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" - }, - "node_modules/through2/node_modules/readable-stream": { - "version": "2.3.7", - "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", - "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", - "dependencies": { - "core-util-is": "~1.0.0", - "inherits": "~2.0.3", - "isarray": "~1.0.0", - "process-nextick-args": "~2.0.0", - "safe-buffer": "~5.1.1", - "string_decoder": "~1.1.1", - "util-deprecate": "~1.0.1" - } - }, - "node_modules/through2/node_modules/string_decoder": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", - "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", - "dependencies": { - "safe-buffer": "~5.1.0" - } - }, "node_modules/timers-browserify": { "version": "2.0.12", "resolved": "https://registry.npmjs.org/timers-browserify/-/timers-browserify-2.0.12.tgz", @@ -21443,7 +21067,8 @@ "node_modules/typedarray": { "version": "0.0.6", "resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz", - "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=" + "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=", + "optional": true }, "node_modules/typedarray-to-buffer": { "version": "3.1.5", @@ -21809,6 +21434,7 @@ "version": "2.0.2", "resolved": "https://registry.npmjs.org/upper-case/-/upper-case-2.0.2.tgz", "integrity": "sha512-KgdgDGJt2TpuwBUIjgG6lzw2GWFRCW9Qkfkiv0DxqHHLYJHmtmdUIKcZd8rHgFSjopVTlw6ggzCm1b8MFQwikg==", + "dev": true, "dependencies": { "tslib": "^2.0.3" } @@ -21817,6 +21443,7 @@ "version": "2.0.2", "resolved": "https://registry.npmjs.org/upper-case-first/-/upper-case-first-2.0.2.tgz", "integrity": "sha512-514ppYHBaKwfJRK/pNC6c/OxfGa0obSnAl106u97Ed0I625Nin96KAjttZF6ZL3e1XLtphxnqrOi9iWgm+u+bg==", + "dev": true, "dependencies": { "tslib": "^2.0.3" } @@ -22083,11 +21710,6 @@ "url": "https://opencollective.com/unified" } }, - "node_modules/vlq": { - "version": "0.2.3", - "resolved": "https://registry.npmjs.org/vlq/-/vlq-0.2.3.tgz", - "integrity": "sha512-DRibZL6DsNhIgYQ+wNdWDL2SL3bKPlVrRiBqV5yuMm++op8W4kGFtaQfCs4KEJn0wBZcHVHJ3eoywX8983k1ow==" - }, "node_modules/vm-browserify": { "version": "1.1.2", "resolved": "https://registry.npmjs.org/vm-browserify/-/vm-browserify-1.1.2.tgz", @@ -22677,6 +22299,7 @@ "version": "1.2.3", "resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz", "integrity": "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==", + "dev": true, "engines": { "node": ">=0.10.0" } @@ -22954,7 +22577,8 @@ "@alex_neo/jest-expect-message": { "version": "1.0.5", "resolved": "https://registry.npmjs.org/@alex_neo/jest-expect-message/-/jest-expect-message-1.0.5.tgz", - "integrity": "sha512-1eBykZCd0pPGl5qKtV6Z5ARA6yuhXzHsVN2h5GH5/H6svYa37Jr7vMio5OFpiw1LBHtscrZs7amSkZkcwm0cvQ==" + "integrity": "sha512-1eBykZCd0pPGl5qKtV6Z5ARA6yuhXzHsVN2h5GH5/H6svYa37Jr7vMio5OFpiw1LBHtscrZs7amSkZkcwm0cvQ==", + "dev": true }, "@babel/code-frame": { "version": "7.16.0", @@ -26310,7 +25934,8 @@ "acorn": { "version": "7.4.1", "resolved": "https://registry.npmjs.org/acorn/-/acorn-7.4.1.tgz", - "integrity": "sha512-nQyp0o1/mNdbTO1PO6kHkwSrmgZ0MT/jCCpNiwbUjGoRN4dlBhqJtoQuCnEOKzgTVwg0ZWiCoQy6SxMebQVh8A==" + "integrity": "sha512-nQyp0o1/mNdbTO1PO6kHkwSrmgZ0MT/jCCpNiwbUjGoRN4dlBhqJtoQuCnEOKzgTVwg0ZWiCoQy6SxMebQVh8A==", + "dev": true }, "acorn-globals": { "version": "6.0.0", @@ -27670,7 +27295,8 @@ "bottleneck": { "version": "2.19.5", "resolved": "https://registry.npmjs.org/bottleneck/-/bottleneck-2.19.5.tgz", - "integrity": "sha512-VHiNCbI1lKdl44tGrhNfU3lup0Tj/ZBMJB5/2ZbNXRCPuRCO7ed2mgcK4r17y+KB2EfuYuRaVlwNbAeaWGSpbw==" + "integrity": "sha512-VHiNCbI1lKdl44tGrhNfU3lup0Tj/ZBMJB5/2ZbNXRCPuRCO7ed2mgcK4r17y+KB2EfuYuRaVlwNbAeaWGSpbw==", + "dev": true }, "boxen": { "version": "5.1.2", @@ -27719,34 +27345,11 @@ "fill-range": "^7.0.1" } }, - "brfs": { - "version": "1.6.1", - "resolved": "https://registry.npmjs.org/brfs/-/brfs-1.6.1.tgz", - "integrity": "sha512-OfZpABRQQf+Xsmju8XE9bDjs+uU4vLREGolP7bDgcpsI17QREyZ4Bl+2KLxxx1kCgA0fAIhKQBaBYh+PEcCqYQ==", - "requires": { - "quote-stream": "^1.0.1", - "resolve": "^1.1.5", - "static-module": "^2.2.0", - "through2": "^2.0.0" - } - }, "brorand": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/brorand/-/brorand-1.1.0.tgz", "integrity": "sha1-EsJe/kCkXjwyPrhnWgoM5XsiNx8=" }, - "browser-date-formatter": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/browser-date-formatter/-/browser-date-formatter-3.0.3.tgz", - "integrity": "sha512-crNsaki/mQRce8SgvRIwpI+lXttxu4HZazMzloziiA57p6LX2d4FPxOg2JTqrW5KIzBQbcSHqfFa485liPvaAw==", - "requires": { - "brfs": "^1.4.3", - "dateutil": "^0.1.0", - "domready": "^1.0.8", - "relative-date": "^1.1.3", - "strftime": "^0.10.0" - } - }, "browser-process-hrtime": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/browser-process-hrtime/-/browser-process-hrtime-1.0.0.tgz", @@ -27867,12 +27470,14 @@ "buffer-equal": { "version": "0.0.1", "resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-0.0.1.tgz", - "integrity": "sha1-kbx0sR6kBbyRa8aqkI+q+ltKrEs=" + "integrity": "sha1-kbx0sR6kBbyRa8aqkI+q+ltKrEs=", + "optional": true }, "buffer-from": { "version": "1.1.2", "resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz", - "integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==" + "integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==", + "devOptional": true }, "buffer-xor": { "version": "1.0.3", @@ -27927,6 +27532,7 @@ "version": "4.1.2", "resolved": "https://registry.npmjs.org/camel-case/-/camel-case-4.1.2.tgz", "integrity": "sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==", + "dev": true, "requires": { "pascal-case": "^3.1.2", "tslib": "^2.0.3" @@ -27971,6 +27577,7 @@ "version": "1.0.4", "resolved": "https://registry.npmjs.org/capital-case/-/capital-case-1.0.4.tgz", "integrity": "sha512-ds37W8CytHgwnhGGTi88pcPyR15qoNkOpYwmMMfnWqqWgESapLqvDx6huFjQ5vqWSn2Z06173XNA7LtMOeUh1A==", + "dev": true, "requires": { "no-case": "^3.0.4", "tslib": "^2.0.3", @@ -28013,6 +27620,7 @@ "version": "4.1.2", "resolved": "https://registry.npmjs.org/change-case/-/change-case-4.1.2.tgz", "integrity": "sha512-bSxY2ws9OtviILG1EiY5K7NNxkqg/JnRnFxLtKQ96JaviiIxi7djMrSd0ECT9AC+lttClmYwKw53BWpOMblo7A==", + "dev": true, "requires": { "camel-case": "^4.1.2", "capital-case": "^1.0.4", @@ -28368,6 +27976,7 @@ "version": "1.6.2", "resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.6.2.tgz", "integrity": "sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==", + "optional": true, "requires": { "buffer-from": "^1.0.0", "inherits": "^2.0.3", @@ -28378,12 +27987,14 @@ "isarray": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" + "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=", + "optional": true }, "readable-stream": { "version": "2.3.7", "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", + "optional": true, "requires": { "core-util-is": "~1.0.0", "inherits": "~2.0.3", @@ -28398,6 +28009,7 @@ "version": "1.1.1", "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", + "optional": true, "requires": { "safe-buffer": "~5.1.0" } @@ -28450,6 +28062,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/constant-case/-/constant-case-3.0.4.tgz", "integrity": "sha512-I2hSBi7Vvs7BEuJDr5dDHfzb/Ruj3FyvFyh7KLilAjNQw3Be+xgqUBA2W6scVEcL0hL1dwPRtIqEPVUCKkSsyQ==", + "dev": true, "requires": { "no-case": "^3.0.4", "tslib": "^2.0.3", @@ -28823,11 +28436,6 @@ "whatwg-url": "^8.0.0" } }, - "dateutil": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/dateutil/-/dateutil-0.1.0.tgz", - "integrity": "sha1-9MAkKeA/knwcnh4hu+KzeDNHfrA=" - }, "dayjs": { "version": "1.10.7", "resolved": "https://registry.npmjs.org/dayjs/-/dayjs-1.10.7.tgz", @@ -29090,11 +28698,6 @@ "domelementtype": "^2.2.0" } }, - "domready": { - "version": "1.0.8", - "resolved": "https://registry.npmjs.org/domready/-/domready-1.0.8.tgz", - "integrity": "sha1-kfJS5Ze2Wvd+dFriTdAYXV4m1Yw=" - }, "domutils": { "version": "2.8.0", "resolved": "https://registry.npmjs.org/domutils/-/domutils-2.8.0.tgz", @@ -29182,6 +28785,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/dot-case/-/dot-case-3.0.4.tgz", "integrity": "sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==", + "dev": true, "requires": { "no-case": "^3.0.4", "tslib": "^2.0.3" @@ -29215,43 +28819,6 @@ "integrity": "sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==", "dev": true }, - "duplexer2": { - "version": "0.1.4", - "resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.1.4.tgz", - "integrity": "sha1-ixLauHjA1p4+eJEFFmKjL8a93ME=", - "requires": { - "readable-stream": "^2.0.2" - }, - "dependencies": { - "isarray": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" - }, - "readable-stream": { - "version": "2.3.7", - "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", - "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", - "requires": { - "core-util-is": "~1.0.0", - "inherits": "~2.0.3", - "isarray": "~1.0.0", - "process-nextick-args": "~2.0.0", - "safe-buffer": "~5.1.1", - "string_decoder": "~1.1.1", - "util-deprecate": "~1.0.1" - } - }, - "string_decoder": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", - "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", - "requires": { - "safe-buffer": "~5.1.0" - } - } - } - }, "duplexer3": { "version": "0.1.4", "resolved": "https://registry.npmjs.org/duplexer3/-/duplexer3-0.1.4.tgz", @@ -29929,12 +29496,14 @@ "estraverse": { "version": "4.3.0", "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz", - "integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==" + "integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==", + "devOptional": true }, "esutils": { "version": "2.0.3", "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz", - "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==" + "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==", + "dev": true }, "etag": { "version": "1.8.1", @@ -30120,14 +29689,6 @@ } } }, - "express-basic-auth": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/express-basic-auth/-/express-basic-auth-1.2.0.tgz", - "integrity": "sha512-iJ0h1Gk6fZRrFmO7tP9nIbxwNgCUJASfNj5fb0Hy15lGtbqqsxpt7609+wq+0XlByZjXmC/rslWQtnuSTVRIcg==", - "requires": { - "basic-auth": "^2.0.1" - } - }, "express-rate-limit": { "version": "5.5.1", "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-5.5.1.tgz", @@ -30169,17 +29730,6 @@ "integrity": "sha1-lpGEQOMEGnpBT4xS48V06zw+HgU=", "dev": true }, - "falafel": { - "version": "2.2.4", - "resolved": "https://registry.npmjs.org/falafel/-/falafel-2.2.4.tgz", - "integrity": "sha512-0HXjo8XASWRmsS0X1EkhwEMZaD3Qvp7FfURwjLKjG1ghfRm/MGZl2r4cWUTv41KdNghTw4OUMmVtdGQp3+H+uQ==", - "requires": { - "acorn": "^7.1.1", - "foreach": "^2.0.5", - "isarray": "^2.0.1", - "object-keys": "^1.0.6" - } - }, "fast-deep-equal": { "version": "3.1.3", "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", @@ -30207,7 +29757,8 @@ "fast-levenshtein": { "version": "2.0.6", "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz", - "integrity": "sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=" + "integrity": "sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=", + "dev": true }, "fast-safe-stringify": { "version": "2.1.1", @@ -31257,6 +30808,7 @@ "version": "2.0.4", "resolved": "https://registry.npmjs.org/header-case/-/header-case-2.0.4.tgz", "integrity": "sha512-H/vuk5TEEVZwrR0lp2zed9OCo1uAILMlx0JEMgC26rzyJJ3N1v6XkwHHXJQdR2doSjcGPM6OKPYoJgf0plJ11Q==", + "dev": true, "requires": { "capital-case": "^1.0.4", "tslib": "^2.0.3" @@ -31766,6 +31318,7 @@ "version": "2.8.0", "resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.8.0.tgz", "integrity": "sha512-vd15qHsaqrRL7dtH6QNuy0ndJmRDrS9HAM1CAiSifNUFv4x1a0CCVsj18hJ1mShxIG6T2i1sO78MkP56r0nYRw==", + "dev": true, "requires": { "has": "^1.0.3" } @@ -32016,11 +31569,6 @@ "is-url": "^1.2.4" } }, - "isarray": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-2.0.5.tgz", - "integrity": "sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==" - }, "isexe": { "version": "2.0.0", "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", @@ -33346,6 +32894,7 @@ "version": "2.0.2", "resolved": "https://registry.npmjs.org/lower-case/-/lower-case-2.0.2.tgz", "integrity": "sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==", + "dev": true, "requires": { "tslib": "^2.0.3" } @@ -33389,14 +32938,6 @@ "resolved": "https://registry.npmjs.org/lunr-languages/-/lunr-languages-1.9.0.tgz", "integrity": "sha512-Be5vFuc8NAheOIjviCRms3ZqFFBlzns3u9DXpPSZvALetgnydAN0poV71pVLFn0keYy/s4VblMMkqewTLe+KPg==" }, - "magic-string": { - "version": "0.22.5", - "resolved": "https://registry.npmjs.org/magic-string/-/magic-string-0.22.5.tgz", - "integrity": "sha512-oreip9rJZkzvA8Qzk9HFs8fZGF/u7H/gtrE8EN6RjKJ9kh2HlC+yQ2QezifqTZfGyiuAV0dRv5a+y/8gBb1m9w==", - "requires": { - "vlq": "^0.2.2" - } - }, "make-dir": { "version": "3.1.0", "resolved": "https://registry.npmjs.org/make-dir/-/make-dir-3.1.0.tgz", @@ -33700,14 +33241,6 @@ "resolved": "https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.1.tgz", "integrity": "sha1-sAqqVW3YtEVoFQ7J0blT8/kMu2E=" }, - "merge-source-map": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/merge-source-map/-/merge-source-map-1.0.4.tgz", - "integrity": "sha1-pd5GU42uhNQRTMXqArR3KmNGcB8=", - "requires": { - "source-map": "^0.5.6" - } - }, "merge-stream": { "version": "2.0.0", "resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz", @@ -34650,6 +34183,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/no-case/-/no-case-3.0.4.tgz", "integrity": "sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==", + "dev": true, "requires": { "lower-case": "^2.0.2", "tslib": "^2.0.3" @@ -35871,6 +35405,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/param-case/-/param-case-3.0.4.tgz", "integrity": "sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==", + "dev": true, "requires": { "dot-case": "^3.0.4", "tslib": "^2.0.3" @@ -35978,6 +35513,7 @@ "version": "3.1.2", "resolved": "https://registry.npmjs.org/pascal-case/-/pascal-case-3.1.2.tgz", "integrity": "sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==", + "dev": true, "requires": { "no-case": "^3.0.4", "tslib": "^2.0.3" @@ -35992,6 +35528,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/path-case/-/path-case-3.0.4.tgz", "integrity": "sha512-qO4qCFjXqVTrcbPt/hQfhTQ+VhFsqNKOPtytgNKkKxSoEp3XPUQ8ObFuePylOIok5gjn69ry8XiULxCwot3Wfg==", + "dev": true, "requires": { "dot-case": "^3.0.4", "tslib": "^2.0.3" @@ -36018,7 +35555,8 @@ "path-parse": { "version": "1.0.7", "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz", - "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==" + "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==", + "dev": true }, "path-to-regexp": { "version": "0.1.7", @@ -36517,16 +36055,6 @@ "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz", "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==" }, - "quote-stream": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/quote-stream/-/quote-stream-1.0.2.tgz", - "integrity": "sha1-hJY/jJwmuULhU/7rU6rnRlK34LI=", - "requires": { - "buffer-equal": "0.0.1", - "minimist": "^1.1.3", - "through2": "^2.0.0" - } - }, "random-bytes": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/random-bytes/-/random-bytes-1.0.0.tgz", @@ -36880,11 +36408,6 @@ "resolved": "https://registry.npmjs.org/redis-errors/-/redis-errors-1.2.0.tgz", "integrity": "sha1-62LSrbFeTq9GEMBK/hUpOEJQq60=" }, - "redis-mock": { - "version": "0.56.3", - "resolved": "https://registry.npmjs.org/redis-mock/-/redis-mock-0.56.3.tgz", - "integrity": "sha512-ynaJhqk0Qf3Qajnwvy4aOjS4Mdf9IBkELWtjd+NYhpiqu4QCNq6Vf3Q7c++XRPGiKiwRj9HWr0crcwy7EiPjYQ==" - }, "redis-parser": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/redis-parser/-/redis-parser-3.0.0.tgz", @@ -37162,11 +36685,6 @@ "unified": "^10.0.0" } }, - "relative-date": { - "version": "1.1.3", - "resolved": "https://registry.npmjs.org/relative-date/-/relative-date-1.1.3.tgz", - "integrity": "sha1-EgkDBAWI7HpKOZxlR/0B0OPS3GM=" - }, "remark-code-extra": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/remark-code-extra/-/remark-code-extra-1.0.1.tgz", @@ -37647,6 +37165,7 @@ "version": "1.20.0", "resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz", "integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==", + "dev": true, "requires": { "is-core-module": "^2.2.0", "path-parse": "^1.0.6" @@ -37982,6 +37501,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/sentence-case/-/sentence-case-3.0.4.tgz", "integrity": "sha512-8LS0JInaQMCRoQ7YUytAo/xUu5W2XnQxV2HI/6uM6U7CITS1RqPElr30V6uIqyMKM9lJGRVFy5/4CuzcixNYSg==", + "dev": true, "requires": { "no-case": "^3.0.4", "tslib": "^2.0.3", @@ -38081,11 +37601,6 @@ } } }, - "shallow-copy": { - "version": "0.0.1", - "resolved": "https://registry.npmjs.org/shallow-copy/-/shallow-copy-0.0.1.tgz", - "integrity": "sha1-QV9CcC1z2BAzApLMXuhurhoRoXA=" - }, "shallowequal": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/shallowequal/-/shallowequal-1.1.0.tgz", @@ -38170,6 +37685,7 @@ "version": "3.0.4", "resolved": "https://registry.npmjs.org/snake-case/-/snake-case-3.0.4.tgz", "integrity": "sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==", + "dev": true, "requires": { "dot-case": "^3.0.4", "tslib": "^2.0.3" @@ -38372,170 +37888,6 @@ "resolved": "https://registry.npmjs.org/state-toggle/-/state-toggle-1.0.3.tgz", "integrity": "sha512-d/5Z4/2iiCnHw6Xzghyhb+GcmF89bxwgXG60wjIiZaxnymbyOmI8Hk4VqHXiVVp6u2ysaskFfXg3ekCj4WNftQ==" }, - "static-eval": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/static-eval/-/static-eval-2.1.0.tgz", - "integrity": "sha512-agtxZ/kWSsCkI5E4QifRwsaPs0P0JmZV6dkLz6ILYfFYQGn+5plctanRN+IC8dJRiFkyXHrwEE3W9Wmx67uDbw==", - "requires": { - "escodegen": "^1.11.1" - }, - "dependencies": { - "escodegen": { - "version": "1.14.3", - "resolved": "https://registry.npmjs.org/escodegen/-/escodegen-1.14.3.tgz", - "integrity": "sha512-qFcX0XJkdg+PB3xjZZG/wKSuT1PnQWx57+TVSjIMmILd2yC/6ByYElPwJnslDsuWuSAp4AwJGumarAAmJch5Kw==", - "requires": { - "esprima": "^4.0.1", - "estraverse": "^4.2.0", - "esutils": "^2.0.2", - "optionator": "^0.8.1", - "source-map": "~0.6.1" - } - }, - "levn": { - "version": "0.3.0", - "resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz", - "integrity": "sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=", - "requires": { - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2" - } - }, - "optionator": { - "version": "0.8.3", - "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz", - "integrity": "sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==", - "requires": { - "deep-is": "~0.1.3", - "fast-levenshtein": "~2.0.6", - "levn": "~0.3.0", - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2", - "word-wrap": "~1.2.3" - } - }, - "prelude-ls": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz", - "integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=" - }, - "type-check": { - "version": "0.3.2", - "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz", - "integrity": "sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=", - "requires": { - "prelude-ls": "~1.1.2" - } - } - } - }, - "static-module": { - "version": "2.2.5", - "resolved": "https://registry.npmjs.org/static-module/-/static-module-2.2.5.tgz", - "integrity": "sha512-D8vv82E/Kpmz3TXHKG8PPsCPg+RAX6cbCOyvjM6x04qZtQ47EtJFVwRsdov3n5d6/6ynrOY9XB4JkaZwB2xoRQ==", - "requires": { - "concat-stream": "~1.6.0", - "convert-source-map": "^1.5.1", - "duplexer2": "~0.1.4", - "escodegen": "~1.9.0", - "falafel": "^2.1.0", - "has": "^1.0.1", - "magic-string": "^0.22.4", - "merge-source-map": "1.0.4", - "object-inspect": "~1.4.0", - "quote-stream": "~1.0.2", - "readable-stream": "~2.3.3", - "shallow-copy": "~0.0.1", - "static-eval": "^2.0.0", - "through2": "~2.0.3" - }, - "dependencies": { - "escodegen": { - "version": "1.9.1", - "resolved": "https://registry.npmjs.org/escodegen/-/escodegen-1.9.1.tgz", - "integrity": "sha512-6hTjO1NAWkHnDk3OqQ4YrCuwwmGHL9S3nPlzBOUG/R44rda3wLNrfvQ5fkSGjyhHFKM7ALPKcKGrwvCLe0lC7Q==", - "requires": { - "esprima": "^3.1.3", - "estraverse": "^4.2.0", - "esutils": "^2.0.2", - "optionator": "^0.8.1", - "source-map": "~0.6.1" - } - }, - "esprima": { - "version": "3.1.3", - "resolved": "https://registry.npmjs.org/esprima/-/esprima-3.1.3.tgz", - "integrity": "sha1-/cpRzuYTOJXjyI1TXOSdv/YqRjM=" - }, - "isarray": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" - }, - "levn": { - "version": "0.3.0", - "resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz", - "integrity": "sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=", - "requires": { - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2" - } - }, - "object-inspect": { - "version": "1.4.1", - "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.4.1.tgz", - "integrity": "sha512-wqdhLpfCUbEsoEwl3FXwGyv8ief1k/1aUdIPCqVnupM6e8l63BEJdiF/0swtn04/8p05tG/T0FrpTlfwvljOdw==" - }, - "optionator": { - "version": "0.8.3", - "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz", - "integrity": "sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==", - "requires": { - "deep-is": "~0.1.3", - "fast-levenshtein": "~2.0.6", - "levn": "~0.3.0", - "prelude-ls": "~1.1.2", - "type-check": "~0.3.2", - "word-wrap": "~1.2.3" - } - }, - "prelude-ls": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz", - "integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=" - }, - "readable-stream": { - "version": "2.3.7", - "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", - "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", - "requires": { - "core-util-is": "~1.0.0", - "inherits": "~2.0.3", - "isarray": "~1.0.0", - "process-nextick-args": "~2.0.0", - "safe-buffer": "~5.1.1", - "string_decoder": "~1.1.1", - "util-deprecate": "~1.0.1" - } - }, - "string_decoder": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", - "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", - "requires": { - "safe-buffer": "~5.1.0" - } - }, - "type-check": { - "version": "0.3.2", - "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz", - "integrity": "sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=", - "requires": { - "prelude-ls": "~1.1.2" - } - } - } - }, "statuses": { "version": "1.5.0", "resolved": "https://registry.npmjs.org/statuses/-/statuses-1.5.0.tgz", @@ -38593,11 +37945,6 @@ } } }, - "strftime": { - "version": "0.10.0", - "resolved": "https://registry.npmjs.org/strftime/-/strftime-0.10.0.tgz", - "integrity": "sha1-s/D6QZKVICpaKJ9ta+n0kJphcZM=" - }, "string_decoder": { "version": "1.3.0", "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.3.0.tgz", @@ -39177,44 +38524,6 @@ "integrity": "sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=", "devOptional": true }, - "through2": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz", - "integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==", - "requires": { - "readable-stream": "~2.3.6", - "xtend": "~4.0.1" - }, - "dependencies": { - "isarray": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", - "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=" - }, - "readable-stream": { - "version": "2.3.7", - "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz", - "integrity": "sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==", - "requires": { - "core-util-is": "~1.0.0", - "inherits": "~2.0.3", - "isarray": "~1.0.0", - "process-nextick-args": "~2.0.0", - "safe-buffer": "~5.1.1", - "string_decoder": "~1.1.1", - "util-deprecate": "~1.0.1" - } - }, - "string_decoder": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", - "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", - "requires": { - "safe-buffer": "~5.1.0" - } - } - } - }, "timers-browserify": { "version": "2.0.12", "resolved": "https://registry.npmjs.org/timers-browserify/-/timers-browserify-2.0.12.tgz", @@ -39482,7 +38791,8 @@ "typedarray": { "version": "0.0.6", "resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz", - "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=" + "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=", + "optional": true }, "typedarray-to-buffer": { "version": "3.1.5", @@ -39748,6 +39058,7 @@ "version": "2.0.2", "resolved": "https://registry.npmjs.org/upper-case/-/upper-case-2.0.2.tgz", "integrity": "sha512-KgdgDGJt2TpuwBUIjgG6lzw2GWFRCW9Qkfkiv0DxqHHLYJHmtmdUIKcZd8rHgFSjopVTlw6ggzCm1b8MFQwikg==", + "dev": true, "requires": { "tslib": "^2.0.3" } @@ -39756,6 +39067,7 @@ "version": "2.0.2", "resolved": "https://registry.npmjs.org/upper-case-first/-/upper-case-first-2.0.2.tgz", "integrity": "sha512-514ppYHBaKwfJRK/pNC6c/OxfGa0obSnAl106u97Ed0I625Nin96KAjttZF6ZL3e1XLtphxnqrOi9iWgm+u+bg==", + "dev": true, "requires": { "tslib": "^2.0.3" } @@ -39975,11 +39287,6 @@ "unist-util-stringify-position": "^3.0.0" } }, - "vlq": { - "version": "0.2.3", - "resolved": "https://registry.npmjs.org/vlq/-/vlq-0.2.3.tgz", - "integrity": "sha512-DRibZL6DsNhIgYQ+wNdWDL2SL3bKPlVrRiBqV5yuMm++op8W4kGFtaQfCs4KEJn0wBZcHVHJ3eoywX8983k1ow==" - }, "vm-browserify": { "version": "1.1.2", "resolved": "https://registry.npmjs.org/vm-browserify/-/vm-browserify-1.1.2.tgz", @@ -40456,7 +39763,8 @@ "word-wrap": { "version": "1.2.3", "resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz", - "integrity": "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==" + "integrity": "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==", + "dev": true }, "wordwrap": { "version": "1.0.0", diff --git a/package.json b/package.json index fd731077da..ef7fbfd6cd 100644 --- a/package.json +++ b/package.json @@ -9,19 +9,16 @@ ".next/cache" ], "dependencies": { - "@alex_neo/jest-expect-message": "^1.0.5", "@github/failbot": "0.7.0", "@hapi/accept": "^5.0.2", "@primer/components": "^31.1.0", "@primer/css": "^18.2.0", "@primer/octicons": "^16.1.1", "@primer/octicons-react": "^16.1.1", + "@react-aria/ssr": "^3.1.0", "accept-language-parser": "^1.5.0", "ajv": "^8.7.1", "ajv-formats": "^2.1.1", - "bottleneck": "^2.19.5", - "browser-date-formatter": "^3.0.3", - "change-case": "^4.1.2", "cheerio": "^1.0.0-rc.10", "classnames": "^2.3.1", "compression": "^1.7.4", @@ -33,7 +30,6 @@ "dayjs": "^1.10.7", "dotenv": "^10.0.0", "express": "^4.17.1", - "express-basic-auth": "^1.2.0", "express-rate-limit": "^5.5.1", "express-timeout-handler": "^2.2.2", "flat": "^5.0.2", @@ -68,11 +64,9 @@ "rate-limit-redis": "^2.1.0", "react": "^17.0.2", "react-dom": "^17.0.2", - "react-is": "^17.0.2", "react-markdown": "^7.1.0", "react-syntax-highlighter": "^15.4.4", "redis": "^3.1.2", - "redis-mock": "^0.56.3", "rehype-autolink-headings": "^6.1.0", "rehype-highlight": "^5.0.0", "rehype-raw": "^6.1.0", @@ -102,6 +96,7 @@ "devDependencies": { "@actions/core": "^1.6.0", "@actions/github": "^5.0.0", + "@alex_neo/jest-expect-message": "^1.0.5", "@babel/core": "^7.16.0", "@babel/eslint-parser": "^7.16.3", "@babel/plugin-syntax-top-level-await": "^7.14.5", @@ -126,7 +121,9 @@ "babel-loader": "^8.2.3", "babel-plugin-styled-components": "^1.13.3", "babel-preset-env": "^1.7.0", + "bottleneck": "^2.19.5", "chalk": "^4.1.2", + "change-case": "^4.1.2", "commander": "^8.3.0", "count-array-values": "^1.2.1", "cross-env": "^7.0.3", @@ -207,7 +204,7 @@ "link-check-server": "cross-env NODE_ENV=production ENABLED_LANGUAGES='en' PORT=4002 node server.mjs", "link-check-test": "cross-env node script/check-internal-links.js", "lint": "eslint '**/*.{js,mjs,ts,tsx}'", - "lint-translation": "cross-env TEST_TRANSLATION=true jest content/lint-files", + "lint-translation": "cross-env NODE_OPTIONS=--experimental-vm-modules TEST_TRANSLATION=true jest tests/linting/lint-files.js", "pa11y-ci": "pa11y-ci", "pa11y-test": "start-server-and-test browser-test-server 4001 pa11y-ci", "prebrowser-test": "npm run build", diff --git a/pages/_app.tsx b/pages/_app.tsx index 5e39547183..7f8f522d97 100644 --- a/pages/_app.tsx +++ b/pages/_app.tsx @@ -3,6 +3,7 @@ import App from 'next/app' import type { AppProps, AppContext } from 'next/app' import Head from 'next/head' import { useTheme, ThemeProvider } from '@primer/components' +import { SSRProvider } from '@react-aria/ssr' import { defaultComponentThemeProps, getThemeProps } from 'components/lib/getThemeProps' import '../stylesheets/index.scss' @@ -43,12 +44,14 @@ const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext } - - - - - - + + + + + + + + ) } diff --git a/script/i18n/lint-translation-files.js b/script/i18n/lint-translation-files.js index 7622ad2f5a..2c3cc63aa8 100755 --- a/script/i18n/lint-translation-files.js +++ b/script/i18n/lint-translation-files.js @@ -9,10 +9,11 @@ import { execSync } from 'child_process' import program from 'commander' +import fs from 'fs' // Set up supported linting check types and their corresponding commands. const CHECK_COMMANDS = { - parsing: 'TEST_TRANSLATION=true npx jest linting/lint-files', + parsing: 'npm run lint-translation', rendering: 'script/i18n/test-render-translation.js', } const SUPPORTED_CHECK_TYPES = Object.keys(CHECK_COMMANDS) @@ -48,7 +49,7 @@ if (SUPPORTED_CHECK_TYPES.includes(specifiedCheckType)) { function lintAndResetFiles(checkType) { console.log(`Running ${checkType} check...`) - const log = `~/docs-translation-${checkType}-error.txt` + const log = `${process.env.HOME}/docs-translation-${checkType}-error.txt` const cmd = `${CHECK_COMMANDS[checkType]} > ${log}` // Lint the files based on the check type and output the errors to a log file. @@ -58,10 +59,28 @@ function lintAndResetFiles(checkType) { console.log(`There were new ${checkType} errors! Check ${log} for more details.`) } - // Reset the files - execSync( - `cat ${log} | egrep "^translations/.*/(.+.md|.+.yml)$" | uniq | xargs -L1 script/i18n/reset-translated-file.js --prefer-main` - ) + // return if file does not exist + if (!fs.existsSync(log)) { + console.log(`${log}: no such file`) + return + } + + const filesToReset = fs + .readFileSync(log) + .toString() + .split('\n') + .filter((p) => p.startsWith('translations') && (p.endsWith('.md') || p.endsWith('.yml'))) + + if (filesToReset.length === 0) { + console.log('There are no violations') + return + } + + // We are not passing --prefer-main because we want to remove the file so we + // reset it directly to the English source + filesToReset.forEach((file) => { + execSync(`script/i18n/reset-translated-file.js ${file}`) + }) // Print a message with next steps console.log(`Success! diff --git a/script/rest/utils/create-code-samples.js b/script/rest/utils/create-code-samples.js index ec9639d485..dd912ebd03 100644 --- a/script/rest/utils/create-code-samples.js +++ b/script/rest/utils/create-code-samples.js @@ -174,6 +174,6 @@ function getExampleParamValue(name, schema) { case 'array': return [getExampleParamValue(name, schema.items)] } - + throw new Error(`Unknown data type in schema:, ${JSON.stringify(schema, null, 2)}`) } diff --git a/script/search/search-qa-test.js b/script/search/search-qa-test.js index 15476812d7..70b82bf65a 100755 --- a/script/search/search-qa-test.js +++ b/script/search/search-qa-test.js @@ -6,8 +6,8 @@ // This test runs example queries and expects a specific page to land in the top // 3 results. // -// The data source used by this script is a JSON file `script/search/search-qa-data.json`, -// which is populated from spreadsheet data here: +// The data source used by this script is a JSON file `script/search/search-qa-data.json`, +// which is populated from spreadsheet data here: // https://docs.google.com/spreadsheets/d/1Dt5JRVcmyAGWKBwGjwmXxi7Ww_vdfYLfZ-EFpu2S2CQ/edit?usp=sharing // // [end-readme] diff --git a/stylesheets/extended-markdown.scss b/stylesheets/extended-markdown.scss index 7fa97ec002..81cdd4c159 100644 --- a/stylesheets/extended-markdown.scss +++ b/stylesheets/extended-markdown.scss @@ -15,7 +15,7 @@ } p:not(:first-child) { - margin-top: 15px; + margin-top: 1rem; } &.note pre code { @@ -24,7 +24,7 @@ &.note pre { background: none; - padding: 10px 10px 10px 0; + padding: 0.5rem 0.5rem 0.5rem 0; margin-bottom: 0; } } diff --git a/stylesheets/images.scss b/stylesheets/images.scss index 034c3cb59a..adfc988969 100644 --- a/stylesheets/images.scss +++ b/stylesheets/images.scss @@ -1,28 +1,28 @@ .markdown-body .procedural-image-wrapper { display: block; - padding: 10px 0; - margin: 20px auto 0 auto; + padding: 1rem 0; + margin: 1rem auto 0 auto; border: none; - max-width: calc(100% - 32px); -} + max-width: calc(100% - 2rem); -.markdown-body .procedural-image-wrapper img { - border-radius: 5px; - border: 2px solid var(--color-border-subtle); - width: auto; - height: auto; - max-height: 500px; - padding: 0; -} + img { + width: auto; + height: auto; + max-height: 32rem; + padding: 0; + box-shadow: var(--color-shadow-medium); + } -// make sure images that contain emoji render at the expected size -.markdown-body img[src*="https://github.githubassets.com/images/icons/emoji"] -{ - height: 20px; - width: 20px; + // make sure images that contain emoji render at the expected size + img[src*="https://github.githubassets.com/images/icons/emoji"] + { + height: 20px; + width: 20px; + box-shadow: none; + } } .markdown-body img { - max-height: 500px; + max-height: 32rem; padding: 0; } diff --git a/stylesheets/syntax-highlighting.scss b/stylesheets/syntax-highlighting.scss index e0b86feb7a..af482d83dc 100644 --- a/stylesheets/syntax-highlighting.scss +++ b/stylesheets/syntax-highlighting.scss @@ -15,80 +15,73 @@ from https://unpkg.com/highlight.js@9.15.8/styles/github.css .hljs-comment, .hljs-quote { - color: var(--color-fg-muted); - font-style: italic; + color: var(--color-prettylights-syntax-comment); } .hljs-keyword, -.hljs-selector-tag, -.hljs-subst { - color: var(--color-fg-default); - font-weight: bold; -} - -.hljs-number, -.hljs-literal, -.hljs-variable, -.hljs-template-variable, -.hljs-tag .hljs-attr { - color: var(--color-success-fg); +.hljs-selector-tag { + color: var(--color-prettylights-syntax-keyword); } .hljs-string, -.hljs-doctag { - color: var(--color-accent-fg); +.hljs-doctag, +.hljs-template-variable { + color: var(--color-prettylights-syntax-string); } .hljs-title, .hljs-section, .hljs-selector-id { - color: var(--color-danger-fg); - font-weight: bold; + color: var(--color-prettylights-syntax-markup-heading); } -.hljs-subst { - font-weight: normal; +.hljs-section { + font-weight: bold; } .hljs-type, -.hljs-class .hljs-title { - color: var(--color-accent-fg); - font-weight: bold; +.hljs-class, +.hljs-variable { + color: var(--color-prettylights-syntax-variable); +} + +.hljs-language, +.hljs-subst { + color: var(--color-prettylights-syntax-storage-modifier-import); +} + +.hljs-number, +.hljs-literal, +.hljs-symbol, +.hljs-property, +.hljs-constant { + color: var(--color-prettylights-syntax-constant); } .hljs-tag, .hljs-name, -.hljs-attribute { - color: var(--color-accent-fg); - font-weight: normal; +.hljs-attribute, +.hljs-attr { + color: var(--color-prettylights-syntax-entity-tag); } .hljs-regexp, .hljs-link { - color: var(--color-success-fg); -} - -.hljs-symbol, -.hljs-bullet { - color: var(--color-done-fg); + color: var(--color-prettylights-syntax-string-regexp); } .hljs-built_in, -.hljs-builtin-name { - color: var(--color-accent-fg); -} - -.hljs-meta { - color: var(--color-fg-subtle); - font-weight: bold; +.hljs-builtin-name, +.hljs-function { + color: var(--color-prettylights-syntax-entity); } .hljs-deletion { - background: var(--color-danger-subtle); + background: var(--color-prettylights-syntax-markup-deleted-bg); } .hljs-addition { - background: var(--color-success-subtle); + background: var(--color-prettylights-syntax-markup-inserted-bg); } .hljs-emphasis { diff --git a/tests/linting/lint-files.js b/tests/linting/lint-files.js index 4a3de39075..668932b5d0 100644 --- a/tests/linting/lint-files.js +++ b/tests/linting/lint-files.js @@ -277,14 +277,15 @@ if (!process.env.TEST_TRANSLATION) { } else { // get all translated markdown or yaml files by comparing files changed to main branch const changedFilesRelPaths = execSync( - 'git -c diff.renameLimit=10000 diff --name-only origin/main | egrep "^translations/.*/.+.(yml|md)$"', + 'git -c diff.renameLimit=10000 diff --name-only origin/main', { maxBuffer: 1024 * 1024 * 100 } ) .toString() .split('\n') - if (changedFilesRelPaths === '') process.exit(0) + .filter((p) => p.startsWith('translations') && (p.endsWith('.md') || p.endsWith('.yml'))) - console.log('testing translations.') + // If there are no changed files, there's nothing to lint: signal a successful termination. + if (changedFilesRelPaths.length === 0) process.exit(0) console.log(`Found ${changedFilesRelPaths.length} translated files.`) @@ -679,10 +680,18 @@ describe('lint yaml content', () => { if (ymlToLint.length < 1) return describe.each(ymlToLint)('%s', (yamlRelPath, yamlAbsPath) => { let dictionary, isEarlyAccess, ifversionConditionals, ifConditionals + // This variable is used to determine if the file was parsed successfully. + // When `yaml.load()` fails to parse the file, it is overwritten with the error message. + // `false` is intentionally chosen since `null` and `undefined` are valid return values. + let dictionaryError = false beforeAll(async () => { const fileContents = await readFileAsync(yamlAbsPath, 'utf8') - dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + try { + dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + } catch (error) { + dictionaryError = error + } isEarlyAccess = yamlRelPath.split('/').includes('early-access') @@ -691,6 +700,10 @@ describe('lint yaml content', () => { ifConditionals = getLiquidConditionals(fileContents, 'if') }) + test('it can be parsed as a single yaml document', () => { + expect(dictionaryError).toBe(false) + }) + test('ifversion conditionals are valid in yaml', async () => { const errors = validateIfversionConditionals(ifversionConditionals) expect(errors.length, errors.join('\n')).toBe(0) @@ -907,10 +920,19 @@ describe('lint GHES release notes', () => { if (ghesReleaseNotesToLint.length < 1) return describe.each(ghesReleaseNotesToLint)('%s', (yamlRelPath, yamlAbsPath) => { let dictionary + let dictionaryError = false beforeAll(async () => { const fileContents = await readFileAsync(yamlAbsPath, 'utf8') - dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + try { + dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + } catch (error) { + dictionaryError = error + } + }) + + it('can be parsed as a single yaml document', () => { + expect(dictionaryError).toBe(false) }) it('matches the schema', () => { @@ -954,10 +976,19 @@ describe('lint GHAE release notes', () => { const currentWeeksFound = [] describe.each(ghaeReleaseNotesToLint)('%s', (yamlRelPath, yamlAbsPath) => { let dictionary + let dictionaryError = false beforeAll(async () => { const fileContents = await readFileAsync(yamlAbsPath, 'utf8') - dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + try { + dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + } catch (error) { + dictionaryError = error + } + }) + + it('can be parsed as a single yaml document', () => { + expect(dictionaryError).toBe(false) }) it('matches the schema', () => { @@ -1008,10 +1039,19 @@ describe('lint learning tracks', () => { if (learningTracksToLint.length < 1) return describe.each(learningTracksToLint)('%s', (yamlRelPath, yamlAbsPath) => { let dictionary + let dictionaryError = false beforeAll(async () => { const fileContents = await readFileAsync(yamlAbsPath, 'utf8') - dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + try { + dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + } catch (error) { + dictionaryError = error + } + }) + + it('can be parsed as a single yaml document', () => { + expect(dictionaryError).toBe(false) }) it('matches the schema', () => { @@ -1083,10 +1123,19 @@ describe('lint feature versions', () => { if (featureVersionsToLint.length < 1) return describe.each(featureVersionsToLint)('%s', (yamlRelPath, yamlAbsPath) => { let dictionary + let dictionaryError = false beforeAll(async () => { const fileContents = await readFileAsync(yamlAbsPath, 'utf8') - dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + try { + dictionary = yaml.load(fileContents, { filename: yamlRelPath }) + } catch (error) { + dictionaryError = error + } + }) + + it('can be parsed as a single yaml document', () => { + expect(dictionaryError).toBe(false) }) it('matches the schema', () => { diff --git a/tests/rendering/server.js b/tests/rendering/server.js index e6a5ba9b8b..bd66edfc46 100644 --- a/tests/rendering/server.js +++ b/tests/rendering/server.js @@ -337,7 +337,7 @@ describe('server', () => { ) expect($('h2#in-this-article').length).toBe(1) expect($('h2#in-this-article + div div ul').length).toBeGreaterThan(0) // non-indented items - expect($('h2#in-this-article + div div ul div div div div ul.ml-3').length).toBeGreaterThan(0) // indented items + expect($('h2#in-this-article + div div ul li div div div ul.ml-3').length).toBeGreaterThan(0) // indented items }) test('does not render mini TOC in articles with only one heading', async () => { @@ -878,11 +878,11 @@ describe('extended Markdown', () => { test('renders expected mini TOC headings in platform-specific content', async () => { const $ = await getDOM('/en/github/using-git/associating-text-editors-with-git') expect($('h2#in-this-article').length).toBe(1) - expect($('h2#in-this-article + div div ul div.extended-markdown.mac').length).toBeGreaterThan(1) + expect($('h2#in-this-article + div div ul li.extended-markdown.mac').length).toBeGreaterThan(1) expect( - $('h2#in-this-article + div div ul div.extended-markdown.windows').length + $('h2#in-this-article + div div ul li.extended-markdown.windows').length ).toBeGreaterThan(1) - expect($('h2#in-this-article + div div ul div.extended-markdown.linux').length).toBeGreaterThan( + expect($('h2#in-this-article + div div ul li.extended-markdown.linux').length).toBeGreaterThan( 1 ) }) diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index e864c00f16..446b3ae223 100644 --- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- -title: Administrar las notificaciones en tu bandeja de entrada -intro: 'Utiliza tu bandeja de entrada para clasificar y sincronizar rápidamente tus notificaciones a través de tu correo electrónico {% ifversion fpt or ghes or ghec %} y dispositivos móviles{% endif %}.' +title: Managing notifications from your inbox +intro: 'Use your inbox to quickly triage and sync your notifications across email{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -13,103 +13,102 @@ versions: ghec: '*' topics: - Notifications -shortTitle: Administrar desde tu bandeja de entrada +shortTitle: Manage from your inbox --- - {% ifversion ghes %} {% data reusables.mobile.ghes-release-phase %} {% endif %} -## Acerca de tu bandeja de entrada +## About your inbox {% ifversion fpt or ghes or ghec %} -{% data reusables.notifications-v2.notifications-inbox-required-setting %}Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". +{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% endif %} -Para acceder a tu bandeja de notificaciones, en la esquina superior derecha de cualquier página, da clic en {% octicon "bell" aria-label="The notifications bell" %}. +To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}. - ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) + ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png) -Tu bandeja de entrada muestra todas las notificaciones de las cuales aún no te has desuscrito o que no has marcado como **Hecho**. Puedes personalizar tu bandeja de entrada como mejor se acople con tu flujo de trabajo utilizando filtros, visualizando todas las notificaciones o únicamente las que no se han leído, y agrupando tus notificaciones para obtener un resumen rápido. +Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview. - ![vista de bandeja de entrada](/assets/images/help/notifications-v2/inbox-view.png) + ![inbox view](/assets/images/help/notifications-v2/inbox-view.png) -Predeterminadamente, tu bandeja de entrada mostrará las notificaciones leídas y no leídas. Para solo ver las no leídas, da clic en **No leídas** o utiliza la consulta `is:unread`. +By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query. - ![vista de no leídos en bandeja de entrada](/assets/images/help/notifications-v2/unread-inbox-view.png) + ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png) -## Opciones de clasificación +## Triaging options -Tienes varias opciones para clasificar las notificaciones de tu bandeja de entrada. +You have several options for triaging notifications from your inbox. -| Opción de clasificación | Descripción | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Save | Guarda tu notificación para revisarla posteriormente. Para guardar una notificación, da clic en {% octicon "bookmark" aria-label="The bookmark icon" %} al lado derecho de la misma.

    Las notificaciones guardadas se mantienen por tiempo indefinido y puedes verlas si das clic en **Guardadas** en la barra lateral o con el query `is:saved`. Si guardas las notificaciones por más de 5 meses y luego las dejas de guardar, estas desaparecerán de tu bandeja de entrada en un día. | -| Done | Marca una notificación como completada y elimina la notificación de tu bandeja de entrada. Puedes ver todas las notificaciones completadas dando clic en **Hecho** dentro de la barra lateral o con el query `is:done`. Las notificaciones marcadas como **Hecho** se guardan por 5 meses. | -| Unsubscribe | Elimina automáticamente la notificación de tu bandeja de entrada y te da de baja de la conversación hasta que se @mencione a tu usuario o a algún equipo al que pertenezcas, o cuando se te solicite una revisión. | -| Read | Marca la notificación como leída. Para ver únicamente las notificaciones leídas en tu bandeja de entrada, utiliza el query `is:read`. Este query no incluirá a las notificaciones marcadas como **Hecho**. | -| Unread | Mara la notificación como no leída. Para ver únicamente las notificaciones sin leer en tu bandeja de entrada, utiliza el query `is:unread`. | +| Triaging option | Description | +|-----------------|-------------| +| Save | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}.

    Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. | +| Done | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months. +| Unsubscribe | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review. +| Read | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**. +| Unread | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. | -Para ver los atajos de teclado disponibles, consulta la sección "[Atajos de Teclado](/github/getting-started-with-github/keyboard-shortcuts#notifications)". +To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)." -Antes de escoger una opción de clasificación, puedes prever los detalles de la notificación e investigar. Para obtener más información, consulta la sección "[Clasificar una sola notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)". +Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)." -## Clasificar varias notificaciones al mismo tiempo +## Triaging multiple notifications at the same time -Para clasificar varias notificaciones de una sola vez, selecciona las notificaciones relevantes y utiliza el menú desplegable de {% octicon "kebab-horizontal" aria-label="The edit icon" %} para elegir una opción de clasificación. +To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option. -![Menú desplegable con opciones de clasificación y notificaciones seleccionadas](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) +![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) -## Filtros de notificación predeterminados +## Default notification filters -Predeterminadamente, tu bandeja de entrada tiene filtros para cuando se te asigna, participas en un hilo, se te solicita revisar una solicitud de extracción, o cuando se @menciona a tu usuario directamente o a un equipo del cual eres miembro. +By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned. - ![Filtros personalizados predeterminados](/assets/images/help/notifications-v2/default-filters.png) + ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png) -## Personalizar tu bandeja de entrada con filtros personalizados +## Customizing your inbox with custom filters -Puedes agregar hasta 15 de tus filtros personalizados. +You can add up to 15 of your own custom filters. {% data reusables.notifications.access_notifications %} -2. Para abrir la configuración de filtros, en la barra lateral izquierda, a lado de "Filtros", da clic en {% octicon "gear" aria-label="The Gear icon" %}. +2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}. {% tip %} - **Tip:** Puedes prever rápidamente los resultados del filtro en la bandeja de entrada si creas un query en ella y das clic en **Guardar**, lo cual abrirá la configuración del filtro personalizado. + **Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings. {% endtip %} -3. Añade un nombre para tu filtro y query del mismo. Por ejemplo, para ver únicamente las notificaciones de un repositorio específico, puedes crear un filtro utilizando el query `repo:octocat/open-source-project-name reason:participating`. También puedes añadir emojis con un teclado que los tenga como nativos. Para ver una lista de queries de búsqueda compatibles, consulta la sección "[Queries compatibles para filtros personalizados](#supported-queries-for-custom-filters)". +3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)." - ![Ejemplo de filtro personalizado](/assets/images/help/notifications-v2/custom-filter-example.png) + ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png) -4. Da clic en **Crear**. +4. Click **Create**. -## Limitaciones de los filtros personalizados +## Custom filter limitations -Los filtros personalizados no son compatibles actualmente con: - - Búsquedas de texto completo en tu bandeja de entrada, incluyendo búsquedas de los títulos de los informes de problemas o solicitudes de extracción. - - Distinción entre los queries de filtro `is:issue`, `is:pr`, y `is:pull-request`. Estos queries darán como resultado tanto informes de verificación como solicitudes de extracción. - - Crear más de 15 filtros personalizados. - - Cambiar los filtros predeterminados o su orden. - - Busca la [exclusión](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) utilizando `NOT` o `-QUALIFIER`. +Custom filters do not currently support: + - Full text search in your inbox, including searching for pull request or issue titles. + - Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests. + - Creating more than 15 custom filters. + - Changing the default filters or their order. + - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`. -## Queries compatibles para filtros personalizados +## Supported queries for custom filters -Estos son los tipos de filtro que puedes utilizar: - - Filtrar por repositorio con `repo:` - - Filtrar por tipo de debate con `is:` - - Filtrar por razón de la notificación con `reason:`{% ifversion fpt or ghec %} - - Filtrar por autor de la notificación con `author:` - - Filtrar por organización con `org:`{% endif %} +These are the types of filters that you can use: + - Filter by repository with `repo:` + - Filter by discussion type with `is:` + - Filter by notification reason with `reason:`{% ifversion fpt or ghec %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -### Consultas de `repo:` compatibles +### Supported `repo:` queries -Para agregar un filtro de `repo:`, debes incluir al propietario del repositorio en la consulta: `repo:owner/repository`. Un propietario es el usuario u organización al que pertenece el activo de {% data variables.product.prodname_dotcom %} que activa la notificación. Por ejemplo, `repo:octo-org/octo-repo` mostrará las notificaciones que se activaron en el repositorio octo-repo dentro de la organización octo-org. +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. -### Queries de tipo `is:` compatibles +### Supported `is:` queries -Para filtrar las notificaciones para una actividad específica en {% data variables.product.product_location %}, puedes utililzar la consulta `is`. Por ejemplo, para ver únicamente las actualizaciones de las invitaciones al repositorio, utiliza `is:repository-invitation`{% ifversion not ghae %}, y para ver únicamente las alertas de {% ifversion fpt or ghes or ghec %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}, utiliza `is:repository-vulnerability-alert`.{% endif %} +To filter notifications for specific activity on {% data variables.product.product_location %}, you can use the `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot %} alerts, use `is:repository-vulnerability-alert`{% endif %}. - `is:check-suite` - `is:commit` @@ -126,64 +125,64 @@ Para filtrar las notificaciones para una actividad específica en {% data variab For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." {% endif %} -También puedes utilizar la consulta `is:` para describir cómo se clasificó la notificación. +You can also use the `is:` query to describe how the notification was triaged. - `is:saved` - `is:done` - `is:unread` - `is:read` -### Queries de tipo `reason:` compatibles +### Supported `reason:` queries -Para filtrar las notificaciones de acuerdo con la razón por la cual recibiste una actualización, puedes utilizar la consulta `reason:`. Por ejemplo, para ver las notificaciones cuando se solicita (a ti o a un equipo al que pertenezcas) revisar una solicitud de extracción, utiliza `reason:review-requested`. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)". +To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." -| Consulta | Descripción | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `reason:assign` | Cuando hay una actualización en un informe de problemas o solicitud de extracción en los que estés asignado. | -| `reason:author` | Cuando abres una solicitud de extracción o informe de problemas y ésta ha tenido una actualización o comentario nuevo. | -| `reason:comment` | Cuando comentas en un informe de problemas, solicitud de extracción o debate de equipo. | -| `reason:participating` | Cuando comentas en un informe de problemas, solicitud de extracción o debate de equipo en el que te @mencionaron. | -| `reason:invitation` | Cuando se te invita a un equipo, organización o repositorio. | -| `reason:manual` | Cuando das clic en **Suscribirse** en un informe de problemas o solicitud de extracción al que no estuvieras suscrito. | -| `reason:mention` | Cuando te @mencionan directamente. | -| `reason:review-requested` | Ya sea tú o un equipo en el que estás solicitó revisar una solicitud de cambios.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| `reason:security-alert` | Cuando se emite una alerta de seguridad para un repositorio.{% endif %} -| `reason:state-change` | Cuando el estado de un informe de problemas o solicitud de extracción cambia. Por ejemplo, se cierra un informe de problemas o se fusiona una solicitud de extracción. | -| `reason:team-mention` | Cuando se @menciona a algún equipo al que pertenezcas. | -| `reason:ci-activity` | Cuando un repositorio tiene una actualización de IC, tal como un nuevo estado de ejecución en un flujo de trabajo. | +| Query | Description | +|-----------------|-------------| +| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. +| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. +| `reason:comment`| When you commented on an issue, pull request, or team discussion. +| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. +| `reason:invitation` | When you're invited to a team, organization, or repository. +| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. +| `reason:mention` | You were directly @mentioned. +| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `reason:security-alert` | When a security alert is issued for a repository.{% endif %} +| `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. +| `reason:team-mention` | When a team you're a member of is @mentioned. +| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. {% ifversion fpt or ghec %} -### Consultas de `author:` compatibles +### Supported `author:` queries -Para filtrar notificaciones por usuario, puedes utilizar la consulta `author:`. Un autor es el autor original del hilo (propuesta, solicitud de cambios, gist, debate, etc.) del cual se te está notificando. Por ejemplo, para ver las notificaciones de los hilos que creó el usuario Octocat, utiliza `author:octocat`. +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. -### Consultas de `org:` compatibles +### Supported `org:` queries -Para filtrar las notificaciones por organización, puedes utilizar la consulta `org`. La organización que necesitas especificar en la consulta es aquella del repositorio del cual se te está notificando en {% data variables.product.prodname_dotcom %}. Esta consulta es útil si perteneces a varias organizaciones y quieres ver las notificaciones de una organización específica. +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. -Por ejemplo, para ver las notificaciones de la organización octo-org, utiliza `org:octo-org`. +For example, to see notifications from the octo-org organization, use `org:octo-org`. {% endif %} {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -## Filtros personalizados del {% data variables.product.prodname_dependabot %} +## {% data variables.product.prodname_dependabot %} custom filters -{% ifversion fpt or ghec %} -Si utilizas el {% data variables.product.prodname_dependabot %} para mantener tus dependencias actualziadas, puedes utilizar y guardar estos filtros personalizados: -- `is:repository_vulnerability_alert` para mostrar notificaciones para las {% data variables.product.prodname_dependabot_alerts %}. -- `reason:security_alert` para mostrar notificaciones para las {% data variables.product.prodname_dependabot_alerts %} y las solicitudes de cambios de las actualizaciones de seguridad. -- `author:app/dependabot` para mostrar las notificaciones que genera el {% data variables.product.prodname_dependabot %}. Esto incluye las {% data variables.product.prodname_dependabot_alerts %}, solicitudes de cambios para actualizaciones de seguridad y solicitudes de cambio para actualizaciones de versión. +{% ifversion fpt or ghec or ghes > 3.2 %} +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. -Para obtener más información acerca del {% data variables.product.prodname_dependabot %}, consulta la sección "[Acerca de administrar dependencias vulnerables](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)". +For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae-issue-4864 %} -If you use {% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: -- `is:repository_vulnerability_alert` +If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: +- `is:repository_vulnerability_alert` - `reason:security_alert` -Para obtener más informació acera de las {% data variables.product.prodname_dependabot %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". +For more information about {% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} {% endif %} diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index b16862db19..060afa3657 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -1,6 +1,6 @@ --- -title: Personalizar tu perfil -intro: 'Puedes compartir información sobre tI con otros usuarios de {% data variables.product.product_name %} al configurar una imagen de perfil y agregar una biografía a tu 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/ @@ -17,200 +17,216 @@ versions: ghec: '*' topics: - Profiles -shortTitle: Personalizar +shortTitle: Personalize --- +## Changing your profile picture -## Cambiar tu imagen de perfil +Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs. -Tu imagen de perfil ayuda a identificarte dentro de {% data variables.product.product_name %} en solicitudes de extracción, comentarios, páginas de contribuciones y gráficos. - -Cuando te registras en una cuenta, {% data variables.product.product_name %} te proporciona un "identicon" generado al azar. [Tu identicon](https://github.com/blog/1586-identicons) se genera a partir de un hash de tu ID de usuario, por lo que no hay manera de controlar su color o patrón. Puedes reemplazar tu identicon con una imagen que te represente. +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. {% tip %} -**Sugerencia**: la imagen de tu perfil debería ser un archivo PNG, JPG, o GIF menor de 1 MB de tamaño. Para mostrar la mejor calidad, recomendamos mantener la imagen en alrededor de 500 por 500 píxeles. +**Tip**: Your profile picture should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels. {% endtip %} -### Configurar una imagen de perfil +### Setting a profile picture {% data reusables.user_settings.access_settings %} -2. Dentro de **Profile Picture (Imagen de perfil)**, haz clic en {% octicon "pencil" aria-label="The edit icon" %} **Edit (Editar)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-photo.png) -3. Haz clic en **Upload a photo... (Cargar una foto...)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-picture-options.png) -3. Recorta tu imagen. Cuando hayas terminado, haz clic en **Set new profile picture (Configurar nueva imagen de perfil)**. ![Recortar foto cargada](/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...**. +![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png) +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) -### Restablecer tu imagen de perfil al identicon +### Resetting your profile picture to the identicon {% data reusables.user_settings.access_settings %} -2. Dentro de **Profile Picture (Imagen de perfil)**, haz clic en {% octicon "pencil" aria-label="The edit icon" %} **Edit (Editar)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-photo.png) -3. Para regresar a tu identicon, haz clic en **Remove photo (Eliminar foto)**. Si tu dirección de correo electrónico está asociada con [Gravatar](https://en.gravatar.com/), no puedes regresar a tu identicon. Haz clic en **Revert to Gravatar (Revertir a Gravatar)** en su lugar. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-picture-options.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. To revert to your identicon, click **Remove photo**. 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) -## Cambiar tu nombre de perfil +## Changing your profile name -Puedes cambiar el nombre que se muestra en tu perfil. Este nombre también podría mostrarse junto a los comentarios que haces en los repositorios privados que pertenezcan a una organización. Para obtener más información, consulta "[Administrar cómo se ven los nombres de los miembros en tu organización](/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 %} -**Nota:** Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, cualquier cambio a tu nombre de perfil debe hacerse a través de tu proveedor de identidad en vez de con {% 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 %} {% data reusables.user_settings.access_settings %} -2. Dentro de "Nombre", escribe el nombre que deseas que se muestre en tu perfil. ![Campo Nombre en configuraciones 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) -## Agregar una biografía en tu perfil +## Adding a bio to your profile -Agrega una biografía a tu perfil para compartir información sobre ti con otros usuarios de {% data variables.product.product_name %}. Con la ayuda de [@mentions](/articles/basic-writing-and-formatting-syntax) y emoji, puedes incluir información sobre dónde estás trabajando actualmente o dónde trabajaste anteriormente, qué tipo de trabajo realizas, o incluso qué tipo de café tomas. +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 encontrar un formato más largo y una forma más prominente de mostrar la información acerca de ti mismo, también puedes utilizar un README de perfil. Para obtener más información, consulta la sección "[Administrar el README de tu 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 %} -**Nota:** Si tienes habilitada la sección de resumen de la actividad para tu perfil y @mencionas a una organización a la que pertenezcas en tu biografía de perfil, esta organización se presentará primero en tu resumen de actividad. Para obtener más información, consulta "[Mostrar un resumen de tu actividad en tu 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. Dentro de **Bio (Biografía)**, agrega el contenido que deseas mostrar en tu perfil. El campo biografía tiene un límite de 160 caracteres. ![Actualizar biografía en el 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 %} - **Sugerencia:** cuando mencionas una organización, únicamente aquellas de las que eres miembro se completarán automáticamente. Incluso puedes mencionar organizaciones de las que no eres miembro, como un antiguo empleador, pero el nombre de la organización no se completará automáticamente. + **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. Haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/profile/update-profile-button.png) +3. Click **Update profile**. + ![Update profile button](/assets/images/help/profile/update-profile-button.png) -## Configurar un estado +## Setting a status -Puedes configurar un estado para mostrar información acerca de tu disponibilidad actual en {% data variables.product.product_name %}. Tu estado se mostrará: -- en tu página de perfil {% data variables.product.product_name %}. -- cuando las personas se desplacen sobre tu nombre de usuario o avatar en {% data variables.product.product_name %}. -- en una página de equipo en un equipo del cual eres un miembro. Para obtener más información, consulta "[Acerca de equipos](/articles/about-teams/#team-pages)." -- en el tablero de la organización en una organización de la cual eres miembro. Para obtener más información, consulta "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard/)." +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/)." -Cuando configuras tu estado, también puedes permitir que las personas sepan que tienes disponibilidad limitada en {% data variables.product.product_name %}. +When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}. -![El nombre de usuario mencionado muestra una nota de "busy" (ocupado) al lado del nombre de usuario](/assets/images/help/profile/username-with-limited-availability-text.png) +![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png) -![El revisor solicitado muestra una nota de "busy" (ocupado) la lado del nombre de usuario](/assets/images/help/profile/request-a-review-limited-availability-status.png) +![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png) -Si seleccionas la opción, "Busy" (Ocupado), cuando las personas mencionan tu nombre de usuario, te asignan una propuesta o una solicitud de extracción o te solicitan una revisión de solicitud de extracción, una nota al lado de tu nombre de usuario mostrará que estás ocupado. También se te excluirá de la tarea de revisión automática para las solicitudes de cambio que se asignen a cualquier equipo al que pertenezcas. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)". +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. ![Botón en el perfil para configurar tu estado](/assets/images/help/profile/set-status-on-profile.png) -2. Para agregar un texto personalizado a tu estado, haz clic en el campo texto y escribe un mensaje de estado. ![Campo para escribir un mensaje de estado](/assets/images/help/profile/type-a-status-message.png) -3. De manera opcional, para configurar un estado de emoji, haz clic en el ícono sonriente y selecciona un emoji de la lista. ![Botón para seleccionar un estado de emoji](/assets/images/help/profile/select-emoji-status.png) -4. Como alternativa, si te gustaría compartir que tienes disponibilidad limitada, selecciona "Busy" (Ocupado). ![Opción ocupado seleccionada en las opciones de Editar estado](/assets/images/help/profile/limited-availability-status.png) -5. Utiliza el menú desplegable **Clear status (Borrar estado)** y selecciona cuándo deseas que venza tu estado. Si no deseas seleccionar un vencimiento de estado, mantendrás tu estado hasta que lo borres o edites. ![Menú desplegable para elegir cuando vence tu estado](/assets/images/help/profile/status-expiration.png) -6. Utiliza el menú desplegable y haz clic en la organización para la que deseas que tu estado sea visible. Si no seleccionas una organización, tu estado será público. ![Menú desplegable para elegir para quién es visible tu estado](/assets/images/help/profile/status-visibility.png) -7. Haz clic en **Set status (Configurar estado)**. ![Botón para establecer el estado](/assets/images/help/profile/set-status-button.png) +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 %} -## Mostrar las insignias en tu perfil +## Displaying badges on your profile -Cuando participas en algunos programas, {% data variables.product.prodname_dotcom %} muestra automáticamente una insignia en tu perfil. +When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile. -| Insignia | Programa | Descripción | -| --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| ![Icono de insignia de Contribuyente Helicóptero de Marte 2020](/assets/images/help/profile/badge-mars-2020-small.png) | **Contribuyente Helicóptero de Marte 2020** | Si eres el autor de cualquier comentario(s) que esté(n) presente(s) en el historial de confirmaciones para la etiqueta relevante en una biblioteca de código abierto que se utilice en la Misión Helicóptero a Marte 2020, obtendrás una insignia de Contribuyente Helicópteor a Marte 2020 en tu perfil. Al pasar el puntero del mouse sobre la insignia se te muestran varios de los repositorios con los que contribuiste, los cuales se utilizaron en la misión. Para obtener la lista completa de repositorios que te calificarán para la insignia, consulta la sección "[Lista de repositorios de calificación para la insignia de Contribuyente Helicóptero de Marte 2020](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)". | -| ![Icono de insignia de Contribuyente de Vóbeda Ártica de Código](/assets/images/help/profile/badge-arctic-code-vault-small.png) | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Si eres el autor de cualquier confirmación en la rama predeterminada de un repositorio que se archivó en el programa del 2020 del Vaúl del Ártico, obtendrás una insignia de colaborador de {% data variables.product.prodname_arctic_vault %} en tu perfil. Al pasar el puntero del mouse sobre la insignia se te muestran varios de los repositorios con los que contribuiste que fueron parte del programa. Para obtener más información sobre el programa, consulta la sección [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). | -| ![Icono de la insignia de Patrocinador de {% data variables.product.prodname_dotcom %}](/assets/images/help/profile/badge-sponsors-small.png) | **Patrocinador de {% data variables.product.prodname_dotcom %}** | Si patrocinaste a un contribuyente de código abierto mediante {% data variables.product.prodname_sponsors %}, obtendrás una insignia de Patrocinador de {% data variables.product.prodname_dotcom %} en tu perfil. Si haces clic en la insignia, se tellevará a la pestaña de **Patrocinio** de tu perfil. Para obtener más información, consulta la sección "[Patrocinar colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)". | -| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Miembro del Programa de Desarrolladores** | 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. Para obtener más información sobre el Programa de Desarrolladores de {% data variables.product.prodname_dotcom %}, consulta la sección [Desarrollador de GitHub](/program/). | -| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | Si utilizas {% data variables.product.prodname_pro %} obtendrás una insignia de PRO en tu perfil. Para obtener más información acerca de {% data variables.product.prodname_pro %}, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)." | -| {% octicon "lock" aria-label="The lock icon" %} | **Cazador de Recompensas por Errores de Seguridad** | Si ayudaste a identificar vulnerabilidades de seguridad, obtendrás una insignia de Cazador de Recompensas por Errores de Seguridad en tu perfil. Para obtener más información acerca del programa de seguridad de {% data variables.product.prodname_dotcom %}, consulta la sección [Seguridad de {% data variables.product.prodname_dotcom %}](https://bounty.github.com/). | -| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **Experto del Campus de GitHub** | Si participas en el Programa del Campus de {% data variables.product.prodname_dotcom %}, necesitarás una insignia de Experto de Campus de {% data variables.product.prodname_dotcom %} en tu perfil. Para obtener más información sobre el programa de expertos del campus, consulta la sección [Expertos del Campus](https://education.github.com/experts). | +| Badge | Program | Description | +| --- | --- | --- | +| ![Mars 2020 Helicopter Contributor badge icon](/assets/images/help/profile/badge-mars-2020-small.png) | **Mars 2020 Helicopter Contributor** | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." | +| ![Arctic Code Vault Contributor badge icon](/assets/images/help/profile/badge-arctic-code-vault-small.png) | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were part of the program. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). | +| ![{% data variables.product.prodname_dotcom %} Sponsor badge icon](/assets/images/help/profile/badge-sponsors-small.png) | **{% data variables.product.prodname_dotcom %} Sponsor** | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)." | +| {% 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). | -## Inhabilitar las insignias en tu perfil +## Disabling badges on your profile -Puedes inhabilitar algunas de las insignias para los programas de {% data variables.product.prodname_dotcom %} en los que estás participando, incluyendo aquellas de PRO, {% data variables.product.prodname_arctic_vault %} y Contribuyente Helicóptero de Marte 2020. +You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges. {% data reusables.user_settings.access_settings %} -2. Debajo de "Configuración del perfil", deselecciona la insignia que quieres inhabilitar. ![Casilla para dejar de mostrar una insignia en tu perfil](/assets/images/help/profile/profile-badge-settings.png) -3. Haz clic en **Update preferences (Actualizar preferencias)**. +2. Under "Profile settings", deselect the badge you want you disable. + ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/profile-badge-settings.png) +3. Click **Update preferences**. {% endif %} -## Lista de repositorios que califican para la insignia de Contributente Helicóptero de Marte 2020 +## List of qualifying repositories for Mars 2020 Helicopter Contributor badge -Si creaste cualquiera de las confirmaciones presentes en el historial de confirmaciones de la etiqueta listada de uno o más de los repositorios siguientes, recibirás la insignia de contribuyente Helicóptero de Marte 2020 en tu perfil. La confirmación que creaste debe hacerse con una dirección de correo electrónico verificada y asociada con tu cuenta en el momento en que {% data variables.product.prodname_dotcom %} determine las contribuciones elegibles para que se te pueda atribuir. Puedes ser el autor original o [ uno de los coautores](/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) de la confirmación. Los cambios futuros a los correos electrónicos verificados no tendrán efecto en la insignia. Creamos la lista con base en la información que recibimos del Laboratorio de Propulsión a Chorro de la 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 badge 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. -| Repositorio de {% data variables.product.prodname_dotcom %} | Versión | Etiqueta | -| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- | -| [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) | -| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) | -| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) | -| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) | -| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) | -| [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) | -| [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) | -| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) | -| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) | -| [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) | -| [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) | -| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) | -| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) | -| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) | -| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) | -| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) | -| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) | -| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) | -| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) | -| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) | -| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) | -| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) | -| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) | -| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) | -| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) | -| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) | -| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) | -| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) | -| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) | -| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) | -| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) | -| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) | -| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) | -| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) | -| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) | -| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) | -| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) | -| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) | -| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) | -| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) | -| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) | -| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) | -| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) | -| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) | -| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) | -| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) | -| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) | -| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) | -| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) | -| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) | -| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) | -| [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/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) | +| {% 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) | +| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) | +| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) | +| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) | +| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) | +| [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) | +| [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) | +| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) | +| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) | +| [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) | +| [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) | +| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) | +| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) | +| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) | +| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) | +| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) | +| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) | +| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) | +| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) | +| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) | +| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) | +| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) | +| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) | +| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) | +| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) | +| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) | +| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) | +| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) | +| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) | +| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) | +| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) | +| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) | +| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) | +| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) | +| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) | +| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) | +| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) | +| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) | +| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) | +| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) | +| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) | +| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) | +| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) | +| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) | +| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) | +| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) | +| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) | +| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) | +| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) | +| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) | +| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) | +| [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/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) | -## Leer más +## Further reading -- "[Acerca de tu perfil](/articles/about-your-profile)" +- "[About your profile](/articles/about-your-profile)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index b12c783b59..2567837344 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -1,5 +1,5 @@ --- -title: Cambiar tu nombre de usuario de GitHub +title: Changing your GitHub username intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.' redirect_from: - /articles/how-to-change-your-username/ @@ -15,7 +15,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Cambiar tu nombre de usuario +shortTitle: Change your username --- {% ifversion ghec or ghes %} @@ -24,7 +24,7 @@ shortTitle: Cambiar tu nombre de usuario {% ifversion ghec %} -**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% elsif ghes %} @@ -36,53 +36,57 @@ shortTitle: Cambiar tu nombre de usuario {% endif %} -## Acerca de los cambios de nombre de usuario +## About username changes -Puedes cambiar tu nombre de usuario a otro que no esté en uso actualmente.{% ifversion fpt or ghec %} si el nombre de usuario que quieres no está disponible, considera otros nombres o variaciones únicas. El utilizar un número, guion o una ortografía alternativa podría ayudarte a encontrar un nombre de usuario similar que esté disponible. +You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available. -Si tienes una marca comercial para el nombre de usuario, puedes encontrar más información sobre cómo hacer un reclamo de una marca comercial en nuestra página de [Política de Marcas Comerciales](/free-pro-team@latest/github/site-policy/github-trademark-policy). +If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. -Si no tienes una marca comercial para el nombre, puedes elegir otro nombre de usuario o mantener el actual. {% data variables.contact.github_support %} no puede publicar el nombre de usuario que no está disponible para ti. Para obtener más información, consulta "[Cambiar tu nombre de usuario](#changing-your-username)".{% endif %} +If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %} -Una vez que cambies tu nombre de usuario, el nombre de usuario anterior estará disponible para todas las personas que lo reclamen. La mayoría de las referencias a tus repositorios con el nombre de usuario anterior automáticamente cambian al nombre de usuario nuevo. Sin embargo, algunos enlaces a tu perfil no se redirigirán automáticamente. +After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect. -{% data variables.product.product_name %} no puede configurar redirecciones para: -- [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) con tu nombre de usuario anterior -- Enlaces a los [gists](/articles/creating-gists) que incluyen tu nombre de usuario anterior +{% data variables.product.product_name %} cannot set up redirects for: +- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username +- Links to [gists](/articles/creating-gists) that include your old username -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec %} -Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, no puedes hacer cambios a tu nombre de usuario. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endif %} -## Referencias del repositorio +## Repository references -Después de cambiar tu nombre de usuario, {% data variables.product.product_name %} automáticamente redirigirá las referencias a tus repositorios. -- Los enlaces web a tus repositorios existentes seguirán funcionando. Esto puede tardar algunos minutos en completarse después de realizar el cambio. -- Las inserciones de la línea de comando desde tus clones de repositorio local hasta las URL del registro remoto anterior seguirán funcionando. +After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories. +- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change. +- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work. -Si el nuevo propietario de tu nombre de usuario anterior crea un repositorio con el mismo nombre que tu repositorio, se sobrescribirá el registro de redirección y tu redirección dejará de funcionar. Debido a esta posibilidad, recomendamos que actualices todas las URL de repositorios remotos existentes luego de cambiar tu nombre de usuario. Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)." +If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Enlaces a tu página de perfil anterior +## Links to your previous profile page -Luego de cambiar tu nombre de usuario, los enlaces a tu página de perfil anterior, como `https://{% data variables.command_line.backticks %}/previoususername`, arrojarán un error 404. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}. +After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}. -## Tus confirmaciones Git +## Your Git commits -{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. Para obtener más información sobre cómo establecer tu dirección de correo electrónico, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". +{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." -## Cambiar tu nombre de usuario +## Changing your username {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.account_settings %} -3. En la sección "Change username" (Cambiar nombre de usuario), haz clic en **Change username** (Cambiar nombre de usuario). ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} -4. Lee las advertencias sobre cómo cambiar tu nombre de usuario. Si aún deseas cambiar tu nombre de usuario, haz clic en **I understand, let's change my username** (Comprendo, cambiaré mi nombre de usuario). ![Cambiar botón Username warning (Advertencia de nombre de usuario)](/assets/images/help/settings/settings-change-username-warning-button.png) -5. Escribe un nuevo nombre de usuario. ![Campo New username (Nuevo nombre de usuario)](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. Si el nombre de usuario que elegiste está disponible, haz clic en **Change my username** (Cambiar mi nombre de usuario). Si el nombre de usuario que elegiste no está disponible, puedes probar un nombre de usuario diferente o una de las sugerencias que ves. ![Cambiar botón Username warning (Advertencia de nombre de usuario)](/assets/images/help/settings/settings-change-my-username-button.png) +3. In the "Change username" section, click **Change username**. + ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} +4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**. + ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png) +5. Type a new username. + ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png) +6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see. + ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png) {% endif %} -## Leer más +## Further reading -- "[Why are my commits linked to the wrong user?](/articles/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %} +- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %} - "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %} diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md index f1ab3e9d8a..fc6276d612 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md @@ -1,6 +1,6 @@ --- -title: Eliminar tu cuenta de usuario -intro: 'Puedes eliminar tu cuenta de usuario de {% data variables.product.product_name %} en cualquier momento.' +title: Deleting your user account +intro: 'You can delete your {% data variables.product.product_name %} user account at any time.' redirect_from: - /articles/deleting-a-user-account/ - /articles/deleting-your-user-account @@ -12,39 +12,40 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Eliminar tu cuenta de usuario +shortTitle: Delete your user account --- - -Al eliminar tu cuenta de usuario se eliminan todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta. {% ifversion fpt or ghec %}No se eliminarán las propuestas ni las solicitudes de extracción que hayas creado ni los comentarios que hayas hecho en repositorios que sean propiedad de otros usuarios. En lugar de eliminarlos, se los asociará con nuestro [Usuario fantasma](https://github.com/ghost).{% else %}No se eliminarán las propuestas ni las solicitudes de extracción que hayas creado ni los comentarios que hayas hecho en repositorios que sean propiedad de otros usuarios.{% endif %} +Deleting your user account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted - instead, they'll be associated with our [Ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %} {% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %} -Si eres el único propietario de una organización, debes transferir la propiedad a otra persona o eliminar la organización primero para que puedas eliminar tu cuenta de usuario. Si hay otros propietarios de la organización, debes eliminarte de la organización primero para que puedas eliminar tu cuenta de usuario. +If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your user account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your user account. -Para obtener más información, consulta: -- "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)" -- "[Eliminar una cuenta de la organización](/articles/deleting-an-organization-account)" -- "[Eliminarte de una organización](/articles/removing-yourself-from-an-organization/)" +For more information, see: +- "[Transferring organization ownership](/articles/transferring-organization-ownership)" +- "[Deleting an organization account](/articles/deleting-an-organization-account)" +- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)" -## Copias de seguridad de los datos de tu cuenta +## Back up your account data -Antes de eliminar tu cuenta de usuario, haz una copia de todos los repositorios, bifurcaciones privadas, wikis, propuestas y solicitudes de extracción que sean propiedad de tu cuenta. +Before you delete your user account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account. {% warning %} -**Advertencia:** Una vez que tu cuenta de usuario se ha eliminado, GitHub no puede restaurar su contenido. +**Warning:** Once your user account has been deleted, GitHub cannot restore your content. {% endwarning %} -## Eliminar tu cuenta de usuario +## Delete your user account {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.account_settings %} -3. En la parte inferior de la página de configuración de la cuenta, en "Eliminar cuenta", haz clic en **Eliminar tu cuenta**. Para que puedas eliminar tu cuenta de usuario, antes debes tener en cuenta lo siguiente: - - Si eres el único propietario de la organización, debes transferir la propiedad a otra persona o eliminar tu organización. - - Si hay otros propietarios de la organización dentro de la organización, debes eliminarte de la organización. ![Botón Eliminación de cuenta](/assets/images/help/settings/settings-account-delete.png) -4. En el cuadro de diálogo "Make sure you want to do this" (Asegúrate de que quieres hacer esto), realiza los siguientes pasos para confirmar que comprendes lo que sucede cuando se elimina tu cuenta: ![Diálogo de confirmación para eliminar cuenta](/assets/images/help/settings/settings-account-deleteconfirm.png) - {% ifversion fpt or ghec %}-Recuerda que se eliminarán todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta, tu facturación finalizará y tu nombre de usuario pasará a estar disponible para que cualquier otra persona lo use en {% data variables.product.product_name %}. - {% else %}-Recuerda que se eliminarán todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta, y tu nombre de usuario pasará a estar disponible para que cualquier otra persona lo use en {% data variables.product.product_name %}. - {% endif %}- En el primer campo, escribe tu nombre de usuario de {% data variables.product.product_name %} o tu correo electrónico. - - En el segundo campo, escribe la frase que se indica. +3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your user account: + - If you're the only owner in the organization, you must transfer ownership to another person or delete your organization. + - If there are other organization owners in the organization, you must remove yourself from the organization. + ![Account deletion button](/assets/images/help/settings/settings-account-delete.png) +4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted: + ![Delete account confirmation dialog](/assets/images/help/settings/settings-account-deleteconfirm.png) + {% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days. + {% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}. + {% endif %}- In the first field, type your {% data variables.product.product_name %} username or email. + - In the second field, type the phrase from the prompt. diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index da9f57cdf2..6ba64d8d33 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -1,6 +1,6 @@ --- -title: Administrar las configuraciones del usuario de la cuenta -intro: 'Puedes cambiar varias configuraciones de tu cuenta personal, lo que incluye cambiar tu nombre de usuario y eliminar tu cuenta.' +title: Managing user account settings +intro: 'You can change several settings for your personal account, including changing your username and deleting your account.' redirect_from: - /categories/29/articles/ - /categories/user-accounts/ @@ -23,12 +23,13 @@ children: - /deleting-your-user-account - /permission-levels-for-a-user-account-repository - /permission-levels-for-user-owned-project-boards + - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - /managing-security-and-analysis-settings-for-your-user-account - /managing-access-to-your-user-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do -shortTitle: Configuración de cuenta de usuario +shortTitle: User account settings --- diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md index 44b47a33c3..2d65e2b11b 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md @@ -1,47 +1,53 @@ --- -title: Administrar la configuración de seguridad y análisis para tu cuenta de usuario -intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tus proyectos dentro de {% data variables.product.prodname_dotcom %}.' +title: Managing security and analysis settings for your user account +intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' ghec: '*' + ghes: '>3.2' topics: - Accounts redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account -shortTitle: Administrar el análisis & seguridad +shortTitle: Manage security & analysis --- +## About management of security and analysis settings -## Acerca de la administración de los parámetros de seguridad y análisis +{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories. -{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar tus repositorios. Este tema te muestra cómo puedes administrar las características de seguridad y análisis para todos tus repositorios existentes o nuevos. +You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." -Aún puedes administrar las características de seguridad y análisis para los repositorios individuales. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +You can also review the security log for all activity on your user account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)." {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} -Para obtener un resumen de la seguridad a nivel de repositorio, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)". +For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." -## Habilitar o inhabilitar las características para los repositorios existentes +## Enabling or disabling features for existing repositories {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security-analysis %} -3. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png) -6. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png) -7. Da clic en **Inhabilitar CARACTERÍSTICA** o **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios que te pertenezcan. ![Botón para inhabilitar o habilitar la característica](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png) +3. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. + {% ifversion ghes > 3.2 %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %} +6. Optionally, enable the feature by default for new repositories that you own. + {% ifversion ghes > 3.2 %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %} +7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own. + {% ifversion ghes > 3.2 %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %} {% data reusables.security.displayed-information %} -## Habilitar o inhabilitar las características para los repositorios nuevos +## Enabling or disabling features for new repositories {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security-analysis %} -3. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, habilítala o inhabilítala para los repositorios nuevos en tu organización. ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png) +3. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories that you own. + {% ifversion ghes > 3.2 %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} -## Leer más +## Further reading -- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Administrar las vulnerabilidades en las dependencias de tu proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" -{% ifversion fpt or ghec %}- "![Mantener tus dependencias actualizadas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" +- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md index 766b36c34b..89530122ee 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -1,16 +1,20 @@ --- -title: Administrar tu preferencia de representación de tamaño de pestaña -intro: Puedes administrar la cantidad de espacios que representa una pestaña en tu cuenta de usuario. +title: Managing your tab size rendering preference +intro: You can manage the number of spaces a tab is equal to for your user account. versions: fpt: '*' + ghae: ghae-issue-5083 + ghes: '>=3.4' ghec: '*' topics: - Accounts -shortTitle: Administrar el tamaño de tu pestaña +shortTitle: Managing your tab size --- -Si crees que la sangría del código que se interpreta en {% data variables.product.product_name %} es demasiado grande o pequeña, puedes cambiar esto en tus ajustes. +If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings. {% data reusables.user_settings.access_settings %} -1. En la barra lateral de configuración de usuario, da clic en **Apariencia**. ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png) -2. Debajo de "Preferencia de tamaño de pestaña"; selecciona el menú desplegable y elige tu preferencia. ![Botón de preferencia de tamaño de pestaña](/assets/images/help/settings/tab-size-preference.png) +1. In the user settings sidebar, click **Appearance**. + !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +2. Under "Tab size preference", select the drop-down menu and choose your preference. + ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png ) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index d1fd0f52d6..ff77342e3d 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -1,6 +1,6 @@ --- -title: Administrar la configuración de tu tema -intro: 'Puedes administrar la forma en que {% data variables.product.product_name %} te ve si configuras las preferencias de tema que ya sea siguen la configuración de tu sistema o siempre utilzian un modo claro u oscuro.' +title: Managing your theme settings +intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.' versions: fpt: '*' ghae: next @@ -11,33 +11,40 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings -shortTitle: Administrar la configuración de temas +shortTitle: Manage theme settings --- -Para obtener elecciones y flexibilidad en la forma y momento de utilizar {% data variables.product.product_name %}, puedes configurar los ajustes de tema para cambiar la forma en la que ves a {% data variables.product.product_name %}. Puedes elegir de entre los temas claros u oscuros o puedes configurar a {% data variables.product.product_name %} para que siga la configuración de tu sistema. +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. -Puede que quieras utilizar un tema oscuro para reducir el consumo de energía en algunos dispositivos, para reducir la fatiga ocular en condiciones de luz baja o porque te gusta más cómo se ve. +You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. -{% ifversion fpt or ghae-issue-4618 or ghec %} Si tu visión es limitada, puedes beneficiarte de un tema de contraste alto, con mayor contraste entre los elementos en primer y segundo plano.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} Si tienes daltonismo, puedes beneficiarte de nuestros temas claro y oscuro para daltónicos. +{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. {% note %} -**Nota:** Los temas para daltónicos se encuentran actualmente en un beta público. Para obtener más información o para habilitar las características del beta público, consulta la sección [Explorar los lanzamientos de acceso adelantado con vista previa de características](/get-started/using-github/exploring-early-access-releases-with-feature-preview)". +**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} {% endif %} {% data reusables.user_settings.access_settings %} -1. En la barra lateral de configuración de usuario, da clic en **Apariencia**. ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png) -2. Debajo de "Modo del tema", selecciona el menú desplegable y haz clic en una preferencia de tema. ![Menú desplegable debajo de "Modo del tema" para la selección de las preferencias del tema](/assets/images/help/settings/theme-mode-drop-down-menu.png) -3. Haz clic en el tema que quieres usar. - - Si eliges un tema simple, haz clic en un tema. - {% ifversion fpt or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - - Si eliges seguir tu configuración de sistema, haz clic en un tema de día y de noche. - {% ifversion fpt or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} +1. In the user settings sidebar, click **Appearance**. + + !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) + +1. Under "Theme mode", select the drop-down menu, then click a theme preference. + + ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png) +1. Click the theme you'd like to use. + - If you chose a single theme, click a theme. + + {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + - If you chose to follow your system settings, click a day theme and a night theme. + + {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghae-issue-4619 or ghec %} - - Si te gustaría elegir un tema que se encuentre actualmente en beta público, primero necesitas habilitarlo con la vista previa de características. Para obtener más información, consulta la sección [Explorar los lanzamientos de acceso adelantado con vista previa de características](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".{% endif %} + - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %} {% if command-palette %} @@ -49,6 +56,6 @@ Puede que quieras utilizar un tema oscuro para reducir el consumo de energía en {% endif %} -## Leer más +## Further reading -- "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" +- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md index b8434a7857..0e1db56667 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md @@ -1,6 +1,6 @@ --- -title: Fusionar cuentas de usuarios múltiples -intro: 'Si tienes cuentas separadas para uso laboral y personal, puedes fusionar las cuentas.' +title: Merging multiple user accounts +intro: 'If you have separate accounts for work and personal use, you can merge the accounts.' redirect_from: - /articles/can-i-merge-two-accounts/ - /articles/keeping-work-and-personal-repositories-separate/ @@ -12,19 +12,19 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Fusionar cuentas de usuario múltiples +shortTitle: Merge multiple user accounts --- - {% tip %} -**Sugerencia:** recomendamos utilizar únicamente una cuenta de usuario para administrar los repositorios personales y laborales. +**Tip:** We recommend using only one user account to manage both personal and professional repositories. {% endtip %} -1. [Transfiere cualquier repositorio](/articles/how-to-transfer-a-repository) desde la cuenta que deseas eliminar a la cuenta que deseas mantener. También se transfieren propuestas, solicitudes de extracción y wikis. Verifica que los repositorios existan en la cuenta que deseas mantener. -2. [Actualiza las URL remotas](/github/getting-started-with-github/managing-remote-repositories) en cualquier clon local de los repositorios que se movieron. -3. [Elimina la cuenta](/articles/deleting-your-user-account) que ya no deseas utilizar. +1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep. +2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved. +3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use. +4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" -## Leer más +## Further reading -- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" +- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 972fd164c2..cc38e874c5 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -1,6 +1,6 @@ --- -title: Niveles de permiso para un repositorio de cuenta de usuario -intro: 'Un repositorio que pertenece a una cuenta de usuario tiene dos niveles de permiso: propietario del repositorio y colaboradores.' +title: Permission levels for a user account repository +intro: 'A repository owned by a user account has two permission levels: the repository owner and collaborators.' redirect_from: - /articles/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository @@ -12,87 +12,80 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permisos bajo los repositorios +shortTitle: Permission user repositories --- +## About permissions levels for a user account repository -## Acerca de los niveles de permisos para un repositorio de una cuenta de usuario +Repositories owned by user accounts have one owner. Ownership permissions can't be shared with another user account. -Los repositorios que pertenecen a las cuentas de usuario tienen un propietario. Los permisos de propiedad no pueden compartirse con otra cuenta de usuario. - -También puedes {% ifversion fpt or ghec %}invitar{% else %}agregar{% endif %} usuarios de {% data variables.product.product_name %} a tu repositorio como colaboradores. Para obtener más información, consulta la sección "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)". +You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)." {% tip %} -**Tip:** Si necesitas un acceso más granular para un repositorio que le pertenezca a tu cuenta de usuario, considera transferirlo a una organización. Para obtener más información, consulta "[Transferir un repositorio](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)". +**Tip:** If you require more granular access to a repository owned by your user account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)." {% endtip %} -## Acceso de propietarios a un repositorio que pertenezca a una cuenta de usuario +## Owner access for a repository owned by a user account -El propietario del repositorio tiene control completo del repositorio. Adicionalmente a las acciones que pudiera realizar cualquier colaborador, el propietario del repositorio puede realizar las siguientes. +The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions. -| Acción | Más información | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% ifversion fpt or ghec %}Invitar colaboradores{% else %}Agregar colaboradores{% endif %} | | -| "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | -| Cambiar la visibilidad del repositorio | "[Configurar la visibilidad del repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %} -| Limitar las interacciones con el repositorio | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -| Renombrar una rama, incluyendo la rama predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" -{% endif %} -| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" | -| Eliminar el repositorio | "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)" | -| Administrar los temas del repositorio | "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %} -| Administrar la seguridad y la configuración de análisis del repositorio | "[Administrar la configuración de análisis y seguridad de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %} -| Habilitar la gráfica de dependencias para un repositorio privado | "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} -| Borrar y restablecer paquetes | "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes = 3.0 or ghae %} -| Borrar paquetes | "[Borrar paquetes](/packages/learn-github-packages/deleting-a-package)" -{% endif %} -| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalizar la vista previa de las redes sociales de tu repositorio](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Crear una plantilla del repositorio | "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| Control access to {% data variables.product.prodname_dependabot_alerts %} alerts for vulnerable dependencies | "[Administrar la configuración de análisis y seguridad de tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} -| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | -| Administrar el uso de datos para un repositorio privado | "[Administrar la configuración del uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)" -{% endif %} -| Definir propietarios del código para un repositorio | "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | -| Archivar el repositorio | "[Archivar repositorios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %} -| Crear asesorías de seguridad | "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Mostrar el botón del patrocinador | "[Mostrar un botón de patrocinador en tu repositorio](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% ifversion fpt or ghae or ghes > 3.0 or ghec %} -| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} +| Action | More information | +| :- | :- | +| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | +| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" | +| Delete the repository | "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)" | +| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %} +| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %} +| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} +| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes = 3.0 or ghae %} +| Delete packages | "[Deleting packages](/packages/learn-github-packages/deleting-a-package)" |{% endif %} +| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| Control access to {% data variables.product.prodname_dependabot_alerts %} alerts for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} +| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| Manage data use for a private repository | "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"|{% endif %} +| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %} +| Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% ifversion fpt or ghae or ghes > 3.0 or ghec %} +| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} -## Acceso de colaborador para un repositorio que pertenezca a una cuenta de usuario +## Collaborator access for a repository owned by a user account -Los colaboradores de un repositorio personal pueden extraer (leer) el contienido del mismo y subir (escribir) los cambios al repositorio. +Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository. {% note %} -**Nota:** en un repositorio privado, los propietarios del repositorio solo pueden otorgar acceso de escritura a los colaboradores. Los colaboradores no pueden tener acceso de solo lectura a los repositorio propiedad de una cuenta de usuario. +**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a user account. {% endnote %} -Los colaboradores también pueden realizar las siguientes acciones. +Collaborators can also perform the following actions. -| Acción | Más información | -|:-------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -| Renombrar una rama diferente a la predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" -{% endif %} -| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio |
    • "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)"
    • "[Comentar en una solilcitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Administrar los comentarios perjudiciales](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | -| Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio | "[Administrar tu trabajo con las propuestas](/github/managing-your-work-on-github/managing-your-work-with-issues)" | -| Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio | "[Etiquetar las propuestas y solicitudes de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | -| Administrar hitos para las propuestas y solicitudes de cambios en el repositorio | "[Crear y editar hitos para propuestas y solicitudes de extracción](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | -| Marcar una propuesta o solicitud de cambios en el repositorio como duplicada | "[Acerca de las propuestas y soicitudes de cambio duplicadas](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | -| Crear, fusionar y cerrar las solicitudes de cambios en el repositorio | "[Proponer cambios en tu trabajo con solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% ifversion fpt or ghae or ghes > 3.0 or ghec %} -| Habilitar e inhabilitar la fusión automática para una solicitud de cambios | "[Fusionar automáticamente una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %} -| Aplicar los cambios sugeridos a las solicitudes de cambios en el repositorio | "[Incorporar retroalimentación en tu solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | -| Crear una solicitud de cambios desde una bifurcación del repositorio | "[Crear una solicitud de extracción desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | -| Emitir una revisión de una solicitud de cambios que afecte la capacidad de fusión de una solicitud de cambios | "[Revisar los cambios propuestos en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | -| Crear y editar un wiki para el repositorio | "[Acerca de los wikis](/communities/documenting-your-project-with-wikis/about-wikis)" | -| Crear y editar los lanzamientos del repositorio | "[Administrar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)" | -| Actuar como propietario del código del repositorio | "[Acerca de los propietarios del código](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %} -| Publicar, ver o instalar paquetes | "[Publicar y mantener paquetes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" -{% endif %} -| Eliminarse como colaboradores del repositorio | "[Eliminarte a ti mismo del repositorio de un colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | +| Action | More information | +| :- | :- | +| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Create, edit, and delete comments on commits, pull requests, and issues in the repository |
    • "[About issues](/github/managing-your-work-on-github/about-issues)"
    • "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
    • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | +| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% ifversion fpt or ghae or ghes > 3.0 or ghec %} +| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"{% endif %} +| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" | +| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" | +| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" | +| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %} +| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | -## Leer más +## Further reading - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index 153b29d2e6..a1e1b56851 100644 --- a/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -1,7 +1,7 @@ --- -title: Almacenar los datos de los flujos de trabajo como artefactos -shortTitle: Almacenar artefactos de los flujos de trabajo -intro: Los artefactos te permiten compartir datos entre puestos en un flujo de trabajo y almacenar los datos una vez que se ha completado ese flujo de trabajo. +title: Storing workflow data as artifacts +shortTitle: Storing workflow artifacts +intro: Artifacts allow you to share data between jobs in a workflow and store data once that workflow has completed. redirect_from: - /articles/persisting-workflow-data-using-artifacts - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts @@ -22,51 +22,51 @@ topics: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de los artefactos de flujo de trabajo +## About workflow artifacts -Los artefactos te permiten hacer datos persistentes después de que se complete un job y comparten estos datos con otro job en el mismo flujo de trabajo. Un artefacto es un archivo o recopilación de archivos producidos durante una ejecución de flujo de trabajo. Por ejemplo, puedes utilizar artefactos para guardar tu compilación y probar el resultado después de que haya terminado una ejecución de flujo de trabajo. {% data reusables.actions.reusable-workflow-artifacts %} +Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %} -{% data reusables.github-actions.artifact-log-retention-statement %} El periodo de retención para una solicitud de cambios se reinicia cada vez que alguien sube una confirmación nueva en dicha solicitud. +{% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. -Estos son algunos de los artefactos comunes que puedes subir: +These are some of the common artifacts that you can upload: -- Archivos de registro y vaciados de memoria -- Resultados de prueba, fallas y capturas de pantalla -- Archivos binarios o comprimidos -- Resultados de la prueba de rendimiento y resultados de cobertura del código +- Log files and core dumps +- Test results, failures, and screenshots +- Binary or compressed files +- Stress test performance output and code coverage results {% ifversion fpt or ghec %} -Almacenar artefactos consume espacio de almacenamiento en {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Administrar la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". +Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)." {% else %} -Los artefactos caducan automáticamente después de 90 días, pero siempre puedes reclamar el almacenamiento utilizado de {% data variables.product.prodname_actions %} si borras artefactos antes de que caduquen en {% data variables.product.product_name %}. +Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.product.product_location %}. {% endif %} -Los artefactos se cargan durante una ejecución de flujo de trabajo y puedes ver el nombre y tamaño de estos en la IU. Cuando se descarga un artefacto utilizando la IU de {% data variables.product.product_name %}, todos los archivos que se hayan subido de manera individual como parte del mismo se comprimirán en un solo archivo. Esto significa que los costos se calcularán con base en el tamaño del artefacto cargado y no en aquél del archivo comprimido. +Artifacts are uploaded during a workflow run, and you can view an artifact's name and size in the UI. When an artifact is downloaded using the {% data variables.product.product_name %} UI, all files that were individually uploaded as part of the artifact get zipped together into a single file. This means that billing is calculated based on the size of the uploaded artifact and not the size of the zip file. -{% data variables.product.product_name %} proporciona dos acciones que puedes usar para cargar y descargar artefactos de construcción. Para obtener más información, consulta las acciones {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) y [download-artifact](https://github.com/actions/download-artifact){% else %} `actions/upload-artifact` y `download-artifact` en {% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} provides two actions that you can use to upload and download build artifacts. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.product.product_location %}{% endif %}. -Para compartir datos entre jobs: +To share data between jobs: -* **Cargar archivos**: Asigna un nombre al archivo cargado y sube los datos antes de que termine el job. -* **Descargar archivos**: Solo puedes descargar artefactos que se hayan subido durante la misma ejecución del flujo de trabajo. Cuando descargas un archivo, puedes referenciarlo por su nombre. +* **Uploading files**: Give the uploaded file a name and upload the data before the job ends. +* **Downloading files**: You can only download artifacts that were uploaded during the same workflow run. When you download a file, you can reference it by name. -Los pasos de un job comparten el mismo ambiente en la máquina ejecutora, pero se ejecutan en su propio proceso individual. Para pasar datos entre pasos en un job, puedes usar entradas y salidas. Para obtener más información sobre entradas y salidas, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)". +The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)." -## Cargar artefactos de construcción y prueba +## Uploading build and test artifacts -Puedes crear un flujo de trabajo de integración continua (CI) para construir y probar tu código. Para obtener más información acerca de cómo utilizar {% data variables.product.prodname_actions %} para realizar la IC, consulta la sección "[Acerca de la integración contínua](/articles/about-continuous-integration)". +You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)." -El resultado de la construcción y la prueba de tu código frecuentemente produce archivos que puedes usar para depurar fallas de prueba y códigos de producción que puedes implementar. Puedes configurar un flujo de trabajo para construir y probar el código subido a tu repositorio e informar un estado satisfactorio o de falla. Puedes cargar los resultados de construcción y prueba para usar en implementaciones, pruebas de depuración fallidas o fallos, y para visualizar la cobertura del conjunto de prueba. +The output of building and testing your code often produces files you can use to debug test failures and production code that you can deploy. You can configure a workflow to build and test the code pushed to your repository and report a success or failure status. You can upload the build and test output to use for deployments, debugging failed tests or crashes, and viewing test suite coverage. -Puedes usar la acción `upload-Artifact` para cargar artefactos. Cuando cargues un artefacto, puedes especificar un archivo sencillo o un directorio, o varios archivos o directorios. También puedes excluir ciertos archivos o directorios y utilizar patrones de comodín. Te recomendamos que proporciones un nombre para cada artefacto pero, si no se lo das, entonces el nombre predeterminado que se utilizará será `artifact`. Para obtener más información sobre la sintaxis, consulta la acción {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact){% else %} `actions/upload-artifact` en {% data variables.product.product_location %}{% endif %}. +You can use the `upload-artifact` action to upload artifacts. When uploading an artifact, you can specify a single file or directory, or multiple files or directories. You can also exclude certain files or directories, and use wildcard patterns. We recommend that you provide a name for an artifact, but if no name is provided then `artifact` will be used as the default name. For more information on syntax, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) action{% else %} `actions/upload-artifact` action on {% data variables.product.product_location %}{% endif %}. -### Ejemplo +### Example -Por ejemplo, tu repositorio o una aplicación web podrían contener archivos de SASS y TypeScript que debes convertir a CSS y JavaScript. Teniendo en cuenta que tu configuración de construcción envía los archivos compilados al directorio `dist`, puedes implementar los archivos en el directorio `dist` para tu servidor de aplicación web si todas las pruebas se completaron satisfactoriamente. +For example, your repository or a web application might contain SASS and TypeScript files that you must convert to CSS and JavaScript. Assuming your build configuration outputs the compiled files in the `dist` directory, you would deploy the files in the `dist` directory to your web application server if all tests completed successfully. ``` |-- hello-world (repository) @@ -80,9 +80,9 @@ Por ejemplo, tu repositorio o una aplicación web podrían contener archivos de | ``` -En este ejemplo se muestra cómo crear un flujo de trabajo para un proyecto Node.js que construye el código en el directorio `src` y ejecuta las pruebas en el directorio `tests`. Puedes suponer que la ejecución `npm test` produce un informe de cobertura de código denominado `code-coverage.html` almacenada en el directorio `output/test/`. +This example shows you how to create a workflow for a Node.js project that builds the code in the `src` directory and runs the tests in the `tests` directory. You can assume that running `npm test` produces a code coverage report named `code-coverage.html` stored in the `output/test/` directory. -El flujo de trabajo carga los artefactos de producción en el directorio `dist`, pero excluye cualquier archivo de markdown. También carga el reporte `code-coverage.html` como otro artefacto. +The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also uploads the `code-coverage.html` report as another artifact. ```yaml{:copy} name: Node CI @@ -114,9 +114,9 @@ jobs: path: output/test/code-coverage.html ``` -## Configurar un periodo de retención de artefactos personalizado +## Configuring a custom artifact retention period -Puedes definir un periodo de retención personalizado para los artefactos indivudales que crea un flujo de trabajo. Cuando utilices un flujo de trabajo para crear un artefacto nuevo, puedes utilizar `retention-days` con la acción `upload-artifact`. Este ejemplo ilustra cómo configurar un periodo de retención personalizado de 5 días para el artefacto que se llama `my-artifact`: +You can define a custom retention period for individual artifacts created by a workflow. When using a workflow to create a new artifact, you can use `retention-days` with the `upload-artifact` action. This example demonstrates how to set a custom retention period of 5 days for the artifact named `my-artifact`: ```yaml{:copy} - name: 'Upload Artifact' @@ -127,25 +127,25 @@ Puedes definir un periodo de retención personalizado para los artefactos indivu retention-days: 5 ``` -El valor `retention-days` no puede exceder el límite de retención que configuró el repositorio, organización o empresa. +The `retention-days` value cannot exceed the retention limit set by the repository, organization, or enterprise. -## Descargar o eliminar artefactos +## Downloading or deleting artifacts -Durante una ejecución de flujo de trabajo, puedes utilizar la acción [`download-artifact`](https://github.com/actions/download-artifact) para descargar artefactos que se hayan cargado previamente en la misma ejecución de flujo de trabajo. +During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run. -Después de que se haya completado una ejecución de flujo de trabajo, puedes descargar o borrar los artefactos en {% data variables.product.prodname_dotcom %} o utilizando la API de REST. Para obtener más información, consulta las secciones "[Descargar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)", "[eliminar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/removing-workflow-artifacts)", y la "[API de REST de Artefactos](/rest/reference/actions#artifacts)". +After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." -### Descargar artefactos durante una ejecución de flujo de trabajo +### Downloading artifacts during a workflow run -La acción [`actions/download-artifact`](https://github.com/actions/download-artifact) puede utilizarse para descargar artefactos que se hayan cargado previamente durante una ejecución de flujo de trabajo. +The [`actions/download-artifact`](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run. {% note %} -**Nota:** Solo podrás descargar los artefactos que se hayan cargado durante la misma ejecución de flujo de trabajo. +**Note:** You can only download artifacts in a workflow that were uploaded during the same workflow run. {% endnote %} -Especificar el nombre de un artefacto para descargar un artefacto individual. Si cargaste un artefacto sin especificar un nombre, el nombre predeterminado de éste será `artifact`. +Specify an artifact's name to download an individual artifact. If you uploaded an artifact without specifying a name, the default name is `artifact`. ```yaml - name: Download a single artifact @@ -154,37 +154,37 @@ Especificar el nombre de un artefacto para descargar un artefacto individual. Si name: my-artifact ``` -También puedes descargar todos los artefactos en una ejecución de flujo de trabajo si no especificas un nombre para éstos. Esto puede ser útil si estás trabajando con muchos artefactos. +You can also download all artifacts in a workflow run by not specifying a name. This can be useful if you are working with lots of artifacts. ```yaml - name: Download all workflow run artifacts uses: actions/download-artifact@v2 ``` -Si descargas todos los artefactos de una ejecución de flujo de trabajo, se creará un directorio para cada uno de ellos utilizando su nombre. +If you download all workflow run's artifacts, a directory for each artifact is created using its name. -Para obtener más información sobre la sintaxis, consulta la acción {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact){% else %} `actions/download-artifact` en {% data variables.product.product_location %}{% endif %}. +For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.product.product_location %}{% endif %}. -## Pasar datos entre jobs en un flujo de trabajo +## Passing data between jobs in a workflow -Puedes usar las acciones `upload-artifact` y `download-artifact` para compartir datos entre jobs en un flujo de trabajo. Este flujo de trabajo de ejemplo ilustra cómo pasar datos entre jobs en el mismo flujo de trabajo. Para obtener más información, consulta las acciones {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) y [download-artifact](https://github.com/actions/download-artifact){% else %} `actions/upload-artifact` y `download-artifact` en {% data variables.product.product_location %}{% endif %}. +You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.product.product_location %}{% endif %}. -Los jobs que dependen de los artefactos de un trabajo anterior deben esperar que el trabajo dependiente se complete exitosamente. Este flujo de trabajo usa la palabra clave `needs` para garantizar que `job_1`, `job_2` y `job_3` se ejecuten secuencialmente. Por ejemplo, `job_2` requiere `job_1` mediante la sintaxis `needs: job_1`. +Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax. -El job 1 realiza estos pasos: -- Realiza un cálculo matemático y guarda el resultado en un archivo de texto llamado `math-homework.txt`. -- Utiliza la acción `upload-artifact` para cargar el archivo `math-homework.txt` con el nombre de archivo `homework`. +Job 1 performs these steps: +- Performs a math calculation and saves the result to a text file called `math-homework.txt`. +- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`. -El job 2 usa el resultado del trabajo anterior: -- Descarga el artefacto `homework` cargado en el trabajo anterior. De manera predeterminada, la acción `download-artifact` descarga artefactos en el directorio del espacio de trabajo que ejecuta el paso. Puedes utilizar el parámetro de entrada `path` para especificar un directorio de descarga diferente. -- Lee el valor en el archivo `math-homework.txt`, realiza un cálculo matemático, y guarda el resultado en `math-homework.txt` nuevamente, sobreescribiendo su contenido. -- Carga el archivo `math-homework.txt`. Esta carga sobreescribe el artefacto que se cargó previamente, ya que comparten el mismo nombre. +Job 2 uses the result in the previous job: +- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory. +- Reads the value in the `math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt` again, overwriting its contents. +- Uploads the `math-homework.txt` file. This upload overwrites the previously uploaded artifact because they share the same name. -El job 3 muestra el resultado cargado en el trabajo anterior: -- Descarga el artefacto `homework`. -- Imprime el resultado de la ecuación matemática en el registro. +Job 3 displays the result uploaded in the previous job: +- Downloads the `homework` artifact. +- Prints the result of the math equation to the log. -La operación matemática completa realizada en este ejemplo de flujo de trabajo es `(3 + 7) x 9 = 90`. +The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`. ```yaml{:copy} name: Share data between jobs @@ -240,17 +240,17 @@ jobs: echo The result is $value ``` -La ejecución de flujo de trabajo archivará cualquier artefacto que haya generado. Para obtener más información sobre cómo descargar los artefactos archivados, consulta la sección "[Descargar artefactos de flujo de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)". +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -![Flujo de trabajo que pasa datos entre jobs para realizar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) {% else %} -![Flujo de trabajo que pasa datos entre jobs para realizar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) {% endif %} {% ifversion fpt or ghec %} -## Leer más +## Further reading -- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". {% endif %} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index bcbec59c70..e1bc4db7ac 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -1,6 +1,6 @@ --- -title: Compilar y probar PowerShell -intro: Puedes crear un flujo de trabajo de integración continua (IC) para compilar y probar tu proyecto de PowerShell. +title: Building and testing PowerShell +intro: You can create a continuous integration (CI) workflow to build and test your PowerShell project. redirect_from: - /actions/guides/building-and-testing-powershell versions: @@ -13,39 +13,39 @@ authors: type: tutorial topics: - CI - - Powershell -shortTitle: Compila & prueba PowerShell + - PowerShell +shortTitle: Build & test PowerShell --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Introducción +## Introduction -Esta guía te muestra cómo utilizar PowerShell para la IC. Describimos cómo utilizar Pester, instalar dependencias, probar tu módulo y publicarlo en la galería de PowerShell. +This guide shows you how to use PowerShell for CI. It describes how to use Pester, install dependencies, test your module, and publish to the PowerShell Gallery. -Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software pre-instalado, lo cual incluye a PowerShell y a Pester. +{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes PowerShell and Pester. -{% ifversion ghae %}Para obtener instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tiene instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". -{% else %}Para encontrar una lista completa de software actualizado y de las versiones preinstaladas de PowerShell y Pester, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +{% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." +{% else %}For a full list of up-to-date software and the pre-installed versions of PowerShell and Pester, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} -## Prerrequisitos +## Prerequisites -Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -Te recomendamos tener un entendimiento básico de PowerShell y de Pester. Para obtener más información, consulta: -- [Iniciar con PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) +We recommend that you have a basic understanding of PowerShell and Pester. For more information, see: +- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) - [Pester](https://pester.dev) {% data reusables.actions.enterprise-setup-prereq %} -## Agregar un flujo de trabajo para Pester +## Adding a workflow for Pester -Para automatizar tus pruebas con PowerShell y con Pester, puedes agregar un flujo de trabajo que se ejecute cada que se sube un cambio en tu repositorio. En el siguiente ejemplo, se utiliza `Test-Path` para verificar la presencia de un archivo que se llama `resultsfile.log`. +To automate your testing with PowerShell and Pester, you can add a workflow that runs every time a change is pushed to your repository. In the following example, `Test-Path` is used to check that a file called `resultsfile.log` is present. -Este ejemplo de archivo de flujo de trabajo debe agregarse al directorio `.github/workflows/` de tu repositorio: +This example workflow file must be added to your repository's `.github/workflows/` directory: {% raw %} ```yaml @@ -69,17 +69,17 @@ jobs: ``` {% endraw %} -* `shell: pwsh` - Configura el job para que utilice PowerShell cuando ejecutas los comandos de `run`. -* `run: Test-Path resultsfile.log` - Revisa si un archivo que se llama `resultsfile.log` está presente en el directorio raíz del repositorio. -* `Should -Be $true` - Utiliza Pester para definir un resultado esperado. Si el resultado es inesperado, entonces {% data variables.product.prodname_actions %} lo marca como una prueba fallida. Por ejemplo: +* `shell: pwsh` - Configures the job to use PowerShell when running the `run` commands. +* `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory. +* `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. For example: {% ifversion fpt or ghes > 3.0 or ghae or ghec %} - ![Prueba fallida de Pester](/assets/images/help/repository/actions-failed-pester-test-updated.png) + ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png) {% else %} - ![Prueba fallida de Pester](/assets/images/help/repository/actions-failed-pester-test.png) + ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) {% endif %} -* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Utiliza Pester para ejecutar las pruebas que se definen en un archivo que se llama `Unit.Tests.ps1`. Por ejempo, para realizar la misma prueba que se describe anteriormente, el `Unit.Tests.ps1` contendrá lo siguiente: +* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following: ``` Describe "Check results file is present" { It "Check results file is present" { @@ -88,29 +88,29 @@ jobs: } ``` -## Ubicaciones de los módulos de PowerShell +## PowerShell module locations -En la siguiente tabla se describen las ubicaciones para varios módulos de PowerShell en cada ejecutor hospedado en {% data variables.product.prodname_dotcom %}. +The table below describes the locations for various PowerShell modules in each {% data variables.product.prodname_dotcom %}-hosted runner. -| | Ubuntu | macOS | Windows | -| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ | -| **Módulos de sistema de PowerShell** | `/opt/microsoft/powershell/7/Modules/*` | `/usr/local/microsoft/powershell/7/Modules/*` | `C:\program files\powershell\7\Modules\*` | -| **Módulos complementarios de PowerShell** | `/usr/local/share/powershell/Modules/*` | `/usr/local/share/powershell/Modules/*` | `C:\Modules\*` | -| **Módulos instalados por el usuario** | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` | +|| Ubuntu | macOS | Windows | +|------|-------|------|----------| +|**PowerShell system modules** |`/opt/microsoft/powershell/7/Modules/*`|`/usr/local/microsoft/powershell/7/Modules/*`|`C:\program files\powershell\7\Modules\*`| +|**PowerShell add-on modules**|`/usr/local/share/powershell/Modules/*`|`/usr/local/share/powershell/Modules/*`|`C:\Modules\*`| +|**User-installed modules**|`/home/runner/.local/share/powershell/Modules/*`|`/Users/runner/.local/share/powershell/Modules/*`|`C:\Users\runneradmin\Documents\PowerShell\Modules\*`| -## Instalar dependencias +## Installing dependencies -Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen PowerShell 7 y Pester instalados. Puedes utilizar `Install-Module` para instalar dependencias adicionales de la galería de PowerShell antes de compilar y probar tu código. +{% data variables.product.prodname_dotcom %}-hosted runners have PowerShell 7 and Pester installed. You can use `Install-Module` to install additional dependencies from the PowerShell Gallery before building and testing your code. {% note %} -**Note:** Los paquetes pre-instalados (tales como Pester) que utilizan los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se actualizan frecuentemente y pueden introducir cambios significativos. Como resultado, se recomienda que siempre especifiques las versiones de los paquetes requeridos utilizando `Install-Module` con `-MaximumVersion`. +**Note:** The pre-installed packages (such as Pester) used by {% data variables.product.prodname_dotcom %}-hosted runners are regularly updated, and can introduce significant changes. As a result, it is recommended that you always specify the required package versions by using `Install-Module` with `-MaximumVersion`. {% endnote %} -Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, también puedes guardar las dependencias en el caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." -Por ejemplo, el siguiente job instala los módulos de `SqlServer` y `PSScriptAnalyzer`: +For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: {% raw %} ```yaml @@ -130,15 +130,15 @@ jobs: {% note %} -**Note:** Predeterminadamente, PowerShell no confía en ningún repositorio. Cuando instales módulos desde la galería de PowerShell, debes configurar explícitamente la política de instalación de `PSGallery` en `Trusted`. +**Note:** By default, no repositories are trusted by PowerShell. When installing modules from the PowerShell Gallery, you must explicitly set the installation policy for `PSGallery` to `Trusted`. {% endnote %} -### Almacenar dependencias en caché +### Caching dependencies -Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar dependencias de PowerShell en el caché utilizando una clave única, lo cual te permite restaurar las dependencias para flujos de trabajo futuros con la acción [`cache`](https://github.com/marketplace/actions/cache). Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "Caching dependencies to speed up workflows." -PowerShell guarda sus dependencias en caché en ubicaciones diferentes, dependiendo del sistema operativo del ejecutor. Por ejemplo, el `path` de la ubicación que se utiliza en el siguiente ejemplo de Ubuntu será diferente a aquél de un sistema operativo Windows. +PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system. {% raw %} ```yaml @@ -159,13 +159,13 @@ steps: ``` {% endraw %} -## Probar tu código +## Testing your code -Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. +You can use the same commands that you use locally to build and test your code. -### Utilizar PSScriptAnalyzer para limpiar el código +### Using PSScriptAnalyzer to lint code -El siguiente ejemplo instala `PSScriptAnalyzer` y lo utiliza para limpiar todos los archivos `ps1` en el repositorio. Para obtener más información, consulta [PSScriptAnalyzer en GitHub](https://github.com/PowerShell/PSScriptAnalyzer). +The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` files in the repository. For more information, see [PSScriptAnalyzer on GitHub](https://github.com/PowerShell/PSScriptAnalyzer). {% raw %} ```yaml @@ -193,11 +193,11 @@ El siguiente ejemplo instala `PSScriptAnalyzer` y lo utiliza para limpiar todos ``` {% endraw %} -## Empaquetar datos de flujo de trabajo como artefactos +## Packaging workflow data as artifacts -Puedes cargar artefactos para ver después de que se complete un flujo de trabajo. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." -El siguiente ejemplo ilustra cómo puedes utilizar la acción `upload-artifact` para archivar los resultados de las pruebas que se recibieron de `Invoke-Pester`. Para obtener más información, consulta la acción [`upload-artifact`](https://github.com/actions/upload-artifact). +The following example demonstrates how you can use the `upload-artifact` action to archive the test results received from `Invoke-Pester`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact). {% raw %} ```yaml @@ -223,13 +223,13 @@ jobs: ``` {% endraw %} -La función `always()` configura el job para seguir el procesamiento aún si existen fallos en las pruebas. Para obtener más información, consulta "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)". +The `always()` function configures the job to continue processing even if there are test failures. For more information, see "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)." -## Publicar en la galería de PowerShell +## Publishing to PowerShell Gallery -Puedes configurar tu flujo de trabajo para que publique tu módulo de PowerShell en la galería de PowerShell cuando pasen tus pruebas de IC. Puedes utilizar los secretos para almacenar cualquier token o credencial que se necesiten para publicar tu paquete. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." +You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." -El siguiente ejemplo crea un paquete y utiliza a `Publish-Module` para publicarlo en la galería de PowerShell: +The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery: {% raw %} ```yaml diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md index 1061cd66a4..9b0b916538 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -1,6 +1,6 @@ --- -title: Crear y probar en Python -intro: Puedes crear un flujo de trabajo de integración continua (CI) para construir y probar tu proyecto de Python. +title: Building and testing Python +intro: You can create a continuous integration (CI) workflow to build and test your Python project. redirect_from: - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions - /actions/language-and-framework-guides/using-python-with-github-actions @@ -15,7 +15,7 @@ hidden: true topics: - CI - Python -shortTitle: Crear & probar con Python +shortTitle: Build & test Python hasExperimentalAlternative: true --- @@ -23,30 +23,30 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Introducción +## Introduction -Esta guía te muestra cómo construir, probar y publicar un paquete de Python. +This guide shows you how to build, test, and publish a Python package. -{% ifversion ghae %} Consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)" para obtener instrucciones para asegurarte de que tu {% data variables.actions.hosted_runner %} tiene instalado el software necesario. -{% else %}Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen una caché de herramientas con un software preinstalado que incluye Python y PyPy. ¡No tienes que instalar nada! Para obtener una lista completa de software actualizado y de las versiones preinstaladas de Python y PyPy, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +{% ifversion ghae %} For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." +{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anything! For a full list of up-to-date software and the pre-installed versions of Python and PyPy, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} -## Prerrequisitos +## Prerequisites -Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -Te recomendamos que tengas una comprensión básica de Python, PyPy y pip. Para obtener más información, consulta: -- [Comenzar con Python](https://www.python.org/about/gettingstarted/) +We recommend that you have a basic understanding of Python, PyPy, and pip. For more information, see: +- [Getting started with Python](https://www.python.org/about/gettingstarted/) - [PyPy](https://pypy.org/) -- [Administrador de paquetes pip](https://pypi.org/project/pip/) +- [Pip package manager](https://pypi.org/project/pip/) {% data reusables.actions.enterprise-setup-prereq %} -## Comenzar con la plantilla de flujo de trabajo de Python +## Starting with the Python workflow template -{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Python que debería funcionar para la mayoría de los proyectos de Python. Esta guía incluye ejemplos que puedes usar para personalizar la plantilla. Para obtener más información, consulta la [Plantilla de flujo de trabajo de Python](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml). +{% data variables.product.prodname_dotcom %} provides a Python workflow template that should work for most Python projects. This guide includes examples that you can use to customize the template. For more information, see the [Python workflow template](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml). -Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. +To get started quickly, add the template to the `.github/workflows` directory of your repository. {% raw %} ```yaml{:copy} @@ -60,7 +60,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - python-version: [3.6, 3.7, 3.8, 3.9] + python-version: ["3.6", "3.7", "3.8", "3.9"] steps: - uses: actions/checkout@v2 @@ -85,25 +85,25 @@ jobs: ``` {% endraw %} -## Especificar una versión de Python +## Specifying a Python version -Para usar una versión preinstalada de Python o PyPy en un ejecutor alojado {% data variables.product.prodname_dotcom %}, usa la acción `setup-python`. Esta acción encuentra una versión específica de Python o PyPy desde la caché de herramientas en cada ejecutor y agrega los binarios necesarios para `PATH`, que persiste durante el resto del trabajo. Si una versión específica de Python no está pre-instalada en el cache de herramientas, la acción `setup-python` se descargará y configurará la versión adecuada desde el repositorio `python-versions`. +To use a pre-installed version of Python or PyPy on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-python` action. This action finds a specific version of Python or PyPy from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. If a specific version of Python is not pre-installed in the tools cache, the `setup-python` action will download and set up the appropriate version from the [`python-versions`](https://github.com/actions/python-versions) repository. -Usar el `setup-action` es la forma recomendada de usar Python con {% data variables.product.prodname_actions %} porque garantiza un comportamiento consistente a través de diferentes ejecutores y diferentes versiones de Python. Si estás usando un ejecutor alojado, debes instalar Python y añadirlo a `PATH`. Para obtener más información, consulta la acción [`setup-python`](https://github.com/marketplace/actions/setup-python). +Using the `setup-python` action is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. If you are using a self-hosted runner, you must install Python and add it to `PATH`. For more information, see the [`setup-python` action](https://github.com/marketplace/actions/setup-python). -La tabla que aparece a continuación describe las ubicaciones de la caché de herramientas en cada ejecutor alojado {% data variables.product.prodname_dotcom %}. +The table below describes the locations for the tools cache in each {% data variables.product.prodname_dotcom %}-hosted runner. -| | Ubuntu | Mac | Windows | -| --------------------------------------- | ------------------------------- | ---------------------------------------- | ------------------------------------------ | -| **Directorio de caché de herramientas** | `/opt/hostedtoolcache/*` | `/Users/runner/hostedtoolcache/*` | `C:\hostedtoolcache\windows\ *` | -| **Caché de herramientas de Python** | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\ *` | -| **Caché de la herramienta de PyPy** | `/opt/hostedtoolcache/PyPy/*` | `/Users/runner/hostedtoolcache/PyPy/*` | `C:\hostedtoolcache\windows\PyPy\ *` | +|| Ubuntu | Mac | Windows | +|------|-------|------|----------| +|**Tool Cache Directory** |`/opt/hostedtoolcache/*`|`/Users/runner/hostedtoolcache/*`|`C:\hostedtoolcache\windows\*`| +|**Python Tool Cache**|`/opt/hostedtoolcache/Python/*`|`/Users/runner/hostedtoolcache/Python/*`|`C:\hostedtoolcache\windows\Python\*`| +|**PyPy Tool Cache**|`/opt/hostedtoolcache/PyPy/*`|`/Users/runner/hostedtoolcache/PyPy/*`|`C:\hostedtoolcache\windows\PyPy\*`| -Si estás utilizando un ejecutor auto-hospedado, puedes configurarlo para utilizar la acción `setup-python` para administrar tus dependencias. Para obtener más información, consulta la sección [utilizar setup-python con un ejecutor auto-hospedado](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) en el README de `setup-python`. +If you are using a self-hosted runner, you can configure the runner to use the `setup-python` action to manage your dependencies. For more information, see [using setup-python with a self-hosted runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in the `setup-python` README. -{% data variables.product.prodname_dotcom %} admite la sintaxis de control de versiones semántico. Para obtener más información, consulta "[Usar versiones semánticas](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" y "[Especificación de control de versiones semántico](https://semver.org/)." +{% data variables.product.prodname_dotcom %} supports semantic versioning syntax. For more information, see "[Using semantic versioning](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" and the "[Semantic versioning specification](https://semver.org/)." -### Usar múltiples versiones de Python +### Using multiple Python versions {% raw %} ```yaml{:copy} @@ -116,10 +116,10 @@ jobs: runs-on: ubuntu-latest strategy: - # Puedes usar las versiones de PyPy en python-version. + # You can use PyPy versions in python-version. # For example, pypy2 and pypy3 matrix: - python-version: [2.7, 3.6, 3.7, 3.8, 3.9] + python-version: ["2.7", "3.6", "3.7", "3.8", "3.9"] steps: - uses: actions/checkout@v2 @@ -133,9 +133,9 @@ jobs: ``` {% endraw %} -### Usar una versión de Python específica +### Using a specific Python version -Puedes configurar una versión específica de Python. Por ejemplo, 3.8. Como alternativa, puedes utilizar una sintaxis de versión semántica para obtener el último lanzamiento menor. En este ejemplo se usa el último lanzamiento menor de Python 3. +You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. {% raw %} ```yaml{:copy} @@ -163,11 +163,11 @@ jobs: ``` {% endraw %} -### Excluir una versión +### Excluding a version -Si especificas una versión de Python que no está disponible, `setup-python` falla con un error como: `##[error]Versión 3.4 con Arch x64 not found`. El mensaje de error incluye las versiones disponibles. +If you specify a version of Python that is not available, `setup-python` fails with an error such as: `##[error]Version 3.4 with arch x64 not found`. The error message includes the available versions. -También puedes usar la palabra clave `exclude` en tu flujo de trabajo si hay una configuración de Python que no deseas ejecutar. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)". +You can also use the `exclude` keyword in your workflow if there is a configuration of Python that you do not wish to run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)." {% raw %} ```yaml{:copy} @@ -182,30 +182,30 @@ jobs: strategy: matrix: os: [ubuntu-latest, macos-latest, windows-latest] - python-version: [3.6, 3.7, 3.8, 3.9, pypy2, pypy3] + python-version: ["3.6", "3.7", "3.8", "3.9", pypy2, pypy3] exclude: - os: macos-latest - python-version: 3.6 + python-version: "3.6" - os: windows-latest - python-version: 3.6 + python-version: "3.6" ``` {% endraw %} -### Usar la versión de Python predeterminada +### Using the default Python version -Recomendamos usar `setup-python` para configurar la versión de Python que se usa en tus flujos de trabajo porque ayuda a hacer que tus dependencias sean explícitas. Si no usas `setup-python`, la versión predeterminada de Python establecida en `PATH` se usa en cualquier shell cuando llamas `python`. La versión predeterminada de Python varía entre los ejecutores alojados {% data variables.product.prodname_dotcom %}, que pueden causar cambios inesperados o usar una versión anterior a la esperada. +We recommend using `setup-python` to configure the version of Python used in your workflows because it helps make your dependencies explicit. If you don't use `setup-python`, the default version of Python set in `PATH` is used in any shell when you call `python`. The default version of Python varies between {% data variables.product.prodname_dotcom %}-hosted runners, which may cause unexpected changes or use an older version than expected. -| Ejecutor alojado {% data variables.product.prodname_dotcom %} | Descripción | -| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Ubuntu | Los ejecutores de Ubuntu tienen múltiples versiones de Python del sistema instaladas bajo `/usr/bin/python` y `/usr/bin/python3`. Las versiones de Python que vienen empaquetadas con Ubuntu se suman a las versiones que {% data variables.product.prodname_dotcom %} instala en la caché de herramientas. | -| Windows | Excluyendo las versiones de Python que están en la caché de herramientas, Windows no se envía con una versión equivalente de Python del sistema. Para mantener un comportamiento consistente con otros ejecutores y para permitir que Python se use de forma integrada sin la acción `setup-python`, {% data variables.product.prodname_dotcom %} agrega algunas versiones desde la caché de herramientas a `PATH`. | -| macOS | Los ejecutores de macOS tienen más de una versión de Python del sistema instalada, además de las versiones que son parte de la caché de las herramientas. Las versiones de Python del sistema se encuentran en el directorio `/usr/local/Cellar/python/*`. | +| {% data variables.product.prodname_dotcom %}-hosted runner | Description | +|----|----| +| Ubuntu | Ubuntu runners have multiple versions of system Python installed under `/usr/bin/python` and `/usr/bin/python3`. The Python versions that come packaged with Ubuntu are in addition to the versions that {% data variables.product.prodname_dotcom %} installs in the tools cache. | +| Windows | Excluding the versions of Python that are in the tools cache, Windows does not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the `setup-python` action, {% data variables.product.prodname_dotcom %} adds a few versions from the tools cache to `PATH`.| +| macOS | The macOS runners have more than one version of system Python installed, in addition to the versions that are part of the tools cache. The system Python versions are located in the `/usr/local/Cellar/python/*` directory. | -## Instalar dependencias +## Installing dependencies -Los ejecutores alojados {% data variables.product.prodname_dotcom %} tienen instalado el administrador del paquete pip. Puedes usar pip para instalar dependencias desde el registro del paquete de PyPI antes de construir y probar tu código. Por ejemplo, el YAML que aparece a continuación instala o actualiza el instalador del paquete `pip` y los paquetes `setuptools` y `wheel`. +{% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages. -Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, también puedes guardar las dependencias en el caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." {% raw %} ```yaml{:copy} @@ -220,9 +220,9 @@ steps: ``` {% endraw %} -### Archivo de requisitos +### Requirements file -Después de actualizar `pip`, un siguiente paso típico es instalar dependencias desde *requirements.txt*. Para obtener más información, consulta la sección de [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file). +After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file). {% raw %} ```yaml{:copy} @@ -239,48 +239,34 @@ steps: ``` {% endraw %} -### Dependencias de almacenamiento en caché +### Caching Dependencies -Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar las dependencias pip en el caché utilizando una clave única y restaurar las dependencias cuando ejecutes flujos de trabajo subsecuentes, utilizando la acción [`cache`](https://github.com/marketplace/actions/cache). Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python). -Pip almacena en caché las dependencias en diferentes ubicaciones, en función del sistema operativo del ejecutor. La ruta que necesitarás para almacenar en caché puede diferir del ejemplo de Ubuntu que aparece a continuación, según el sistema operativo que uses. Para obtener más información, consulta los [Ejemplos de almacenamiento en caché de Python](https://github.com/actions/cache/blob/main/examples.md#python---pip). +The following example caches dependencies for pip. -{% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 -- name: Setup Python - uses: actions/setup-python@v2 +- uses: actions/setup-python@v2 with: - python-version: '3.x' -- name: Cache pip - uses: actions/cache@v2 - with: - # This path is specific to Ubuntu - path: ~/.cache/pip - # Look to see if there is a cache hit for the corresponding requirements file - key: ${{ runner.os }}-pip-${{ hashFiles('requirements.txt') }} - restore-keys: | - ${{ runner.os }}-pip- - ${{ runner.os }}- -- name: Install dependencies - run: pip install -r requirements.txt + python-version: '3.9' + cache: 'pip' +- run: pip install -r requirements.txt +- run: pip test ``` -{% endraw %} -{% note %} +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "Caching packages dependencies" in the `setup-python` actions README. -**Nota:** Dependiendo de la cantidad de dependencias, puede ser más rápido usar la caché de dependencias. Los proyectos con muchas dependencias de gran tamaño deberían ver un aumento del rendimiento, ya que reduce el tiempo necesario para la descarga. Los proyectos con menos dependencias pueden no ver un aumento significativo del rendimiento e incluso pueden ver una ligera disminución debido a la manera en que pip instala las dependencias almacenadas en caché. El rendimiento varía de un proyecto a otro. +If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository. -{% endnote %} +## Testing your code -## Probar tu código +You can use the same commands that you use locally to build and test your code. -Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. +### Testing with pytest and pytest-cov -### Pruebas con pytest y pytest-cov - -Este ejemplo instala o actualiza `pytest` y `pytest-cov`. A continuación, se ejecutan y se emiten pruebas en formato JUnit, mientras que los resultados de la cobertura de código se emiten en Cobertura. Para obtener más información, consulta [JUnit](https://junit.org/junit5/) y [Cobertura](https://cobertura.github.io/Cobertura/). +This example installs or upgrades `pytest` and `pytest-cov`. Tests are then run and output in JUnit format while code coverage results are output in Cobertura. For more information, see [JUnit](https://junit.org/junit5/) and [Cobertura](https://cobertura.github.io/cobertura/). {% raw %} ```yaml{:copy} @@ -302,9 +288,9 @@ steps: ``` {% endraw %} -### Usar Flake8 para el código lint +### Using Flake8 to lint code -En el siguiente ejemplo se instala o actualiza `flake8` y se usa para limpiar todos los archivos. Para obtener más información, consulta [Flake8](http://flake8.pycqa.org/en/latest/). +The following example installs or upgrades `flake8` and uses it to lint all files. For more information, see [Flake8](http://flake8.pycqa.org/en/latest/). {% raw %} ```yaml{:copy} @@ -326,11 +312,11 @@ steps: ``` {% endraw %} -El paso de limpieza de código se configuró con `continue-on-error: true`. Esto prevendrá que el flujo de trabajo falle si el paso de limpieza de código no tiene éxito. Una vez que hayas abordado todos los errores de limpieza de código, puedes eliminar esta opción para que el flujo de trabajo atrape propuestas nuevas. +The linting step has `continue-on-error: true` set. This will keep the workflow from failing if the linting step doesn't succeed. Once you've addressed all of the linting errors, you can remove this option so the workflow will catch new issues. -### Ejecutar pruebas con tox +### Running tests with tox -Con {% data variables.product.prodname_actions %}, puedes ejecutar pruebas con tox y repartir el trabajo a través de múltiples trabajos. Necesitarás invocar tox utilizando la opción `-e py` para elegir la versión de Python en tu `PATH`, en lugar de especificar una versión específica. Para obtener más información, consulta [tox](https://tox.readthedocs.io/en/latest/). +With {% data variables.product.prodname_actions %}, you can run tests with tox and spread the work across multiple jobs. You'll need to invoke tox using the `-e py` option to choose the version of Python in your `PATH`, rather than specifying a specific version. For more information, see [tox](https://tox.readthedocs.io/en/latest/). {% raw %} ```yaml{:copy} @@ -344,7 +330,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - python: [3.7, 3.8, 3.9] + python: ["3.7", "3.8", "3.9"] steps: - uses: actions/checkout@v2 @@ -360,11 +346,11 @@ jobs: ``` {% endraw %} -## Empaquetar datos de flujo de trabajo como artefactos +## Packaging workflow data as artifacts -Puedes cargar artefactos para ver después de que se complete un flujo de trabajo. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." -En el siguiente ejemplo se muestra cómo puedes usar la acción `upload-artifact` para archivar los resultados de las pruebas de ejecución `pytest`. Para obtener más información, consulta la acción [`upload-artifact`](https://github.com/actions/upload-artifact). +The following example demonstrates how you can use the `upload-artifact` action to archive test results from running `pytest`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact). {% raw %} ```yaml{:copy} @@ -378,7 +364,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - python-version: [3.6, 3.7, 3.8, 3.9] + python-version: ["3.6", "3.7", "3.8", "3.9"] steps: - uses: actions/checkout@v2 @@ -403,11 +389,11 @@ jobs: ``` {% endraw %} -## Publicar en registros de paquetes +## Publishing to package registries -Puedes configurar tu flujo de trabajo para publicar tu paquete de Python a un registro de paquetes una vez que pasen tus pruebas de IC. Esta sección demuestra cómo puedes utilizar {% data variables.product.prodname_actions %} para cargar to paquete a PyPI cada vez que [publicas un lanzamiento](/github/administering-a-repository/managing-releases-in-a-repository). +You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository). -Para este ejemplo, necesitarás crear dos [Tokens de la API de PyPI](https://pypi.org/help/#apitoken). Puedes utilizar secretos para almacenar los tokens de acceso o las credenciales que se necesitan publicar en tu paquete. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." +For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -440,4 +426,4 @@ jobs: password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %} ``` -Para obtener más información sobre la plantilla de flujo de trabajo, consulta a [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml). +For more information about the template workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml). diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md index 9cbe280995..c7f91b3a43 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md @@ -1,6 +1,6 @@ --- -title: Crear una acción de contenedor de Docker -intro: Esta guía te muestra los pasos mínimos necesarios para desarrollar una acción de contenedor Docker. +title: Creating a Docker container action +intro: 'This guide shows you the minimal steps required to build a Docker container action. ' redirect_from: - /articles/creating-a-docker-container-action - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action @@ -22,58 +22,58 @@ shortTitle: Docker container action {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Introducción +## Introduction -Esta guía te muestra los pasos mínimos necesarios para desarrollar una acción de contenedor de Docker. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" en los registros o "Hello [who-to-greet]"si proporcionas un nombre personalizado. +In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name. -Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de contenedor Docker y probarla en un flujo de trabajo. +Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow. {% data reusables.github-actions.self-hosted-runner-reqs-docker %} {% data reusables.github-actions.context-injection-warning %} -## Prerrequisitos +## Prerequisites -Puede ser útil tener un entendimiento básico de variables de entorno de las {% data variables.product.prodname_actions %} y del sistema de archivos de contenedor Docker: +You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem: -- "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" +- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" {% ifversion ghae %} -- "[Sistema de archivos para contenedores de Docker](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)." -{% else %} -- "[Entornos virtuales para {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)" +- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)." +{% else %} +- "[Virtual environments for {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)" {% endif %} -Antes de comenzar, necesitarás crear un repositorio de {% data variables.product.prodname_dotcom %}. +Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository. -1. Crea un repositorio nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o usar "hello-world-docker-action" como este ejemplo. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)". +1. Create a new repository on {% data variables.product.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." -1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". +1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -1. Desde tu terminal, cambia los directorios en el repositorio nuevo. +1. From your terminal, change directories into your new repository. ```shell{:copy} cd hello-world-docker-action ``` -## Crear un Dockerfile +## Creating a Dockerfile -En tu nuevo directorio `hello-world-docker-action`, crea un nuevo archivo `Dockerfile`. Para obtener más información, consulta al "[Sporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)". +In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)." **Dockerfile** ```Dockerfile{:copy} -# Imagen del contenedor que ejecuta tu código +# Container image that runs your code FROM alpine:3.10 -# Copias tu archivo de código de tu repositorio de acción a la ruta `/`del contenedor +# Copies your code file from your action repository to the filesystem path `/` of the container COPY entrypoint.sh /entrypoint.sh -# Archivo del código a ejecutar cuando comienza el contedor del docker (`entrypoint.sh`) +# Code file to execute when the docker container starts up (`entrypoint.sh`) ENTRYPOINT ["/entrypoint.sh"] ``` -## Crear un archivo de metadatos de una acción +## Creating an action metadata file -Crea un archivo `action.yml` nuevo en el directorio `hello-world-docker` que creaste anteriormente. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)". +Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)." {% raw %} **action.yml** @@ -97,19 +97,19 @@ runs: ``` {% endraw %} -Este metado define un parámetro de entrada `who-to-greet` y uno de salida `time`. Para pasar las entradas al contenedor de Docker, debes declarar la entrada usando `inputs` y pasarla a la palabra clave `args`. +This metadata defines one `who-to-greet` input and one `time` output parameter. To pass inputs to the Docker container, you must declare the input using `inputs` and pass the input in the `args` keyword. -{% data variables.product.prodname_dotcom %} creará una imagen desde tu `Dockerfile` y ejecutar comandos en nuevo contenedor usando esta imagen. +{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image. -## Escribir el código de la acción +## Writing the action code -Puedes elegir cualquier imagen de Docker base y, por lo tanto, cualquier idioma para tu acción. El siguiente ejemplo de script del shell usa la variable de entrada `who-to-greet` para imprimir "Hello [who-to-greet]" en el archivo de registro. +You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file. -A continuación, el script obtiene la hora actual y la establece como una variable de salida que pueden usar las acciones que se ejecutan posteriormente en unt rabajo. Para que {% data variables.product.prodname_dotcom %} reconozca las variables de salida, debes usar un comando de flujo de trabajo en una sintaxis específica: `echo ":: set-Output Name =::"`. Para obtener más información, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)". +Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must use a workflow command in a specific syntax: `echo "::set-output name=::"`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)." -1. Crea un archivo `entrypoint.sh` nuevo en el directorio `hello-world-docker-action`. +1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory. -1. Agrega el siguiente código a tu archivo `entrypoint.sh`. +1. Add the following code to your `entrypoint.sh` file. **entrypoint.sh** ```shell{:copy} @@ -119,32 +119,32 @@ A continuación, el script obtiene la hora actual y la establece como una variab time=$(date) echo "::set-output name=time::$time" ``` - Si `entrypoint.sh` se ejecuta sin errores, el estado de la acción se establece en `exitoso`. También puedes establecer explícitamente códigos de salida en el código de tu acción para proporcionar el estado de una acción. Para obtener más información, consulta la sección "[Configurar los códigos de salida para las acciones](/actions/creating-actions/setting-exit-codes-for-actions)". + If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)." -1. Haz ejecutable tu archivo `entrypoint.sh` ejecutando el siguiente comando en tu sistema. +1. Make your `entrypoint.sh` file executable by running the following command on your system. ```shell{:copy} $ chmod +x entrypoint.sh ``` -## Crear un README +## Creating a README -Puedes crear un archivo README para que las personas sepan cómo usar tu acción. Un archivo README resulta más útil cuando planificas el intercambio de tu acción públicamente, pero también es una buena manera de recordarle a tu equipo cómo usar la acción. +To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action. -En tu directorio <`hello-world-docker-action`, crea un archivo `README.md` que especifique la siguiente información: +In your `hello-world-docker-action` directory, create a `README.md` file that specifies the following information: -- Una descripción detallada de lo que hace la acción. -- Argumentos necesarios de entrada y salida. -- Argumentos opcionales de entrada y salida. -- Secretos que utiliza la acción. -- Variables de entorno que utiliza la acción. -- Un ejemplo de cómo usar tu acción en un flujo de trabajo. +- A detailed description of what the action does. +- Required input and output arguments. +- Optional input and output arguments. +- Secrets the action uses. +- Environment variables the action uses. +- An example of how to use your action in a workflow. **README.md** ```markdown{:copy} -# Acción de docker Hello world +# Hello world docker action -Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro. +This action prints "Hello World" or "Hello" + the name of a person to greet to the log. ## Inputs @@ -158,35 +158,35 @@ Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien The time we greeted you. -## Ejemplo de uso +## Example usage uses: actions/hello-world-docker-action@v1 with: who-to-greet: 'Mona the Octocat' ``` -## Confirmar, etiquetar y subir tu acción a {% data variables.product.product_name %} +## Commit, tag, and push your action to {% data variables.product.product_name %} -Desde tu terminal, confirma tus archivos `action.yml`, `entrypoint.sh`, `Dockerfile`, y `README.md`. +From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and `README.md` files. -También se recomienda agregarles una etiqueta de versión a los lanzamientos de tu acción. Para obtener más información sobre el control de versiones de tu acción, consulta la sección "[Acerca de las acciones](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". +It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)." ```shell{:copy} git add action.yml entrypoint.sh Dockerfile README.md -git commit -m "Mi primera acción está lista" -git tag -a -m "Mi primera versión de acción" v1 +git commit -m "My first action is ready" +git tag -a -m "My first action release" v1 git push --follow-tags ``` -## Probar tu acción en un flujo de trabajo +## Testing out your action in a workflow -Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acción esté en un repositorio privado, la acción solo puede usarse en flujos de trabajo en el mismo repositorio. Las acciones públicas pueden ser usadas por flujos de trabajo en cualquier repositorio. +Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository. {% data reusables.actions.enterprise-marketplace-actions %} -### Ejemplo usando una acción pública +### Example using a public action -El siguiente código de flujo de trabajo utiliza la acción completa _hello world_ en el repositorio público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copia el siguiente código de ejemplo de flujo de trabajo en un archivo `.github/workflows/main.yml`, pero reemplaza `actions/hello-world-docker-action` con tu nombre de repositorio y acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Publicar una acción](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)". {% endif %} +The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %} {% raw %} **.github/workflows/main.yml** @@ -209,9 +209,9 @@ jobs: ``` {% endraw %} -### Ejemplo usando una acción privada +### Example using a private action -Copia el siguiente ejemplo de código de flujo de trabajo en un archivo `.github/workflows/main.yml` en tu repositorio de acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %} +Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %} {% raw %} **.github/workflows/main.yml** @@ -238,10 +238,10 @@ jobs: ``` {% endraw %} -Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}Debrás ver la frase "Hello Mona the Octocat" o el nombre que utilizaste para la entrada `who-to-greet` y la marca de tiempo impresa en la bitácora. +From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/docker-action-workflow-run-updated.png) +![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png) {% else %} -![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/docker-action-workflow-run.png) +![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run.png) {% endif %} diff --git a/translations/es-ES/content/actions/deployment/about-deployments/index.md b/translations/es-ES/content/actions/deployment/about-deployments/index.md index f038c974df..3267edb591 100644 --- a/translations/es-ES/content/actions/deployment/about-deployments/index.md +++ b/translations/es-ES/content/actions/deployment/about-deployments/index.md @@ -10,4 +10,3 @@ children: - /about-continuous-deployment - /deploying-with-github-actions --- - diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md index a43a4570ce..463324f7b7 100644 --- a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md +++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md @@ -11,4 +11,3 @@ children: - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine --- - diff --git a/translations/es-ES/content/actions/deployment/managing-your-deployments/index.md b/translations/es-ES/content/actions/deployment/managing-your-deployments/index.md index 01e2784d0d..7aea761e3a 100644 --- a/translations/es-ES/content/actions/deployment/managing-your-deployments/index.md +++ b/translations/es-ES/content/actions/deployment/managing-your-deployments/index.md @@ -9,4 +9,3 @@ versions: children: - /viewing-deployment-history --- - diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md index 9afd694127..69c03b61a4 100644 --- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md +++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md @@ -1,11 +1,11 @@ --- title: About security hardening with OpenID Connect shortTitle: About security hardening with OpenID Connect -intro: OpenID Connect allows your workflows to exchange short-lived tokens directly from your cloud provider. +intro: 'OpenID Connect allows your workflows to exchange short-lived tokens directly from your cloud provider.' miniTocMaxHeadingLevel: 4 versions: fpt: '*' - ghae: issue-4856 + ghae: 'issue-4856' ghec: '*' type: tutorial topics: @@ -17,9 +17,9 @@ topics: ## Overview of OpenID Connect -{% data variables.product.prodname_actions %} workflows are often designed to access a cloud provider (such as AWS, Azure, GCP, or HashiCorp Vault) in order to deploy software or use the cloud's services. Before the workflow can access these resources, it will supply credentials, such as a password or token, to the cloud provider. These credentials are usually stored as a secret in {% data variables.product.prodname_dotcom %}, and the workflow presents this secret to the cloud provider every time it runs. +{% data variables.product.prodname_actions %} workflows are often designed to access a cloud provider (such as AWS, Azure, GCP, or HashiCorp Vault) in order to deploy software or use the cloud's services. Before the workflow can access these resources, it will supply credentials, such as a password or token, to the cloud provider. These credentials are usually stored as a secret in {% data variables.product.prodname_dotcom %}, and the workflow presents this secret to the cloud provider every time it runs. -However, using hardcoded secrets requires you to create credentials in the cloud provider and then duplicate them in {% data variables.product.prodname_dotcom %} as a secret. +However, using hardcoded secrets requires you to create credentials in the cloud provider and then duplicate them in {% data variables.product.prodname_dotcom %} as a secret. With OpenID Connect (OIDC), you can take a different approach by configuring your workflow to request a short-lived access token directly from the cloud provider. Your cloud provider also needs to support OIDC on their end, and you must configure a trust relationship that controls which workflows are able to request the access tokens. Providers that currently support OIDC include Amazon Web Services, Azure, Google Cloud Platform, and HashiCorp Vault, among others. @@ -27,7 +27,7 @@ With OpenID Connect (OIDC), you can take a different approach by configuring you By updating your workflows to use OIDC tokens, you can adopt the following good security practices: -- **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC. +- **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC. - **Authentication and authorization management**: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources. - **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single workflow run, and then automatically expires. @@ -48,7 +48,7 @@ When you configure your cloud to trust {% data variables.product.prodname_dotcom - Before granting an access token, your cloud provider checks that the [`subject`](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) and other claims used to set conditions in its trust settings match those in the request's JSON Web Token (JWT). As a result, you must take care to correctly define the _subject_ and other conditions in your cloud provider. - The OIDC trust configuration steps and the syntax to set conditions for cloud roles (using _Subject_ and other claims) will vary depending on which cloud provider you're using. For some examples, see "[Examples](#examples)." - + ### Understanding the OIDC token Each workflow run requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. During a workflow run, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition. @@ -65,6 +65,7 @@ The following example OIDC token uses a subject (`sub`) that references a job en { "jti": "example-id", "sub": "repo:octo-org/octo-repo:environment:prod", + "environment": "prod", "aud": "https://github.com/octo-org", "ref": "refs/heads/main", "sha": "example-sha", @@ -87,46 +88,46 @@ The following example OIDC token uses a subject (`sub`) that references a job en } ``` -To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at https://token.actions.githubusercontent.com/.well-known/openid-configuration. +To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at https://token.actions.githubusercontent.com/.well-known/openid-configuration. The token includes the standard audience, issuer, and subject claims: -| Claim | Descripción | -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `aud` | _(Audience)_ By default, this is the URL of the repository owner, such as the organization that owns the repository. This is the only claim that can be customized. You can set a custom audience with a toolkit command: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | -| `iss` | _(Issuer)_ The issuer of the OIDC token: `https://token.actions.githubusercontent.com` | -| `sub` | _(Subject)_ Defines the subject claim that is to be validated by the cloud provider. This setting is essential for making sure that access tokens are only allocated in a predictable way. | +| Claim | Description | +| ----------- | ---------------------- | +| `aud`| _(Audience)_ By default, this is the URL of the repository owner, such as the organization that owns the repository. This is the only claim that can be customized. You can set a custom audience with a toolkit command: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | +| `iss`| _(Issuer)_ The issuer of the OIDC token: `https://token.actions.githubusercontent.com` | +| `sub`| _(Subject)_ Defines the subject claim that is to be validated by the cloud provider. This setting is essential for making sure that access tokens are only allocated in a predictable way.| The OIDC token also includes additional standard claims: -| Claim | Descripción | -| ----- | --------------------------------------------------------------------- | -| `alg` | _(Algorithm)_ The algorithm used by the OIDC provider. | -| `exp` | _(Expires at)_ Identifies the expiry time of the JWT. | -| `iat` | _(Issued at)_ The time when the JWT was issued. | -| `jti` | _(JWT token identifier)_ Unique identifier for the OIDC token. | -| `kid` | _(Key identifier)_ Unique key for the OIDC token. | -| `nbf` | _(Not before)_ JWT is not valid for use before this time. | -| `typ` | _(Type)_ Describes the type of token. This is a JSON Web Token (JWT). | +| Claim | Description | +| ----------- | ---------------------- | +| `alg`| _(Algorithm)_ The algorithm used by the OIDC provider. | +| `exp`| _(Expires at)_ Identifies the expiry time of the JWT. | +| `iat`| _(Issued at)_ The time when the JWT was issued. | +| `jti`| _(JWT token identifier)_ Unique identifier for the OIDC token. | +| `kid`| _(Key identifier)_ Unique key for the OIDC token. | +| `nbf`| _(Not before)_ JWT is not valid for use before this time. | +| `typ`| _(Type)_ Describes the type of token. This is a JSON Web Token (JWT). | The token also includes custom claims provided by {% data variables.product.prodname_dotcom %}: -| Claim | Descripción | -| ------------------ | ------------------------------------------------------------------ | -| `actor (actor)` | The user account that initiated the workflow run. | -| `base_ref` | The target branch of the pull request in a workflow run. | -| `environment` | The name of the environment used by the job. | -| `event_name` | El nombre del evento que activó la ejecución del flujo de trabajo. | -| `head_ref` | The source branch of the pull request in a workflow run. | -| `job_workflow_ref` | This is the ref path to the reusable workflow used by this job. | -| `ref` | _(Reference)_ The git ref that triggered the workflow run. | -| `ref_type` | The type of `ref`, for example: "branch". | -| `repositorio` | The repository from where the workflow is running. | -| `repository_owner` | The name of the organization in which the `repository` is stored. | -| `run_id` | The ID of the workflow run that triggered the workflow. | -| `run_number` | The number of times this workflow has been run. | -| `run_attempt` | The number of time this workflow run was been retried. | -| `flujo de trabajo` | El nombre del flujo de trabajo. | +| Claim | Description | +| ----------- | ---------------------- | +| `actor`| The user account that initiated the workflow run. | +| `base_ref`| The target branch of the pull request in a workflow run. | +| `environment`| The name of the environment used by the job. | +| `event_name`| The name of the event that triggered the workflow run. | +| `head_ref`| The source branch of the pull request in a workflow run. | +| `job_workflow_ref`| This is the ref path to the reusable workflow used by this job. For more information, see "["Using OpenID Connect with reusable workflows"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." | +| `ref`| _(Reference)_ The git ref that triggered the workflow run. | +| `ref_type`| The type of `ref`, for example: "branch". | +| `repository`| The repository from where the workflow is running. | +| `repository_owner`| The name of the organization in which the `repository` is stored. | +| `run_id`| The ID of the workflow run that triggered the workflow. | +| `run_number`| The number of times this workflow has been run. | +| `run_attempt`| The number of time this workflow run was been retried. | +| `workflow`| The name of the workflow. | ### Defining trust conditions on cloud roles using OIDC claims @@ -134,7 +135,8 @@ With OIDC, a {% data variables.product.prodname_actions %} workflow requires a t Audience and Subject claims are typically used in combination while setting conditions on the cloud role/resources to scope its access to the GitHub workflows. - **Audience**: By default, this value uses the URL of the organization or repository owner. This can be used to set a condition that only the workflows in the specific organization can access the cloud role. -- **Subject**: Has a predefined format and is a concatenation of some of the key metadata about the workflow, such as the {% data variables.product.prodname_dotcom %} organization, repository, branch or associated [`job`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment) environment. There are also many additional claims supported in the OIDC token that can also be used for setting these conditions. +- **Subject**: Has a predefined format and is a concatenation of some of the key metadata about the workflow, such as the {% data variables.product.prodname_dotcom %} organization, repository, branch or associated [`job`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment) environment. +There are also many additional claims supported in the OIDC token that can also be used for setting these conditions. In addition, your cloud provider could allow you to assign a role to the access tokens, letting you specify even more granular permissions. @@ -144,7 +146,7 @@ In addition, your cloud provider could allow you to assign a role to the access {% endnote %} -### Ejemplos +### Examples The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the workflow run's [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use. @@ -152,49 +154,49 @@ The following examples demonstrate how to use "Subject" as a condition. The [sub You can configure a subject that filters for a specific [environment](/actions/deployment/using-environments-for-deployment) name. In this example, the workflow run must have originated from a job that has an environment named `Production`, in a repository named `octo-repo` that is owned by the `octo-org` organization: -| | | -| -------- | --------------------------------------------------- | -| Syntax: | `repo:orgName/repoName:environment:environmentName` | -| Ejemplo: | `repo:octo-org/octo-repo:environment:Production` | +| | | +| ------ | ----------- | +| Syntax: | `repo:orgName/repoName:environment:environmentName` | +| Example:| `repo:octo-org/octo-repo:environment:Production` | #### Filtering for `pull_request` events You can configure a subject that filters for the [`pull_request`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) event. In this example, the workflow run must have been triggered by a `pull_request` event in a repository named `octo-repo` that is owned by the `octo-org` organization: -| | | -| -------- | -------------------------------------- | -| Syntax: | `repo:orgName/repoName:pull_request` | -| Ejemplo: | `repo:octo-org/octo-repo:pull_request` | +| | | +| ------ | ----------- | +| Syntax: | `repo:orgName/repoName:pull_request` | +| Example:| `repo:octo-org/octo-repo:pull_request` | #### Filtering for a specific branch You can configure a subject that filters for a specific branch name. In this example, the workflow run must have originated from a branch named `demo-branch`, in a repository named `octo-repo` that is owned by the `octo-org` organization: -| | | -| -------- | ---------------------------------------------------- | -| Syntax: | `repo:orgName/repoName:ref:refs/heads/branchName` | -| Ejemplo: | `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | +| | | +| ------ | ----------- | +| Syntax: | `repo:orgName/repoName:ref:refs/heads/branchName` | +| Example:| `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | #### Filtering for a specific tag You can create a subject that filters for specific tag. In this example, the workflow run must have originated with a tag named `demo-tag`, in a repository named `octo-repo` that is owned by the `octo-org` organization: -| | | -| -------- | ------------------------------------------------ | -| Syntax: | `repo:orgName/repoName:ref:refs/tags/tagName` | -| Ejemplo: | `repo:octo-org/octo-repo:ref:refs/tags/demo-tag` | +| | | +| ------ | ----------- | +| Syntax: | `repo:orgName/repoName:ref:refs/tags/tagName` | +| Example:| `repo:octo-org/octo-repo:ref:refs/tags/demo-tag` | ### Configuring the subject in your cloud provider To configure the subject in your cloud provider's trust relationship, you must add the subject string to its trust configuration. The following examples demonstrate how various cloud providers can accept the same `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` subject in different ways: -| | | -| -------------------------- | ------------------------------------------------------------------------------------------------- | -| Amazon Web Services | `"token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | -| Azure | `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | -| Plataforma de Google Cloud | `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')` | -| HashiCorp Vault | `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | +| | | +| ------ | ----------- | +| Amazon Web Services | `"token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | +| Azure| `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | +| Google Cloud Platform| `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')` | +| HashiCorp Vault| `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch" ` | For more information, see the guides listed in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)." @@ -204,13 +206,13 @@ To update your custom actions to authenticate using OIDC, you can use `getIDToke You could also use a `curl` command to request the JWT, using the following environment variables: -| | | -| -------------------------------- | ------------------------------------------------------------------------- | -| `ACTIONS_ID_TOKEN_REQUEST_URL` | The URL for {% data variables.product.prodname_dotcom %}'s OIDC provider. | -| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | Bearer token for the request to the OIDC provider. | +| | | +| ------ | ----------- | +| `ACTIONS_ID_TOKEN_REQUEST_URL` | The URL for {% data variables.product.prodname_dotcom %}'s OIDC provider. | +| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | Bearer token for the request to the OIDC provider. | -Por ejemplo: +For example: ```shell{:copy} curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange" diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index 4a16c64cd3..af36775458 100644 --- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -1,11 +1,11 @@ --- title: Configuring OpenID Connect in Amazon Web Services shortTitle: Configuring OpenID Connect in Amazon Web Services -intro: Use OpenID Connect within your workflows to authenticate with Amazon Web Services. +intro: 'Use OpenID Connect within your workflows to authenticate with Amazon Web Services.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' - ghae: issue-4856 + ghae: 'issue-4856' ghec: '*' type: tutorial topics: @@ -15,13 +15,13 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Resumen +## Overview -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. +OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. This guide explains how to configure AWS to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) that uses tokens to authenticate to AWS and access resources. -## Prerrequisitos +## Prerequisites {% data reusables.actions.oidc-link-to-intro %} @@ -38,16 +38,18 @@ To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, se To configure the role and trust in IAM, see the AWS documentation for ["Assuming a Role"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) and ["Creating a role for web identity or OpenID connect federation"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html). -By default, the validation only includes the audience (`aud`) condition, so you must manually add a subject (`sub`) condition. Edit the trust relationship to add the `sub` field to the validation conditions. Por ejemplo: +By default, the validation only includes the audience (`aud`) condition, so you must manually add a subject (`sub`) condition. Edit the trust relationship to add the `sub` field to the validation conditions. For example: -```yaml{:copy} +```json{:copy} "Condition": { "StringEquals": { "token.actions.githubusercontent.com:aud": "https://github.com/octo-org", - "token.actions.githubusercontent.com:sub": "token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch" + "token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch" + } +} ``` -## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %} +## Updating your {% data variables.product.prodname_actions %} workflow To update your workflows for OIDC, you will need to make two changes to your YAML: 1. Add permissions settings for the token. @@ -55,14 +57,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM ### Adding permissions settings -The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por ejemplo: +The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example: ```yaml{:copy} permissions: id-token: write ``` -You may need to specify additional permissions here, depending on your workflow's requirements. +You may need to specify additional permissions here, depending on your workflow's requirements. ### Requesting the access token @@ -70,7 +72,7 @@ The `aws-actions/configure-aws-credentials` action receives a JWT from the {% da - ``: Add the name of your S3 bucket here. - ``: Replace the example with your AWS role. -- ``: Add the name of your AWs region here. +- ``: Add the name of your AWS region here. ```yaml{:copy} # Sample workflow to access AWS resources when workflow is tied to branch @@ -96,9 +98,9 @@ jobs: with: role-to-assume: arn:aws:iam::1234567890:role/example-role role-session-name: samplerolesession - aws-region: ${{ env.AWS_REGION }} + aws-region: {% raw %}${{ env.AWS_REGION }}{% endraw %} # Upload a file to AWS s3 - name: Copy index.html to s3 run: | - aws s3 cp ./index.html s3://${{ env.BUCKET_NAME }}/ + aws s3 cp ./index.html s3://{% raw %}${{ env.BUCKET_NAME }}{% endraw %}/ ``` diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md index 75ea24ae56..80231b121a 100644 --- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md +++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md @@ -1,11 +1,11 @@ --- title: Configuring OpenID Connect in Azure shortTitle: Configuring OpenID Connect in Azure -intro: Use OpenID Connect within your workflows to authenticate with Azure. +intro: 'Use OpenID Connect within your workflows to authenticate with Azure.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' - ghae: issue-4856 + ghae: 'issue-4856' ghec: '*' type: tutorial topics: @@ -15,13 +15,13 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Resumen +## Overview -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. +OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. This guide gives an overview of how to configure Azure to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`azure/login`](https://github.com/Azure/login) action that uses tokens to authenticate to Azure and access resources. -## Prerrequisitos +## Prerequisites {% data reusables.actions.oidc-link-to-intro %} @@ -33,8 +33,8 @@ This guide gives an overview of how to configure Azure to trust {% data variable To configure the OIDC identity provider in Azure, you will need to perform the following configuration. For instructions on making these changes, refer to [the Azure documentation](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure). -1. Create an Active Directory application and a service principal. -2. Add federated credentials for the Active Directory application. +1. Create an Azure Active Directory application and a service principal. +2. Add federated credentials for the Azure Active Directory application. 3. Create {% data variables.product.prodname_dotcom %} secrets for storing Azure configuration. Additional guidance for configuring the identity provider: @@ -42,7 +42,7 @@ Additional guidance for configuring the identity provider: - For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). - For the `audience` setting, `api://AzureADTokenExchange` is the recommended value, but you can also specify other values here. -## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %} +## Updating your {% data variables.product.prodname_actions %} workflow To update your workflows for OIDC, you will need to make two changes to your YAML: 1. Add permissions settings for the token. @@ -50,14 +50,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM ### Adding permissions settings -The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por ejemplo: +The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example: ```yaml{:copy} permissions: id-token: write ``` -You may need to specify additional permissions here, depending on your workflow's requirements. +You may need to specify additional permissions here, depending on your workflow's requirements. ### Requesting the access token @@ -65,36 +65,28 @@ The [`azure/login`](https://github.com/Azure/login) action receives a JWT from t The following example exchanges an OIDC ID token with Azure to receive an access token, which can then be used to access cloud resources. +{% raw %} ```yaml{:copy} -name: Run Azure Login with OpenID Connect +name: Run Azure Login with OIDC on: [push] permissions: id-token: write - + contents: read jobs: build-and-deploy: runs-on: ubuntu-latest steps: - - - name: Installing CLI-beta for OpenID Connect - run: | - cd ../.. - CWD="$(pwd)" - python3 -m venv oidc-venv - . oidc-venv/bin/activate - echo "activated environment" - python3 -m pip install -q --upgrade pip - echo "started installing cli beta" - pip install -q --extra-index-url https://azcliprod.blob.core.windows.net/beta/simple/ azure-cli - echo "***************installed cli beta*******************" - echo "$CWD/oidc-venv/bin" >> $GITHUB_PATH - - - name: 'Az CLI login' - uses: azure/login@v1.4.0 - with: - client-id: {% raw %}${{ secrets.AZURE_CLIENTID }}{% endraw %} - tenant-id: {% raw %}${{ secrets.AZURE_TENANTID }}{% endraw %} - subscription-id: {% raw %}${{ secrets.AZURE_SUBSCRIPTIONID }}{% endraw %} + - name: 'Az CLI login' + uses: azure/login@v1 + with: + client-id: ${{ secrets.AZURE_CLIENT_ID }} + tenant-id: ${{ secrets.AZURE_TENANT_ID }} + subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }} + + - name: 'Run az commands' + run: | + az account show + az group list ``` - + {% endraw %} diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md index 58235d101f..ce25ef4811 100644 --- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md +++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md @@ -13,5 +13,5 @@ children: - /configuring-openid-connect-in-google-cloud-platform - /configuring-openid-connect-in-hashicorp-vault - /configuring-openid-connect-in-cloud-providers + - /using-openid-connect-with-reusable-workflows --- - diff --git a/translations/es-ES/content/actions/guides.md b/translations/es-ES/content/actions/guides.md index 06cceb3dce..7ac00d9b29 100644 --- a/translations/es-ES/content/actions/guides.md +++ b/translations/es-ES/content/actions/guides.md @@ -1,6 +1,6 @@ --- title: Guides for GitHub Actions -intro: 'Estas guías para {% data variables.product.prodname_actions %} incluyen casos de uso y ejemplos específicos que te ayudarán a configurar los flujos de trabajo.' +intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -13,6 +13,7 @@ learningTracks: - continuous_integration - continuous_deployment - deploy_to_the_cloud + - '{% ifversion ghec or ghes or ghae %}adopting_github_actions_for_your_enterprise{% endif %}' - hosting_your_own_runners - create_actions includeGuides: diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index c26134a32d..40d2652bc4 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Acerca de los ejecutores autoalojados -intro: 'Puedes alojar tus propios ejecutores y personalizar el entorno utilizado para ejecutar trabajos en tus flujos de trabajo de {% data variables.product.prodname_actions %}.' +title: About self-hosted runners +intro: 'You can host your own runners and customize the environment used to run jobs in your {% data variables.product.prodname_actions %} workflows.' redirect_from: - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners - /actions/automating-your-workflow-with-github-actions/about-self-hosted-runners @@ -17,83 +17,83 @@ type: overview {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de los ejecutores autoalojados +## About self-hosted runners -{% data reusables.github-actions.self-hosted-runner-description %} Los ejecutores auto-hospedados pueden ser físicos, virtuales, estar en un contenedor, en los servidores del usuario, o en la nube. +{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud. -Puedes agregar ejecutores auto-hospedados en varios niveles dentro de la jerarquía de administración: -- Los ejecutores a nivel de repositorio están dedicados a un solo repositorio. -- Los ejecutores a nivel de organización pueden procesar jobs para varios repositorios dentro de una organización. -- Los ejecutores a nivel de empresa puede asignarse a varias organizaciones en una cuenta empresarial. +You can add self-hosted runners at various levels in the management hierarchy: +- Repository-level runners are dedicated to a single repository. +- Organization-level runners can process jobs for multiple repositories in an organization. +- Enterprise-level runners can be assigned to multiple organizations in an enterprise account. -La máquina de tu ejecutor se conecta a{% data variables.product.product_name %} utilizando la aplicación para ejecutores auto-hospedados de {% data variables.product.prodname_actions %}. {% data reusables.github-actions.runner-app-open-source %} Cuando se lanza una nueva versión, la aplicación del ejecutor se actualiza automáticamente cuando se asigna un job al ejecutor, o dentro de una semana de lanzamiento si dicho ejecutor no se ha asignado a ningún job. +Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs. {% data reusables.github-actions.self-hosted-runner-auto-removal %} -Para obtener más información acerca de la instalación y el uso de los ejecutores autoalojados, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" y "[Usar ejecutores autoalojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." +For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." -## Diferencias entre ejecutores alojados en {% data variables.product.prodname_dotcom %} y autoalojados +## Differences between {% data variables.product.prodname_dotcom %}-hosted and self-hosted runners -Los ejecutores alojados en {% data variables.product.prodname_dotcom %} ofrecen una manera más rápida y sencilla de ejecutar tus flujos de trabajo, mientras que los ejecutores autoalojados son una manera altamente configurable de ejecutar flujos de trabajo en tu propio entorno personalizado. +{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted runners are a highly configurable way to run workflows in your own custom environment. -**Ejecutores alojados en {% data variables.product.prodname_dotcom %}:** -- Reciben actualizaciones automáticas para el sistema operativo, paquetes y herramientas pre-instalados, y la aplicación del ejecutor auto-hospedado. -- Son administrados y mantenidos por {% data variables.product.prodname_dotcom %}. -- Proporcionan una instancia limpia para cada ejecución de trabajo. -- Usan minutos libres en tu plan de {% data variables.product.prodname_dotcom %}, con tarifas por minuto aplicadas después de superar los minutos libres. +**{% data variables.product.prodname_dotcom %}-hosted runners:** +- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application. +- Are managed and maintained by {% data variables.product.prodname_dotcom %}. +- Provide a clean instance for every job execution. +- Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes. -**Ejecutores autoalojados:** -- Reciben actualizaciones automáticas únicamente para la aplicación del ejecutor auto-hospedado. Eres responsable de actualizar el sistema operativo y el resto del software. -- Puedes usar los servicios en la nube o las máquinas locales que ya pagas. -- Son personalizables para tu hardware, sistema operativo, software y requisitos de seguridad. -- No es necesario tener una instancia limpia para cada ejecución de trabajo. -- Son de uso gratuito con las {% data variables.product.prodname_actions %}, pero eres responsable del costo de mantener tus máquinas de ejecutores. +**Self-hosted runners:** +- Receive automatic updates for the self-hosted runner application only. You are responsible for updating the operating system and all other software. +- Can use cloud services or local machines that you already pay for. +- Are customizable to your hardware, operating system, software, and security requirements. +- Don't need to have a clean instance for every job execution. +- Are free to use with {% data variables.product.prodname_actions %}, but you are responsible for the cost of maintaining your runner machines. -## Requisitos para máquinas de ejecutores autoalojados +## Requirements for self-hosted runner machines -Puedes usar cualquier máquina como ejecutor autoalojado, siempre que cumpla con estos requisitos: +You can use any machine as a self-hosted runner as long at it meets these requirements: -* Puedes instalar y ejecutar la aplicación del ejecutor autoalojado en la máquina. Para obtener más información, consulta la sección "[Arquitecturas y sistemas operativos compatibles para ejecutores auto-hospedados](#supported-architectures-and-operating-systems-for-self-hosted-runners)". -* La máquina puede comunicarse con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." -* La máquina tiene suficientes recursos de hardware para el tipo de flujos de trabajo que planeas ejecutar. La propia aplicación del ejecutor autoalojado solo requiere unos recursos mínimos. -* Si quieres ejecutar flujos de trabajo que usan acciones del contenedor Docker o contenedores de servicio, debes usar una máquina Linux y Docker debe estar instalado. +* You can install and run the self-hosted runner application on the machine. For more information, see "[Supported architectures and operating systems for self-hosted runners](#supported-architectures-and-operating-systems-for-self-hosted-runners)." +* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." +* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources. +* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed. {% ifversion fpt or ghes > 3.2 or ghec %} -## Autoescalar tus ejecutores auto-hospedados +## Autoscaling your self-hosted runners -Puedes aumentar o disminuir la cantidad de ejecutores auto-hospedados automáticamente en tu ambiente como respuesta a los eventos de webhook que recibes. Para obtener más información, consulta la sección "[Autoescalar con ejecutores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)". +You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." {% endif %} -## Límites de uso +## Usage limits -Hay algunos límites para el uso de las {% data variables.product.prodname_actions %} cuando se utilizan ejecutores auto-hospedados. Estos límites están sujetos a cambios. +There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change. {% data reusables.github-actions.usage-workflow-run-time %} -- **Tiempo de cola de espera para el job** - Cada job para ejecutores auto-hospedados puede ponerse en cola de espera por un máximo de 24 horas. Si un ejecutor auto-hospedado no comienza a ejecutar el job dentro de este límite de tiempo, dicho job se terminará y no se podrá completar. +- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete. {% data reusables.github-actions.usage-api-requests %} -- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %} +- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %} {% data reusables.github-actions.usage-workflow-queue-limits %} -## Continuidad de los flujos de trabajo para los ejecutores auto-hospedados +## Workflow continuity for self-hosted runners {% data reusables.github-actions.runner-workflow-continuity %} -## Sistemas operativos y arquitecturas compatibles para los ejecutores auto-hospedados +## Supported architectures and operating systems for self-hosted runners -Los siguientes sistemas operativos son compatibles con la aplicación del ejecutor auto-hospedado. +The following operating systems are supported for the self-hosted runner application. ### Linux -- Red Hat Enterprise Linux 7 o superior -- CentOS 7 o superior +- Red Hat Enterprise Linux 7 or later +- CentOS 7 or later - Oracle Linux 7 -- Fedora 29 o posterior -- Debian 9 o posterior -- Ubuntu 16.04 o posterior -- Linux Mint 18 o posterior -- openSUSE 15 o posterior -- SUSE Enterprise Linux (SLES) 12 SP2 o posterior +- Fedora 29 or later +- Debian 9 or later +- Ubuntu 16.04 or later +- Linux Mint 18 or later +- openSUSE 15 or later +- SUSE Enterprise Linux (SLES) 12 SP2 or later ### Windows @@ -106,82 +106,130 @@ Los siguientes sistemas operativos son compatibles con la aplicación del ejecut ### macOS -- macOS 10.13 (High Sierra) o posterior +- macOS 10.13 (High Sierra) or later -### Arquitecturas +### Architectures -Las siguientes arquitecturas de procesamiento son compatibles para la aplicación del ejecutor auto-hospedado. +The following processor architectures are supported for the self-hosted runner application. - `x64` - Linux, macOS, Windows. -- `ARM64` - Solo Linux. -- `ARM32` - Solo Linux. +- `ARM64` - Linux only. +- `ARM32` - Linux only. {% ifversion ghes %} -## La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }} +## Supported actions on self-hosted runners -Podría requerirse algo de configuración adicional para utilizar acciones de {% data variables.product.prodname_dotcom_the_website %} con {% data variables.product.prodname_ghe_server %} o para utilizar las acciones de `actions/setup-LANGUAGE` con ejecutores auto-hospedados que no tengan acceso a internet. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." +Some extra configuration might be required to use actions from {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator. {% endif %} -## La comunicación entre ejecutores autoalojados y {% data variables.product.product_name %} +## Communication between self-hosted runners and {% data variables.product.product_name %} -El ejecutor auto-hospedado sondea a {% data variables.product.product_name %} para solicitar actualizaciones de aplicaciones y para revisar si hay jobs en cola para su procesamiento. El ejecutor auto-hospedado utiliza un _sondeo largo_ de HTTPS que abre una conexión a {% data variables.product.product_name %} por 50 segundos, y si no recibe respuesta alguna, expira y crea un nuevo sondeo largo. La aplicación debe estar ejecutándose en la máquina para aceptar y ejecutar trabajos de {% data variables.product.prodname_actions %}. +The self-hosted runner polls {% data variables.product.product_name %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs. + +{% data reusables.actions.self-hosted-runner-ports-protocols %} {% ifversion ghae %} -Debes asegurarte de que el ejecutor auto-hospedado tenga un acceso adecuado a la red para comunicarse con la -URL de {% data variables.product.prodname_ghe_managed %}. -Por ejemplo, si el nombre de tu instancia es `octoghae`, entonces necesitarás permitir que el ejecutor auto-hospedado acceda a `octoghae.github.com`. -Si utilizas una lista blanca para las direcciones IP para tu +You must ensure that the self-hosted runner has appropriate network access to communicate with the {% data variables.product.prodname_ghe_managed %} URL and its subdomains. +For example, if your instance name is `octoghae`, then you will need to allow the self-hosted runner to access `octoghae.githubenterprise.com`, `api.octoghae.githubenterprise.com`, and `codeload.octoghae.githubenterprise.com`. -cuenta empresarial u organizacional de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-.hospedado a dicha lista. Para obtener más información, consulta "[Administrar las direcciones IP permitidas en tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)". +If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." {% endif %} {% ifversion fpt or ghec %} -Debes asegurarte de que la máquina tiene el acceso a la red adecuado para comunicarte con las URL de {% data variables.product.prodname_dotcom %} listadas a continuación. +Since the self-hosted runner opens a connection to {% data variables.product.prodname_dotcom %}, you do not need to allow {% data variables.product.prodname_dotcom %} to make inbound connections to your self-hosted runner. + +You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} hosts listed below. Some hosts are required for essential runner operations, while other hosts are only required for certain functionality. {% note %} -**Nota:** Algunos de los dominios que se listan a continuación se configuraron utilizando registros de `CNAME`. Algunos cortafuegos podrían requerir que agregues reglas recursivamente apra todos los registros de `CNAME`. Nota que los registros de `CNAME` podrían cambiar en el futuro y que solo los dominios que se listan a continuación seguirán siendo constantes. +**Note:** Some of the domains listed below are configured using `CNAME` records. Some firewalls might require you to add rules recursively for all `CNAME` records. Note that the `CNAME` records might change in the future, and that only the domains listed below will remain constant. + +{% endnote %} + +**Needed for essential operations:** + +``` +github.com +api.github.com +``` + +**Needed for downloading actions:** + +``` +codeload.github.com +``` + +**Needed for runner version updates:** + +``` +objects.githubusercontent.com +objects-origin.githubusercontent.com +github-releases.githubusercontent.com +github-registry-files.githubusercontent.com +``` + +**Needed for uploading/downloading caches and workflow artifacts:** + +``` +*.blob.core.windows.net +``` + +**Needed for retrieving OIDC tokens:** + +``` +*.actions.githubusercontent.com +``` + +In addition, your workflow may require access to other network resources. For example, if your workflow installs packages or publishes containers to {% data variables.product.prodname_dotcom %} Packages, then the runner will also require access to those network endpoints. + +If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)". + +{% else %} + +You must ensure that the machine has the appropriate network access to communicate with {% data variables.product.product_location %}.{% ifversion ghes %} Self-hosted runners connect directly to {% data variables.product.product_location %} and do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.product.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.product.product_location %}, with no need for traffic to traverse a public network.{% endif %} + +{% endif %} + +You can also use self-hosted runners with a proxy server. For more information, see "[Using a proxy server with self-hosted runners](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)." + +{% ifversion ghes %} + +## Communication between self-hosted runners and {% data variables.product.prodname_dotcom_the_website %} + +Self-hosted runners do not need to connect to {% data variables.product.prodname_dotcom_the_website %} unless you have [enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect). + +If you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}, then the self-hosted runner will connect directly to {% data variables.product.prodname_dotcom_the_website %} to download actions. You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below. + +{% note %} + +**Note:** Some of the domains listed below are configured using `CNAME` records. Some firewalls might require you to add rules recursively for all `CNAME` records. Note that the `CNAME` records might change in the future, and that only the domains listed below will remain constant. {% endnote %} ``` github.com api.github.com -*.actions.githubusercontent.com -github-releases.githubusercontent.com -github-registry-files.githubusercontent.com codeload.github.com -*.pkg.github.com -pkg-cache.githubusercontent.com -pkg-containers.githubusercontent.com -pkg-containers-az.githubusercontent.com -*.blob.core.windows.net ``` -Si utilizas un listado de direcciones IP permitidas para tu cuenta organizacional o empresarial de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-hospedado a dicha lista. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)". - -{% else %} - -Debes asegurarte de que la máquina tenga el acceso a la red adecuado para comunicarse con {% data variables.product.product_location %}. - {% endif %} -También puedes usar ejecutores autoalojados con un servidor proxy. Para obtener más información, consulta "[Usar un servidor proxy con ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)." +{% ifversion fpt or ghec %} -## Seguridad de ejecutores autoalojdados con repositorios públicos +## Self-hosted runner security with public repositories -{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} + +This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution. + +Untrusted workflows running on your self-hosted runner pose significant security risks for your machine and network environment, especially if your machine persists its environment between jobs. Some of the risks include: + +* Malicious programs running on the machine. +* Escaping the machine's runner sandbox. +* Exposing access to the machine's network environment. +* Persisting unwanted or dangerous data on the machine. + {% endif %} - -Este no es un problema con los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, ya que cada uno de estos ejecutores hospedados en {% data variables.product.prodname_dotcom %} siempre constituye una máquina virtual limpia y aislada, la cual se destruya al final de la ejecución del job. - -Los flujos de trabajo que no son de confianza y se ejecutan en tu ejecutor autoalojado plantean riesgos de seguridad considerables para tu máquina y entorno de red, en especial si tu máquina se mantiene en su entorno entre trabajos. Algunos de los riesgos incluyen: - -* Programas maliciosos que se ejecutan en la máquina. -* Escapar del entorno Sandbox del ejecutor de la máquina. -* Exponer el acceso al entorno de red de la máquina. -* Mantener datos peligrosos o no deseados en la máquina. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 1543b80ac4..e53e41204e 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Agrega ejecutores auto-hospedados -intro: 'Puedes agregar un ejecutor auto-hospedado a {{ site.data.variables.product.prodname_actions }}.' +title: Adding self-hosted runners +intro: 'You can add a self-hosted runner to a repository, an organization, or an enterprise.' redirect_from: - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners @@ -10,69 +10,68 @@ versions: ghae: '*' ghec: '*' type: tutorial -shortTitle: Agregar ejecutores auto-hospedados +shortTitle: Add self-hosted runners --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -Puedes agregar un ejecutor auto-hospedado a {{ site.data.variables.product.prodname_actions }}. +You can add a self-hosted runner to a repository, an organization, or an enterprise. -So eres un administrador de alguna organización o empresa, podría que quisieras agregar tus ejecutores auto-hospedados a nivel organizacional o empresarial. Este acercamiento hace que el ejecutor esté disponible para múltiples repositorios en tu organización o empresa y también te permite administrar tus ejecutores en un solo lugar. +If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. -Para obtener información sobre los sistemas operativos compatibles para los ejecutores autoalojados o el uso de ejecutores autoalojados con un servidor proxy, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% ifversion not ghae %} {% warning %} -**Advertencia:** {% data reusables.github-actions.self-hosted-runner-security %} +**Warning:** {% data reusables.github-actions.self-hosted-runner-security %} -Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)". +For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} {% endif %} -## Agregar un ejecutor auto-hospedado a un repositorio +## Adding a self-hosted runner to a repository -Puedes agregar ejecutores auto-hospedados a un solo repositorio. Para agregar un ejecutor autoalojado a un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. +You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt %} +{% ifversion fpt or ghec %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} -1. Haz clic en **Ejecutor auto-hospedado nuevo**. +1. Click **New self-hosted runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% ifversion ghae or ghes %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Debajo de -{% ifversion fpt or ghes > 3.1 or ghae %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar ejecutor**. +1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} -## Agregar un ejecutor auto-hospedado a una organización +## Adding a self-hosted runner to an organization -Puedes agregar ejecutores auto-hospedados a nivel organizacional, en donde se podrán utilizar para procesar jobs para varios repositorios en una organización. Para agregar un ejecutor auto-hospedado a una organización, debes ser el dueño de la misma. +You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt %} +{% ifversion fpt or ghec %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} -1. Haz clic en **Ejecutor nuevo**. +1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% ifversion ghae or ghes %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Debajo de -{% ifversion fpt or ghes > 3.1 or ghae %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar ejecutor**. +1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} @@ -80,40 +79,39 @@ Puedes agregar ejecutores auto-hospedados a nivel organizacional, en donde se po {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -## Agregar un ejecutor auto-hospedado a una empresa +## Adding a self-hosted runner to an enterprise -Puedes agregar ejecutores auto-hospedados a una empresa, en donde pueden asignarse a organizaciones múltiples. Los administradores de la organización podrán controlar entonces qué repositorios pueden utilizarlo. +You can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. -Los ejecutores nuevos se asignan al grupo predeterminado. Puedes modificar el grupo del ejecutor después de que lo hayas registrado. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". +New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." -{% ifversion fpt %} -Para agregar un ejecutor auto-hospedado a una cuenta empresarial, debes ser un propietario de la empresa. +{% ifversion fpt or ghec %} +To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} -1. Haz clic en **Ejecutor nuevo**. +1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% ifversion ghae or ghes %} -Para agregar un ejecutor auto-hospedado a nivel empresarial de -{% data variables.product.product_location %}, debes ser un administrador de sitio. +To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} -1. Da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. +1. Click **Add new**, then click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -### Hacer que los ejecutores empresariales estén disponibles para los repositorios +### Making enterprise runners available to repositories -Predeterminadamente, los ejecutores en un grupo de ejecutores auto hospedados "Predeterminado" de una empresa se encontrarán disponibles para todas las organizaciones de ésta, pero no así para todos los repositorios en cada una de las organizaciones. +By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. -Para que un grupo de ejecutores auto-hospedados a nivel empresarial se encuentre disponible para el repositorio de una organización, podría que necesites cambiar la configuración heredada de dicha organización para que el grupo de ejecutores pueda poner el ejecutor disponible para sus repositorios. +To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. -Para obtener más información acerca de cómo cambiar la configuración de acceso en un grupo de ejecutores, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados utilizando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". +For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index 1f5dde82bd..794d71707e 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Autoescalar con ejecutores auto-hospedados -intro: Puedes escalar tus ejecutores auto-hospedados automáticamente en respuesta a eventos de webhook. +title: Autoscaling with self-hosted runners +intro: You can automatically scale your self-hosted runners in response to webhook events. versions: fpt: '*' ghec: '*' @@ -13,68 +13,68 @@ type: overview {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca del autoescalamiento +## About autoscaling -Puedes incrementar o decrementar la cantidad de ejecutores auto-hospedados en tu ambiente automáticamente como respuesta a los eventos de webhook que recibes con una etiqueta particular. Por ejemplo, puedes crear una automatización que agregue un ejecutor auto-hospedado cada vez que recibes un [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) evento de webhook con la actividad de [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job), el cual te notifica que hay un job nuevo listo para procesarse. La carga útil de un webhook incluye datos de etiqueta, así que puedes identificar el tipo de ejecutor que está solicitando el job. Una vez que haya terminado un job, puedes crear una automatización que elimine el ejecutor en respuesta a la actividad [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) del `workflow_job`. +You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. ## Recommended autoscaling solutions -{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. +{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. -The following repositories have detailed instructions for setting up these autoscalers: +The following repositories have detailed instructions for setting up these autoscalers: -- [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runnners. +- [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runners. - [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - A Terraform module for scalable {% data variables.product.prodname_actions %} runners on Amazon Web Services. Each solution has certain specifics that may be important to consider: -| **Características** | **actions-runner-controller** | **terraform-aws-github-runner** | -|:------------------------------ |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- | -| Tiempo de ejecución | Kubernetes | Linux and Windows VMs | -| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services | -| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. | -| Pull-based autoscaling support | Sí | No | +| **Features** | **actions-runner-controller** | **terraform-aws-github-runner** | +| :--- | :--- | :--- | +| Runtime | Kubernetes | Linux and Windows VMs | +| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services | +| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. | +| Pull-based autoscaling support | Yes | No | -## Utilizar ejecutores efímeros para autoescalar +## Using ephemeral runners for autoscaling -{% data variables.product.prodname_dotcom %} recomienda implementar el autoescalamiento con ejecutores auto-hospedados efímeros; no se recomienda autoescalar con ejecutores auto-hospedados persistentes. En casos específicos, {% data variables.product.prodname_dotcom %} no puede garantizar que los jobs no se asignen a los ejecutores persistentes mientras están cerrados. Con los ejecutores efímeros, esto puede garantizarse, ya que {% data variables.product.prodname_dotcom %} solo asigna un job a un ejecutor. +{% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner. -Este acercamiento te permite administrar tus ejecutores como sistemas efímeros, ya que puedes utilizar la automatización para proporcionar un ambiente limpio para cada job. Esto ayuda a limitar la exposición de cualquier recurso sensible de los jobs anteriores y también ayuda a mitigar el riesgo de un ejecutor puesto en riesgo que esté recibiendo jobs nuevos. +This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs. -Para agregar un ejecutor efímero a tu ambiente, incluye el parámetro `--ephemeral` cuando registres tu ejecutor utilizando `config.sh`. Por ejemplo: +To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. For example: ``` $ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral ``` -El servicio de {% data variables.product.prodname_actions %} entonces quitará el registro del ejecutor automáticamente después de que haya procesado un job. Entonces podrás crear tu propia automatización que elimine el ejecutor después de que se desregistró. +The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered. {% note %} -**Nota:** Si un job se etiqueta por algún tipo de ejecutor, pero no hay ninguno disponible que empate con este tipo, dicho job no fallará inmediatamente en el momento de ponerse en cola. En vez de esto, el job permanecerá en cola hasta que venza el tiempo límite de 24 horas. +**Note:** If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. Instead, the job will remain queued until the 24 hour timeout period expires. {% endnote %} -## Utilizar webhooks para autoescalar +## Using webhooks for autoscaling -Puedes crear tu propio ambiente de autoescalamiento utilizando cargas útiles que recibas del webhook de [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job). Este webhook está disponible en los niveles de repositorio, organización y empresa y la carga útil de este evento contiene una clave de `action` que corresponde a las etapas del ciclo de vida de un job de un flujo de trabajo; por ejemplo, cuando los jobs se ponen como `queued`, `in_progress`, y `completed`. Entonces debes crear tu propia automatización de escalamiento en respuesta a estas cargas útiles de webhook. +You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads. -- Para obtener más información sobre el webhook de `workflow_job`, consulta la sección de "[Eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)". -- Para aprender cómo trabajar con los webhooks, consulta la sección "[Crear webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)". +- For more information about the `workflow_job` webhook, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." +- To learn how to work with webhooks, see "[Creating webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)." -## Requisitos de autenticación +## Authentication requirements -You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). Para autenticarte en la API, tu implementación de auto-escalamiento puede utilizar un token de acceso o una app de {% data variables.product.prodname_dotcom %}. +You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. -Tu token de acceso necesitará el siguiente alcance: +Your access token will require the following scope: -- Para los repositorios privados, utiliza un token de acceso con el [alcance de `repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). -- Para los repositorios públicos, utiliza un token de acceso con el [alcance de `public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). +- For private repositories, use an access token with the [`repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). +- For public repositories, use an access token with the [`public_repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). -Para autenticarte utilizando una App de {% data variables.product.prodname_dotcom %}, se le debe asignar los siguientes permisos: -- Para los repositorios, asigna el permiso de `administration`. -- Para las organizaciones, asigna el permiso de `organization_self_hosted_runners`. +To authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions: +- For repositories, assign the `administration` permission. +- For organizations, assign the `organization_self_hosted_runners` permission. You can register and delete enterprise self-hosted runners using [the API](/rest/reference/enterprise-admin#github-actions). To authenticate to the API, your autoscaling implementation can use an access token. -Your access token will requite the `manage_runners:enterprise` scope. +Your access token will require the `manage_runners:enterprise` scope. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 450b907c1d..ef4fa168c6 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Monitorear y solucionar problemas para los ejecutores auto-hospedados -intro: Puedes monitorear tus ejecutores auto-hospedados para ver su actividad y diagnosticar problemas comunes. +title: Monitoring and troubleshooting self-hosted runners +intro: You can monitor your self-hosted runners to view their activity and diagnose common issues. redirect_from: - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners @@ -12,7 +12,7 @@ versions: ghec: '*' type: tutorial defaultPlatform: linux -shortTitle: Monitorear & solucionar problemas +shortTitle: Monitor & troubleshoot --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -20,7 +20,7 @@ shortTitle: Monitorear & solucionar problemas {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Comprobar el estado de un ejecutor autoalojado utilizando {{ site.data.variables.product.prodname_dotcom }} +## Checking the status of a self-hosted runner {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} @@ -28,41 +28,41 @@ shortTitle: Monitorear & solucionar problemas {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. - El estado puede ser uno de los siguientes: + The status can be one of the following: - * **Idle (Inactivo)**: El ejecutor está conectado a {% data variables.product.product_name %} y está listo para ejecutar puestos de trabajo. - * **Active (Activo)**: Actualmente, el ejecutor está ejecutando un puesto de trabajo. - * **Offline (Sin conexión)**: El ejecutor no está conectado a {% data variables.product.product_name %}. Esto puede deberse a que la máquina está fuera de línea, la aplicación del ejecutor autoalojado no se está ejecutando en la máquina o la aplicación del ejecutor autoalojado no se puede comunicar con {% data variables.product.product_name %}. + * **Idle**: The runner is connected to {% data variables.product.product_name %} and is ready to execute jobs. + * **Active**: The runner is currently executing a job. + * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}. -## Revisar los archivos de bitácora de la aplicación del ejecutor auto-hospedado +## Reviewing the self-hosted runner application log files -Puedes monitorear el estado de la aplicación del ejecutor auto-hospedado y de sus actividades. Los archivos de bitácora se mantienen en el directorio `_diag`, y se genera uno nuevo cada que se inicia la aplicación. El nombre de archivo comienza con *Runner_*, y le sige una marca de tiempo UTC de cuando se inició la aplicación. +You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory, and a new one is generated each time the application is started. The filename begins with *Runner_*, and is followed by a UTC timestamp of when the application was started. -Para obtener registros detallados sobre las ejecuciones de jobs en el flujo de trabajo, consulta la siguiente sección que describe los archivos *Worker_*. +For detailed logs on workflow job executions, see the next section describing the *Worker_* files. -## Revisar el archivo de bitácora de un job +## Reviewing a job's log file -La aplicación del ejecutor auto-hospedado crea un archivo de bitácora detallado para cada job que procesa. Estos archivos se guardan en el directorio `_diag`, y el nombre de archivo comienza con el prefijo *Worker_*. +The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory, and the filename begins with *Worker_*. {% linux %} -## Utilizar journalctl para revisar el servicio de la aplicación del ejecutor auto-hospedado +## Using journalctl to check the self-hosted runner application service -Para los ejecutores auto-hospedados basados en Linux que se ejecutan en la aplicación utilizando un servicio, puedes utilizar `journalctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en systemd utiliza la siguiente convención de nomenclatura: `actions.runner.-..service`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre de un servicio es revisando el archivo _.service_. Por ejemplo: +For Linux-based self-hosted runners running the application using a service, you can use `journalctl` to monitor their real-time activity. The default systemd-based service uses the following naming convention: `actions.runner.-..service`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file. For example: ```shell $ cat ~/actions-runner/.service actions.runner.octo-org-octo-repo.runner01.service ``` -Puedes utilizar `journalctl` para monitorear la actividad del ejecutor auto-hospedado en tiempo real: +You can use `journalctl` to monitor the real-time activity of the self-hosted runner: ```shell $ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f ``` -En este ejemplo de salida, puedes ver como inicia `runner01`, recibe un job llamado `testAction`, y luego muestra el estado resultante: +In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status: ```shell Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service @@ -74,22 +74,23 @@ Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: test Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded ``` -Para ver la configuración de systemd, puedes ubicar archivo de servicio aquí: `/etc/systemd/system/actions.runner.-..service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)". +To view the systemd configuration, you can locate the service file here: `/etc/systemd/system/actions.runner.-..service`. +If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)." {% endlinux %} {% mac %} -## Utilizar launchd para revisar el servicio de la aplicación del ejecutor auto-hospedado +## Using launchd to check the self-hosted runner application service -Para los ejecutores auto-hospedados basados en macOS que se ejecutan en la aplicación como un servicio, puedes utilizar `launchctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en launchd utiliza la siguiente convención de nomenclatura: `actions.runner.-.`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre del servicio es revisando el archivo _.service_ en el directorio del ejecutor: +For macOS-based self-hosted runners running the application as a service, you can use `launchctl` to monitor their real-time activity. The default launchd-based service uses the following naming convention: `actions.runner.-.`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file in the runner directory: ```shell % cat ~/actions-runner/.service /Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist ``` -El script `svc.sh` utiliza `launchctl` para revisar si la aplicación se está ejecutando. Por ejemplo: +The `svc.sh` script uses `launchctl` to check whether the application is running. For example: ```shell $ ./svc.sh status @@ -99,25 +100,26 @@ Started: 379 0 actions.runner.example.runner01 ``` -La salida generada incluye la ID del proceso y el nombre del servicio launchd de la aplicación. +The resulting output includes the process ID and the name of the application’s launchd service. -Para ver la configuración de launchd, puedes ubicar el archivo del servicio aquí: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)". +To view the launchd configuration, you can locate the service file here: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. +If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)." {% endmac %} {% windows %} -## Utilizar PowerShell para revisar el servicio de la aplicación del ejecutor auto-hospedado +## Using PowerShell to check the self-hosted runner application service -Para los ejecutores auto-hospedados basados en Windows que se ejecuten en la aplicación como servicio, puedes utilizar PowerShell para monitorear su actividad en tiempo real. El servicio utiliza la convención de nomenclatura `GitHub Actions Runner (-.)`. También puedes encontrar el nombre del servicio si revisas el archivo _.service_ en el directorio del ejecutor: +For Windows-based self-hosted runners running the application as a service, you can use PowerShell to monitor their real-time activity. The service uses the naming convention `GitHub Actions Runner (-.)`. You can also find the service's name by checking the _.service_ file in the runner directory: ```shell PS C:\actions-runner> Get-Content .service actions.runner.octo-org-octo-repo.runner01.service ``` -Puedes ver el estado del ejecutor en la aplicación _Services_ de Windows (`services.msc`). También puedes utilizar PowerShell para revisar si el servicio se está ejecutando: +You can view the status of the runner in the Windows _Services_ application (`services.msc`). You can also use PowerShell to check whether the service is running: ```shell PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status @@ -126,7 +128,7 @@ Name Status actions.runner.octo-org-octo-repo.runner01.service Running ``` -Puedes utilizar PowerShell para revisar la actividad reciente del ejecutor auto-hospedado. En este ejemplo de salida, puedes ver que la aplicación comienza, recibe un job llamado `testAction`, y después muestra el estado resultante: +You can use PowerShell to check the recent activity of the self-hosted runner. In this example output, you can see the application start, receive a job named `testAction`, and then display the resulting status: ```shell PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService @@ -145,34 +147,34 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% endwindows %} -## Monitorear el proceso de actualización automática +## Monitoring the automatic update process -Te recomendamos que revises el proceso de actualización automático a menudo, ya que el ejecutor auto-hospedado no podrá procesar jobs si cae debajo de cierto umbral de versiones. La aplicación del ejecutor auto-hospedado se actualiza automáticamente, pero nota que este proceso no incluye ninguna actualización al sistema operativo ni a otro tipo de software; necesitarás administrar estas actualizaciones por separado. +We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates. -Puedes ver las actividades de actualización en los archivos de bitácora *Runner_*. Por ejemplo: +You can view the update activities in the *Runner_* log files. For example: ```shell [Feb 12 12:37:07 INFO SelfUpdater] An update is available. ``` -Adicionalmente, puedes encontrar más información en los archivos de bitácora _SelfUpdate_ ubicados en el directorio `_diag`. +In addition, you can find more information in the _SelfUpdate_ log files located in the `_diag` directory. {% linux %} -## Solucionar problemas en los contenedores de los ejecutores auto-hospedados +## Troubleshooting containers in self-hosted runners -### Revisar que se haya instalado Docker +### Checking that Docker is installed -Si tus jobs necesitan contenedores, entonces el ejecutor auto-hospedado debe estar basado en Linux y necesita contar con Docker instalado. Revisa que tu ejecutor auto-hospedado tenga Docker instalado y que el servicio se esté ejecutando. +If your jobs require containers, then the self-hosted runner must be Linux-based and needs to have Docker installed. Check that your self-hosted runner has Docker installed and that the service is running. -Puedes utilizar `systemctl` para revisar el estado del servicio: +You can use `systemctl` to check the service status: ```shell $ sudo systemctl is-active docker.service active ``` -Si no se ha instalado Docker, entonces las acciones dependientes fallarán con los siguientes errores: +If Docker is not installed, then dependent actions will fail with the following errors: ```shell [2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker' @@ -180,15 +182,15 @@ Si no se ha instalado Docker, entonces las acciones dependientes fallarán con l [2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' ``` -### Revisar los permisos de Docker +### Checking the Docker permissions -Si tu job falla con el siguiente error: +If your job fails with the following error: ```shell dial unix /var/run/docker.sock: connect: permission denied ``` -Revisa que la cuenta de servicio del ejecutor auto-hospedado tenga permiso de utilizar el servicio de Docker. Puedes identificar esta cuenta revisando la configuración del ejecutor auto-hospedado en systemd. Por ejemplo: +Check that the self-hosted runner's service account has permission to use the Docker service. You can identify this account by checking the configuration of the self-hosted runner in systemd. For example: ```shell $ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md index d5266d2eca..4eabb1ec41 100644 --- a/translations/es-ES/content/actions/index.md +++ b/translations/es-ES/content/actions/index.md @@ -1,7 +1,7 @@ --- -title: Documentación de GitHub Actions +title: GitHub Actions Documentation shortTitle: GitHub Actions -intro: 'Automatiza, personaliza y ejecuta tus flujos de trabajo de desarrollo de software directamente en tu repositorio con {% data variables.product.prodname_actions %}. Puedes descubrir, crear y compartir acciones para realizar cualquier trabajo que quieras, incluido CI/CD, y combinar acciones en un flujo de trabajo completamente personalizado.' +intro: 'Automate, customize, and execute your software development workflows right in your repository with {% data variables.product.prodname_actions %}. You can discover, create, and share actions to perform any job you''d like, including CI/CD, and combine actions in a completely customized workflow.' introLinks: overview: /actions/learn-github-actions/understanding-github-actions quickstart: /actions/quickstart @@ -47,19 +47,19 @@ versions: children: - /quickstart - /learn-github-actions - - /creating-actions - - /security-guides + - /managing-workflow-runs - /automating-builds-and-tests - /deployment - - /managing-issues-and-pull-requests - - /publishing-packages - /using-containerized-services - - /advanced-guides - - /managing-workflow-runs + - /publishing-packages + - /managing-issues-and-pull-requests + - /migrating-to-github-actions - /monitoring-and-troubleshooting-workflows - /using-github-hosted-runners - /hosting-your-own-runners - - /migrating-to-github-actions + - /security-guides + - /advanced-guides + - /creating-actions - /guides --- diff --git a/translations/es-ES/content/actions/learn-github-actions/contexts.md b/translations/es-ES/content/actions/learn-github-actions/contexts.md index ddc3219ded..84abe983fe 100644 --- a/translations/es-ES/content/actions/learn-github-actions/contexts.md +++ b/translations/es-ES/content/actions/learn-github-actions/contexts.md @@ -1,7 +1,7 @@ --- -title: Contextos -shortTitle: Contextos -intro: Puedes acceder a información de contexto en los flujos de trabajo y acciones. +title: Contexts +shortTitle: Contexts +intro: You can access context information in workflows and actions. redirect_from: - /articles/contexts-and-expression-syntax-for-github-actions - /github/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions @@ -20,137 +20,156 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de los contextos +## About contexts {% data reusables.github-actions.context-injection-warning %} -Los contextos son una manera de acceder a información acerca de las ejecuciones de flujo de trabajo, los entornos del ejecutor, los trabajos y los pasos. Los contextos usan la sintaxis de expresión. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Contexts use the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." {% raw %} `${{ }}` {% endraw %} -| Nombre del contexto | Type | Descripción | -| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `github` | `objeto` | Información sobre la ejecución del flujo de trabajo. Para obtener más información, consulta [github context](#github-context). | -| `env` | `objeto` | Contiene variables de entorno establecidas en un flujo de trabajo, trabajo o paso. Para obtener más información, consulta el [contexto `env`](#env-context). | -| `job` | `objeto` | Información sobre el trabajo actualmente en ejecución. Para obtener más información, consulta contexto de [`job`](#job-context). | -| `pasos` | `objeto` | Información sobre los pasos que se han ejecutado en este trabajo. Para obtener más información, consulta contexto de [`steps`](#steps-context). | -| `runner` | `objeto` | Incluye información sobre el ejecutor que está realizando el trabajo actual. Para más información, consulta [Contexto del `ejecutador (runner)`](#runner-context). | -| `secrets` | `objeto` | Habilita el acceso a los secretos. Para más información sobre secretos, consulta "[Creando y usando secretos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." | -| `strategy` | `objeto` | Brinda acceso a los parámetros de estrategia configurados y a la información sobre el puesto actual. Los parámetros de estrategia incluyen `fail-fast`, `job-index`, `job-total` y `max-parallel`. | -| `matrix` | `objeto` | Brinda acceso a los parámetros de la matriz que configuraste para el puesto actual. Por ejemplo, si configuraste una matriz de construcción con las versiones `os` y `node`, el objeto de contexto `matrix` incluye las versiones `os` y `node` del puesto actual. | -| `needs` | `objeto` | Habilita el acceso de las salidas de todos los jobs que se definen como una dependencia para el job actual. Para obtener más información, consulta [`needs` context](#needs-context). | +| Context name | Type | Description | +|---------------|------|-------------| +| `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). | +| `env` | `object` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context). | +| `job` | `object` | Information about the currently executing job. For more information, see [`job` context](#job-context). | +| `steps` | `object` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context). | +| `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). | +| `secrets` | `object` | Enables access to secrets. For more information about secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." | +| `strategy` | `object` | Enables access to the configured strategy parameters and information about the current job. Strategy parameters include `fail-fast`, `job-index`, `job-total`, and `max-parallel`. | +| `matrix` | `object` | Enables access to the matrix parameters you configured for the current job. For example, if you configure a matrix build with the `os` and `node` versions, the `matrix` context object includes the `os` and `node` versions of the current job. | +| `needs` | `object` | Enables access to the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). | +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}| `inputs` | `object` | Enables access to the inputs of reusable workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %} -Como parte de una expresión, puedes acceder a la información del contexto usando una de las siguientes dos sintaxis. -- Sintaxis de índice: `github['sha']` -- Sintaxis de desreferencia de propiedad: `github.sha` +As part of an expression, you may access context information using one of two syntaxes. +- Index syntax: `github['sha']` +- Property dereference syntax: `github.sha` -Para usar la sintaxis de desreferencia de propiedad, el nombre de la propiedad debe cumplir con lo siguiente: -- comenzar con `a-Z` o `_`. -- estar seguida por `a-Z` `0-9` `-` o `_`. +In order to use property dereference syntax, the property name must: +- start with `a-Z` or `_`. +- be followed by `a-Z` `0-9` `-` or `_`. -### Determinar cuándo utilizar contextos +### Determining when to use contexts {% data reusables.github-actions.using-context-or-environment-variables %} -### contexto de `github` +### `github` context -El contexto de `github` contiene información sobre la ejecución del flujo de trabajo y el evento que desencadenó la ejecución. Puedes leer la mayoría de los datos de contexto de `github` en las variables del entorno. Para más información sobre las variables de entorno, consulta "[Utilizando variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." +The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| Nombre de la propiedad | Type | Descripción | -| ------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `objeto` | El contexto de nivel superior disponible durante cualquier trabajo o paso en un flujo de trabajo. | -| `github.action` | `secuencia` | El nombre de la acción que se está ejecutando actualmente. {% data variables.product.prodname_dotcom %} elimina caracteres especiales o usa el nombre `__run` cuando el paso actual ejecuta un script. Si utilizas la misma acción más de una vez en el mismo job, el nombre incluirá un sufijo con el número de secuencia con un guion bajo antes de este. Por ejemplo, el primer script que ejecutes tendrá el nombre `__run`, y el segundo script será nombrado `__run_2`. Del mismo modo, la segunda invocación de `actions/checkout` será `actionscheckout2`. | -| `github.action_path` | `secuencia` | La ruta en donde se ubica tu acción. Puedes utilizar esta ruta para acceder fácilmente a los archivos ubicados en el mismo repositorio que tu acción. Este atributo solo es compatible en las acciones compuestas. | -| `github.actor` | `secuencia` | El inicio de sesión del usuario que inició la ejecución del flujo de trabajo. | -| `github.base_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`. | -| `github.event` | `objeto` | La carga de webhook del evento completo. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/articles/events-that-trigger-workflows/)". "Puedes acceder a propiedades individuales del evento que utiliza este contexto. | -| `github.event_name` | `secuencia` | El nombre del evento que activó la ejecución del flujo de trabajo. | -| `github.event_path` | `secuencia` | La ruta a la carga del webhook del evento completo en el ejecutor. | -| `github.head_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`. | -| `github.job` | `secuencia` | El [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual. | -| `github.ref` | `secuencia` | La rama o ref de etiqueta que activó la ejecución del flujo de trabajo. Para las ramas, este es el formato `refs/heads/` y, para las etiquetas, es `refs/tags/`. | -| `github.repository` | `secuencia` | El nombre del repositorio y del propietario. Por ejemplo, `Codertocat/Hello-World`. | -| `github.repository_owner` | `secuencia` | El nombre del propietario del repositorio. Por ejemplo, `Codertocat`. | -| `github. run_id` | `secuencia` | {% data reusables.github-actions.run_id_description %} -| `github. run_number` | `secuencia` | {% data reusables.github-actions.run_number_description %} -| `github.run_attempt` | `secuencia` | Un número único para cada intento de ejecución de un flujo de trabajo particular en un repositorio. Este número comienza en 1 para el primer intento de ejecución del flujo de trabajo e incrementa con cada re-ejecución. | -| `github.server_url` | `secuencia` | Devuelve la URL al servidor de GitHub. Por ejemplo: `https://github.com`. | -| `github.sha` | `secuencia` | El SHA de confirmación que activó la ejecución del flujo de trabajo. | -| `github.token` | `secuencia` | Un token para autenticar en nombre de la aplicación de GitHub instalada en tu repositorio. Esto es funcionalmente equivalente al secreto de `GITHUB_TOKEN`. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | -| `github.workflow` | `secuencia` | El nombre del flujo de trabajo. Si el archivo de flujo de trabajo no especifica un `nombre`, el valor de esta propiedad es la ruta completa del archivo del flujo de trabajo en el repositorio. | -| `github.workspace` | `secuencia` | El directorio de trabajo predeterminado para los pasos y la ubicación predeterminada de tu repositorio cuando usas la acción [`checkout`](https://github.com/actions/checkout). | +| Property name | Type | Description | +|---------------|------|-------------| +| `github` | `object` | The top-level context available during any job or step in a workflow. | +| `github.action` | `string` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. | +| `github.action_path` | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | +| `github.actor` | `string` | The login of the user that initiated the workflow run. | +| `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.event` | `object` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. | +| `github.event_name` | `string` | The name of the event that triggered the workflow run. | +| `github.event_path` | `string` | The path to the full event webhook payload on the runner. | +| `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.job` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | +| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %} +| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | +| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | +| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} | +{%- endif %} +| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. | +| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. | +| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | +| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} | +| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | +| `github.server_url` | `string` | Returns the URL of the GitHub server. For example: `https://github.com`. | +| `github.sha` | `string` | The commit SHA that triggered the workflow run. | +| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | +| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | +| `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | -### contexto de `env` +### `env` context -El contexto de `Env` contiene las variables de entorno que se han establecido en un flujo de trabajo, puesto o paso. Para obtener más información acerca de la configuración de variables de entorno en tu flujo de trabajo, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)". +The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)." -La sintaxis de contexto `env` te permite usar el valor de una variable de entorno en tu archivo de flujo de trabajo. Puedes utilizar el contexto `env` en el valor de cualquier clave en un **paso**, con excepción de las claves `id` y `uses`. Para obtener más información sobre la sintaxis del paso, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". +The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)." -Si quieres usar el valor de una variable de entorno dentro de un ejecutor, usa el método normal del sistema operativo del ejecutor para leer las variables de entorno. +If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables. -| Nombre de la propiedad | Type | Descripción | -| ---------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------- | -| `env` | `objeto` | Este contexto cambia para cada paso de un trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | -| `Env.` | `secuencia` | El valor de una variable de entorno específica. | +| Property name | Type | Description | +|---------------|------|-------------| +| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. | +| `env.` | `string` | The value of a specific environment variable. | -### contexto de `job` +### `job` context -El contexto de `job` contiene información sobre el trabajo de ejecución actual. +The `job` context contains information about the currently running job. -| Nombre de la propiedad | Type | Descripción | -| ----------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `job` | `objeto` | Este contexto cambia para cada trabajo de una ejecución de flujo de trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | -| `job.container` | `objeto` | Información sobre el contenedor del trabajo. Para obtener más información sobre los contenedores, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)". | -| `job.container.id` | `secuencia` | La Id de la red del contenedor. | -| `job.container.network` | `secuencia` | La Id. de la red del contenedor. El ejecutor crea la red usada por todos los contenedores en un trabajo. | -| `job.services` | `objeto` | Los contenedores de servicio creados para un trabajo. Para obtener más información sobre los contenedores de servicios, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)". | -| `job.services..id` | `secuencia` | La Id del contenedor de servicio. | -| `job.services..network` | `secuencia` | La Id. de la red del contenedor de servicios. El ejecutor crea la red usada por todos los contenedores en un trabajo. | -| `job.services..ports` | `objeto` | Los puertos expuestos del contenedor del servicio. | -| `job.status` | `secuencia` | El estado actual del trabajo. Los valores posibles son `success`, `failure` o `cancelled`. | +| Property name | Type | Description | +|---------------|------|-------------| +| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. | +| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." | +| `job.container.id` | `string` | The id of the container. | +| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. | +| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." | +| `job.services..id` | `string` | The id of the service container. | +| `job.services..network` | `string` | The id of the service container network. The runner creates the network used by all containers in a job. | +| `job.services..ports` | `object` | The exposed ports of the service container. | +| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. | -### contexto de `steps` +### `steps` context -El contexto de `steps` contiene información sobre los pasos del trabajo actual que ya se han ejecutado. +The `steps` context contains information about the steps in the current job that have already run. -| Nombre de la propiedad | Type | Descripción | -| --------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `pasos` | `objeto` | Este contexto cambia para cada paso de un trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | -| `steps..outputs` | `objeto` | El conjunto de salidas definido para el paso. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". | -| `steps..conclusion` | `secuencia` | El resultado de un paso completado después de que se aplica [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error). Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. Cuando falla un paso de `continue-on-error`, el `outcome` es `failure`, pero la `conclusion` final es `success`. | -| `steps..outcome` | `secuencia` | El resultado de un paso completado antes de que se aplique [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error). Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. Cuando falla un paso de `continue-on-error`, el `outcome` es `failure`, pero la `conclusion` final es `success`. | -| `steps..outputs.` | `secuencia` | El valor de un resultado específico. | +| Property name | Type | Description | +|---------------|------|-------------| +| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. | +| `steps..outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." | +| `steps..conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. | +| `steps..outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. | +| `steps..outputs.` | `string` | The value of a specific output. | -### Contexto de `runner` +### `runner` context -El contexto de `runner` contiene información sobre el ejecutor que está ejecutando el trabajo actual. +The `runner` context contains information about the runner that is executing the current job. -| Nombre de la propiedad | Type | Descripción | -| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `runner.name` | `secuencia` | {% data reusables.actions.runner-name-description %} -| `runner.os` | `secuencia` | {% data reusables.actions.runner-os-description %} -| `runner.temp` | `secuencia` | {% data reusables.actions.runner-temp-directory-description %} -| `runner.tool_cache` | `secuencia` | {% ifversion ghae %}Para obtener instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tiene instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} +| Property name | Type | Description | +|---------------|------|-------------| +| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} | +| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} | +| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} | +| `runner.tool_cache` | `string` | {% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}| -### Contexto `needs` +### `needs` context -El contexto `needs` contiene salidas de todos los jobs que se definen como dependencia del job actual. Para obtener más información sobre la definición de dependencias de jobs, consulta la sección "[Sintaxis de flujos de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". +The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)." -| Nombre de la propiedad | Type | Descripción | -| -------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------- | -| `needs.` | `objeto` | Un solo job del cual depende el job actual. | -| `needs..outputs` | `objeto` | El conjunto de resultados de un job del cual depende el job actual. | -| `needs..outputs.` | `secuencia` | El valor de un resultado específico para un job del cual depende el job actual. | -| `needs..result` | `secuencia` | El resultado de un job del cual depende el job actual. Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. | +| Property name | Type | Description | +|---------------|------|-------------| +| `needs.` | `object` | A single job that the current job depends on. | +| `needs..outputs` | `object` | The set of outputs of a job that the current job depends on. | +| `needs..outputs.` | `string` | The value of a specific output for a job that the current job depends on. | +| `needs..result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. | -#### Ejemplo de impresión de información de contexto de un archivo de registro +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %} +### `inputs` context -Para revisar la información accesible en cada contexto, puedes utilizar este ejemplo de archivo de flujo de trabajo. +The `inputs` context contains information about the inputs of reusable workflow. The inputs are defined in [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events). These inputs are passed from [`jobs..with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow. + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)". + +| Property name | Type | Description | +|---------------|------|-------------| +| `inputs` | `object` | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). | +| `inputs.` | `string` or `number` or `boolean` | Each input value passed from an external workflow. | +{% endif %} + +#### Example printing context information to the log file + +To inspect the information that is accessible in each context, you can use this workflow file example. {% data reusables.github-actions.github-context-warning %} @@ -190,41 +209,79 @@ jobs: ``` {% endraw %} -## Disponibilidad de contexto +## Context availability -Hay diferentes contextos disponibles a lo largo de un ejecutor de flujo de trabajo. Por ejemplo, el contexto `secrets` solo puede utilizarse en algunos lugares dentro de un job. +Different contexts are available throughout a workflow run. For example, the `secrets` context may only be used at certain places within a job. -Adicionalmente, algunas funcionalidades solo pueden utilizarse en algunos lugares. Por ejemplo, la función `hashFiles` no está disponible en todas partes. +In addition, some functions may only be used in certain places. For example, the `hashFiles` function is not available everywhere. -La siguiente tabla indica si cada contexto y fución especial puede utilizarse dentro de un flujo de trabajo. A menos de que se liste a continuación, las funciones se pueden utilizar donde sea. +The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere. -| Ruta | Contexto | Funciones especiales | -| -------------------------- | -------------------------- | -------------------------- | -| concurrency | github | | -| env | github, secretos | | -| jobs.<job_id>.concurrency | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.container | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.container.credentials | github, necesidades, estrategia, matriz, env, secretos | | -| jobs.<job_id>.container.env.<env_id> | github, necesidades, estrategia, matriz, job, ejecutar, env, secretos | | -| jobs.<job_id>.continue-on-error | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.defaults.run | github, necesidades, estrategia, matriz, env | | -| jobs.<job_id>.env | github, necesidades, estrategia, matriz, secretos | | -| jobs.<job_id>.environment | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.environment.url | github, necesidades, estrategia, matriz, job, ejecutor, env, pasos | | -| jobs.<job_id>.if | github, necesidades | siempre, cancellado, éxito, fallo | -| jobs.<job_id>.name | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.outputs.<output_id> | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | | -| jobs.<job_id>.runs-on | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.services | github, necesidades, estrategia, matriz | | -| jobs.<job_id>.services.<service_id>.credentials | github, necesidades, estrategia, matriz, env, secretos | | -| jobs.<job_id>.services.<service_id>.env.<env_id> | github, necesidades, estrategia, matriz, job, ejecutar, env, secretos | | -| jobs.<job_id>.steps.continue-on-error | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.steps.env | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.steps.if | github, necesidades, estrategia, matriz, job, ejecutor, env, pasos | siempre, cancelado, éxito, fallo, hashFiles | -| jobs.<job_id>.steps.name | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.steps.run | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.steps.timeout-minutes | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.steps.with | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.steps.working-directory | github, necesidades, estrategia, matriz, job, ejecutor, env, secretos, pasos | hashFiles | -| jobs.<job_id>.strategy | github, necesidades | | -| jobs.<job_id>.timeout-minutes | github, necesidades, estrategia, matriz | | +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} + +| Path | Context | Special functions | +| ---- | ------- | ----------------- | +| concurrency | github | | +| env | github, secrets, inputs | | +| jobs.<job_id>.concurrency | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.container | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.container.credentials | github, needs, strategy, matrix, env, secrets, inputs | | +| jobs.<job_id>.container.env.<env_id> | github, needs, strategy, matrix, job, runner, env, secrets, inputs | | +| jobs.<job_id>.continue-on-error | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.defaults.run | github, needs, strategy, matrix, env, inputs | | +| jobs.<job_id>.env | github, needs, strategy, matrix, secrets, inputs | | +| jobs.<job_id>.environment | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.environment.url | github, needs, strategy, matrix, job, runner, env, steps, inputs | | +| jobs.<job_id>.if | github, needs, inputs | always, cancelled, success, failure | +| jobs.<job_id>.name | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.outputs.<output_id> | github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs | | +| jobs.<job_id>.runs-on | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.secrets.<secrets_id> | github, needs, secrets | | +| jobs.<job_id>.services | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.services.<service_id>.credentials | github, needs, strategy, matrix, env, secrets, inputs | | +| jobs.<job_id>.services.<service_id>.env.<env_id> | github, needs, strategy, matrix, job, runner, env, secrets, inputs | | +| jobs.<job_id>.steps.continue-on-error | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.env | github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs | hashFiles | +| jobs.<job_id>.steps.if | github, needs, strategy, matrix, job, runner, env, steps, inputs | always, cancelled, success, failure, hashFiles | +| jobs.<job_id>.steps.name | github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs | hashFiles | +| jobs.<job_id>.steps.run | github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs | hashFiles | +| jobs.<job_id>.steps.timeout-minutes | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.with | github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs | hashFiles | +| jobs.<job_id>.steps.working-directory | github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs | hashFiles | +| jobs.<job_id>.strategy | github, needs, inputs | | +| jobs.<job_id>.timeout-minutes | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.with.<with_id> | github, needs | | +| on.workflow_call.inputs.<inputs_id>.default | github | | +| on.workflow_call.outputs.<output_id>.value | github, jobs, inputs | | +{% else %} +| Path | Context | Special functions | +| ---- | ------- | ----------------- | +| concurrency | github | | +| env | github, secrets | | +| jobs.<job_id>.concurrency | github, needs, strategy, matrix | | +| jobs.<job_id>.container | github, needs, strategy, matrix | | +| jobs.<job_id>.container.credentials | github, needs, strategy, matrix, env, secrets | | +| jobs.<job_id>.container.env.<env_id> | github, needs, strategy, matrix, job, runner, env, secrets | | +| jobs.<job_id>.continue-on-error | github, needs, strategy, matrix | | +| jobs.<job_id>.defaults.run | github, needs, strategy, matrix, env | | +| jobs.<job_id>.env | github, needs, strategy, matrix, secrets | | +| jobs.<job_id>.environment | github, needs, strategy, matrix | | +| jobs.<job_id>.environment.url | github, needs, strategy, matrix, job, runner, env, steps | | +| jobs.<job_id>.if | github, needs | always, cancelled, success, failure | +| jobs.<job_id>.name | github, needs, strategy, matrix | | +| jobs.<job_id>.outputs.<output_id> | github, needs, strategy, matrix, job, runner, env, secrets, steps | | +| jobs.<job_id>.runs-on | github, needs, strategy, matrix | | +| jobs.<job_id>.services | github, needs, strategy, matrix | | +| jobs.<job_id>.services.<service_id>.credentials | github, needs, strategy, matrix, env, secrets | | +| jobs.<job_id>.services.<service_id>.env.<env_id> | github, needs, strategy, matrix, job, runner, env, secrets | | +| jobs.<job_id>.steps.continue-on-error | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.env | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.if | github, needs, strategy, matrix, job, runner, env, steps | always, cancelled, success, failure, hashFiles | +| jobs.<job_id>.steps.name | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.run | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.timeout-minutes | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.with | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.steps.working-directory | github, needs, strategy, matrix, job, runner, env, secrets, steps | hashFiles | +| jobs.<job_id>.strategy | github, needs | | +| jobs.<job_id>.timeout-minutes | github, needs, strategy, matrix | | +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md index fa589387d8..abc75f7a6d 100644 --- a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md +++ b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md @@ -1,6 +1,6 @@ --- -title: Variables del entorno -intro: '{% data variables.product.prodname_dotcom %} establece variables de entorno predeterminadas para cada ejecución de flujo de trabajo de {% data variables.product.prodname_actions %}. También puedes establecer variables de entorno personalizadas en tu archivo de flujo de trabajo.' +title: Environment variables +intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each {% data variables.product.prodname_actions %} workflow run. You can also set custom environment variables in your workflow file.' redirect_from: - /github/automating-your-workflow-with-github-actions/using-environment-variables - /actions/automating-your-workflow-with-github-actions/using-environment-variables @@ -17,11 +17,11 @@ versions: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de las variables de entorno +## About environment variables -{% data variables.product.prodname_dotcom %} establece las variables de entorno predeterminadas que están disponibles para cada paso en una ejecución de flujo de trabajo. Las variables de entorno distinguen mayúsculas de minúsculas. Los comandos que se ejecutan en acciones o pasos pueden crear, leer y modificar variables de entorno. +{% data variables.product.prodname_dotcom %} sets default environment variables that are available to every step in a workflow run. Environment variables are case-sensitive. Commands run in actions or steps can create, read, and modify environment variables. -Para establecer variables de entorno personalizadas, debes especificar las variables en el archivo de flujo de trabajo. Puedes definir variables de ambiente para un paso, job o para todo el flujo de trabajo si utilizas las palabras clave [`jobs..steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs..env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), y [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env). Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)". +To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the [`jobs..steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs..env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)." {% raw %} ```yaml @@ -41,55 +41,60 @@ jobs: ``` {% endraw %} -Para utilizar el valor de una variable de ambiente en un archivo de flujo de trabajo, deberías utilizar el [contexto `env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). Si quieres utilizar el valor de una variable de ambiente dentro de un ejecutor, puedes utilizar el método normal del sistema operativo ejecutor para leer las variables de ambiente. +To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables. -Si utilizas la clave `run` de los archivos del flujo de trabajo para leer las variables de ambiente desde dentro del sistema operativo ejecutor (como se muestra en el ejemplo anterior), dicha variable se sustituirá en el sistema operativo ejecutor después de que se envíe el job al ejecutor. En el caso de otras partes de un archivo de flujo de trabajo, debes utilizar el contexto `env` para leer las variables de ambiente; esto es porque las claves de flujo de trabajo (tales como `if`) requieren que se sustituya la variable durante el procesamiento de dicho flujo de trabajo antes de que se envíe al ejecutor. +If you use the workflow file's `run` key to read environment variables from within the runner operating system (as shown in the example above), the variable is substituted in the runner operating system after the job is sent to the runner. For other parts of a workflow file, you must use the `env` context to read environment variables; this is because workflow keys (such as `if`) require the variable to be substituted during workflow processing before it is sent to the runner. -You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. Para obtener más información, consulta "[Comandos de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)." +You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)." -## Variables de entorno predeterminadas +## Default environment variables -Te recomendamos encarecidamente que las acciones usen variables de entorno para acceder al sistema de archivos en lugar de usar rutas de archivo codificadas de forma rígida. {% data variables.product.prodname_dotcom %} establece variables de entorno para que las acciones se utilicen en todos los entornos del ejecutador. +We strongly recommend that actions use environment variables to access the filesystem rather than using hardcoded file paths. {% data variables.product.prodname_dotcom %} sets environment variables for actions to use in all runner environments. -| Variable de entorno | Descripción | -| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `CI` | Siempre configurar en `true`. | -| `GITHUB_WORKFLOW` | El nombre del flujo de trabajo. | -| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} -| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} -| `GITHUB_JOB` | La [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual. | -| `GITHUB_ACTION` | El único identificador (`id`) de la acción. | -| `GITHUB_ACTION_PATH` | La ruta en donde se ubica tu acción. Puedes utilizar esta ruta para acceder a los archivos ubicados en el mismo repositorio que tu acción. Esta variable solo es compatible con las acciones compuestas. | -| `GITHUB_ACTIONS` | Siempre establecido en `true` cuando {% data variables.product.prodname_actions %} está ejecutando el flujo de trabajo. Puedes usar esta variable para diferenciar cuando las pruebas se ejecutan de forma local o mediante {% data variables.product.prodname_actions %}. | -| `GITHUB_ACTOR` | El nombre de la persona o de la aplicación que inició el flujo de trabajo. Por ejemplo, `octocat`. | -| `GITHUB_REPOSITORY` | El nombre del repositorio y del propietario. Por ejemplo, `octocat/Hello-World`. | -| `GITHUB_EVENT_NAME` | El nombre del evento webhook que activó el flujo de trabajo. | -| `GITHUB_EVENT_PATH` | La ruta del archivo con la carga completa del evento webhook. Por ejemplo, `/github/workflow/event.json`. | -| `GITHUB_WORKSPACE` | La ruta de directorio del espacio de trabajo de {% data variables.product.prodname_dotcom %}, inicialmente vacía. Por ejemplo, `/home/runner/work/my-repo-name/my-repo-name`. La acción [actions/checkout](https://github.com/actions/checkout) verificará los archivos, predeterminadamente una copia de tu repositorio, dentro de este directorio. | -| `GITHUB_SHA` | El SHA de confirmación que activó el flujo de trabajo. Por ejemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | -| `GITHUB_REF` | La referencia de etiqueta o rama que activó el flujo de trabajo. Por ejemplo, `refs/heads/feature-branch-1`. Si no hay una rama o una etiqueta disponible para el tipo de evento, la variable no existirá. | -| `GITHUB_HEAD_REF` | Solo se configura para eventos de solicitudes de cambio. El nombre de la rama principal. | -| `GITHUB_BASE_REF` | Solo se configura para eventos de solicitudes de cambio. El nombre de la rama base. | -| `GITHUB_SERVER_URL` | Devuelve la URL del servidor de {% data variables.product.product_name %}. Por ejemplo: `https://{% data variables.product.product_url %}`. | -| `GITHUB_API_URL` | Devuelve la URL de la API. Por ejemplo: `{% data variables.product.api_url_code %}`. | -| `GITHUB_GRAPHQL_URL` | Devuelve la URL de la API de GraphQL. Por ejemplo: `{% data variables.product.graphql_url_code %}`. | -| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} -| `RUNNER_OS` | {% data reusables.actions.runner-os-description %} -| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} +| Environment variable | Description | +| ---------------------|------------ | +| `CI` | Always set to `true`. | +| `GITHUB_WORKFLOW` | The name of the workflow. | +| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} | +| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} | +| `GITHUB_JOB` | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | +| `GITHUB_ACTION` | The unique identifier (`id`) of the action. | +| `GITHUB_ACTION_PATH` | The path where your action is located. You can use this path to access files located in the same repository as your action. This variable is only supported in composite actions. | +| `GITHUB_ACTIONS` | Always set to `true` when {% data variables.product.prodname_actions %} is running the workflow. You can use this variable to differentiate when tests are being run locally or by {% data variables.product.prodname_actions %}. +| `GITHUB_ACTOR` | The name of the person or app that initiated the workflow. For example, `octocat`. | +| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. | +| `GITHUB_EVENT_NAME` | The name of the webhook event that triggered the workflow. | +| `GITHUB_EVENT_PATH` | The path of the file with the complete webhook event payload. For example, `/github/workflow/event.json`. | +| `GITHUB_WORKSPACE` | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. For example, `/home/runner/work/my-repo-name/my-repo-name`. The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. | +| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. | +| `GITHUB_REF` | The branch or tag ref that triggered the workflow. For example, `refs/heads/feature-branch-1`. If neither a branch or tag is available for the event type, the variable will not exist. | +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %} +| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} | +| `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} | +| `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} | +{%- endif %} +| `GITHUB_HEAD_REF` | Only set for pull request events. The name of the head branch. +| `GITHUB_BASE_REF` | Only set for pull request events. The name of the base branch. +| `GITHUB_SERVER_URL`| Returns the URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. +| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`. +| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`. +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} +| `RUNNER_OS` | {% data reusables.actions.runner-os-description %} +| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} {% tip %} -**Nota:** Si necesitas utilizar la URL de la ejecución de un flujo de trabajo desde dentro de un job, puedes combinar estas variables de ambiente: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` +**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` {% endtip %} -### Determinar cuándo utilizar las variables de ambiente o contextos predeterminados +### Determining when to use default environment variables or contexts {% data reusables.github-actions.using-context-or-environment-variables %} -## Convenciones de nomenclatura para las variables de entorno +## Naming conventions for environment variables -Cuando configuras una variable de ambiente personalizada, no puedes utilizar ninguno de los nombres de variable de ambiente predeterminados que se listan anteriormente con el prefijo `GITHUB_`. Si intentas anular el valor de estas variables de ambiente predeterminadas, se ignorará la tarea. +When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored. -Toda variable de entorno nueva que configures y que apunte a una ubicación en el sistema de archivos debe tener un sufijo `_PATH`. Las variables predeterminadas `HOME` y `GITHUB_WORKSPACE` son excepciones a esta convención, porque las palabras "inicio" (home) y "espacio de trabajo" (workspace) ya implican una ubicación. +Any new environment variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `HOME` and `GITHUB_WORKSPACE` default variables are exceptions to this convention because the words "home" and "workspace" already imply a location. diff --git a/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md index 7cc3d98874..387185f8ca 100644 --- a/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -1,6 +1,6 @@ --- -title: Eventos que desencadenan flujos de trabajo -intro: 'Puedes configurar tus flujos de trabajo para que se ejecuten cuando ocurre una actividad específica en {% data variables.product.product_name %}, en un horario programado o cuando se produce un evento fuera de {% data variables.product.product_name %}.' +title: Events that trigger workflows +intro: 'You can configure your workflows to run when specific activity on {% data variables.product.product_name %} happens, at a scheduled time, or when an event outside of {% data variables.product.product_name %} occurs.' miniTocMaxHeadingLevel: 3 redirect_from: - /articles/events-that-trigger-workflows @@ -12,50 +12,50 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Eventos que desencadenan flujos de trabajo +shortTitle: Events that trigger workflows --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Configurar los eventos del flujo de trabajo +## Configuring workflow events -Puedes configurar los flujos de trabajo para que se ejecuten una o más veces utilizando la sintaxis de flujo de trabajo `on`. Para obtener más información, consulta la sección "[Sintaxis del flujo de trabajo para las {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)". +You can configure workflows to run for one or more events using the `on` workflow syntax. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)." {% data reusables.github-actions.actions-on-examples %} {% note %} -**Nota:** No puedes activar nuevas ejecuciones de flujo de trabajo usando el `GITHUB_TOKEN`. Para obtener más información, consulta "[Activar nuevos flujos de trabajo mediante un token de acceso personal](#triggering-new-workflows-using-a-personal-access-token)". +**Note:** You cannot trigger new workflow runs using the `GITHUB_TOKEN`. For more information, see "[Triggering new workflows using a personal access token](#triggering-new-workflows-using-a-personal-access-token)." {% endnote %} -Los siguientes pasos se producen para activar una ejecución de flujo de trabajo: +The following steps occur to trigger a workflow run: -1. Se produce un evento en tu repositorio, y el evento resultante tiene una confirmación de SHA y una referencia de Git asociadas. -2. El directorio `.github/workflows` en tu repositorio se busca para los archivos de flujo de trabajo en la confirmación SHA o la referencia de Git asociadas. Los archivos de flujo de trabajo deben estar presentes en la confirmación SHA o la referencia de Git que se debe tener en cuenta. +1. An event occurs on your repository, and the resulting event has an associated commit SHA and Git ref. +2. The `.github/workflows` directory in your repository is searched for workflow files at the associated commit SHA or Git ref. The workflow files must be present in that commit SHA or Git ref to be considered. - Por ejemplo, si el evento se produjo en una rama particular del repositorio, los archivos de flujo de trabajo deben estar presentes en el repositorio en esa rama. -1. Se inspeccionarán los archivos de flujo de trabajo para esa confirmación de SHA y referencia de Git, y se activará una nueva ejecución de flujo de trabajo para cualquier flujo de trabajo que tenga valores `on:` que coincidan con el evento desencadenante. + For example, if the event occurred on a particular repository branch, then the workflow files must be present in the repository on that branch. +1. The workflow files for that commit SHA and Git ref are inspected, and a new workflow run is triggered for any workflows that have `on:` values that match the triggering event. - El flujo de trabajo se ejecuta en el código de tu repositorio en la misma confirmación SHA y la referencia de Git que desencadenó el evento. Cuando se ejecuta un flujo de trabajo, {% data variables.product.product_name %} establece las variables de entorno `GITHUB_SHA` (confirmar SHA) y `GITHUB_REF` (referencia de Git) en el entorno del ejecutor. Para obtener más información, consulta "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)". + The workflow runs on your repository's code at the same commit SHA and Git ref that triggered the event. When a workflow runs, {% data variables.product.product_name %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." -## Eventos programados +## Scheduled events -El evento `schedule` te permite activar un flujo de trabajo en una hora programada. +The `schedule` event allows you to trigger a workflow at a scheduled time. {% data reusables.actions.schedule-delay %} -### `programación` +### `schedule` -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------ | ------------------ | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| n/a | n/a | Última confirmación en la rama predeterminada | Rama por defecto | Cuando se establece la ejecución del flujo de trabajo programado. Un flujo de trabajo programado usa[sintaxis cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Para obtener más información, consulta "[Desencadenar un flujo de trabajo con eventos](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)". | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| n/a | n/a | Last commit on default branch | Default branch | When the scheduled workflow is set to run. A scheduled workflow uses [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). For more information, see "[Triggering a workflow with events](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)." | {% data reusables.repositories.actions-scheduled-workflow-example %} -La sintaxis de cron tiene cinco campos separados por un espacio, y cada campo representa una unidad de tiempo. +Cron syntax has five fields separated by a space, and each field represents a unit of time. ``` ┌───────────── minute (0 - 59) @@ -69,54 +69,54 @@ La sintaxis de cron tiene cinco campos separados por un espacio, y cada campo re * * * * * ``` -Puedes usar estos operadores en cualquiera de los cinco campos: +You can use these operators in any of the five fields: -| Operador | Descripción | Ejemplo | -| -------- | -------------------------------- | ----------------------------------------------------------------------------------------------------------- | -| * | Cualquier valor | `* * * * *` se ejecuta todos los días a cada minuto. | -| , | Separador de la lista de valores | `2,10 4,5 * * *` se ejecuta en el minuto 2 y 10 de la cuarta y quinta hora de cada día. | -| - | Rango de valores | `0 4-6 * * *` se ejecuta en el minuto 0 de la cuarta, quinta y sexta hora. | -| / | Valores del paso | `20/15 * * * *` se ejecuta cada 15 minutos a partir del minuto 20 hasta el minuto 59 (minutos 20, 35 y 50). | +| Operator | Description | Example | +| -------- | ----------- | ------- | +| * | Any value | `* * * * *` runs every minute of every day. | +| , | Value list separator | `2,10 4,5 * * *` runs at minute 2 and 10 of the 4th and 5th hour of every day. | +| - | Range of values | `0 4-6 * * *` runs at minute 0 of the 4th, 5th, and 6th hour. | +| / | Step values | `20/15 * * * *` runs every 15 minutes starting from minute 20 through 59 (minutes 20, 35, and 50). | {% note %} -**Nota:** {% data variables.product.prodname_actions %} no es compatible con la sintaxis que no es estándar `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly` y `@reboot`. +**Note:** {% data variables.product.prodname_actions %} does not support the non-standard syntax `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`, and `@reboot`. {% endnote %} -Puedes usar [contrab guru](https://crontab.guru/) para generar tu sintaxis de cron y confirmar a qué hora se ejecutará. Para que puedas comenzar, hay también una lista de [ejemplos de crontab guru](https://crontab.guru/examples.html). +You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html). -Las notificaciones para los flujos de trabajo programados se envían al usuario que modificó por última vez la sintaxis de cron en el archivo de flujo de trabajo. Para obtener más información, por favor consulta la sección "[Notificaciones para las ejecuciones de flujo de trabajo](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)". +Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." -## Eventos manuales +## Manual events -Puedes activar ejecuciones de flujo de trabajo manualmente. Para activar flujos de trabajo específicos en un repositorio, utiliza el evento `workflow_dispatch`. Para activar más de un flujo de trabajo en un repositorio y crear eventos personalizados y tipos de eventos, utiliza el evento `repository_dispatch`. +You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event. ### `workflow_dispatch` -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------- | ------------------ | ---------------------------------------------- | ------------------------- | -| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Última confirmacion en la rama de `GITHUB_REF` | Rama que recibió el envío | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------ | ------------ | ------------ | ------------------| +| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch | -Puedes configurar propiedades de entrada definidas personalmente, valores de entrada predeterminados y entradas requeridas para el evento directamente en tu flujo de trabajo. Cuando se ejecuta el flujod e trabajo, puedes acceder a los valores de entrada en el contexto de `github.event.inputs`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)". +You can configure custom-defined input properties, default input values, and required inputs for the event directly in your workflow. When the workflow runs, you can access the input values in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." -You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Ejecutar un flujo de trabajo manualmente](/actions/managing-workflow-runs/manually-running-a-workflow)". +You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)." - Cuando activas el evento en {% data variables.product.prodname_dotcom %}, puedes proporcionar la `ref` y cualquier `input` directamente en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Utilizar entradas y salidas con una acción](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)". + When you trigger the event on {% data variables.product.prodname_dotcom %}, you can provide the `ref` and any `inputs` directly on {% data variables.product.prodname_dotcom %}. For more information, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)." - To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. Para obtener más información, consulta terminal "[Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)" de la API de REST. + To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. For more information, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" REST API endpoint. -#### Ejemplo +#### Example -Para utilizar el evento de `workflow_dispatch`, necesitas incluirlo como un activador en tu archivo de flujo de trabajo de GitHub Actions. El siguiente ejemplo ejecuta el flujo de trabajo únicamente cuando se activa manualmente: +To use the `workflow_dispatch` event, you need to include it as a trigger in your GitHub Actions workflow file. The example below only runs the workflow when it's manually triggered: ```yaml on: workflow_dispatch ``` -#### Ejemplo de configuración de flujo de trabajo +#### Example workflow configuration -Este ejemplo define las entradas `name` y `home` y las imprime utilizando los contextos `github.event.inputs.name` y `github.event.inputs.home`. Si no se proporciona un `home`, se imprime el valor predeterminado 'The Octoverse'. +This example defines the `name` and `home` inputs and prints them using the `github.event.inputs.name` and `github.event.inputs.home` contexts. If a `home` isn't provided, the default value 'The Octoverse' is printed. {% raw %} ```yaml @@ -145,19 +145,19 @@ jobs: ### `repository_dispatch` -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------ | ------------ | ------------ | ------------------| +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on default branch | Default branch | {% data reusables.github-actions.branch-requirement %} -You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Crear un evento de envío de repositorio](/rest/reference/repos#create-a-repository-dispatch-event)". +You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)." -To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. Para desencadenar la ejecución de un flujo de trabajo, también debes configurar tu flujo de trabajo para usar el evento `repository_dispatch`. +To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the `repository_dispatch` event. -#### Ejemplo +#### Example -Predeterminadamente, todos los `event_types` desencadenan la ejecución de un flujo de trabajo. Puedes limitar tu flujo de trabajo para que se ejecute cuando un valor específico de `event_type` se envíe en la carga útil del webhook de `repository_dispatch`. Tú defines los tipos de evento enviados en la carga útil de `repository_dispatch` cuando creas el repositorio. +By default, all `event_types` trigger a workflow to run. You can limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload. You define the event types sent in the `repository_dispatch` payload when you create the repository dispatch event. ```yaml on: @@ -166,30 +166,30 @@ on: ``` {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} -## Eventos de reutilización de flujos de trabajo +## Workflow reuse events -`workflow_call` es una palabra clave que se utiliza como el valor de `on` en un flujo de trabajo de la misma forma que un evento. Esto indica que se puede llamar a un flujo de trabajo desde otro. Para obtener más información, consulta la sección "[Reutilizar los flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". +`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." ### `workflow_call` -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------ | ------------------ | ------------------------------------------ | ------------------------------------------ | -| El mismo que el flujo de trabajo que llama | n/a | El mismo que el flujo de trabajo que llama | El mismo que el flujo de trabajo que llama | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------ | ------------ | ------------ | ------------------| +| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow | -#### Ejemplo +#### Example -Para que un flujo de trabajo sea reutilizable, debe incluir `workflow_call` como uno de los valores de `on`. El siguiente ejemplo solo ejecuta el flujo de trabajo cuando se le llama desde otro flujo de trabajo: +To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow: ```yaml on: workflow_call ``` {% endif %} -## Eventos de webhook +## Webhook events -Puedes configurar tu flujo de trabajo para que se ejecute cuando se generen los eventos de webhook en {% data variables.product.product_name %}. Algunos eventos tienen más de un tipo de actividad que activa el evento. Si más de un tipo de actividad activa el evento, puedes especificar qué tipos de actividad activarán el flujo de trabajo para que se ejecute. Para obtener más información, consulta la sección "[webhooks](/webhooks)". +You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Some events have more than one activity type that triggers the event. If more than one activity type triggers the event, you can specify which activity types will trigger the workflow to run. For more information, see "[Webhooks](/webhooks)." -No todos los eventos de webhook activan flujos de trabajo. Para encontrar una lista completa de eventos de webhook disponibles y sus cargas útiles, consulta la sección "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads)". +Not all webhook events trigger workflows. For the complete list of available webhook events and their payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} ### `branch_protection_rule` @@ -198,9 +198,9 @@ Runs your workflow anytime the `branch_protection_rule` event occurs. {% data re {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------- | ---------------- | -| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`
    - `edited`
    - `deleted` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`
    - `edited`
    - `deleted` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} @@ -215,17 +215,17 @@ on: ### `check_run` -Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento `check_run`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Ejecuciones de verificación](/rest/reference/checks#runs)". +Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------- | ------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`
    - `rerequested`
    - `completed` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`
    - `rerequested`
    - `completed` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una ejecución de verificación esté como `rerequested` o `completed`. +For example, you can run a workflow when a check run has been `rerequested` or `completed`. ```yaml on: @@ -235,23 +235,23 @@ on: ### `check_suite` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `check_suite`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Suites de verificación](/rest/reference/checks#suites)". +Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)." {% data reusables.github-actions.branch-requirement %} {% note %} -**Nota:** Para evitar flujos de trabajo recurrentes, este evento no activa flujos de trabajo si la comprobación de suite fue creada por {% data variables.product.prodname_actions %}. +**Note:** To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %}. {% endnote %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------ | -------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`
    - `requested`
    - `rerequested`
    | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`
    - `requested`
    - `rerequested`
    | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una comprobación de ejecución ha sido `resolicitada` o `completada`. +For example, you can run a workflow when a check suite has been `rerequested` or `completed`. ```yaml on: @@ -259,15 +259,15 @@ on: types: [rerequested, completed] ``` -### `create (crear)` +### `create` -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, que activa el evento `crear`. Para obtener más información sobre la API de REST, consulta la sección "[Crear una referencia](/rest/reference/git#create-a-reference)". +Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)." -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------- | ------------------ | ------------------------------------------------ | ---------------------- | -| [`create (crear)`](/webhooks/event-payloads/#create) | n/a | Última confirmación en la rama o etiqueta creada | Rama o etiqueta creada | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`create`](/webhooks/event-payloads/#create) | n/a | Last commit on the created branch or tag | Branch or tag created | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `crear`. +For example, you can run a workflow when the `create` event occurs. ```yaml on: @@ -276,15 +276,15 @@ on: ### `delete` -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, que activa el evento `eliminar`. Para obtener más información sobre la API de REST, consulta la sección "[Borrar una referencia](/rest/reference/git#delete-a-reference)". +Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [`delete`](/webhooks/event-payloads/#delete) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`delete`](/webhooks/event-payloads/#delete) | n/a | Last commit on default branch | Default branch | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `eliminar`. +For example, you can run a workflow when the `delete` event occurs. ```yaml on: @@ -293,13 +293,13 @@ on: ### `deployment` -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una implementación, que activa el evento `implementación`. Las implementaciones creadas con SHA de confirmación pueden no tener una referencia de Git. Para obtener más información acerca de la API de REST, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". +Runs your workflow anytime someone creates a deployment, which triggers the `deployment` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Deployments](/rest/reference/repos#deployments)." -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------- | ------------------ | ------------------------------ | ------------------------------------------------------------------ | -| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Confirmación de implementación | Rama o etiqueta que se debe implementar (vacío si está confirmada) | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)| -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `implementación`. +For example, you can run a workflow when the `deployment` event occurs. ```yaml on: @@ -308,13 +308,13 @@ on: ### `deployment_status` -Ejecuta tu flujo de trabajo en cualquier momento en que un tercero proporcione un estado de implementación, que activa un evento de `deployment_status`. Las implementaciones creadas con SHA de confirmación pueden no tener una referencia de Git. Para obtener más información acerca de la API de REST, consulta la sección "[Crear un estado de despliegue](/rest/reference/repos#create-a-deployment-status)". +Runs your workflow anytime a third party provides a deployment status, which triggers the `deployment_status` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Create a deployment status](/rest/reference/repos#create-a-deployment-status)." -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------------ | ------------------ | ------------------------------ | ------------------------------------------------------------------ | -| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Confirmación de implementación | Rama o etiqueta que se debe implementar (vacío si está confirmada) | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)| -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `implementación`. +For example, you can run a workflow when the `deployment_status` event occurs. ```yaml on: @@ -323,24 +323,24 @@ on: {% note %} -**Nota:** Cuando el estado de un estatus de despliegue se configure como `inactive`, no se creará un evento de webhook. +**Note:** When a deployment status's state is set to `inactive`, a webhook event will not be created. {% endnote %} {% ifversion fpt or ghec %} -### `debate` +### `discussion` -Ejecuta tu flujo de trabajo cada que ocurra el evento `discussion`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de GraphQL, consulta la sección "[Debates]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)". +Runs your workflow anytime the `discussion` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`debate`](/webhooks/event-payloads/#discussion) | - `created`
    - `edited`
    - `deleted`
    - `transferred`
    - `pinned`
    - `unpinned`
    - `labeled`
    - `unlabeled`
    - `locked`
    - `unlocked`
    - `category_changed`
    - `answered`
    - `unanswered` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`discussion`](/webhooks/event-payloads/#discussion) | - `created`
    - `edited`
    - `deleted`
    - `transferred`
    - `pinned`
    - `unpinned`
    - `labeled`
    - `unlabeled`
    - `locked`
    - `unlocked`
    - `category_changed`
    - `answered`
    - `unanswered` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un debate está como `created`, `edited`, o `answered`. +For example, you can run a workflow when a discussion has been `created`, `edited`, or `answered`. ```yaml on: @@ -350,17 +350,17 @@ on: ### `discussion_comment` -Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento `discussion_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de GraphQL, consulta la sección "[Debates]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)". +Runs your workflow anytime the `discussion_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`
    - `edited`
    - `deleted`
    | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una propuesta ha sido `created` (creada) o `deleted` (eliminada). +For example, you can run a workflow when an issue comment has been `created` or `deleted`. ```yaml on: @@ -369,17 +369,17 @@ on: ``` {% endif %} -### `bifurcación` +### `fork` -Ejecuta tu flujo de trabajo en cualquier momento en que alguien bifurque un repositorio, lo que activa el evento de `fork`. Para obtener más información sobre la API de REST, consulta la sección "[Crear una bifurcación](/rest/reference/repos#create-a-fork)". +Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [`bifurcación`](/webhooks/event-payloads/#fork) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`fork`](/webhooks/event-payloads/#fork) | n/a | Last commit on default branch | Default branch | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `fork`. +For example, you can run a workflow when the `fork` event occurs. ```yaml on: @@ -388,34 +388,34 @@ on: ### `gollum` -Ejecuta tu flujo de trabajo cuando alguien crea o actualiza una página Wiki, lo que activa el evento `gollum`. +Runs your workflow when someone creates or updates a Wiki page, which triggers the `gollum` event. {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Last commit on default branch | Default branch | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `gollum`. +For example, you can run a workflow when the `gollum` event occurs. ```yaml on: gollum ``` -### `comentario_propuesta` +### `issue_comment` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `issue_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[comentarios de una propuesta](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)". +Runs your workflow anytime the `issue_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`comentario_propuesta`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`
    - `edited`
    - `deleted`
    | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una propuesta ha sido `created` (creada) o `deleted` (eliminada). +For example, you can run a workflow when an issue comment has been `created` or `deleted`. ```yaml on: @@ -423,9 +423,9 @@ on: types: [created, deleted] ``` -El evento `issue_comment` ocurre para los comentarios tanto en propuestas como en solicitudes de cambios. Para determinar si el evento `issue_comment` se activó desde una propuesta o solicitud de cambios, puedes verificar la carga útil del evento para la propiedad `issue.pull_request` y utilizarla como condición para saltarse un job. +The `issue_comment` event occurs for comments on both issues and pull requests. To determine whether the `issue_comment` event was triggered from an issue or pull request, you can check the event payload for the `issue.pull_request` property and use it as a condition to skip a job. -Por ejemplo, puedes elegir ejecutar el job `pr_commented` cuando ocurren los comentarios de evento en una solicitud de cambios, y el job `issue_commented` cuando ocurran eventos de comentarios en una propuesta. +For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue. {% raw %} ```yaml @@ -452,19 +452,19 @@ jobs: ``` {% endraw %} -### `propuestas` +### `issues` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `issues`. {% data reusables.developer-site.multiple_activity_types %} Para obtener información acerca de la API de REST, consulta la sección "[propuestas](/rest/reference/issues)". +Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`propuestas`](/webhooks/event-payloads/#issues) | - `opened`
    - `edited`
    - `deleted`
    - `transferred`
    - `pinned`
    - `unpinned`
    - `closed`
    - `reopened`
    - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `locked`
    - `unlocked`
    - `milestoned`
    - `demilestoned` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`issues`](/webhooks/event-payloads/#issues) | - `opened`
    - `edited`
    - `deleted`
    - `transferred`
    - `pinned`
    - `unpinned`
    - `closed`
    - `reopened`
    - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `locked`
    - `unlocked`
    - `milestoned`
    - `demilestoned` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una propuesta ha sido `opened` (abierta), `edited` (editada), o `milestoned` (marcada como hito). +For example, you can run a workflow when an issue has been `opened`, `edited`, or `milestoned`. ```yaml on: @@ -472,19 +472,19 @@ on: types: [opened, edited, milestoned] ``` -### `etiqueta` +### `label` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `etiquetado`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Etiquetas](/rest/reference/issues#labels)". +Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Labels](/rest/reference/issues#labels)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`etiqueta`](/webhooks/event-payloads/#label) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`label`](/webhooks/event-payloads/#label) | - `created`
    - `edited`
    - `deleted`
    | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un miembro ha sido `creado` o `eliminado`. +For example, you can run a workflow when a label has been `created` or `deleted`. ```yaml on: @@ -492,19 +492,19 @@ on: types: [created, deleted] ``` -### `hito` +### `milestone` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `milestone`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Hitos](/rest/reference/issues#milestones)". +Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`hito`](/webhooks/event-payloads/#milestone) | - `created`
    - `closed`
    - `opened`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`milestone`](/webhooks/event-payloads/#milestone) | - `created`
    - `closed`
    - `opened`
    - `edited`
    - `deleted`
    | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un hito ha sido `abierto` o `eliminado`. +For example, you can run a workflow when a milestone has been `opened` or `deleted`. ```yaml on: @@ -514,15 +514,15 @@ on: ### `page_build` -Ejecuta tu flujo de trabajo en cualquier momento en que alguien suba a una {% data variables.product.product_name %} Rama habilitada para páginas, que activa el evento `page_build`. Para obtener información acerca de la API de REST, consulta la sección "[Páginas](/rest/reference/repos#pages)". +Runs your workflow anytime someone pushes to a {% data variables.product.product_name %} Pages-enabled branch, which triggers the `page_build` event. For information about the REST API, see "[Pages](/rest/reference/repos#pages)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------- | ------------------ | --------------------------------------------- | ------------ | -| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Última confirmación en la rama predeterminada | n/a | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Last commit on default branch | n/a | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `page_build`. +For example, you can run a workflow when the `page_build` event occurs. ```yaml on: @@ -531,17 +531,17 @@ on: ### `project` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Proyectos](/rest/reference/projects)". +Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`project`](/webhooks/event-payloads/#project) | - `created`
    - `updated`
    - `closed`
    - `reopened`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`project`](/webhooks/event-payloads/#project) | - `created`
    - `updated`
    - `closed`
    - `reopened`
    - `edited`
    - `deleted`
    | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un proyecto ha sido `creado` o `eliminado`. +For example, you can run a workflow when a project has been `created` or `deleted`. ```yaml on: @@ -551,17 +551,17 @@ on: ### `project_card` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project_card`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Tarjetas de proyecto](/rest/reference/projects#cards)". +Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`
    - `moved`
    - `converted` to an issue
    - `edited`
    - `deleted` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`
    - `moved`
    - `converted` to an issue
    - `edited`
    - `deleted` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un proyecto ha sido `abierto` o `eliminado`. +For example, you can run a workflow when a project card has been `opened` or `deleted`. ```yaml on: @@ -571,17 +571,17 @@ on: ### `project_column` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project_column`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Columnas de proyecto](/rest/reference/projects#columns)". +Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------ | --------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | -| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`
    - `updated`
    - `moved`
    - `deleted` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`
    - `updated`
    - `moved`
    - `deleted` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una columna de proyecto ha sido `created` o `deleted`. +For example, you can run a workflow when a project column has been `created` or `deleted`. ```yaml on: @@ -591,40 +591,40 @@ on: ### `public` -Ejecuta tu flujo de trabajo en cualquier momento en que alguien haga público un repositorio privado, lo que activa el evento `public`. Para obtener más información acerca de la API de REST, consulta la sección "[Editar repositorios](/rest/reference/repos#edit)". +Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [`public`](/webhooks/event-payloads/#public) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`public`](/webhooks/event-payloads/#public) | n/a | Last commit on default branch | Default branch | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `public`. +For example, you can run a workflow when the `public` event occurs. ```yaml on: public ``` -### `solicitud_extracción` +### `pull_request` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `pull_request`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Solicitudes de cambios](/rest/reference/pulls)". +Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)." {% note %} -**Notas:** -- Predeterminadamente, un flujo de trabajo solo se ejecuta cuando el tipo de actividad de una `pull_request` es `opened`, `synchronize`, o `reopened`. Para activar los flujos de trabajo para más tipos de actividades, usa la palabra clave `tipos`. -- Los flujos de trabajo no se ejecutarán en la actividad de la `pull_request` si esta tiene un conflicto de fusión. El conflicto de fusión se debe resolver primero. +**Notes:** +- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword. +- Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first. {% endnote %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------ | -| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `converted_to_draft`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
    - `auto_merge_enabled`
    - `auto_merge_disabled`{% endif %} | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `converted_to_draft`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
    - `auto_merge_enabled`
    - `auto_merge_disabled`{% endif %} | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` | -Puedes extender o limitar los tipos de actividad por defecto usando la palabra clave `types`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". +You extend or limit the default activity types using the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)." -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una solicitud de extracción ha sido `assigned` (asignada), `opened`, `syncronize` o `reopened`. +For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`. ```yaml on: @@ -634,17 +634,17 @@ on: {% data reusables.developer-site.pull_request_forked_repos_link %} -### `revisión_solicitud de extracción` +### `pull_request_review` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `pull_request_review`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Revisiones de solicitudes de extracción](/rest/reference/pulls#reviews)". +Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)." -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------ | -| [`revisión_solicitud de extracción`](/webhooks/event-payloads/#pull_request_review) | - `submitted`
    - `edited`
    - `dismissed` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`
    - `edited`
    - `dismissed` | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una revisión de solicitud de extracción ha sido `edited` (editada) o `dismissed` (descartada). +For example, you can run a workflow when a pull request review has been `edited` or `dismissed`. ```yaml on: @@ -654,17 +654,17 @@ on: {% data reusables.developer-site.pull_request_forked_repos_link %} -### `comentarios _revisiones_solicitudes de extracción` +### `pull_request_review_comment` -Ejecuta tu flujo de trabajo en cualquier momento en que se modifique una diferencia unificada de solicitud de extracción, que activa el evento `pull_request_review_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección [Revisar comentarios](/rest/reference/pulls#comments). +Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments). -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | ----------------------------------------------------- | ------------------------------------------------ | -| [`comentarios _revisiones_solicitudes de extracción`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`
    - `edited`
    - `deleted` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`
    - `edited`
    - `deleted`| Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un comentario de revisión de solicitud de extracción ha sido `created` o `deleted`. +For example, you can run a workflow when a pull request review comment has been `created` or `deleted`. ```yaml on: @@ -676,21 +676,21 @@ on: ### `pull_request_target` -Este evento se ejecuta en el contexto de la base de la solicitud de cambios en vez de en la confirmación fusionada como lo hace el evento `pull_request`. Esto previene que se ejecute el código inseguro del flujo de trabajo desde el encabezado de la solicitud de cambios, el cual pudiera alterar a tu repositorio, o borrar cualquier secreto que utilices en tu flujo de trabajo. Este evento te permite hacer cosas como crear flujos de trabajo que etiquetan y comentan las solicitudes de cambios, con base en el contenido de la carga útil del evento. +This event runs in the context of the base of the pull request, rather than in the merge commit as the `pull_request` event does. This prevents executing unsafe workflow code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows you to do things like create workflows that label and comment on pull requests based on the contents of the event payload. {% warning %} -**Advertencia:** Se otorga un token de repositorio con permisos de lectura/escritura al evento `pull_request_target` y éste puede acceder a los secretos, aún cuando se activa desde una bifurcación. Aunque las ejecuciones de flujo de trabajo se ejecutan en el contexto de la base de la solicitud de cambios, debes asegurarte de que no revisas, compilas o ejecutas código no confiable desde ella con este evento. Adicionalmente, cualquier caché comparte el mismo alcance que la rama base y, para ayudar a prevenir que se vicie el caché, no deberías guardarlo si existe una posibilidad de que su contenido se haya alterado. Para obtener más información, consulta la sección "[Mantener seguros tus GitHub Actions y flujos de trabajo: Prevenir solicitudes de pwn](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" en el sitio web de GitHub Security Lab. +**Warning:** The `pull_request_target` event is granted a read/write repository token and can access secrets, even when it is triggered from a fork. Although the workflow runs in the context of the base of the pull request, you should make sure that you do not check out, build, or run untrusted code from the pull request with this event. Additionally, any caches share the same scope as the base branch, and to help prevent cache poisoning, you should not save the cache if there is a possibility that the cache contents were altered. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" on the GitHub Security Lab website. {% endwarning %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------- | -| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `converted_to_draft`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
    - `auto_merge_enabled`
    - `auto_merge_disabled`{% endif %} | Última confirmación en la rama base de la solicitud de extracción | Rama base de la solicitud de extracción | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `converted_to_draft`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
    - `auto_merge_enabled`
    - `auto_merge_disabled`{% endif %} | Last commit on the PR base branch | PR base branch | -Predeterminadamente, un flujo de trabajo se ejecuta únicamente cuando el tipo de actividad de un `pull_request_target` se encuentra como `opened`, `synchronize`, o `reopened`. Para activar los flujos de trabajo para más tipos de actividades, usa la palabra clave `tipos`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". +By default, a workflow only runs when a `pull_request_target`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)." -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una solicitud de extracción ha sido `assigned` (asignada), `opened`, `syncronize` o `reopened`. +For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`. ```yaml on: @@ -698,21 +698,21 @@ on: types: [assigned, opened, synchronize, reopened] ``` -### `subir` +### `push` {% note %} -**Nota:** La carga disponible del webhook para las acciones de GitHub no incluye los atributos `added`, `removed` y `modified` en el objeto `commit`. Puedes recuperar el objeto de confirmación completo usando la API REST. Para obtener más información, consulta la sección "[Obtener una confirmación](/rest/reference/repos#get-a-commit)". +**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a commit](/rest/reference/repos#get-a-commit)". {% endnote %} -Ejecuta tu flujo de trabajo cuando alguien sube a una rama de repositorio, lo que activa el evento `push`. +Runs your workflow when someone pushes to a repository branch, which triggers the `push` event. -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------- | ---------------------- | -| [`subir`](/webhooks/event-payloads/#push) | n/a | Confirmación subida, a menos que se elimine una rama (cuando se trata de la rama por defecto) | Referencia actualizada | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`push`](/webhooks/event-payloads/#push) | n/a | Commit pushed, unless deleting a branch (when it's the default branch) | Updated ref | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `push`. +For example, you can run a workflow when the `push` event occurs. ```yaml on: @@ -721,15 +721,15 @@ on: ### `registry_package` -Ejecuta tu flujo de trabajo en cualquier momento en que un paquete `publicado` o `actualizado`. Para obtener más información, consulta "[Administrar paquetes con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)." +Runs your workflow anytime a package is `published` or `updated`. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)." -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------- | --------------------------------------- | ---------------------------------- | ------------------------------------- | -| [`registry_package`](/webhooks/event-payloads/#package) | - `publicado`
    - `actualizado` | Confirmación del paquete publicado | Rama o etiqueta del paquete publicado | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`registry_package`](/webhooks/event-payloads/#package) | - `published`
    - `updated` | Commit of the published package | Branch or tag of the published package | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un paquete ha sido `publicado`. +For example, you can run a workflow when a package has been `published`. ```yaml on: @@ -737,23 +737,23 @@ on: types: [published] ``` -### `lanzamiento` +### `release` {% note %} -**Nota:** El evento `release` no se activará para los lanzamientos en borrador. +**Note:** The `release` event is not triggered for draft releases. {% endnote %} -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `release`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Lanzamientos](/rest/reference/repos#releases)". +Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)." -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------- | -| [`lanzamiento`](/webhooks/event-payloads/#release) | - `published`
    - `unpublished`
    - `created`
    - `edited`
    - `deleted`
    - `prereleased`
    - `released` | Última confirmación en el lanzamiento etiquetado | Etiqueta de lanzamiento | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`release`](/webhooks/event-payloads/#release) | - `published`
    - `unpublished`
    - `created`
    - `edited`
    - `deleted`
    - `prereleased`
    - `released` | Last commit in the tagged release | Tag of release | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un lanzamiento ha sido `publish`. +For example, you can run a workflow when a release has been `published`. ```yaml on: @@ -763,40 +763,40 @@ on: {% note %} -**Nota:** El tipo `prereleased` no se activará para los pre-lanzamientos publicados desde los borradores de lanzamientos, pero el tipo `published` sí lo hará. Si quieres que se ejecute un flujo de trabajo cuando se publiquen los lanzamientos estables *y* los pre-lanzamientos, mejor suscríbete a `published` en vez de a `released` y `prereleased`. +**Note:** The `prereleased` type will not trigger for pre-releases published from draft releases, but the `published` type will trigger. If you want a workflow to run when stable *and* pre-releases publish, subscribe to `published` instead of `released` and `prereleased`. {% endnote %} -### `estado` +### `status` -Ejecuta tu flujo de trabajo en cualquier momento en que cambia el estado de una confirmación de Git, lo que activa el evento `status`. Para obtener más información acerca de la API de REST, consulta la sección "[Estados](/rest/reference/repos#statuses)". +Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/rest/reference/repos#statuses). {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | --------------------------------------------- | ------------ | -| [`estado`](/webhooks/event-payloads/#status) | n/a | Última confirmación en la rama predeterminada | n/a | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`status`](/webhooks/event-payloads/#status) | n/a | Last commit on default branch | n/a | -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `status`. +For example, you can run a workflow when the `status` event occurs. ```yaml on: status ``` -### `observar` +### `watch` -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `watch`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Marcar con una estrella](/rest/reference/activity#starring)". +Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)." {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [`observar`](/webhooks/event-payloads/#watch) | - `comenzado` | Última confirmación en la rama predeterminada | Rama por defecto | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`watch`](/webhooks/event-payloads/#watch) | - `started` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Por ejemplo, puedes ejecutar un flujo de trabajo cuando alguien coloca una estrella en un repositorio, que es el tipo de actividad `started` que activa el evento Ver. +For example, you can run a workflow when someone stars a repository, which is the `started` activity type that triggers the watch event. ```yaml on: @@ -808,17 +808,25 @@ on: {% data reusables.webhooks.workflow_run_desc %} -{% data reusables.github-actions.branch-requirement %} +{% note %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------- | ------------------------------------- | --------------------------------------------- | ---------------- | -| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`
    - `requested` | Última confirmación en la rama predeterminada | Rama por defecto | +**Notes:** + +* This event will only trigger a workflow run if the workflow file is on the default branch. + +* You can't use `workflow_run` to chain together more than three levels of workflows. For example, if you attempt to trigger five workflows (named `B` to `F`) to run sequentially after an initial workflow `A` has run (that is: `A` → `B` → `C` → `D` → `E` → `F`), workflows `E` and `F` will not be run. + +{% endnote %} + +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------- | -------------- | ------------ | -------------| +| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`
    - `requested` | Last commit on default branch | Default branch | {% data reusables.developer-site.limit_workflow_to_activity_types %} -Si necesitas filtrar las ramas de este evento, puedes utilizar `branches` o `branches-ignore`. +If you need to filter branches from this event, you can use `branches` or `branches-ignore`. -En este ejemplo, se configura un flujo de trabajo para que se ejecute después de que se complete el flujo de trabajo separado de "Run Tests". +In this example, a workflow is configured to run after the separate "Run Tests" workflow completes. ```yaml on: @@ -830,7 +838,7 @@ on: - requested ``` -Para ejecutar un job de un flujo de trabajo condicionalmente con base en el resultado de la ejecución de flujo de trabajo anterior, puedes utilizar los condicionales [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) o [`jobs..steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) con la `conclusion` de la ejecución previa. Por ejemplo: +To run a workflow job conditionally based on the result of the previous workflow run, you can use the [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) or [`jobs..steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) conditional combined with the `conclusion` of the previous run. For example: ```yaml on: @@ -851,8 +859,8 @@ jobs: ... ``` -## Activar nuevos flujos de trabajo mediante un token de acceso personal +## Triggering new workflows using a personal access token -{% data reusables.github-actions.actions-do-not-trigger-workflows %} Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". +{% data reusables.github-actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." -Si deseas activar un flujo de trabajo desde una ejecución de flujo de trabajo, puedes desencadenar el evento mediante un token de acceso personal. Necesitaras crear un token de acceso personal y almacenarlo como un secreto. Para minimizar tus costos de uso de {% data variables.product.prodname_actions %}, asegúrate de no crear ejecuciones de flujo de trabajo recurrentes o involuntarias. Para obtener más información sobre almacenr un token de acceso personal como secreto, consulta la sección "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". +If you would like to trigger a workflow from a workflow run, you can trigger the event using a personal access token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information on storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." diff --git a/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 68149850a2..ef1dd1c4bc 100644 --- a/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -1,7 +1,7 @@ --- -title: Comandos de flujo de trabajo para Acciones de GitHub -shortTitle: Comandos de flujo de trabajo -intro: Puedes usar comandos de flujo de trabajo cuando ejecutas comandos de Shell en un flujo de trabajo o en el código de una acción. +title: Workflow commands for GitHub Actions +shortTitle: Workflow commands +intro: You can use workflow commands when running shell commands in a workflow or in an action's code. redirect_from: - /articles/development-tools-for-github-actions - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions @@ -20,37 +20,37 @@ versions: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de los comandos de flujo +## About workflow commands -Las acciones pueden comunicarse con la máquina del ejecutor para establecer variables de entorno, valores de salida utilizados por otras acciones, agregar mensajes de depuración a los registros de salida y otras tareas. +Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks. -La mayoría de los comandos de los flujos de trabajo utilizan el comando `echo` en un formato específico, mientras que otras se invocan si escribes a un archivo. Para obtener más información, consulta la sección ["Archivos de ambiente".](#environment-files) +Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see ["Environment files".](#environment-files) ``` bash -echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value}" +echo "::workflow-command parameter1={data},parameter2={data}::{command value}" ``` {% note %} -**Nota:** los nombres de comandos y parámetros de flujo de trabajo no distinguen mayúsculas de minúsculas. +**Note:** Workflow command and parameter names are not case-sensitive. {% endnote %} {% warning %} -**Advertencia:** si estás usando el símbolo del sistema, omite los caracteres de comillas dobles (`"`) cuando uses comandos de flujo de trabajo. +**Warning:** If you are using Command Prompt, omit double quote characters (`"`) when using workflow commands. {% endwarning %} -## Utilizar comandos de flujo de trabajo para acceder a las funciones de toolkit +## Using workflow commands to access toolkit functions -El [actions/toolkit](https://github.com/actions/toolkit) incluye varias funciones que se pueden ejecutar como comandos de flujo de trabajo. Utiliza la sintaxis `::` para ejecutar los comandos de flujo de trabajo dentro de tu archivo YAML; estos comandos se envían entonces a través de `stdout`. Por ejemplo, en vez de utilizar código para configurar una salida, como se muestra aquí: +The [actions/toolkit](https://github.com/actions/toolkit) includes a number of functions that can be executed as workflow commands. Use the `::` syntax to run the workflow commands within your YAML file; these commands are then sent to the runner over `stdout`. For example, instead of using code to set an output, as below: ```javascript core.setOutput('SELECTED_COLOR', 'green'); ``` -Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar el mismo valor: +You can use the `set-output` command in your workflow to set the same value: {% raw %} ``` yaml @@ -62,52 +62,52 @@ Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar e ``` {% endraw %} -La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo: +The following table shows which toolkit functions are available within a workflow: -| Funcion del Toolkit | Comando equivalente del flujo de trabajo | -| --------------------- | --------------------------------------------------------------------- | -| `core.addPath` | Accessible using environment file `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} -| `core.notice` | `notice` -{% endif %} -| `core.error` | `error` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | -| `core.getInput` | Accesible utilizando la variable de ambiente `INPUT_{NAME}` | -| `core.getState` | Accesible utilizando la variable de ambiente`STATE_{NAME}` | -| `core.isDebug` | Accesible utilizando la variable de ambiente `RUNNER_DEBUG` | -| `core.saveState` | `save-state` | -| `core.setFailed` | Utilizada como un atajo para `::error` y `exit 1` | -| `core.setOutput` | `set-output` | -| `core.setSecret` | `add-mask` | -| `core.startGroup` | `grupo` | -| `core.warning` | `advertencia` | +| Toolkit function | Equivalent workflow command | +| ----------------- | ------------- | +| `core.addPath` | Accessible using environment file `GITHUB_PATH` | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| `core.notice` | `notice` |{% endif %} +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | +| `core.getInput` | Accessible using environment variable `INPUT_{NAME}` | +| `core.getState` | Accessible using environment variable `STATE_{NAME}` | +| `core.isDebug` | Accessible using environment variable `RUNNER_DEBUG` | +| `core.saveState` | `save-state` | +| `core.setCommandEcho` | `echo` | +| `core.setFailed` | Used as a shortcut for `::error` and `exit 1` | +| `core.setOutput` | `set-output` | +| `core.setSecret` | `add-mask` | +| `core.startGroup` | `group` | +| `core.warning` | `warning` | -## Configurar un parámetro de salida +## Setting an output parameter ``` ::set-output name={name}::{value} ``` -Establece un parámetro de salida de la acción. +Sets an action's output parameter. -Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". +Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." -### Ejemplo +### Example ``` bash echo "::set-output name=action_fruit::strawberry" ``` -## Agregar un mensaje de depuración +## Setting a debug message ``` ::debug::{message} ``` -Imprime un mensaje de depuración para el registro. Debes crear un archivo `ACTIONS_STEP_DEBUG` designado secretamente con el valor `true` para ver los mensajes de depuración establecidos por este comando en el registro. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)." +Prints a debug message to the log. You must create a secret named `ACTIONS_STEP_DEBUG` with the value `true` to see the debug messages set by this command in the log. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)." -### Ejemplo +### Example ``` bash echo "::debug::Set the Octocat variable" @@ -115,17 +115,17 @@ echo "::debug::Set the Octocat variable" {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} -## Configurar un mensaje de aviso +## Setting a notice message ``` ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -Crea un mensaje de aviso e imprime el mensaje en la bitácora. {% data reusables.actions.message-annotation-explanation %} +Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} -### Ejemplo +### Example ``` bash echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" @@ -133,48 +133,48 @@ echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" {% endif %} -## Configurar un mensaje de advertencia +## Setting a warning message ``` ::warning file={name},line={line},endLine={endLine},title={title}::{message} ``` -Crea un mensaje de advertencia e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %} +Creates a warning message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} -### Ejemplo +### Example ``` bash echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` -## Configurar un mensaje de error +## Setting an error message ``` ::error file={name},line={line},endLine={endLine},title={title}::{message} ``` -Crea un mensaje de error e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %} +Creates an error message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} -### Ejemplo +### Example ``` bash echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` -## Agrupar líneas de las bitácoras +## Grouping log lines ``` ::group::{title} ::endgroup:: ``` -Crea un grupo expansible en la bitácora. Para crear un grupo, utiliza el comando `group` y especifica un `title`. Todo lo que imprimas en la bitácora entre los comandos `group` y `endgroup` se anidará dentro de una entrada expansible en la misma. +Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log. -### Ejemplo +### Example ```bash echo "::group::My title" @@ -182,44 +182,44 @@ echo "Inside group" echo "::endgroup::" ``` -![Grupo plegable en la bitácora de una ejecución de flujo de trabajo](/assets/images/actions-log-group.png) +![Foldable group in workflow run log](/assets/images/actions-log-group.png) -## Enmascarar un valor en el registro +## Masking a value in log ``` ::add-mask::{value} ``` -El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara. +Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`. -### Ejemplo de enmascaramiento de una cadena +### Example masking a string -Cuando imprimas `"Mona The Octocat"` en el registro, verás `"***"`. +When you print `"Mona The Octocat"` in the log, you'll see `"***"`. ```bash echo "::add-mask::Mona The Octocat" ``` -### Ejemplo de enmascaramiento de una variable de entorno +### Example masking an environment variable -Cuando imprimes la variable `MY_NAME` o el valor `"Mona The Octocat"` en el registro, verás `"***"` en lugar de `"Mona The Octocat"`. +When you print the variable `MY_NAME` or the value `"Mona The Octocat"` in the log, you'll see `"***"` instead of `"Mona The Octocat"`. ```bash MY_NAME="Mona The Octocat" echo "::add-mask::$MY_NAME" ``` -## Detener e iniciar comandos de flujo de trabajo +## Stopping and starting workflow commands `::stop-commands::{endtoken}` -Detiene el procesamiento de cualquier comando de flujo de trabajo. Este comando especial te permite registrar cualquier cosa sin ejecutar accidentalmente un comando de flujo de trabajo. Por ejemplo, podrías dejar de registrar para producir un script completo que tenga comentarios. +Stops processing any workflow commands. This special command allows you to log anything without accidentally running a workflow command. For example, you could stop logging to output an entire script that has comments. -Para parar el procesamiento de los comandos de flujo de trabajo, pasa un token único a `stop-commands`. Para resumir los comandos de flujo de trabajo de procesamiento, pasa el mismo token que utilizaste para detener los comandos de flujo de trabajo. +To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands. {% warning %} -**Advertencia:** Asegúrate de que el token que estás utilizando se genere aleatoriamente y sea único para cada ejecución. Tal como se demuestra en el siguiente ejemplo, puedes generar un hash único de tu `github.token` para cada ejecución. +**Warning:** Make sure the token you're using is randomly generated and unique for each run. As demonstrated in the example below, you can generate a unique hash of your `github.token` for each run. {% endwarning %} @@ -227,7 +227,7 @@ Para parar el procesamiento de los comandos de flujo de trabajo, pasa un token ::{endtoken}:: ``` -### Ejemplo deteniendo e iniciando los comandos de un flujo de trabajo +### Example stopping and starting workflow commands {% raw %} @@ -247,56 +247,116 @@ jobs: {% endraw %} -## Enviar valores a las acciones pre y post +## Echoing command outputs -Puedes utilizar el comando `save-state` para crear variables de ambiente para compartir con tus acciones `pre:` o `post:` de flujo de trabajo. Por ejemplo, puedes crear un archivo con la acción `pre:`, pasar la ubicación del archivo a la acción `main:`, y después, utilizar la acción `post:` para borrar el archivo. Como alternativa, puedes crear un archivo con la acción `main:`, pasar la ubicación del archivo a la acción `post:`, y también utilizar la acción `post:` para borrar el archivo. +``` +::echo::on +::echo::off +``` -Si tienes varias acciones `pre:` o `post:`, solo podrás acceder al valor que se guardó en la acción donde se utilizó `save-state`. Para obtener más información sobre la acción `post:`, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)". +Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. -El comando `save-state` solo puede ejecutarse dentro de una acción y no está disponible para archivos YAML. El valor guardado se almacena en un valor de ambiente con el prefijo `STATE_`. +Command echoing is disabled by default. However, a workflow command is echoed if there are any errors processing the command. -Este ejemplo utiliza JavaScript para ejecutar el comando `save-state`. La variable de ambiente resultante se nombra `STATE_processID` con el valor de `12345`: +The `add-mask`, `debug`, `warning`, and `error` commands do not support echoing because their outputs are already echoed to the log. + +You can also enable command echoing globally by turning on step debug logging using the `ACTIONS_STEP_DEBUG` secret. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)". In contrast, the `echo` workflow command lets you enable command echoing at a more granular level, rather than enabling it for every workflow in a repository. + +### Example toggling command echoing + +```yaml +jobs: + workflow-command-job: + runs-on: ubuntu-latest + steps: + - name: toggle workflow command echoing + run: | + echo '::set-output name=action_echo::disabled' + echo '::echo::on' + echo '::set-output name=action_echo::enabled' + echo '::echo::off' + echo '::set-output name=action_echo::disabled' +``` + +The step above prints the following lines to the log: + +``` +::set-output name=action_echo::enabled +::echo::off +``` + +Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases. + +## Sending values to the pre and post actions + +You can use the `save-state` command to create environment variables for sharing with your workflow's `pre:` or `post:` actions. For example, you can create a file with the `pre:` action, pass the file location to the `main:` action, and then use the `post:` action to delete the file. Alternatively, you could create a file with the `main:` action, pass the file location to the `post:` action, and also use the `post:` action to delete the file. + +If you have multiple `pre:` or `post:` actions, you can only access the saved value in the action where `save-state` was used. For more information on the `post:` action, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)." + +The `save-state` command can only be run within an action, and is not available to YAML files. The saved value is stored as an environment value with the `STATE_` prefix. + +This example uses JavaScript to run the `save-state` command. The resulting environment variable is named `STATE_processID` with the value of `12345`: ``` javascript console.log('::save-state name=processID::12345') ``` -La variable `STATE_processID` se encontrará entonces exclusivamente disponible para el script de limpieza que se ejecuta bajo la acción `main`. Este ejemplo se ejecuta en `main` y utiliza JavaScript para mostrar el valor asignado a la variable de ambiente `STATE_processID`: +The `STATE_processID` variable is then exclusively available to the cleanup script running under the `main` action. This example runs in `main` and uses JavaScript to display the value assigned to the `STATE_processID` environment variable: ``` javascript console.log("The running PID from the main action is: " + process.env.STATE_processID); ``` -## Archivos de ambiente +## Environment Files -Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos temporales que pueden utilizarse para llevar a cabo ciertas acciones. La ruta a estos archivos se expone a través de variables de ambiente. Necesitarás utilizar codificación UTF-8 cuando escribas en estos archivos para garantizar el procesamiento adecuado de los comandos. Se pueden escribir varios comandos en el mismo archivo, separados por líneas nuevas. +During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines. {% warning %} -**Advertencia:** Powershell no utiliza UTF-8 predeterminadamente. Asegúrate que escribes los archivos utilizando la codificación correcta. Por ejemplo, necesitas configurar la codificación UTF-8 cuando configuras la ruta: +**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. Make sure you write files using the correct encoding. For example, you need to set UTF-8 encoding when you set the path: ```yaml -steps: - - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append +jobs: + legacy-powershell-example: + uses: windows-2019 + steps: + - shell: powershell + run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` +Or switch to PowerShell Core, which defaults to UTF-8: + +```yaml +jobs: + modern-pwsh-example: + uses: windows-2019 + steps: + - shell: pwsh + run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8 +``` + +More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow answer](https://stackoverflow.com/a/40098904/162694): + +> ### Optional reading: The cross-platform perspective: PowerShell _Core_: +> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - **defaults to *BOM-less UTF-8***, in line with Unix-like platforms. + {% endwarning %} -## Configurar una variable de ambiente +## Setting an environment variable ``` bash echo "{name}={value}" >> $GITHUB_ENV ``` -Crea o actualiza una variable de ambiente para cualquier paso que sea el siguiente en ejecutarse en un job. El paso que crea o actualiza la variable de ambiente no tiene acceso al valor nuevo, pero todos los pasos subsecuentes en un job tendrán acceso. Las variables de entorno distinguen mayúsculas de minúsculas y puedes incluir puntuación. +Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation. {% note %} -**Nota:** Las variables de ambiente deben referenciarse explícitamente utilizando el [contexto`env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) en la sintaxis de expresión o mediante el uso del archivo `$GITHUB_ENV` directamente; las variables de ambiente no están disponibles implícitamente en los comandos del shell. +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. {% endnote %} -### Ejemplo +### Example {% raw %} ``` @@ -312,9 +372,9 @@ steps: ``` {% endraw %} -### Secuencias de línea múltiple +### Multiline strings -Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la siguiente sintaxis. +For multiline strings, you may use a delimiter with the following syntax. ``` {name}<<{delimiter} @@ -322,9 +382,9 @@ Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la s {delimiter} ``` -#### Ejemplo +#### Example -En este ejemplo, utilizamos `EOF` como delimitador y configuramos la variable de ambiente `JSON_RESPONSE` para el valor de la respuesta de curl. +In this example, we use `EOF` as a delimiter and set the `JSON_RESPONSE` environment variable to the value of the curl response. ```yaml steps: - name: Set the value @@ -335,17 +395,17 @@ steps: echo 'EOF' >> $GITHUB_ENV ``` -## Agregar una ruta de sistema +## Adding a system path ``` bash echo "{path}" >> $GITHUB_PATH ``` -Antepone un directorio a la variable de sistema `PATH` y la hace disponible automáticamente para todas las acciones subsecuentes en el job actual; la acción que se está ejecutando actualmente no puede acceder a la variable de ruta actualizada. Para ver las rutas definidas actualmente para tu job, puedes utilizar `echo "$PATH"` en un paso o en una acción. +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. -### Ejemplo +### Example -Este ejemplo demuestra cómo agregar el directorio `$HOME/.local/bin` del usuario al `PATH`: +This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`: ``` bash echo "$HOME/.local/bin" >> $GITHUB_PATH diff --git a/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index 74be059822..8cafaf8c6b 100644 --- a/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -1,7 +1,7 @@ --- -title: Sintaxis de flujo de trabajo para acciones de GitHub -shortTitle: Sintaxis de flujos de trabajo -intro: Un flujo de trabajo es un proceso automatizado configurable formado por uno o más trabajos. Debes crear un archivo YAML para definir tu configuración de flujo de trabajo. +title: Workflow syntax for GitHub Actions +shortTitle: Workflow syntax +intro: A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration. redirect_from: - /articles/workflow-syntax-for-github-actions - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions @@ -18,27 +18,27 @@ versions: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de la sintaxis de YAML para flujos de trabajo +## About YAML syntax for workflows -Los archivos de flujo de trabajo usan la sintaxis YAML y deben tener una extensión de archivo `.yml` o `.yaml`. {% data reusables.actions.learn-more-about-yaml %} +Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. {% data reusables.actions.learn-more-about-yaml %} -Debes almacenar los archivos de flujos de trabajo en el directorio `.github/workflows` en tu repositorio. +You must store workflow files in the `.github/workflows` directory of your repository. -## `name (nombre)` +## `name` -El nombre de tu flujo de trabajo. {% data variables.product.prodname_dotcom %} muestra los nombres de tus flujos de trabajo en la página de acciones de tu repositorio. Si omites `nombre`, {% data variables.product.prodname_dotcom %} lo establece en la ruta del archivo de flujo de trabajo en relación con la raíz del repositorio. +The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository. ## `on` -**Requerido**. El nombre del evento de {% data variables.product.prodname_dotcom %} que activa el flujo de trabajo. Puedes proporcionar una única `cadena` de eventos, `matriz` de eventos, `matriz` de `tipos` de eventos o `mapa` de configuración de eventos que programe un flujo de trabajo o restrinja la ejecución de un flujo de trabajo para archivos, etiquetas o cambios de rama específicos. Para obtener una lista de eventos disponibles, consulta "[Eventos que desencadenan flujos de trabajo](/articles/events-that-trigger-workflows)". +**Required**. The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. You can provide a single event `string`, `array` of events, `array` of event `types`, or an event configuration `map` that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see "[Events that trigger workflows](/articles/events-that-trigger-workflows)." {% data reusables.github-actions.actions-on-examples %} ## `on..types` -Selecciona los tipos de actividad que desencadenarán una ejecución de flujo de trabajo. La mayoría de los eventos GitHub son desencadenados por más de un tipo de actividad. Por ejemplo, el evento para el recurso release (lanzamiento) se activa cuando se `publica`, `se cancela la publicación`, `se crea`, `edita`, `elimina` o `lanza previamente` una publicación. La palabra clave `types` (tipos) te permite reducir la actividad que hace que se ejecute el flujo de trabajo. Cuando solo un tipo de actividad activa el evento webhook, la palabra clave `types` (tipos) es innecesaria. +Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is `published`, `unpublished`, `created`, `edited`, `deleted`, or `prereleased`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary. -Puedes usar una matriz de `tipos` de eventos. Para obtener más información acerca de cada evento y sus tipos de actividad, consulta "[Eventos que desencadenan flujos de trabajo](/articles/events-that-trigger-workflows#webhook-events)". +You can use an array of event `types`. For more information about each event and their activity types, see "[Events that trigger workflows](/articles/events-that-trigger-workflows#webhook-events)." ```yaml # Trigger the workflow on release activity @@ -50,13 +50,13 @@ on: ## `on..` -Cuando uses los eventos `push` y `pull_request` debes configurar un flujo de trabajo para ejecutarlo en ramas o etiquetas específicas. Para un evento `pull_request`, solo se evalúan las ramas y las etiquetas en la base. Si defines solo `etiquetas` o solo `ramas`, el flujo de trabajo no se ejecutará para los eventos que afecten a la ref de Git indefinida. +When using the `push` and `pull_request` events, you can configure a workflow to run on specific branches or tags. For a `pull_request` event, only branches and tags on the base are evaluated. If you define only `tags` or only `branches`, the workflow won't run for events affecting the undefined Git ref. -Las palabras clave `branches`, `branches-ignore`, `tags`, y `tags-ignore` aceptan patrones globales que utilizan caracteres como `*`, `**`, `+`, `?`, `!` y otros para empatar con más de una rama o nombre de etiqueta. Si un nombre contiene cualquiera de estos caracteres y quieres tener una coincidencia literal, necesitas *escapar* cada uno de estos caracteres especiales con una `\`. Para obtener más información sobre los patrones globales, consulta "[Hoja de información para filtrar patrones](#filter-pattern-cheat-sheet)". +The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." -### Ejemplo: Incluyendo ramas y etiquetas +### Example: Including branches and tags -Los patrones definidos en `branches` y `tags` se evalúan con el nombre de ref de Git. Por ejemplo, al definir el patrón `mona/octocat` en `branches`, se encontrará la ref de Git `refs/heads/mona/octocat`. El patrón `releases/**` encontrará la ref de Git `refs/heads/releases/10`. +The patterns defined in `branches` and `tags` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**` will match the `refs/heads/releases/10` Git ref. ```yaml on: @@ -75,9 +75,9 @@ on: - v1.* # Push events to v1.0, v1.1, and v1.9 tags ``` -### Ejemplo: Ignorando ramas y etiquetas +### Example: Ignoring branches and tags -Cada vez que un patrón coincida con el patrón `branches-ignore` o `tags-ignore`, no se ejecutará el flujo de trabajo. Los patrones definidos en `branches-ignore` y `tags-ignore` se evalúan con el nombre de ref de Git. Por ejemplo, al definir el patrón `mona/octocat` en `branches`, se encontrará la ref de Git `refs/heads/mona/octocat`. El patrón `releases/**-alpha` en `branches` encontrará la ref de Git `refs/releases/beta/3-alpha`. +Anytime a pattern matches the `branches-ignore` or `tags-ignore` pattern, the workflow will not run. The patterns defined in `branches-ignore` and `tags-ignore` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**-alpha` in `branches` will match the `refs/releases/beta/3-alpha` Git ref. ```yaml on: @@ -93,19 +93,19 @@ on: - v1.* # Do not push events to tags v1.0, v1.1, and v1.9 ``` -### Excluir ramas y etiquetas +### Excluding branches and tags -Puedes usar dos tipos de filtros para evitar que un flujo de trabajo se ejecute en las subidas y las solicitudes de extracción a las etiquetas y las ramas. -- `branches` o `branches-ignore`: no puedes usar ambos filtros `branches` y `branches-ignore` para el mismo evento de un flujo de trabajo. Usa el filtro `branches` cuando debas filtrar ramas de coincidencias positivas y para excluir ramas. Usa el filtro `branches-ignore` cuando solo debas excluir nombres de ramas. -- `tags` o `tags-ignore`: no puedes usar ambos filtros `tags` y `tags-ignore` para el mismo evento de un flujo de trabajo. Usa el filtro `tags` cuando debas filtrar etiquetas de coincidencias positivas y para excluir etiquetas. Usa el filtro `tags-ignore` cuando solo debas excluir nombres de etiquetas. +You can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches. +- `branches` or `branches-ignore` - You cannot use both the `branches` and `branches-ignore` filters for the same event in a workflow. Use the `branches` filter when you need to filter branches for positive matches and exclude branches. Use the `branches-ignore` filter when you only need to exclude branch names. +- `tags` or `tags-ignore` - You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow. Use the `tags` filter when you need to filter tags for positive matches and exclude tags. Use the `tags-ignore` filter when you only need to exclude tag names. -### Ejemplo: utilizando patrones positivos y negativos +### Example: Using positive and negative patterns -Puedes excluir `etiquetas` y `ramas` usando el caracter `!`. El orden en que defines los patrones importa. - - Un patrón negativo de coincidencia (con prefijo `!`) luego de una coincidencia positiva excluirá la ref de Git. - - Un patrón positivo de coincidencia luego de una coincidencia negativa volverá a incluir la ref de Git. +You can exclude `tags` and `branches` using the `!` character. The order that you define patterns matters. + - A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref. + - A matching positive pattern after a negative match will include the Git ref again. -El siguiente flujo de trabajo se ejecutará en las subidas a `releases/10` o `releases/beta/mona`, pero no en `releases/10-alpha` o `releases/beta/3-alpha` porque el patrón negativo `!releases/**-alpha` le sigue al patrón positivo. +The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern. ```yaml on: @@ -117,13 +117,13 @@ on: ## `on..paths` -Cuando uses los eventos `push` y `pull_request`, puedes configurar que se ejecute un flujo de trabajo cuando al menos un archivo no coincida con `paths-ignore` o al menos uno de los archivos modificados coincida con las `rutas` configuradas. Los filtros de ruta no se evalúan para las subidas a etiquetas. +When using the `push` and `pull_request` events, you can configure a workflow to run when at least one file does not match `paths-ignore` or at least one modified file matches the configured `paths`. Path filters are not evaluated for pushes to tags. -Las palabras clave `paths-ignore` y `paths` aceptan los patrones globales que usan los caracteres comodines `*` y `**` para encontrar más de un nombre de ruta. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](#filter-pattern-cheat-sheet)". +The `paths-ignore` and `paths` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." -### Ejemplo: Ignorando rutas +### Example: Ignoring paths -Cuando todos los nombres de ruta coincidan con los patrones en `paths-ignore`, el flujo de trabajo no se ejecutará. {% data variables.product.prodname_dotcom %} evalúa los patrones definidos en `paths-ignore` para compararlos con el nombre de ruta. Un flujo de trabajo con el siguiente filtro de ruta solo se ejecutará en los eventos de `subida` que incluyan al menos un archivo externo al directorio `docs` en la raíz del repositorio. +When all the path names match patterns in `paths-ignore`, the workflow will not run. {% data variables.product.prodname_dotcom %} evaluates patterns defined in `paths-ignore` against the path name. A workflow with the following path filter will only run on `push` events that include at least one file outside the `docs` directory at the root of the repository. ```yaml on: @@ -132,9 +132,9 @@ on: - 'docs/**' ``` -### Ejemplo: Incluyendo rutas +### Example: Including paths -Si al menos una ruta coincide con un patrón del filtro de `rutas`, se ejecuta el flujo de trabajo. Para desencadenar una compilación cada vez que subes un archivo JavaScript, puedes usar un patrón comodín. +If at least one path matches a pattern in the `paths` filter, the workflow runs. To trigger a build anytime you push a JavaScript file, you can use a wildcard pattern. ```yaml on: @@ -143,19 +143,19 @@ on: - '**.js' ``` -### Excluir rutas +### Excluding paths -Puedes excluir rutas usando dos tipos de filtros. No puedes usar ambos filtros para el mismo evento de un flujo de trabajo. -- `paths-ignore`: usa el filtro `paths-ignore` cuando solo debas excluir nombres de ruta. -- `paths`: usa el filtro `paths` cuando debas filtrar rutas de coincidencias positivas y excluir rutas. +You can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow. +- `paths-ignore` - Use the `paths-ignore` filter when you only need to exclude path names. +- `paths` - Use the `paths` filter when you need to filter paths for positive matches and exclude paths. -### Ejemplo: utilizando patrones positivos y negativos +### Example: Using positive and negative patterns -Puedes excluir `rutas` usando el caracter `!`. El orden en que defines los patrones importa: - - Una coincidencia de patrón negativo (con prefijo `!`) luego de una coincidencia positiva excluirá la ruta. - - Un patrón de coincidencia positiva luego de una coincidencia negativa excluirá nuevamente la ruta. +You can exclude `paths` using the `!` character. The order that you define patterns matters: + - A matching negative pattern (prefixed with `!`) after a positive match will exclude the path. + - A matching positive pattern after a negative match will include the path again. -Este ejemplo se ejecuta cada vez que el evento de `subida` incluye un archivo en el directorio `sub-project` o sus subdirectorios, a menos que el archivo esté en el directorio `sub-project/docs`. Por ejemplo, una subida que haya cambiado `sub-project/index.js` o `sub-project/src/index.js` desencadenará una ejecución de flujo de trabajo, pero una subida que cambie solo `sub-project/docs/readme.md` no lo hará. +This example runs anytime the `push` event includes a file in the `sub-project` directory or its subdirectories, unless the file is in the `sub-project/docs` directory. For example, a push that changed `sub-project/index.js` or `sub-project/src/index.js` will trigger a workflow run, but a push changing only `sub-project/docs/readme.md` will not. ```yaml on: @@ -165,39 +165,39 @@ on: - '!sub-project/docs/**' ``` -### Comparaciones de diferencias de Git +### Git diff comparisons {% note %} -**Nota:** Si subes más de 1,000 confirmaciones o si {% data variables.product.prodname_dotcom %} no genera el diff debido a que se excedió el tiempo, el flujo de trabajo siempre se ejecutará. +**Note:** If you push more than 1,000 commits, or if {% data variables.product.prodname_dotcom %} does not generate the diff due to a timeout, the workflow will always run. {% endnote %} -El filtro determina si un flujo de trabajo se debe ejecutar al evaluar los archivos modificados y al ejecutarlos comparándolos con la lista de `paths-ignore` o `paths`. Si no hay archivos modificados, no se ejecutará el flujo de trabajo. +The filter determines if a workflow should run by evaluating the changed files and running them against the `paths-ignore` or `paths` list. If there are no files changed, the workflow will not run. -{% data variables.product.prodname_dotcom %} genera la lista de archivos modificados usando diferencias de dos puntos para las subidas y de tres puntos para las solicitudes de extracción: -- **Solicitudes de extracción:** las diferencias de tres puntos son una comparación entre la versión más reciente de la rama de tema y la confirmación, cuando la rama de tema se sincronizó por última vez con la rama base. -- **Subidas a ramas existentes:** una diferencia de dos puntos compara las SHA de encabezado y de base directamente entre sí. -- **Subidas a ramas nuevas:** una diferencia de dos puntos comparada con el padre del antepasado de la confirmación más profunda subida. +{% data variables.product.prodname_dotcom %} generates the list of changed files using two-dot diffs for pushes and three-dot diffs for pull requests: +- **Pull requests:** Three-dot diffs are a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch. +- **Pushes to existing branches:** A two-dot diff compares the head and base SHAs directly with each other. +- **Pushes to new branches:** A two-dot diff against the parent of the ancestor of the deepest commit pushed. -Los diffs se limitan a 300 archivos. Si hay archivos que cambiaron y no se empataron en los primeros 300 archivos que devuelve el filtro, el flujo de trabajo no se ejecutará. Puede que necesites crear filtros más específicos para que el flujo de trabajo se ejecute automáticamente. +Diffs are limited to 300 files. If there are files changed that aren't matched in the first 300 files returned by the filter, the workflow will not run. You may need to create more specific filters so that the workflow will run automatically. -Para obtener más información, consulta "[Acerca de comparar ramas en las solicitudes de extracción](/articles/about-comparing-branches-in-pull-requests)". +For more information, see "[About comparing branches in pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)." {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## `on.workflow_call.inputs` -Cuando se utiliza la palabra clave `workflow_call`, puedes especificar opcionalmente entradas que se pasan al flujo de trabajo al que ese llamó desde aquél del llamante. Las entradas para los flujos de trabajo reutilizables se especifican con el mismo formato que las entradas de las acciones. Para obtener más información sobre las entradas, consulta la sección "[Sintaxis de metadatos para GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". Para obtener más información sobre la palabra clave de `workflow_call`, consulta la sección "[Eventos que activan los flujos de trabajo](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)". +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." -Adicionalmente a los parámetros de entrada estándar que están disponibles, `on.workflow_call.inputs` requiere un parámetro de `type`. Para obtener más información, consulta [`on.workflow_call..type`](#onworkflow_callinput_idtype). +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call.inputs..type`](#onworkflow_callinputsinput_idtype). -Si un parámetro `default` no se configura, el valor predeterminado de la entrada es `false` en el caso de un booleano, `0` en el caso de un número y `""` para una llamada. +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. -Dentro del flujo de trabajo llamado, puedes utilizar el contexto `inputs` para referirte a una entrada. +Within the called workflow, you can use the `inputs` context to refer to an input. -Si un flujo de trabajo llamante pasa una entrada que no se especifica en el flujo llamado, dará un error como resultado. +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. -### Ejemplo +### Example {% raw %} ```yaml @@ -209,7 +209,7 @@ on: default: 'john-doe' required: false type: string - + jobs: print-username: runs-on: ubuntu-latest @@ -220,21 +220,21 @@ jobs: ``` {% endraw %} -Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." -## `on.workflow_call..type` +## `on.workflow_call.inputs..type` -Requerido si se define una entrada para la palabra clave `on.workflow_call`. El valor de este parámetro es una secuencia que especifica el tipo de datos de la entrada. Este debe ser alguno de entre: `boolean`, `number` o `string`. +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. ## `on.workflow_call.secrets` -Un mapa de los secretos que puede utilizarse en el flujo de trabajo llamado. +A map of the secrets that can be used in the called workflow. -Dentro del flujo de trabajo llamado, puedes utilizar el contexto `secrets` para referirte a un secreto. +Within the called workflow, you can use the `secrets` context to refer to a secret. -Si un flujo de trabajo llamante pasa un secreto que no se especifica en el flujo de trabajo llamado, esto da un error como resultado. +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. -### Ejemplo +### Example {% raw %} ```yaml @@ -244,7 +244,7 @@ on: access-token: description: 'A token passed from the caller workflow' required: false - + jobs: pass-secret-to-action: runs-on: ubuntu-latest @@ -259,16 +259,16 @@ jobs: ## `on.workflow_call.secrets.` -Un identificador de secuencia para asociar con el secreto. +A string identifier to associate with the secret. ## `on.workflow_call.secrets..required` -Un booleano que especifica si el secreto debe suministrarse. +A boolean specifying whether the secret must be supplied. {% endif %} ## `on.workflow_dispatch.inputs` -Cuando se utiliza el evento `workflow_dispatch`, puedes especificar opcionalmente entradas que se pasan al flujo de trabajo. Las entradas de envío de flujo de trabajo se especifican en el mismo formato que las entradas de acción. Para obtener más información sobre el formato, consulta la sección "[Sintaxis de metadatos para las GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. ```yaml on: @@ -277,33 +277,43 @@ on: logLevel: description: 'Log level' required: true - default: 'warning' + default: 'warning' {% ifversion ghec or ghes > 3.3 or ghae-issue-5511 %} + type: choice + options: + - info + - warning + - debug {% endif %} tags: description: 'Test scenario tags' - required: false + required: false {% ifversion ghec or ghes > 3.3 or ghae-issue-5511 %} + type: boolean + environment: + description: 'Environment to run tests against' + type: environment + required: true {% endif %} ``` -El flujo de trabajo que se activa recibe las entradas en el contexto de `github.event.inputs`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)". +The triggered workflow receives the inputs in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)." ## `on.schedule` {% data reusables.repositories.actions-scheduled-workflow-example %} -Para obtener más información acerca de la sintaxis cron, consulta "[Eventos que activan flujos de trabajo](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." +For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## `permisos` +## `permissions` -Puedes modificar los permisos predeterminados que se otorgaron al `GITHUB_TOKEN` si agregas o eliminas el acceso según se requiera para que solo permitas el acceso mínimo requerido. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." -Puedes utilizar los `permissions` ya sea como una clave de nivel superior, para aplicar todos los jobs en el flujo de trabajo, o dentro de jobs específicos. Cuando agregas la clave `permissions` dentro de un job específico, todas las acciones y comandos de ejecución dentro de este que utilicen el `GITHUB_TOKEN` obtendrán los derechos de acceso que especificas. Para obtener más información, consulta los [`jobspermissions`](#jobsjob_idpermissions). +You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify. For more information, see [`jobs..permissions`](#jobsjob_idpermissions). {% data reusables.github-actions.github-token-available-permissions %} {% data reusables.github-actions.forked-write-permission %} -### Ejemplo +### Example -Este ejemplo muestra los permisos que se están configurando para el `GITHUB_TOKEN` que aplicará a todos los jobs en el flujo de trabajo. Se otorga acceso de lectura a todos los permisos. +This example shows permissions being set for the `GITHUB_TOKEN` that will apply to all jobs in the workflow. All permissions are granted read access. ```yaml name: "My workflow" @@ -319,11 +329,11 @@ jobs: ## `env` -Un `map` de las variables de ambiente que se encuentran disponibles para los pasos de todos los jobs en el flujo de trabajo. También puedes configurar variables de ambiente que solo estén disponibles para los pasos en un solo job o en un solo paso. Para obtener más información, consulta [`jobs..env`](#jobsjob_idenv) y [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -### Ejemplo +### Example ```yaml env: @@ -332,17 +342,17 @@ env: ## `defaults` -Un `map` de configuración predeterminada que se aplicará a todos los jobs en el flujo de trabajo. También puedes configurar los ajustes predeterminados que solo estén disponibles para un job. Para obtener más información, consulta la sección [`jobs..defaults`](#jobsjob_iddefaults). +A `map` of default settings that will apply to all jobs in the workflow. You can also set default settings that are only available to a job. For more information, see [`jobs..defaults`](#jobsjob_iddefaults). {% data reusables.github-actions.defaults-override %} ## `defaults.run` -Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](#jobsjob_idstepsrun) en un flujo de trabajo. También puedes configurar ajustes predeterminados para `run` que solo estén disponibles para un job. Para obtener más información, consulta [`jobs..defaults.run`](#jobsjob_iddefaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave. +You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a workflow. You can also set default settings for `run` that are only available to a job. For more information, see [`jobs..defaults.run`](#jobsjob_iddefaultsrun). You cannot use contexts or expressions in this keyword. {% data reusables.github-actions.defaults-override %} -### Ejemplo +### Example ```yaml defaults: @@ -354,28 +364,28 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} ## `concurrency` -La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión solo puede utilizar el [contexto`github`](/actions/learn-github-actions/contexts#github-context). Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." -También puedes especificar la `concurrency` a nivel del job. Para obtener más información, consulta la [`jobsconcurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). +You can also specify `concurrency` at the job level. For more information, see [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). {% data reusables.actions.actions-group-concurrency %} {% endif %} -## `Trabajos` +## `jobs` -Una ejecución de flujo de trabajo está compuesta por uno o más trabajos. De forma predeterminada, los trabajos se ejecutan en paralelo. Para ejecutar trabajos de manera secuencial, puedes definir dependencias en otros trabajos utilizando la palabra clave `jobs..needs`. +A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs..needs` keyword. -Cada job se ejecuta en un ambiente ejecutor que especifica `runs-on`. +Each job runs in a runner environment specified by `runs-on`. -Puedes ejecutar una cantidad ilimitada de trabajos siempre que estés dentro de los límites de uso del flujo de trabajo. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados. +You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. Para obtener más información, consulta la sección "[Jobs de los Flujos de Trabajo](/rest/reference/actions#workflow-jobs)". +If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." ## `jobs.` -Create an identifier for your job by giving it a unique name. La clave `job_id` es una cadena y su valor es un mapa de los datos de configuración del trabajo. Debes reemplazar `` con una cadena que sea exclusiva del objeto `jobs`. El `` debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. +Create an identifier for your job by giving it a unique name. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `` with a string that is unique to the `jobs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. -### Ejemplo +### Example In this example, two jobs have been created, and their `job_id` values are `my_first_job` and `my_second_job`. @@ -389,13 +399,13 @@ jobs: ## `jobs..name` -El nombre del trabajo que se muestra en {% data variables.product.prodname_dotcom %}. +The name of the job displayed on {% data variables.product.prodname_dotcom %}. ## `jobs..needs` -Identifica los trabajos que se deben completar con éxito antes de que se ejecute este trabajo. Puede ser una cadena o matriz de cadenas. Si un job falla, se saltarán todos los jobs que lo necesiten a menos de que éstos utilicen una expresión condicional que ocasione que el job continúe. +Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. -### Ejeemplo: Requerir que los jobs dependientes tengan éxito +### Example: Requiring dependent jobs to be successful ```yaml jobs: @@ -406,15 +416,15 @@ jobs: needs: [job1, job2] ``` -En este ejemplo, `job1` debe completarse con éxito antes de que `job2` comience, y `job3` espera a que `job1` y `job2` se completen. +In this example, `job1` must complete successfully before `job2` begins, and `job3` waits for both `job1` and `job2` to complete. -En este ejemplo, los trabajos se ejecutan de manera secuencial: +The jobs in this example run sequentially: 1. `job1` 2. `job2` 3. `job3` -### Ejemplo: No requerir que los jobs dependientes tengan éxito +### Example: Not requiring dependent jobs to be successful ```yaml jobs: @@ -426,72 +436,72 @@ jobs: needs: [job1, job2] ``` -En este ejemplo, `job3` utiliza la expresión condicional `always()` para que siempre se ejecute después de que el `job1` y el `job2` se hayan completado, sin importar si tuvieron éxito o no. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions#job-status-check-functions)". +In this example, `job3` uses the `always()` conditional expression so that it always runs after `job1` and `job2` have completed, regardless of whether they were successful. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." ## `jobs..runs-on` -**Requerido**. El tipo de máquina en la cual se ejecutará el job. La máquina puede ser un ejecutor alojado {% data variables.product.prodname_dotcom %} o un ejecutor autoalojado. +**Required**. The type of machine to run the job on. The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner. {% ifversion ghae %} ### {% data variables.actions.hosted_runner %}s -Si utilizas un {% data variables.actions.hosted_runner %}, cada job se ejecutará en una instancia nueva de un ambiente virtual que especifique `runs-on`. +If you use an {% data variables.actions.hosted_runner %}, each job runs in a fresh instance of a virtual environment specified by `runs-on`. -#### Ejemplo +#### Example ```yaml runs-on: [AE-runner-for-CI] ``` -Para obtener más información, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)". +For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." {% else %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Ejecutores alojados {% data variables.product.prodname_dotcom %} +### {% data variables.product.prodname_dotcom %}-hosted runners -Si usas un ejecutor alojado {% data variables.product.prodname_dotcom %}, cada trabajo se ejecuta en una nueva instancia de un entorno virtual especificado por `runs-on`. +If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a virtual environment specified by `runs-on`. -Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} disponibles son: +Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.supported-github-runners %} -#### Ejemplo +#### Example ```yaml runs-on: ubuntu-latest ``` -Para obtener más información, consulta "[Entornos virtuales para ejecutores alojados de {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". +For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." {% endif %} -### Ejecutores autoalojados +### Self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -#### Ejemplo +#### Example ```yaml runs-on: [self-hosted, linux] ``` -Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" y "[Usar ejecutores autoalojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)". +For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} ## `jobs..permissions` -Puedes modificar los permisos predeterminados que se otorgaron al `GITHUB_TOKEN` si agregas o eliminas el acceso según se requiera para que solo permitas el acceso mínimo requerido. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." -Si especificas el permiso dentro de una definición de job, puedes configurar un conjunto diferente de permisos para el `GITHUB_TOKEN` de cada job, en caso de que se requiera. Como alternativa, puedes especificar los permisos para todos los jobs en el flujo de trabajo. Para obtener más información sobre los permisos que se definen a nivel del flujo de trabajo, consulta los [`permissions`](#permissions). +By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](#permissions). {% data reusables.github-actions.github-token-available-permissions %} {% data reusables.github-actions.forked-write-permission %} -### Ejemplo +### Example -Este ejemplo muestra los permisos que se están configurando para el `GITHUB_TOKEN`, los cuales solo aplicarán al job que se llama `stale`. Se otorga permiso de escritura a los alcances `issues` y `pull-requests`. El resto de los alcances no tendrán acceso. +This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access. ```yaml jobs: @@ -510,18 +520,18 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae or ghec %} ## `jobs..environment` -El ambiente que referencia el job. Todas las reglas de protección del ambiente deben pasar antes de que un job que referencie dicho ambiente se envie a un ejecutor. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". +The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." -Puedes proporcionar el ambiente como solo el `name` de éste, o como un objeto de ambiente con el `name` y `url`. La URL mapea hacia `environment_url` en la API de despliegues. Para obtener más información sobre la API de despliegues, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". +You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)." -#### Ejemplo utilizando solo el nombre de un ambiente +#### Example using a single environment name {% raw %} ```yaml environment: staging_environment ``` {% endraw %} -#### Ejemplo utilizando un nombre y URL del ambiente +#### Example using environment name and URL ```yaml environment: @@ -529,9 +539,9 @@ environment: url: https://github.com ``` -La URL puede ser una expresión y puede utilizar cualquier contexto, excepto el de [`secrets`](/actions/learn-github-actions/contexts#contexts). Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." -### Ejemplo +### Example {% raw %} ```yaml environment: @@ -546,26 +556,26 @@ environment: {% note %} -**Nota:** Cuando se especifica la concurrencia a nivel del job, no se garantiza el orden para los jobs o ejecuciones que se ponen en fila a 5 minutos uno del otro. +**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other. {% endnote %} -La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión puede utilizar cualquier contexto, con excepción del contexto `secrets`. Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." -También puedes especificar la `concurrency` a nivel del flujo de trabajo. Para obtener más información, consulta la [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency). +You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency). {% data reusables.actions.actions-group-concurrency %} {% endif %} ## `jobs..outputs` -Un `map` de salidas para un job. Las salidas de un job se encuentran disponibles para todos los jobs descendentes que dependan de este job. Para obtener más información sobre la definición de dependencias, consulta [`jobs..needs`](#jobsjob_idneeds). +A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs..needs`](#jobsjob_idneeds). -Las salidas de un job son secuencias, y las salidas de un job que contienen expresiones se evalúan en el ejecutor al final de cada job. Las salidas que contienen secretos se redactan en el ejecutor y no se envían a {% data variables.product.prodname_actions %}. +Job outputs are strings, and job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. -Para utilizar salidas de jobs en un job dependiente, puedes utilizar el contexto `needs`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#needs-context)". +To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)." -### Ejemplo +### Example {% raw %} ```yaml @@ -591,11 +601,11 @@ jobs: ## `jobs..env` -Un `mapa` de las variables de entorno que están disponibles para todos los pasos de la tarea. También puedes establecer las variables de entorno para todo el flujo de trabajo o para un paso en particular. Para obtener más información, consulta la sección [`env`](#env) y [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -### Ejemplo +### Example ```yaml jobs: @@ -606,19 +616,19 @@ jobs: ## `jobs..defaults` -Un `map` de configuración predeterminada que se aplicará a todos los pasos del job. También puedes configurar ajustes predeterminados para todo el flujo de trabajo. Para obtener más información, consulta [`defaults`](#defaults). +A `map` of default settings that will apply to all steps in the job. You can also set default settings for the entire workflow. For more information, see [`defaults`](#defaults). {% data reusables.github-actions.defaults-override %} ## `jobs..defaults.run` -Proporciona `shell` y `working-directory` predeterminados a todos los pasos de `run` en el job. No se permiten las expresiones ni contexto en esta sección. +Provide default `shell` and `working-directory` to all `run` steps in the job. Context and expression are not allowed in this section. -Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](#jobsjob_idstepsrun) en un job. También puedes configurar ajustes predeterminados para `run` para todo el flujo de trabajo. Para obtener más información, consulta [`jobs.defaults.run`](#defaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave. +You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`jobs.defaults.run`](#defaultsrun). You cannot use contexts or expressions in this keyword. {% data reusables.github-actions.defaults-override %} -### Ejemplo +### Example ```yaml jobs: @@ -632,17 +642,17 @@ jobs: ## `jobs..if` -Puedes usar el condicional `if` para impedir que se ejecute una tarea si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional. +You can use the `if` conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional. -{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." ## `jobs..steps` -Un trabajo contiene una secuencia de tareas llamadas `pasos`. Los pasos pueden ejecutar comandos, tareas de configuración o una acción en tu repositorio, un repositorio público o una acción publicada en un registro de Docker. Not all steps run actions, but all actions run as a step. Cada paso se ejecuta en su propio proceso en el entorno del ejecutor y tiene acceso al espacio de trabajo y al sistema de archivos. Debido a que los pasos se ejecutan en su propio proceso, los cambios en las variables de entorno no se conservan entre los pasos. {% data variables.product.prodname_dotcom %} proporciona pasos integrados para configurar y completar un trabajo. +A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job. -Puedes ejecutar un número de pasos ilimitado siempre que estés dentro de los límites de uso del flujo de trabajo. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados. +You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -### Ejemplo +### Example {% raw %} ```yaml @@ -668,17 +678,17 @@ jobs: ## `jobs..steps[*].id` -Un identificador único para el paso. Puede usar el `id` para hacer referencia al paso en contextos. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)". +A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." ## `jobs..steps[*].if` -Puedes usar el condiciona `if` para impedir que se ejecute un paso si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional. +You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional. -{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". +{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." -### Ejemplo: Utilizando contextos +### Example: Using contexts - Este paso solo se ejecuta cuando el tipo de evento es una `pull_request` y la acción del evento está `unassigned` (sin asignar). + This step only runs when the event type is a `pull_request` and the event action is `unassigned`. ```yaml steps: @@ -687,9 +697,9 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -### Ejemplo: Utilizando funciones de verificación de estado +### Example: Using status check functions -El `paso mi copia de seguridad` solo se ejecuta cuando se produce un error en el paso anterior de un trabajo. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions#job-status-check-functions)". +The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." ```yaml steps: @@ -702,22 +712,22 @@ steps: ## `jobs..steps[*].name` -Un nombre para que tu paso se muestre en {% data variables.product.prodname_dotcom %}. +A name for your step to display on {% data variables.product.prodname_dotcom %}. ## `jobs..steps[*].uses` -Selecciona una acción para ejecutar como parte de un paso en tu trabajo. Una acción es una unidad de código reutilizable. Puedes usar una acción definida en el mismo repositorio que el flujo de trabajo, un repositorio público o en una [imagen del contenedor Docker publicada](https://hub.docker.com/). +Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/). -Te recomendamos encarecidamente que incluyas la versión de la acción que estás utilizando y especifiques un número de etiqueta de Git ref, SHA o Docker. Si no especificas una versión, podrías interrumpir tus flujos de trabajo o provocar un comportamiento inesperado cuando el propietario de la acción publique una actualización. -- El uso del SHA de confirmación de una versión de acción lanzada es lo más seguro para la estabilidad y la seguridad. -- Usar la versión de acción principal específica te permite recibir correcciones críticas y parches de seguridad y al mismo tiempo mantener la compatibilidad. También asegura que tu flujo de trabajo aún debería funcionar. -- Puede ser conveniente utilizar la rama predeterminada de una acciòn, pero si alguien lanza una versiòn principal nueva con un cambio importante, tu flujo de trabajo podrìa fallar. +We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update. +- Using the commit SHA of a released action version is the safest for stability and security. +- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work. +- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break. -Algunas acciones requieren entradas que se deben establecer usando la palabra clave [`with`](#jobsjob_idstepswith) (con). Revisa el archivo README de la acción para determinar las entradas requeridas. +Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required. -Las acciones son archivos JavaScript o contenedores Docker. Si la acción que estás usando es un contenedor Docker, debes ejecutar el trabajo en un entorno Linux. Para obtener más detalles, consulta [`runs-on`](#jobsjob_idruns-on). +Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on). -### Ejemplo: Utilizando acciones versionadas +### Example: Using versioned actions ```yaml steps: @@ -731,11 +741,11 @@ steps: - uses: actions/checkout@main ``` -### Ejemplo: Utilizando una acción pública +### Example: Using a public action `{owner}/{repo}@{ref}` -Puedes especificar una rema, ref, o SHA en un repositorio público de {% data variables.product.prodname_dotcom %}. +You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository. ```yaml jobs: @@ -749,11 +759,11 @@ jobs: uses: actions/aws@v2.0.1 ``` -### Ejemplo: Utilizando una acción pública en un subdirectorio +### Example: Using a public action in a subdirectory `{owner}/{repo}/{path}@{ref}` -Un subdirectorio en un repositorio público de {% data variables.product.prodname_dotcom %} en una rama específica, ref o SHA. +A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA. ```yaml jobs: @@ -763,11 +773,11 @@ jobs: uses: actions/aws/ec2@main ``` -### Ejemplo: Utilizando una acción en el mismo repositorio que el flujo de trabajo +### Example: Using an action in the same repository as the workflow `./path/to/dir` -La ruta al directorio que contiene la acción en el repositorio de tu flujo de trabajo. Debes revisar tu repositorio antes de usar la acción. +The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action. ```yaml jobs: @@ -779,11 +789,11 @@ jobs: uses: ./.github/actions/my-action ``` -### Ejemplo: Utilizando una acción de Docker Hub +### Example: Using a Docker Hub action `docker://{image}:{tag}` -Una imagen de Docker publicada en [Docker Hub](https://hub.docker.com/). +A Docker image published on [Docker Hub](https://hub.docker.com/). ```yaml jobs: @@ -794,11 +804,11 @@ jobs: ``` {% ifversion fpt or ghec %} -#### Ejemplo: Utilizando el {% data variables.product.prodname_container_registry %} del {% data variables.product.prodname_registry %} +#### Example: Using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} `docker://{host}/{image}:{tag}` -Una imagen de Docker en el {% data variables.product.prodname_container_registry %} del {% data variables.product.prodname_registry %}. +A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}. ```yaml jobs: @@ -808,11 +818,11 @@ jobs: uses: docker://ghcr.io/OWNER/IMAGE_NAME ``` {% endif %} -#### Ejemplo: Utilizando una acción del registro público de Docker +#### Example: Using a Docker public registry action `docker://{host}/{image}:{tag}` -Una imagen de Docker en un registro público. Este ejemplo utiliza el Registro del Contenedor de Google en `gcr.io`. +A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`. ```yaml jobs: @@ -822,11 +832,11 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -### Ejemplo: Utilizando una acción dentro de un repositorio privado diferente al del flujo de trabajo +### Example: Using an action inside a different private repository than the workflow -Tu flujo de trabajo debe registrar el repositorio privado y referenciar la acción de forma local. Genera un token de acceso personal y agrega el token como un secreto cifrado. Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)". +Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." -Reemplaza a `PERSONAL_ACCESS_TOKEN` en el ejemplo con el nombre de tu secreto. +Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret. {% raw %} ```yaml @@ -847,20 +857,20 @@ jobs: ## `jobs..steps[*].run` -Ejecuta programas de la línea de comandos usando el shell del sistema operativo. Si no proporcionas un `nombre`, el paso de establecimiento de nombre se completará por defecto con el texto especificado en el comando `run`. +Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command. -Por defecto, los comandos se ejecutan utilizando shells sin inicio de sesión. Puedes elegir un shell diferente y personalizar el shell utilizado para ejecutar los comandos. Para obtener más información, consulta "[Usar un shell específico](#using-a-specific-shell)". +Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell). -Cada palabra clave `run` representa un nuevo proceso y shell en el entorno del ejecutor. Cuando proporcionas comandos de varias líneas, cada línea se ejecuta en el mismo shell. Por ejemplo: +Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example: -* Comando de una sola línea: +* A single-line command: ```yaml - name: Install Dependencies run: npm install ``` -* Comando de varias líneas: +* A multi-line command: ```yaml - name: Clean install dependencies and build @@ -869,7 +879,7 @@ Cada palabra clave `run` representa un nuevo proceso y shell en el entorno del e npm run build ``` -Usando la palabra clave `working-directory`, puedes especificar el directorio de trabajo de dónde ejecutar el comando. +Using the `working-directory` keyword, you can specify the working directory of where to run the command. ```yaml - name: Clean temp directory @@ -877,21 +887,21 @@ Usando la palabra clave `working-directory`, puedes especificar el directorio de working-directory: ./temp ``` -### Uso de un shell específico +## `jobs..steps[*].shell` -Puedes anular los parámetros predeterminados del shell en el sistema operativo del ejecutor utilizando la palabra clave `shell`. Puedes usar palabras clave incorporadas de `shell` keywords, o puedes definir un conjunto personalizado de opciones de shell. El comando de shell que se ejecuta internamente ejecuta un archivo temporal que contiene los comandos que se especifican en la palabra clave `run`. +You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword. -| Plataforma compatible | parámetro `shell` | Descripción | Comando ejecutado interamente | -| --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| Todas | `bash` | El shell predeterminado en plataformas que no son de Windows con una reserva para `sh`. Al especificar un bash shell en Windows, se usa el bash shell incluido con Git para Windows. | `bash --noprofile --norc -eo pipefail {0}` | -| Todas | `pwsh` | Powershell Core. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. | `pwsh -command ". '{0}'"` | -| Todas | `python` | Ejecuta el comando python. | `python {0}` | -| Linux / macOS | `sh` | El comportamiento de reserva para plataformas que no son Windows si no se proporciona un shell y `bash` no se encuentra en la ruta. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} agrega la extensión `.cmd` a tu nombre de script y la sustituye por `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `pwsh` | Este es el shell predeterminado que se usa en Windows. Powershell Core. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. Si tu ejecutor auto-hospedado de Windows no tiene instalado _PowerShell Core_, entonces se utilizará _PowerShell Desktop_ en su lugar. | `pwsh -command ". '{0}'"`. | -| Windows | `powershell` | El PowerShell Desktop. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. | `powershell -command ". '{0}'"`. | +| Supported platform | `shell` parameter | Description | Command run internally | +|--------------------|-------------------|-------------|------------------------| +| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | +| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | +| All | `python` | Executes the python command. | `python {0}` | +| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | -### Ejemplo: Ejecutando un script utilizando bash +### Example: Running a script using bash ```yaml steps: @@ -900,7 +910,7 @@ steps: shell: bash ``` -### Ejemplo: Ejecutando un script utilizando el `cmd` de Windows +### Example: Running a script using Windows `cmd` ```yaml steps: @@ -909,7 +919,7 @@ steps: shell: cmd ``` -### Ejemplo: Ejecutando un script utilizando PowerShell Core +### Example: Running a script using PowerShell Core ```yaml steps: @@ -918,7 +928,7 @@ steps: shell: pwsh ``` -### Ejemplo: Utilizar PowerShell Desktop para ejecutar un script +### Example: Using PowerShell Desktop to run a script ```yaml steps: @@ -927,7 +937,7 @@ steps: shell: powershell ``` -### Ejemplo: Ejecutando un script de python +### Example: Running a python script ```yaml steps: @@ -938,11 +948,11 @@ steps: shell: python ``` -### Shell personalizado +### Custom shell -Puede establecer el valor `shell` en una cadena de plantilla utilizando el comando `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interpreta la primera palabra delimitada por espacios en blanco de la cadena como el comando, e inserta el nombre del archivo para el script temporal en `{0}`. +You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`. -Por ejemplo: +For example: ```yaml steps: @@ -952,38 +962,38 @@ steps: shell: perl {0} ``` -El comando que se utiliza, (en este ejemplo, `perl`) debe instalarse en el ejecutor. +The command used, `perl` in this example, must be installed on the runner. -{% ifversion ghae %}Para obtener instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tiene instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". +{% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} -Para obtener más información sobre el software que se incluye en los ejecutores hospedados en GitHub, consulta la sección "[Especificaciones para los ejecutores hospedados en GitHub](/actions/reference/specifications-for-github-hosted-runners#supported-software)". +For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." {% endif %} -### Códigos de salida y preferencia de acción de error +### Exit codes and error action preference -Para palabras clave shell incorporadas, brindamos los siguientes valores predeterminados accionados por los ejecutadores alojados por {% data variables.product.prodname_dotcom %}. Deberías usar estos lineamientos al ejecutar scripts shell. +For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts. - `bash`/`sh`: - - Comportamiento a prueba de fallos utilizando `set -eo pipefail`: Valor predeterminado para `bash` y `shell` incorporado. También es el valor predeterminado cuando no proporcionas una opción en plataformas que no son de Windows. - - Puedes excluir la función de falla rápida y tomar el control total al proporcionar una cadena de plantilla a las opciones del shell. Por ejemplo, `bash {0}`. - - Los shells tipo sh salen con el código de salida del último comando ejecutado en un script, que también es el comportamiento predeterminado para las acciones. El ejecutor informará el estado del paso como fallido o exitoso según este código de salida. + - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms. + - You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`. + - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code. - `powershell`/`pwsh` - - Comportamiento de falla rápida cuando sea posible. Para el shell incorporado `pwsh` y `powershell`, vamos a anteponer `$ErrorActionPreference = 'stop'` a los contenidos del script. - - Añadimos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a los scripts de powershell para que los estados de acción reflejen el último código de salida del script. - - Los usuarios siempre pueden optar por no usar el shell incorporado y proporcionar una opción de shell personalizada como: `pwsh -File {0}`, o `powershell -Command "& '{0}'"`, según la necesidad. + - Fail-fast behavior when possible. For `pwsh` and `powershell` built-in shell, we will prepend `$ErrorActionPreference = 'stop'` to script contents. + - We append `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` to powershell scripts so action statuses reflect the script's last exit code. + - Users can always opt out by not using the built-in shell, and providing a custom shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need. - `cmd` - - No parece haber una manera de optar por completo por un comportamiento de falla rápida que no sea escribir tu script para verificar cada código de error y responder en consecuencia. Debido a que en realidad no podemos proporcionar ese comportamiento por defecto, debes escribir este comportamiento en tu script. - - `cmd.exe` saldrá con el nivel de error del último programa que ejecutó y devolverá el código de error al ejecutor. Este comportamiento es internamente coherente con el comportamiento predeterminado anterior `sh` y `pwsh` y es el valor predeterminado `cmd.exe`, por lo que este comportamiento permanece intacto. + - There doesn't seem to be a way to fully opt into fail-fast behavior other than writing your script to check each error code and respond accordingly. Because we can't actually provide that behavior by default, you need to write this behavior into your script. + - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. This behavior is internally consistent with the previous `sh` and `pwsh` default behavior and is the `cmd.exe` default, so this behavior remains intact. ## `jobs..steps[*].with` -Un `mapa` de los parámetros de entrada definidos por la acción. Cada parámetro de entrada es un par clave/valor. Los parámetros de entrada se establecen como variables del entorno. La variable tiene el prefijo `INPUT_` y se convierte en mayúsculas. +A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case. -### Ejemplo +### Example -Define los tres parámetros de entrada (`first_name`, `middle_name`, and `last_name`) definidos por la acción `hello_world`. Es posible acceder a estas variables de entrada con la acción `hello-world` como `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` y las variables de entorno `INPUT_LAST_NAME`. +Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables. ```yaml jobs: @@ -999,9 +1009,9 @@ jobs: ## `jobs..steps[*].with.args` -Una `cadena` que define las entradas para un contenedor Docker. {% data variables.product.prodname_dotcom %} comunica los `args` en el `ENTRYPOINT` del contenedor cuando se inicia el contenedor. Una `matriz de cadenas` no es compatible para este parámetro. +A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter. -### Ejemplo +### Example {% raw %} ```yaml @@ -1014,17 +1024,17 @@ steps: ``` {% endraw %} -Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia: +The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference: -1. Los documentos requerían argumentos en el README de las acciones y las omiten desde la instrucción `CMD`. -1. Usa los valores predeterminados que permiten usar la acción sin especificar ningún `args`. -1. Si la acción expone un indicador `--help` o algo similar, usa ese como el valor predeterminado para que la acción se documente automáticamente. +1. Document required arguments in the action's README and omit them from the `CMD` instruction. +1. Use defaults that allow using the action without specifying any `args`. +1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting. ## `jobs..steps[*].with.entrypoint` -Anula el Docker `ENTRYPOINT` en el `Dockerfile` o lo establece si es que no tiene uno especificado. A diferencia de la instrucción Docker `ENTRYPOINT` que tiene un shell y formulario de ejecución, la palabra clave `entrypoint` acepta solo una cadena que define el ejecutable que se ejecutará. +Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run. -### Ejemplo +### Example ```yaml steps: @@ -1034,17 +1044,17 @@ steps: entrypoint: /a/different/executable ``` -Se pretende que la palabra clave `entrypoint` se utilice con acciones de contenedor de Docker, pero también puedes utilizarla con acciones de JavaScript que no definan ninguna entrada. +The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. ## `jobs..steps[*].env` -Establece variables de entorno para los pasos a utilizar en el entorno del ejecutor. También puedes establecer las variables de entorno para todo el flujo de trabajo o para una tarea. Para obtener más información, consulta [`env`](#env) y [`jobs..env`](#jobsjob_idenv). +Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs..env`](#jobsjob_idenv). {% data reusables.repositories.actions-env-var-note %} -Es posible que las acciones públicas especifiquen las variables de entorno esperadas en el archivo README. Si estás estableciendo un secreto en una variable de entorno, debes establecer secretos usando el contexto `secretos`. Para obtener más información, consulta las secciones "[Utilizar variables de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" y "[Contextos](/actions/learn-github-actions/contexts)". +Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)." -### Ejemplo +### Example {% raw %} ```yaml @@ -1059,37 +1069,37 @@ steps: ## `jobs..steps[*].continue-on-error` -Impide que un trabajo falle cuando falla un paso. Se lo debe establecer en `true` para permitir que un trabajo pase cuando falla este paso. +Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails. ## `jobs..steps[*].timeout-minutes` -El número máximo de minutos para ejecutar el paso antes de terminar el proceso. +The maximum number of minutes to run the step before killing the process. ## `jobs..timeout-minutes` -La cantidad máxima de minutos para permitir que un trabajo se ejecute antes que {% data variables.product.prodname_dotcom %} lo cancele automáticamente. Predeterminado: 360 +The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 -Si el tiempo de espera excede el límite de tiempo de ejecución del job para el ejecutor, dicho job se cancelará cuando se llegue al límite de tiempo de ejecución. Para obtener más información sobre los límites de tiempo de ejecución de los jobs, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#usage-limits)". +If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#usage-limits)." ## `jobs..strategy` -Una estrategia crea una matriz de construcción para tus trabajos. Puedes definir variaciones diferentes para que ejecuten cada job. +A strategy creates a build matrix for your jobs. You can define different variations to run each job in. ## `jobs..strategy.matrix` -Puedes definir una matriz de diferentes configuraciones de trabajo. Una matriz te permite crear múltiples trabajos realizando la sustitución de variables en una definición de trabajo único. Por ejemplo, puedes usar una matriz para crear trabajos para más de una versión compatible de un lenguaje de programación, sistema operativo o herramienta. Una matriz reutiliza la configuración del trabajo y crea un trabajo para cada matriz que configuras. +You can define a matrix of different job configurations. A matrix allows you to create multiple jobs by performing variable substitution in a single job definition. For example, you can use a matrix to create jobs for more than one supported version of a programming language, operating system, or tool. A matrix reuses the job's configuration and creates a job for each matrix you configure. {% data reusables.github-actions.usage-matrix-limits %} -Cada opción que definas en la `matriz` tiene una clave y un valor. Las claves que defines se convierten en propiedades en el contexto `matriz` y puedes hacer referencia a la propiedad en otras áreas de tu archivo de flujo de trabajo. Por ejemplo, si defines la clave `os` que contiene una matriz de sistemas operativos, puedes usar la propiedad `matrix.os` como el valor de la palabra clave `runs-on` para crear un trabajo para cada sistema operativo. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)". +Each option you define in the `matrix` has a key and value. The keys you define become properties in the `matrix` context and you can reference the property in other areas of your workflow file. For example, if you define the key `os` that contains an array of operating systems, you can use the `matrix.os` property as the value of the `runs-on` keyword to create a job for each operating system. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." -El orden en que defines una `matriz` importa. La primera opción que definas será el primer trabajo que se ejecuta en tu flujo de trabajo. +The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. -### Ejemplo: Ejecutando versiones múltiples de Node.js +### Example: Running multiple versions of Node.js -Puedes especificar una matriz proporcionando una variedad de opciones de configuración. Por ejemplo, si el ejecutor admite las versiones 10, 12 y 14 de Node.js, puedes especificar una matriz de esas versiones en la `matriz`. +You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 10, 12, and 14, you could specify an array of those versions in the `matrix`. -Este ejemplo crea una matriz de tres trabajos estableciendo la clave `node` para una matriz de tres versiones de Node.js. Para usar la matriz, el ejemplo establece la propiedad de contexto `matrix.node` como el valor del parámetro `node-version` de la entrada de la acción `setup-node`. Como resultado, se ejecutarán tres trabajos, cada uno usando una versión diferente de Node.js. +This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version. {% raw %} ```yaml @@ -1105,14 +1115,14 @@ steps: ``` {% endraw %} -La acción `setup-node` es la forma recomendada de configurar una versión de Node.js cuando se usan ejecutores alojados {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la acción [`setup-node`](https://github.com/actions/setup-node). +The `setup-node` action is the recommended way to configure a Node.js version when using {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see the [`setup-node`](https://github.com/actions/setup-node) action. -### Ejemplo: Ejecutando sistemas operativos múltiples +### Example: Running with multiple operating systems -Puedes crear una matriz para ejecutar flujos de trabajo en más de un sistema operativo del ejecutor. También puedes especificar más de una configuración de matriz. Este ejemplo crea una matriz de 6 trabajos: +You can create a matrix to run workflows on more than one runner operating system. You can also specify more than one matrix configuration. This example creates a matrix of 6 jobs: -- 2 sistemas operativos especificados en la matriz `os` -- 3 versiones de Node.js especificadas en la matriz `node` +- 2 operating systems specified in the `os` array +- 3 Node.js versions specified in the `node` array {% data reusables.repositories.actions-matrix-builds-os %} @@ -1130,13 +1140,13 @@ steps: ``` {% endraw %} -{% ifversion ghae %}Para encontrar las opciones de configuración compatibles para los {% data variables.actions.hosted_runner %}, consulta las "[Especificaciones de software](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)". -{% else %}Para encontrar las opciones de la configuración compatible para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". +{% ifversion ghae %}To find supported configuration options for {% data variables.actions.hosted_runner %}s, see "[Software specifications](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)." +{% else %}To find supported configuration options for {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." {% endif %} -### Ejemplo: Incluyendo valores adicionales en combinaciones +### Example: Including additional values into combinations -Puedes agregar más opciones de configuración a un trabajo de una matriz de construcción ya existente. Por ejemplo, si quieres usar una versión específica de `npm` cuando se ejecuta el trabajo que usa `windows-latest` y la versión 8 de `node`, puedes usar `incluir` para especificar esa opción adicional. +You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 8 of `node` runs, you can use `include` to specify that additional option. {% raw %} ```yaml @@ -1154,9 +1164,9 @@ strategy: ``` {% endraw %} -### Ejemplo: Incluyendo combinaciones nuevas +### Example: Including new combinations -Puedes utilizar `include` para agregar jobs nuevos a una matriz de compilaciones. Cualquier configuración de "include" sin coincidencia exacta e agregará a la matriz. Por ejemplo, si quieres utilizar `node` versión 14 para compilar en varios sistemas operativos, pero quieres un job experimental extra que utilice node versión 15 en Ubintu, puedes utilizar `include` para especificar este job adicional. +You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 14 to build on multiple operating systems, but wanted one extra experimental job using node version 15 on Ubuntu, you can use `include` to specify that additional job. {% raw %} ```yaml @@ -1172,9 +1182,9 @@ strategy: ``` {% endraw %} -### Ejemplo: Excluyendo las configuraciones de una matriz +### Example: Excluding configurations from a matrix -Puedes eliminar una configuración específica definida en la matriz de construcción mediante la opción `exclude`. Si usas `exclude`, se elimina un puesto definido por la matriz de construcción. El número de puestos es el producto cruzado de la cantidad de sistemas operativos (`os`) incluidos en las matrices que brindas, menos todas las sustracciones (`exclude`). +You can remove a specific configurations defined in the build matrix using the `exclude` option. Using `exclude` removes a job defined by the build matrix. The number of jobs is the cross product of the number of operating systems (`os`) included in the arrays you provide, minus any subtractions (`exclude`). {% raw %} ```yaml @@ -1192,23 +1202,23 @@ strategy: {% note %} -**Nota:** Todas las combinaciones de `include` se procesan después de `exclude`. Esto te permite utilizar `include` para volver a agregar combinaciones que se excluyeron previamente. +**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded. {% endnote %} -#### Utilizar variables de ambiente en una matriz +#### Using environment variables in a matrix -Puedes agregar variables de ambiente personalizadas para cada combinación de prueba si utilizas la clave `include`. Posteriormente, puedes referirte a las variables de ambiente personalizadas en un paso subsecuente. +You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. {% data reusables.github-actions.matrix-variable-example %} ## `jobs..strategy.fail-fast` -Cuando se establece en `verdadero`, {% data variables.product.prodname_dotcom %} cancela todos los trabajos en curso si falla cualquier trabajo de `matriz`. Predeterminado: `true` +When set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs if any `matrix` job fails. Default: `true` ## `jobs..strategy.max-parallel` -La cantidad máxima de trabajos que se pueden ejecutar de manera simultánea cuando se utiliza una estrategia de trabajo `matrix`. De manera predeterminada, {% data variables.product.prodname_dotcom %} maximizará el número de trabajos ejecutados en paralelo dependiendo de los ejecutadores disponibles en las máquinas virtuales alojadas en {% data variables.product.prodname_dotcom %}. +The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. By default, {% data variables.product.prodname_dotcom %} will maximize the number of jobs run in parallel depending on the available runners on {% data variables.product.prodname_dotcom %}-hosted virtual machines. ```yaml strategy: @@ -1217,11 +1227,11 @@ strategy: ## `jobs..continue-on-error` -Previene que una ejecución de flujo de trabajo falle cuando un job falle. Configúralo como `true` para permitir que la ejecución del flujo de trabajo pase cuando este job falle. +Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails. -### Ejemplo: Previniendo un job de matriz específico que falle desde una ejecución de flujo de trabajo que también falle +### Example: Preventing a specific failing matrix job from failing a workflow run -Puedes permitir que ciertos jobs en una matriz de jobs fallen sin que la ejecución de flujo de trabajo falle. Por ejemplo, si querías permitir que fallara únicamente un job experimental con el `node` configurado en `15` sin que fallara la ejecución del flujo de trabajo. +You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run. {% raw %} ```yaml @@ -1242,11 +1252,11 @@ strategy: ## `jobs..container` -Un contenedor para ejecutar todos los pasos de un trabajo que aún no especifica un contenedor. Si tienes pasos que usan tanto acciones de script como de contenedor, las acciones de contenedor se ejecutarán como contenedores hermanos en la misma red con los mismos montajes de volumen. +A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts. -Si no configuras un `container`, todos los pasos se ejecutan directamente en el host especificado por `runs-on` a menos que un paso se refiera a una acción configurada para ejecutarse en un contenedor. +If you do not set a `container`, all steps will run directly on the host specified by `runs-on` unless a step refers to an action configured to run in a container. -### Ejemplo +### Example ```yaml jobs: @@ -1262,7 +1272,7 @@ jobs: options: --cpus 1 ``` -Cuando solo especificas una imagen de contenedor, puedes omitir la palabra clave `image`. +When you only specify a container image, you can omit the `image` keyword. ```yaml jobs: @@ -1272,13 +1282,13 @@ jobs: ## `jobs..container.image` -La imagen de Docker para usar como el contenedor para ejecutar la acción. The value can be the Docker Hub image name or a registry name. +The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a registry name. ## `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -### Ejemplo +### Example {% raw %} ```yaml @@ -1292,23 +1302,23 @@ container: ## `jobs..container.env` -Establece una `mapa` de variables de entorno en el contenedor. +Sets a `map` of environment variables in the container. ## `jobs..container.ports` -Establece una `matriz` de puertos para exponer en el contenedor. +Sets an `array` of ports to expose on the container. ## `jobs..container.volumes` -Establece una `matriz` de volúmenes para que el contenedor los use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host. +Sets an `array` of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. -Para especificar un volumen, especifica la ruta de origen y destino: +To specify a volume, you specify the source and destination path: `:`. -`` es un nombre de volumen o una ruta absoluta en la máquina host, y `` es una ruta absoluta en el contenedor. +The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -### Ejemplo +### Example ```yaml volumes: @@ -1319,11 +1329,11 @@ volumes: ## `jobs..container.options` -Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". +Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." {% warning %} -**Advertencia:** La opción `--network` no es compatible. +**Warning:** The `--network` option is not supported. {% endwarning %} @@ -1331,41 +1341,41 @@ Opciones adicionales de recursos del contenedor Docker. Para obtener una lista d {% data reusables.github-actions.docker-container-os-support %} -Se usa para hospedar contenedores de servicio para un trabajo en un flujo de trabajo. Los contenedores de servicio son útiles para crear bases de datos o servicios de caché como Redis. El ejecutor crea automáticamente una red Docker y administra el ciclo de vida de los contenedores de servicio. +Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers. -Si configuras tu trabajo para que se ejecute en un contenedor, o si tu paso usa acciones del contenedor, no necesitas asignar puertos para acceder al servicio o a la acción. Docker expone automáticamente todos los puertos entre contenedores en la misma red de puente definida por el usuario de Docker. Puedes hacer referencia directamente al contenedor de servicio por su nombre de host. El nombre del host se correlaciona automáticamente con el nombre de la etiqueta que configuraste para el servicio en el flujo de trabajo. +If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow. -Si configuras el trabajo para que se ejecute directamente en la máquina del ejecutor y tu paso no usa una acción de contenedor, debes asignar cualquier puerto del contenedor de servicio Docker que sea necesario para el host Docker (la máquina del ejecutor). Puedes acceder al contenedor de servicio utilizando host local y el puerto asignado. +If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port. -Para obtener más información acerca de las diferencias entre los contenedores de servicios de red, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers)". +For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)." -### Ejemplo: Utilizando al host local +### Example: Using localhost -Este ejemplo crea dos servicios: nginx y Redis. Cuando especificas el puerto del host de Docker pero no el puerto del contenedor, el puerto del contenedor se asigna aleatoriamente a un puerto gratuito. {% data variables.product.prodname_dotcom %} establece el puerto del contenedor asignado en el contexto {% raw %}`$ {{job.services..ports}}`{% endraw %}. En este ejemplo, puedes acceder a los puertos del contenedor de servicio utilizando los contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} y {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}. +This example creates two services: nginx and redis. When you specify the Docker host port but not the container port, the container port is randomly assigned to a free port. {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services..ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts. ```yaml services: nginx: image: nginx - # Asignar puerto 8080 en el host de Docker al puerto 80 en el contenedor nginx + # Map port 8080 on the Docker host to port 80 on the nginx container ports: - 8080:80 redis: image: redis - # Asignar puerto TCP 6379 en el host de Docker a un puerto gratuito aleatorio en el contenedor Redis + # Map TCP port 6379 on Docker host to a random free port on the Redis container ports: - 6379/tcp ``` ## `jobs..services..image` -La imagen de Docker para usar como el contenedor de servicios para ejecutar la acción. The value can be the Docker Hub image name or a registry name. +The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a registry name. ## `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -### Ejemplo +### Example {% raw %} ```yaml @@ -1385,23 +1395,23 @@ services: ## `jobs..services..env` -Establece un `mapa` de variables de entorno en el contenedor de servicio. +Sets a `map` of environment variables in the service container. ## `jobs..services..ports` -Establece una `matriz` de puertos para exponer en el contenedor de servicios. +Sets an `array` of ports to expose on the service container. ## `jobs..services..volumes` -Establece una `matriz` de volúmenes para que el contenedor de servicios los use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host. +Sets an `array` of volumes for the service container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. -Para especificar un volumen, especifica la ruta de origen y destino: +To specify a volume, you specify the source and destination path: `:`. -`` es un nombre de volumen o una ruta absoluta en la máquina host, y `` es una ruta absoluta en el contenedor. +The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -### Ejemplo +### Example ```yaml volumes: @@ -1412,38 +1422,38 @@ volumes: ## `jobs..services..options` -Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". +Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." {% warning %} -**Advertencia:** La opción `--network` no es compatible. +**Warning:** The `--network` option is not supported. {% endwarning %} {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## `jobs..uses` -La ubicación y versión de un archivo de flujo de trabajo reutilizable a ejecutar como un job. +The location and version of a reusable workflow file to run as a job. `{owner}/{repo}/{path}/{filename}@{ref}` -`{ref}` puede ser un SHA, una etiqueta de lanzamiento o un nombre de rama. Utilizar el SHA de la confirmación es lo más seguro para la estabilidad y seguridad. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)." -### Ejemplo +### Example {% data reusables.actions.uses-keyword-example %} -Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." ## `jobs..with` -Cuando se utiliza un job para llamar a un flujo de trabajo reutilizable, puedes usar `with` para proporcionar un mapa de entradas que se pasen al flujo de trabajo llamado. +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. -Cualquier entrada que pases debe coincidir con las especificaciones de la entrada que se define en el flujo de trabajo llamado. +Any inputs that you pass must match the input specifications defined in the called workflow. -A diferencia de [`jobs..steps[*].with`](#jobsjob_idstepswith), las entradas que pases con `jobs..with` no están disponibles como variables de ambiente en el flujo de trabajo llamado. En vez de esto, puedes referenciar las entradas utilizando el contexto `inputs`. +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. -### Ejemplo +### Example ```yaml jobs: @@ -1455,17 +1465,17 @@ jobs: ## `jobs..with.` -Un par que consiste de un identificador de secuencias para la entrada y del valor de entrada. El identificador debe coincidir con el nombre de una entrada que defina [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) en el flujo de trabajo llamado. El tipo de datos del valor debe coincidir con el tipo que definió [`on.workflow_call..type`](#onworkflow_callinput_idtype) en el flujo de trabajo llamado. +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call.inputs..type`](#onworkflow_callinputsinput_idtype) in the called workflow. -Contextos de expresión permitidos: `github`, y `needs`. +Allowed expression contexts: `github`, and `needs`. ## `jobs..secrets` -Cuando se utiliza un job para llamar a un flujo de trabajo reutilizable, puedes utilizar `secrets` para proporcionar un mapa de secretos que se pasa al flujo de trabajo llamado. +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. -Cualquier secreto que pases debe coincidir con los nombres que se definen en el flujo de trabajo llamado. +Any secrets that you pass must match the names defined in the called workflow. -### Ejemplo +### Example {% raw %} ```yaml @@ -1479,23 +1489,23 @@ jobs: ## `jobs..secrets.` -Un par que consiste de un identificador de secuencias para el secreto y el valor de dicho secreto. El identificador debe coincidir con el nombre de una entrada que defina [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) en el flujo de trabajo llamado. +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. -Contextos de expresión permitidos: `github`, `needs` y `secrets`. +Allowed expression contexts: `github`, `needs`, and `secrets`. {% endif %} -## Hoja de referencia de patrones de filtro +## Filter pattern cheat sheet -Puedes usar caracteres especiales en los filtros de ruta, de rama y de etiqueta. +You can use special characters in path, branch, and tag filters. -- `*`: Coincide con cero o más caracteres, pero no coincide con el caracter `/`. Por ejemplo, `Octo*` coincide con `Octocat`. -- `**`: Coincide con cero o más de cualquier caracter. -- `?`: Empata con cero o con uno de los caracteres antesesores. -- `+`: Empata con uno o más de los caracteres precedentes. -- `[]` Coincide con un caracter que aparece en los corchetes o que se incluye en los rangos. Los rangos solo pueden incluir `a-z`, `A-Z` y `0-9`. Por ejemplo, el rango`[0-9a-z]` empata con cualquier dígito o letra en minúscula. Por ejemplo, `[CB]at` coincide con `Cat` o `Bat` y `[1-2]00` coincide con `100` y `200`. -- `!`: Al comienzo de un patrón hace que niegue los patrones positivos previos. No tiene ningún significado especial si no es el primer caracter. +- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`. +- `**`: Matches zero or more of any character. +- `?`: Matches zero or one of the preceding character. +- `+`: Matches one or more of the preceding character. +- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. +- `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. -Los caracteres `*`, `[` y `!` son caracteres especiales en YAML. Si comienzas un patrón con `*`, `[` o `!`, tienes que encerrar el patrón entre comillas. +The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. ```yaml # Valid @@ -1506,39 +1516,39 @@ Los caracteres `*`, `[` y `!` son caracteres especiales en YAML. Si comienzas un - **/README.md ``` -Para obtener más información acerca de la sintaxis de filtro de ramas, de etiquetas y de rutas, consulta "[`on..`](#onpushpull_requestbranchestags)" y "[`on..paths`](#onpushpull_requestpaths)." +For more information about branch, tag, and path filter syntax, see "[`on..`](#onpushpull_requestbranchestags)" and "[`on..paths`](#onpushpull_requestpaths)." -### Patrones para encontrar ramas y etiquetas +### Patterns to match branches and tags -| Patrón | Descripción | Ejemplo de coincidencias | -| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -| `feature/*` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). | `feature/my-branch`

    `feature/your-branch` | -| `feature/**` | El comodín `**` encuentra cualquier caracter, incluida la barra (`/`) en los nombres de ramas y etiquetas. | `feature/beta-a/my-branch`

    `feature/your-branch`

    `feature/mona/the/octocat` | -| `main`

    `releases/mona-the-octocat` | Encuentra el nombre exacto de una rama o el nombre de etiqueta. | `main`

    `releases/mona-the-octocat` | -| `'*'` | Encuentra todos los nombres de rama o de etiqueta que no contienen barra (`/`). El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | `main`

    `releases` | -| `'**'` | Encuentra todos los nombres de rama y de etiqueta. Este es el comportamiento predeterminado cuando no usas un filtro de `ramas` o `etiquetas`. | `all/the/branches`

    `every/tag` | -| `'*feature'` | El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | `mona-feature`

    `feature`

    `ver-10-feature` | -| `v2*` | Encuentra los nombres de rama y de etiqueta que comienzan con `v2`. | `v2`

    `v2.0`

    `v2.9` | -| `v[12].[0-9]+.[0-9]+` | Coincide con todas las etiquetas y ramas de versionamiento semántico con una versión principal 1 o 2 | `v1.10.1`

    `v2.0.0` | +| Pattern | Description | Example matches | +|---------|------------------------|---------| +| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | `feature/my-branch`

    `feature/your-branch` | +| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`

    `feature/your-branch`

    `feature/mona/the/octocat` | +| `main`

    `releases/mona-the-octocat` | Matches the exact name of a branch or tag name. | `main`

    `releases/mona-the-octocat` | +| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `main`

    `releases` | +| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`

    `every/tag` | +| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`

    `feature`

    `ver-10-feature` | +| `v2*` | Matches branch and tag names that start with `v2`. | `v2`

    `v2.0`

    `v2.9` | +| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`

    `v2.0.0` | -### Patrones para encontrar rutas de archivos +### Patterns to match file paths -Los patrones de ruta deben coincidir con toda la ruta y comenzar desde la raíz del repositorio. +Path patterns must match the whole path, and start from the repository's root. -| Patrón | Descripción de coincidencias | Ejemplo de coincidencias | -| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | -| `'*'` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | `README.md`

    `server.rb` | -| `'*.jsx?'` | El caracter `?` encuentra cero o uno de los caracteres de procedimiento. | `page.js`

    `page.jsx` | -| `'**'` | El comodín `*` encuentra cualquier caracter, incluida la barra (`/`). Este es el comportamiento predeterminado cuando no usas un filtro de `rutas`. | `all/the/files.md` | -| `'*.js'` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). Encuentra todos los archivos `.js` en la raíz del repositorio. | `app.js`

    `index.js` | -| `'**.js'` | Encuentra todos los archivos `.js` en el repositorio. | `index.js`

    `js/index.js`

    `src/js/app.js` | -| `docs/*` | Todos los archivos dentro de la raíz del directorio `docs` en la raíz del repositorio. | `docs/README.md`

    `docs/file.txt` | -| `docs/**` | Todos los archivos en el directorio `docs` en la raíz del repositorio. | `docs/README.md`

    `docs/mona/octocat.txt` | -| `docs/**/*.md` | Un archivo con un sufijo `.md` en cualquier parte del directorio `docs`. | `docs/README.md`

    `docs/mona/hello-world.md`

    `docs/a/markdown/file.md` | -| `'**/docs/**'` | Cualquier archivo en un directorio `docs` en cualquier parte del repositorio. | `docs/hello.md`

    `dir/docs/my-file.txt`

    `space/docs/plan/space.doc` | -| `'**/README.md'` | Un archivo README.md en cualquier parte del repositorio. | `README.md`

    `js/README.md` | -| `'**/*src/**'` | Cualquier archivo en una carpeta con un sufijo `src` en cualquier parte del repositorio. | `a/src/app.js`

    `my-src/code/js/app.js` | -| `'**/*-post.md'` | Un archivo con el sufijo `-post.md` en cualquier parte del repositorio. | `my-post.md`

    `path/their-post.md` | -| `'**/migrate-*.sql'` | Un archivo con el prefijo `migrate-` y el sufijo `.sql` en cualquier parte del repositorio. | `migrate-10909.sql`

    `db/migrate-v1.0.sql`

    `db/sept/migrate-v1.sql` | -| `*.md`

    `!README.md` | Usar un signo de exclamación (`!`) frente a un patrón lo niega. Cuando un archivo coincida con un patrón y también coincida con un patrón negativo definido más adelante en el archivo, no se incluirá el archivo. | `hello.md`

    _Does not match_

    `README.md`

    `docs/hello.md` | -| `*.md`

    `!README.md`

    `README*` | Los patrones se marcan de forma secuencial. Un patrón que niega un patrón previo volverá a incluir las rutas del archivo. | `hello.md`

    `README.md`

    `README.doc` | +| Pattern | Description of matches | Example matches | +|---------|------------------------|-----------------| +| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `README.md`

    `server.rb` | +| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`

    `page.jsx` | +| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | `all/the/files.md` | +| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | `app.js`

    `index.js` +| `'**.js'` | Matches all `.js` files in the repository. | `index.js`

    `js/index.js`

    `src/js/app.js` | +| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | `docs/README.md`

    `docs/file.txt` | +| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`

    `docs/mona/octocat.txt` | +| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`

    `docs/mona/hello-world.md`

    `docs/a/markdown/file.md` +| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | `docs/hello.md`

    `dir/docs/my-file.txt`

    `space/docs/plan/space.doc` +| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`

    `js/README.md` +| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`

    `my-src/code/js/app.js` +| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`

    `path/their-post.md` | +| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`

    `db/migrate-v1.0.sql`

    `db/sept/migrate-v1.sql` | +| `*.md`

    `!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`

    _Does not match_

    `README.md`

    `docs/hello.md` | +| `*.md`

    `!README.md`

    `README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`

    `README.md`

    `README.doc`| diff --git a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md index b50bc15926..c04931e0f1 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -1,25 +1,25 @@ --- -title: Ejecutar un flujo de trabajo manualmente -intro: 'Cuando se configura un flujo de trabajo para que se ejecute en el evento `workflow_dispatch`, puedes ejecutarlo utilizando la pestaña de Acciones en {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, o en la API de REST.' +title: Manually running a workflow +intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -shortTitle: Ejecutar un flujo de trabajo manualmente +shortTitle: Manually run a workflow --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Configurar un flujo de trabajo para que se ejecute manualmente +## Configuring a workflow to run manually -Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para ejecutarse en el evento `workflow_dispatch`. Para activar el evento `workflow_dispatch`, tu flujo de trabajo debe estar en la rama predeterminada. Para obtener más información sobre cómo configurar el evento `workflow_dispatch`, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". +To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". {% data reusables.repositories.permissions-statement-write %} -## Ejecutar un flujo de trabajo +## Running a workflow {% include tool-switcher %} @@ -27,9 +27,12 @@ Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. En la barra lateral izquierda, da clic ene l flujo de trabajo que quieras ejecutar. ![flujo de trabajo de la selección en las acciones](/assets/images/actions-select-workflow.png) -1. Sobre la lista de ejecuciones de flujo de trabajo, selecciona **Ejecutar flujo de trabajo**. ![envío del flujo de trabajo de las acciónes](/assets/images/actions-workflow-dispatch.png) -1. Utiliza el menú desplegable de **Rama** para seleccionar la rama del flujo de trabajo y para teclear los parámetros de entrada. Da clic en **Ejecutar flujo de trabajo**. ![flujo de trabajo de la ejecución manual de las acciones](/assets/images/actions-manually-run-workflow.png) +1. In the left sidebar, click the workflow you want to run. +![actions select workflow](/assets/images/actions-select-workflow.png) +1. Above the list of workflow runs, select **Run workflow**. +![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png) +1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**. +![actions manually run workflow](/assets/images/actions-manually-run-workflow.png) {% endwebui %} @@ -37,31 +40,31 @@ Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para {% data reusables.cli.cli-learn-more %} -Para ejecutar un flujo de trabajo, utiliza el subcomando `workflow run`. Reemplaza el parámetro `workflow` ya sea con el nombre, ID, o nombre de archivo del flujo de trabajo que quieres ejecutar. Por ejemplo `"Link Checker"`, `1234567`, o `"link-check-test.yml"`. Si no especificas un flujo de trabajo, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas un flujo de trabajo. +To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow. ```shell gh workflow run workflow ``` -Si tu flujo de trabajo acepta entradas, {% data variables.product.prodname_cli %} te pedirá que las ingreses. Como alternativa, puedes utilizar `-f` o `-F` para agregar una entrada en formato `key=value`. Utiliza `-F` para leer desde un archivo. +If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file. ```shell gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt ``` -También puedes pasar las entradas como JSON utilizando una entrada estándar. +You can also pass inputs as JSON by using standard input. ```shell echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json ``` -Para ejecutar un flujo de trabajo en una rama del repositorio diferente a la predeterminada, utiliza el marcador `--ref`. +To run a workflow on a branch other than the repository's default branch, use the `--ref` flag. ```shell gh workflow run workflow --ref branch-name ``` -Para ver el progreso de la ejecución del flujo de trabajo, utiliza el subcomando `run watch` y selecciona la ejecución de la lista interactiva. +To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list. ```shell gh run watch @@ -69,8 +72,8 @@ gh run watch {% endcli %} -## Ejecutar un flujo de trabajo utilizando la API de REST +## Running a workflow using the REST API -Para obtener más información acerca de cómo utilizar la API de REST, consulta la sección [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Si omites las entradas, se utilizarán los valores predeterminados que se hayan definido en el flujo de trabajo. +When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used. -Puedes activar el evento de `workflow_dispatch` desde la pestaña de Acciones en {{ site.data.variables.product.prodname_dotcom }} o utilizar la API de REST. +For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)." diff --git a/translations/es-ES/content/actions/quickstart.md b/translations/es-ES/content/actions/quickstart.md index 9b3cec4ad7..c0e23bd7ca 100644 --- a/translations/es-ES/content/actions/quickstart.md +++ b/translations/es-ES/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- -title: Guía de inicio rápido para GitHub Actions -intro: 'Prueba las características de las {% data variables.product.prodname_actions %} en 5 minutos o menos.' +title: Quickstart for GitHub Actions +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -12,23 +12,24 @@ versions: type: quick_start topics: - Fundamentals -shortTitle: Inicio Rápido +shortTitle: Quickstart --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -## Introducción +## Introduction -Solo necesitas un repositorio de {% data variables.product.prodname_dotcom %} para crear y ejecutar un flujo de trabajo de {% data variables.product.prodname_actions %}. En esta guía, agregarás un flujo de trabajo que demuestre algunas de las características esenciales de las {% data variables.product.prodname_actions %}. +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. -El siguiente ejemplo te muestra cómo los jobs de las {% data variables.product.prodname_actions %} pueden activarse automáticamente, dónde se ejecutan y cómo pueden interactuar con el código en tu repositorio. +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. -## Crear tu primer flujo de trabajo +## Creating your first workflow -1. Crea un directorio de `.github/workflows` en tu repositorio en {% data variables.product.prodname_dotcom %} si es que dicho directorio aún no existe. -2. En el directorio `.github/workflows`, crea un archivo llamado `github-actions-demo.yml`. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." -3. Copia el siguiente contenido de YAML en el arcvhivo `github-actions-demo.yml`: +1. Create a `.github/workflows` directory in your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist. +2. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +3. Copy the following YAML contents into the `github-actions-demo.yml` file: {% raw %} ```yaml{:copy} name: GitHub Actions Demo @@ -51,40 +52,42 @@ El siguiente ejemplo te muestra cómo los jobs de las {% data variables.product. ``` {% endraw %} -3. Desplázate hasta el final de la página y selecciona **Crear una rama nueva para esta confirmación e iniciar una solicitud de cambios**. Después, para crear una solicitud de cambios, da clic en **Proponer un archivo nuevo**. ![Archivo de flujo de trabajo de la confirmación](/assets/images/help/repository/actions-quickstart-commit-new-file.png) +3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. + ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -El confirmar el flujo de trabajo en una rama de tu repositorio activa el evento `push` y ejecuta tu flujo de trabajo. +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. -## Ver los resultados de tu flujo de trabajo +## Viewing your workflow results {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres ver. +1. In the left sidebar, click the workflow you want to see. - ![Lista de flujos de trabajo en la barra lateral izquierda](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) -1. Desde la lista de ejecuciones de flujo de trabajo, da clic en el nombre de la ejecución que quieres ver. + ![Workflow list in left sidebar](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. From the list of workflow runs, click the name of the run you want to see. - ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/actions-quickstart-run-name.png) -1. Debajo de **Jobs**, haz clic en el job **Explore-GitHub-Actions**. + ![Name of workflow run](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. - ![Ubicar un job](/assets/images/help/repository/actions-quickstart-job.png) -1. La bitácora muestra cómo se procesó cada uno de los pasos. Expande cualquiera de los pasos para ver sus detalles. + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. - ![Resultados del flujo de trabajo de ejemplo](/assets/images/help/repository/actions-quickstart-logs.png) - - Por ejemplo, puedes ver la lista de archivos en tu repositorio: ![Detalle de la acción de ejemplo](/assets/images/help/repository/actions-quickstart-log-detail.png) - -## Más plantillas de flujo de trabajo + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: + ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) + +## More workflow templates {% data reusables.actions.workflow-template-overview %} -## Pasos siguientes +## Next steps -El flujo de trabajo de ejemplo que acabas de agregar se ejecuta cada vez que se sube el código a la rama y te muestra cómo pueden funcionar las {% data variables.product.prodname_actions %} con el contenido de tu repositorio. Pero esto es solo el inicio de lo que puedes hacer con {% data variables.product.prodname_actions %}: +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: -- Tu repositorio puede contener varios flujos de trabajo que activen jobs diferentes basándose en eventos diferentes. -- Puedes utilizar un flujo de trabajo apra instalar las apps de prueba de software y hacer que prueben tu código automáticamente en los ejecutores de {% data variables.product.prodname_dotcom %}. +- Your repository can contain multiple workflows that trigger different jobs based on different events. +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. -{% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu s procesos de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_actions %}: +{% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}: -- "[Aprende más sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" con este tutorial detallado. +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial. diff --git a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md index 1a52318f65..f48f8f759b 100644 --- a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md @@ -1,6 +1,6 @@ --- -title: Autenticación automática de token -intro: '{% data variables.product.prodname_dotcom %} proporciona un token que puedes usar para autenticar en nombre de {% data variables.product.prodname_actions %}.' +title: Automatic token authentication +intro: '{% data variables.product.prodname_dotcom %} provides a token that you can use to authenticate on behalf of {% data variables.product.prodname_actions %}.' redirect_from: - /github/automating-your-workflow-with-github-actions/authenticating-with-the-github_token - /actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token @@ -11,40 +11,40 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Autenticación automática de token +shortTitle: Automatic token authentication --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca del secreto del `GITHUB_TOKEN` +## About the `GITHUB_TOKEN` secret -Al inicio de cada ejecución de flujo de trabajo, {% data variables.product.prodname_dotcom %} crea automáticamente un secreto único de `GITHUB_TOKEN` para utilizar en tu flujo de trabajo. Puedes usar el `GITHUB_TOKEN` para autenticarte en una ejecución de flujo de trabajo. +At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. You can use the `GITHUB_TOKEN` to authenticate in a workflow run. -Cuando habilitas {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} instala una {% data variables.product.prodname_github_app %} en tu repositorio. El secreto del `GITHUB_TOKEN` es un token de acceso de instalación de {% data variables.product.prodname_github_app %}. Puedes usar el token de acceso de instalación para autenticarte en nombre de la {% data variables.product.prodname_github_app %} instalado en tu repositorio. Los permisos del token están limitados al repositorio que contiene tu flujo de trabajo. Para obtener más información, consulta "[Permisos para el `GITHUB_TOKEN`](#permissions-for-the-github_token)." +When you enable {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} installs a {% data variables.product.prodname_github_app %} on your repository. The `GITHUB_TOKEN` secret is a {% data variables.product.prodname_github_app %} installation access token. You can use the installation access token to authenticate on behalf of the {% data variables.product.prodname_github_app %} installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)." -Antes de que comience cada job, {% data variables.product.prodname_dotcom %} extrae un token de acceso de instalación para éste. El token expira cuando el trabajo termina. +Before each job begins, {% data variables.product.prodname_dotcom %} fetches an installation access token for the job. The token expires when the job is finished. -El token también está disponible en el contexto `github.token`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)". +The token is also available in the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)." -## Usar el `GITHUB_TOKEN` en un flujo de trabajo +## Using the `GITHUB_TOKEN` in a workflow -Puedes utilizar el `GITHUB_TOKEN` si utilizas la sintaxis estándar para referenciar secretos: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request. +You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} {% note %} -**Importante:** Las acciones pueden acceder al `GITHUB_TOKEN` mediante el contexto `github.token` aún si el flujo de trabajo no pasa el `GITHUB_TOKEN` específicamente a la acción. Como buena práctica de seguridad. siempre deberías asegurarte de que las acciones solo tengan el acceso mínimo que necesitan para limitar los permisos que se le otorgan al `GITHUB_TOKEN`. Para obtener más información, consulta "[Permisos para el `GITHUB_TOKEN`](#permissions-for-the-github_token)." +**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)." {% endnote %} {% endif %} {% data reusables.github-actions.actions-do-not-trigger-workflows %} -### Ejemplo 1: pasar el `GITHUB_TOKEN` como entrada +### Example 1: passing the `GITHUB_TOKEN` as an input -Este flujo de trabajo de ejemplo usa la [acción de etiquetadora](https://github.com/actions/labeler), que necesita el `GITHUB_TOKEN` como el valor para el parámetro de entrada `repo-token`: +This example workflow uses the [labeler action](https://github.com/actions/labeler), which requires the `GITHUB_TOKEN` as the value for the `repo-token` input parameter: ```yaml name: Pull request labeler @@ -65,9 +65,9 @@ jobs: repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %} ``` -### Ejemplo 2: llamar a la API de REST +### Example 2: calling the REST API -Puedes usar el `GITHUB_TOKEN` para realizar llamadas API autenticadas. Este flujo de trabajo de ejemplo crea una propuesta mediante la API REST del {% data variables.product.prodname_dotcom %}: +You can use the `GITHUB_TOKEN` to make authenticated API calls. This example workflow creates an issue using the {% data variables.product.prodname_dotcom %} REST API: ```yaml name: Create issue on commit @@ -93,67 +93,67 @@ jobs: --fail ``` -## Permisos para el `GITHUB_TOKEN` +## Permissions for the `GITHUB_TOKEN` -Para obtener mpas información sobre las terminales de la API a los que pueden acceder las {% data variables.product.prodname_github_apps %} con cada permiso, consulta la sección "[ Permisos de las {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)". +For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)." {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -La siguiente tabla muestra los permisos que se otorgan al `GITHUB_TOKEN` predeterminadamente. Las personas con permisos administrativos en una {% ifversion not ghes %}empresa, organización o repositorio{% else %}organización o repositorio{% endif %} pueden configurar los permisos predeterminados para que sean permisivos o restringidos. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)." +The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)." -| Ámbito | Acceso predeterminado
    (permisivo) | Acceso predeterminado
    (restringido) | Acceso máximo
    de los repos bifurcados | -| ------------------------- | ------------------------------------------ | -------------------------------------------- | ---------------------------------------------- | -| acciones | lectura/escritura | ninguno | lectura | -| verificaciones | lectura/escritura | ninguno | lectura | -| contenidos | lectura/escritura | lectura | lectura | -| implementaciones | lectura/escritura | ninguno | lectura | -| id_token | lectura/escritura | ninguno | lectura | -| propuestas | lectura/escritura | ninguno | lectura | -| metadatos | lectura | lectura | lectura | -| paquetes | lectura/escritura | ninguno | lectura | -| solicitudes de extracción | lectura/escritura | ninguno | lectura | -| proyectos de repositorio | lectura/escritura | ninguno | lectura | -| eventos de seguridad | lectura/escritura | ninguno | lectura | -| estados | lectura/escritura | ninguno | lectura | +| Scope | Default access
    (permissive) | Default access
    (restricted) | Maximum access
    by forked repos | +|---------------|-----------------------------|-----------------------------|--------------------------------| +| actions | read/write | none | read | +| checks | read/write | none | read | +| contents | read/write | read | read | +| deployments | read/write | none | read | +| id-token | read/write | none | read | +| issues | read/write | none | read | +| metadata | read | read | read | +| packages | read/write | none | read | +| pull requests | read/write | none | read | +| repository projects | read/write | none | read | +| security events | read/write | none | read | +| statuses | read/write | none | read | {% else %} -| Ámbito | Tipo de acceso | Acceso por repositorios bifurcados | -| ------------------------- | ----------------- | ---------------------------------- | -| acciones | lectura/escritura | lectura | -| verificaciones | lectura/escritura | lectura | -| contenidos | lectura/escritura | lectura | -| implementaciones | lectura/escritura | lectura | -| propuestas | lectura/escritura | lectura | -| metadatos | lectura | lectura | -| paquetes | lectura/escritura | lectura | -| solicitudes de extracción | lectura/escritura | lectura | -| proyectos de repositorio | lectura/escritura | lectura | -| estados | lectura/escritura | lectura | +| Scope | Access type | Access by forked repos | +|----------|-------------|--------------------------| +| actions | read/write | read | +| checks | read/write | read | +| contents | read/write | read | +| deployments | read/write | read | +| issues | read/write | read | +| metadata | read | read | +| packages | read/write | read | +| pull requests | read/write | read | +| repository projects | read/write | read | +| statuses | read/write | read | {% endif %} {% data reusables.actions.workflow-runs-dependabot-note %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -### Modificar los permisos del `GITHUB_TOKEN` +### Modifying the permissions for the `GITHUB_TOKEN` -Puedes modificar los permisos del `GITHUB_TOKEN` en archivos de flujo de trabajo individuales. Si los permisos predeterminados del `GITHUB_TOKEN` son restrictivos, podría que necesites elevar los permisos para permitir que las acciones y comandos se ejecuten con éxito. Si los permisos predeterminados son permisivos, puedes editar el archivo de flujo de trabajo para eliminar algunos de ellos del `GITHUB_TOKEN`. Como buena práctica de seguridad, debes otorgar al `GITHUB_TOKEN` el menor acceso requerido. +You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access. -Puedes ver los permisos que tuvo el `GITHUB_TOKEN` para un job específico en la sección "Configurar job" de la bitácora de la ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Utilizar bitácoras de ejecución de flujos de trabajo](/actions/managing-workflow-runs/using-workflow-run-logs)". +You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "Set up job" section of the workflow run log. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." -Puedes utilizar la clave `permissions` en tu archivo de flujo de trabajo para modificar los permisos del `GITHUB_TOKEN` para un flujo de trabajo entero o para jobs individuales. Esto te permite configurar los permisos mínimos requeridos para un flujo de trabajo o job. Cuando se utiliza la clave `permissions`, todos los permisos no especificados se configuran como "sin acceso", con la excepción del alcance `metadata`, el cual siempre obtiene acceso de lectura. +You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access. {% data reusables.github-actions.forked-write-permission %} -Los dos ejemplos de flujo de trabajo que se mostraron anteriormente en este artículo muestran como se utiliza la clave `permissions` a nivel de flujo de trabajo y de job. En el [Ejemplo 1](#example-1-passing-the-github_token-as-an-input) se especifican los dos permisos para todo el flujo de trabajo. En el [Ejemplo 2](#example-2-calling-the-rest-api) se otorga acceso de escritura para un alcance para un solo job. +The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job. -Para conocer todos los detalles de la clave `permissions`, consulta la sección "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)". +For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)." -#### Cómo se calculan los permisos para un job de un flujo de trabajo +#### How the permissions are calculated for a workflow job -Los permisos para el `GITHUB_TOKEN` se configuran inicialmente con los ajustes predeterminados para la empresa, organización o repositorio. Si lo predeterminado se configura para los permisos restringidos en cualquiera de estos niveles, esto aplicará a los repositorios relevantes. Por ejemplo, si eliges las restricciones predeterminadas a nivel organizacional, entonces todos los repositorios de la organización utilizarán estos permisos restringidos como los predeterminados. Entonces, los permisos se ajustarán con base en cualquier configuración dentro del archivo de flujo de trabajo, primero a nivel del flujo de trabajo y luego al nivel de los jobs. Por último, si una solilcitud de cambios activó el flujo de trabajo desde un repositorio bifurcado y no se selecciona el ajuste de **Enviar tokens de escritura a los flujos de trabajo desde las solicitudes de cambios**, los permisos se ajustarán para cambiar cualquier permiso de escritura a solo lectura. +The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only. -### Otorgar permisos adicionales +### Granting additional permissions {% endif %} -Si necesitas un token que requiere permisos que no están disponibles en el `GITHUB_TOKEN`, puedes crear un token de acceso personal y establecerlo como un secreto en tu repositorio: +If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a personal access token and set it as a secret in your repository: -1. Usa o crea un token con los permisos adecuados para ese repositorio. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". -1. Añade el token como un secreto en el repositorio de tu flujo de trabajo y haz referencia a él mediante la sintaxis {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %}. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." +1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +1. Add the token as a secret in your workflow's repository, and refer to it using the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 04493cf49a..b1956d1a34 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Acerca de los ejecutores hospedados en GitHub -intro: '{% data variables.product.prodname_dotcom %} ofrece máquinas virtuales alojadas para ejecutar flujos de trabajo. La máquina virtual contiene un entorno de herramientas, paquetes y configuraciones disponibles para que {% data variables.product.prodname_actions %} los utilice.' +title: About GitHub-hosted runners +intro: '{% data variables.product.prodname_dotcom %} offers hosted virtual machines to run workflows. The virtual machine contains an environment of tools, packages, and settings available for {% data variables.product.prodname_actions %} to use.' redirect_from: - /articles/virtual-environments-for-github-actions - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-actions @@ -13,7 +13,7 @@ versions: fpt: '*' ghes: '*' ghec: '*' -shortTitle: Ejecutores hospedados en GitHub +shortTitle: GitHub-hosted runners --- {% data reusables.actions.ae-hosted-runners-beta %} @@ -21,58 +21,62 @@ shortTitle: Ejecutores hospedados en GitHub {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Acerca de ejecutores alojados en {% data variables.product.prodname_dotcom %} +## About {% data variables.product.prodname_dotcom %}-hosted runners -Un ejecutor alojado en {% data variables.product.prodname_dotcom %} es una máquina virtual alojada por {% data variables.product.prodname_dotcom %} con la aplicación del ejecutor {% data variables.product.prodname_actions %} instalada. {% data variables.product.prodname_dotcom %} ofrece ejecutores con sistemas operativos Linux, Windows y macOS. +A {% data variables.product.prodname_dotcom %}-hosted runner is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner application installed. {% data variables.product.prodname_dotcom %} offers runners with Linux, Windows, and macOS operating systems. -Cuando usas un ejecutor alojado en {% data variables.product.prodname_dotcom %}, se contemplan el mantenimiento de la máquina y las actualizaciones. Puedes ejecutar flujos de trabajo directamente en la máquina virtual o en un contenedor Docker. +When you use a {% data variables.product.prodname_dotcom %}-hosted runner, machine maintenance and upgrades are taken care of for you. You can run workflows directly on the virtual machine or in a Docker container. -Puedes especificar el tipo de ejecutor para cada puesto en un flujo de trabajo. Cada puesto en un flujo de trabajo se ejecuta en una instancia nueva de la máquina virtual. Todos los pasos del trabajo se ejecutan en la misma instancia de la máquina virtual, lo que permite que las acciones de ese trabajo compartan información usando el sistema de archivos. +You can specify the runner type for each job in a workflow. Each job in a workflow executes in a fresh instance of the virtual machine. All steps in the job execute in the same instance of the virtual machine, allowing the actions in that job to share information using the filesystem. + +{% ifversion not ghes %} {% data reusables.github-actions.runner-app-open-source %} -### Hosts en la nube para ejecutores alojados en {% data variables.product.prodname_dotcom %} +### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners -{% data variables.product.prodname_dotcom %} aloja ejecutores de Linux y Windows en máquinas virtuales Standard_DS2_v2 en Microsoft Azure con la aplicación del ejecutor de {% data variables.product.prodname_actions %} instalada. La aplicación del ejecutor alojada en {% data variables.product.prodname_dotcom %} es una bifurcación del agente de Azure Pipelines. Los paquetes ICMP entrantes están bloqueados para todas las máquinas virtuales de Azure, por lo tanto, es posible que los comandos ping o traceroute no funcionen. Para obtener más información acerca de los recursos de la máquina Standard_DS2_v2, consulta "[Dv2 y DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)"en la documentación de Microsoft Azure. +{% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation. -{% data variables.product.prodname_dotcom %} hospeda ejecutores de macOS en la nube de macOS propia de {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. -### Continuidad del flujo de trabajo para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} +### Workflow continuity for {% data variables.product.prodname_dotcom %}-hosted runners {% data reusables.github-actions.runner-workflow-continuity %} -Adicionalmente, si la ejecución de flujo de trabajo se puso en cola con éxito, pero no la ha procesado un ejecutor hospedado en {% data variables.product.prodname_dotcom %} en los 45 minutos subsecuentes, entonces la ejecución de flujo de trabajo en cola se descartará. +In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded. -### Privilegios administrativos de los ejecutores alojados en {% data variables.product.prodname_dotcom %} +### Administrative privileges of {% data variables.product.prodname_dotcom %}-hosted runners -Las máquinas virtuales Linux y macPS se ejecutan sin la contraseña `sudo`. Cuando necesitas ejecutar comandos o instalar herramientas que requieren más privilegios que el usuario actual, puedes usar `sudo` sin la necesidad de brindar una contraseña. Para obtener más información, consulta "[Manual de sudo](https://www.sudo.ws/man/1.8.27/sudo.man.html)." +The Linux and macOS virtual machines both run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the "[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)." -Las máquinas virtuales de Windows están configuradas para ejecutarse como administradores con el control de cuentas de usuario (UAC) inhabilitado. Para obtener más información, consulta "[Cómo funciona el control de cuentas de usuario](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" en la documentación de Windows. +Windows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation. -## Ejecutores y recursos de hardware compatibles +## Supported runners and hardware resources -Especificación de hardware para las máquinas virtuales Windows y Linux: -- CPU de 2 núcleos -- 7 GB de memoria RAM -- 14 GB de espacio en el disco SSD +Hardware specification for Windows and Linux virtual machines: +- 2-core CPU +- 7 GB of RAM memory +- 14 GB of SSD disk space -Especificación de hardware para las máquinas virtuales macOS: -- CPU de 3 núcleos -- 14 GB de memoria RAM -- 14 GB de espacio en el disco SSD +Hardware specification for macOS virtual machines: +- 3-core CPU +- 14 GB of RAM memory +- 14 GB of SSD disk space {% data reusables.github-actions.supported-github-runners %} -Las bitácoras de flujos de trabajo listan los ejecutores que se usan para ejecutar un job. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". +Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -## Software compatible +## Supported software -Las herramientas de software que se incluyen en los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se actualizan semanalmente. El proceso de actualización toma varios días y la lista de software pre-instalado en la rama `main` se actualiza después de que termine todo el despliegue. -### Software preinstalado +The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. The update process takes several days, and the list of preinstalled software on the `main` branch is updated after the whole deployment ends. +### Preinstalled software -Las bitácoras de flujo de trabajo incluyen un enlace a las herramientas preinstaladas en el ejecutor exacto. Para encontrar eta información en la bitácora del flujo de trabajo, expande la sección `Configurar job`. Debajo de esta sección, expande la sección `Ambiente Virtual`. El enlace que sigue de `Software Incluído` describirá las herramientas preinstaladas en el ejecutor que ejecutó el flujo de trabajo. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) Para obtener más información, consulta la sección "[Ver el hstorial de ejecuciones del flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. +![Installed software link](/assets/images/actions-runner-installed-software-link.png) +For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -Para encontrar una lista general de las herramientas que se incluyen en cada sistema operativo de los ejecutores, visita los siguientes enlaces: +For the overall list of included tools for each runner operating system, see the links below: * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md) * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md) @@ -82,51 +86,53 @@ Para encontrar una lista general de las herramientas que se incluyen en cada sis * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -Los ejecutores alojados en {% data variables.product.prodname_dotcom %} incluyen las herramientas integradas predeterminadas del sistema operativo, además de los paquetes enumerados en las referencias anteriores. Por ejemplo, los ejecutores de Ubuntu y macOS incluyen `grep`, `find` y `which`, entre otras herramientas predeterminadas. +{% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. -### Utilizar el software preinstalado +### Using preinstalled software -Te recomendamos utilizar acciones para interactuar con el software instalado en los ejecutores. Este acercamiento tiene varios beneficios: -- Habitualmente, las acciones proporcionan una funcionalidad más flexible, como la selección de versiones, la capacidad de pasar argumentos y los parámetros -- Garantiza que las versiones de herramienta que se utilizan en tu flujo de trabajo permanecerán iguales sin importar las actualizaciones de software +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates -Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments). Este repositorio también contiene anuncios sobre todas las actualizaciones de software principales en los ejecutores. +If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. -### Instalar software adicional +### Installing additional software -Puedes instalar software adicional en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección [Personalizar los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/customizing-github-hosted-runners)". +You can install additional software on {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Customizing GitHub-hosted runners](/actions/using-github-hosted-runners/customizing-github-hosted-runners)". -## Direcciones IP +## IP addresses {% note %} -**Nota:** Si usas una lista de direcciones IP permitidas para tu cuenta de organización o de empresa {% data variables.product.prodname_dotcom %}, no puedes usar ejecutores alojados en {% data variables.product.prodname_dotcom %} y, en su lugar, debes usar ejecutores autoalojados. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)." +**Note:** If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you cannot use {% data variables.product.prodname_dotcom %}-hosted runners and must instead use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% endnote %} -Los ejecutores de Windows y de Ubuntu se hospedan en Azure y, subsecuentemente, tienen los mismos rangos de direcciones IP que los centros de datos de Azure. Los ejecutores de macOS se hospedan en la nube de macOS propia de {% data variables.product.prodname_dotcom %}. +To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API. For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. -Para obtener una lista de los rangos de direcciones IP que utiliza {% data variables.product.prodname_actions %} para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la clave `actions` en la respuesta de la terminal de [Obtener información meta de GitHub](/rest/reference/meta#get-github-meta-information)". Puedes utilizar esta lista de direcciones IP si requieres prevenir acceso no autorizados a tus recursos internos mediante una lista de direcciones IP permitidas. +Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. -La lista de direcciones IP permitidas de {% data variables.product.prodname_actions %} que devuelve la API se actualiza una vez por semana. +Since there are so many IP address ranges for {% data variables.product.prodname_dotcom %}-hosted runners, we do not recommend that you use these as allow-lists for your internal resources. -## Sistemas de archivos +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. -{% data variables.product.prodname_dotcom %} ejecuta acciones y comandos de shell en directorios específicos en la máquina virtual. Las rutas de archivo en las máquinas virtuales no son estáticas. Usa las variables de entorno que proporciona {% data variables.product.prodname_dotcom %} para construir rutas de archivo para los directorios `home`, `workspace` y `workflow`. +## File systems -| Directorio | Variable de entorno | Descripción | -| --------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `home` | `HOME` | Contiene datos relacionados con el usuario. Por ejemplo, este directorio podría contener las credenciales de un intento de inicio de sesión. | -| `workspace` | `GITHUB_WORKSPACE` | Las acciones y los comandos del shell se ejecutan en este directorio. Una acción puede modificar los contenidos de este directorio, al que pueden tener acceso acciones posteriores. | -| `workflow/event.json` | `GITHUB_EVENT_PATH` | La carga `POST` del evento de webhook que activó el flujo de trabajo. {% data variables.product.prodname_dotcom %} reescribe esto cada vez que se ejecuta una acción para aislar el contenido del archivo entre acciones. | +{% data variables.product.prodname_dotcom %} executes actions and shell commands in specific directories on the virtual machine. The file paths on virtual machines are not static. Use the environment variables {% data variables.product.prodname_dotcom %} provides to construct file paths for the `home`, `workspace`, and `workflow` directories. -Para obtener una lista de las variables de entorno que crea {% data variables.product.prodname_dotcom %} para cada flujo de trabajo, consulta "[Usar variables de entorno](/github/automating-your-workflow-with-github-actions/using-environment-variables)". +| Directory | Environment variable | Description | +|-----------|----------------------|-------------| +| `home` | `HOME` | Contains user-related data. For example, this directory could contain credentials from a login attempt. | +| `workspace` | `GITHUB_WORKSPACE` | Actions and shell commands execute in this directory. An action can modify the contents of this directory, which subsequent actions can access. | +| `workflow/event.json` | `GITHUB_EVENT_PATH` | The `POST` payload of the webhook event that triggered the workflow. {% data variables.product.prodname_dotcom %} rewrites this each time an action executes to isolate file content between actions. -### Sistema de archivos del contenedor de Docker +For a list of the environment variables {% data variables.product.prodname_dotcom %} creates for each workflow, see "[Using environment variables](/github/automating-your-workflow-with-github-actions/using-environment-variables)." -Las acciones que se ejecutan en contenedores Docker tienen directorios estáticos en la ruta `/github`. Sin embargo, te recomendamos encarecidamente que uses las variables de entorno predeterminadas para construir rutas de archivos en contenedores de Docker. +### Docker container filesystem -{% data variables.product.prodname_dotcom %} se reserva el prefijo de ruta `/github` y crea tres directorios para las acciones. +Actions that run in Docker containers have static directories under the `/github` path. However, we strongly recommend using the default environment variables to construct file paths in Docker containers. + +{% data variables.product.prodname_dotcom %} reserves the `/github` path prefix and creates three directories for actions. - `/github/home` - `/github/workspace` - {% data reusables.repositories.action-root-user-required %} @@ -134,7 +140,9 @@ Las acciones que se ejecutan en contenedores Docker tienen directorios estático {% ifversion fpt or ghec %} -## Leer más -- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +## Further reading +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" + +{% endif %} {% endif %} diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index 0b82cfac39..d018cd842e 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -1,29 +1,28 @@ --- -title: Personalizar los ejecutores hospedados en GitHub -intro: Puedes instalar software adicional en los ejecutores hospedados en GitHub como parte de tu flujo de trabajo. +title: Customizing GitHub-hosted runners +intro: You can install additional software on GitHub-hosted runners as a part of your workflow. versions: fpt: '*' - ghes: '*' ghec: '*' type: tutorial topics: - Workflows -shortTitle: Personalizar los ejecutores +shortTitle: Customize runners --- {% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -Si requieres paquetes de software adicionales en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes crear un job que instale los paquetes como parte de tu flujo de trabajo. +If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow. -Para ver los paquetes que ya se instalaron predeterminadamente, consulta la sección "[Software preinstalado](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)". +To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)." -Esta guía demuestra cómo crear un job que instala software adicional en un ejecutor hospedado en {% data variables.product.prodname_dotcom %}. +This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner. -## Instalar software en ejecutores Ubuntu +## Installing software on Ubuntu runners -El siguiente ejemplo demuestra cómo instalar un paquete de `apt` como parte de un job. +The following example demonstrates how to install an `apt` package as part of a job. {% raw %} ```yaml @@ -45,13 +44,13 @@ jobs: {% note %} -**Nota:** Ejecuta siempre `sudo apt-get update` antes de instalar un paquete. En caso de que el índice de `apt` esté desactualizado, este comando recupera y re-indiza cualquier paquete disponible, lo cual ayuda a prevenir los fallos en la instalación de paquetes. +**Note:** Always run `sudo apt-get update` before installing a package. In case the `apt` index is stale, this command fetches and re-indexes any available packages, which helps prevent package installation failures. {% endnote %} -## Instalar el software en los ejecutores de macOS +## Installing software on macOS runners -El siguiente ejemplo demuestra cómo instalar paquetes y barriles de Brew como parte de un job. +The following example demonstrates how to install Brew packages and casks as part of a job. {% raw %} ```yaml @@ -75,9 +74,9 @@ jobs: ``` {% endraw %} -## Instalar software en ejecutores Windows +## Installing software on Windows runners -El siguiente ejemplo demuestra cómo utilizar [Chocolatey](https://community.chocolatey.org/packages) para instalar el CLI de {% data variables.product.prodname_dotcom %} como parte de un job. +The following example demonstrates how to use [Chocolatey](https://community.chocolatey.org/packages) to install the {% data variables.product.prodname_dotcom %} CLI as part of a job. {% raw %} ```yaml diff --git a/translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md b/translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md index 4852e6b8c5..86d82736f6 100644 --- a/translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md +++ b/translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md @@ -80,10 +80,12 @@ We recommend you cover these topics in your internal kickoff meeting at your com - What are your business success metrics, how do you plan to measure and report on those measures? - If these have not been defined, please define them. If they have been defined, communicate them and talk about how you plan to provide data-driven progress updates. -- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is expected to work for your company. +- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is +expected to work for your company. - Review of best practices if your company did not participate in the Proof of Concept exercise (or a refresher if your team finds value in this review) - How does this compare/contrast with your existing Application Security Program? -- Discuss and agree how your internal team will work best together throughout rollout and implementation. +- Discuss and agree how your internal team will work best together throughout rollout and +implementation. - Align on your communications plans and frequency of meetings for your internal team - Review tasks for rollout and implementation completion, defining roles and responsibilities. We have outlined the majority of the tasks in this article, but there may be additional tasks your company requires we have not included. - Consider establishing a “Champions Program” for scaled enablement @@ -104,7 +106,8 @@ If you’re working independently, this section outlines some things to ensure a Plans for process changes (if needed) and training for team members as needed: - Documented team assignments for roles and responsibilities. For more information on the permissions required for each feature, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)." - Documented plan of tasks and timelines/timeframes where possible. This should include infrastructure changes, process changes/training, and all subsequent phases of enablement of GHAS, allowing for timeframes for remediations and configuration adjustments as needed. For more information, see "[Phase 1: Pilot projects(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" below. - - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent plans for which projects/teams will come in following phases + - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent +plans for which projects/teams will come in following phases - Success metrics based on business goals. This will be a crucial reference point following the Pilot Project(s) to gain buy-in for the full rollout. {% note %} @@ -117,11 +120,11 @@ Plans for process changes (if needed) and training for team members as needed: For {% data variables.product.prodname_ghe_server %} customers, to help ensure your instance can support the rollout and implementation of GHAS, review the following: -- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." +- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -- En una configuración de alta disponibilidad, un aparato secundario {% data variables.product.prodname_ghe_server %} totalmente redundante se mantiene en sincronización con el aparato principal mediante la replicación de todos los almacenes de datos importantes. For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)." +- In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores. For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)." -- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. Para obtener más información, consulta "[Resumen del sistema](/admin/overview/system-overview)". +- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. For more information, see "[System overview](/admin/overview/system-overview)." {% endif %} @@ -129,10 +132,12 @@ For {% data variables.product.prodname_ghe_server %} customers, to help ensure y As your company prepares to begin your pilot project(s), it’s crucial to ensure that you have set a baseline for where your enterprise is today and have defined clear success metrics to measure your pilot project(s) progress against. -There are likely key business goals your company has that will need to be measured against, but there are other metrics we can identify to help gauge your pilot’s success. +There are likely key business goals your company has that will need to be measured +against, but there are other metrics we can identify to help gauge your pilot’s success. As a starting point, some of these metrics might include: - - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and practices the pilot project(s) / team(s) utilized. + - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and +practices the pilot project(s) / team(s) utilized. - The code scanning integration's findings for the top X most critical applications. - The number of applications that have SAST (Static application security testing) integrated versus before the engagement. @@ -141,14 +146,20 @@ If you participated in the POC exercise prior to purchasing GHAS, these objectiv - Security / CISO (Chief Information Security Officer) - Application Development Teams -If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main evaluation criteria in DSOMM: +If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps +Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main +evaluation criteria in DSOMM: -- **Static depth:** How comprehensive is the static code scan that you’re performing within the AppSec CI pipeline -- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the AppSec CI pipeline +- **Static depth:** How comprehensive is the static code scan that you’re performing within +the AppSec CI pipeline +- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the +AppSec CI pipeline - **Intensity:** Your schedule frequency for the security scans running in AppSec CI pipeline -- **Consolidation:** Your remediation workflow for handling findings and process completeness +- **Consolidation:** Your remediation workflow for handling findings and process +completeness -To learn more about this approach and how to implement it in GHAS, you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)." +To learn more about this approach and how to implement it in GHAS, +you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)." Based on your wider company’s goals and current levels of DevSecOps maturity, we can help you determine how to best measure your pilot’s progress and success. @@ -160,7 +171,9 @@ Based on your wider company’s goals and current levels of DevSecOps maturity, {% endnote %} -To begin enabling GHAS across your company, we recommend beginning with a few high-impact projects or teams to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company. +To begin enabling GHAS across your company, we recommend beginning with a few +high-impact projects or teams to pilot an initial rollout. This will allow an initial +group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company. Before you start your pilot project(s), we recommend that you schedule some checkpoint meetings for your team(s), such as an initial meeting, midpoint review, and a wrap-up session when the pilot is complete. These checkpoint meetings will help you all make adjustments as needed and ensure your team(s) are prepared and supported to complete the pilot successfully. @@ -180,7 +193,7 @@ You need to enable GHAS for each pilot project, either by enabling the GHAS feat The vast majority of GHAS set-up and installation is centered around enabling and configuring code scanning on your enterprise and in your repositories. -Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. Para obtener más información, consulta la sección "[Acerca del escaneo de código"](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning). +Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)." ### Step 2: Set up {% data variables.product.prodname_code_scanning_capc %} @@ -196,23 +209,24 @@ To set up code scanning, you must decide whether you'll run code scanning with [ {% ifversion ghes %} -To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)." +To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your +environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)." {% endif %} -For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners)." +For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners)." For more information about {% data variables.product.prodname_actions %}, see: - "[Learn GitHub Actions](/actions/learn-github-actions)" - "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)" - - "[Eventos que desencadenan flujos de trabajo](/actions/learn-github-actions/events-that-trigger-workflows)" + - "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)" - "[Filter Pattern Cheat Sheet](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)" #### Using a third-party CI system with the CodeQL CLI for {% data variables.product.prodname_code_scanning %} If you’re not using {% data variables.product.prodname_actions %} and have your own continuous integration system, you can use the CodeQL CLI to perform CodeQL code scanning in a third-party CI system. -Para obtener más información, consulta: +For more information, see: - "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)" ### Step 3: Enable {% data variables.product.prodname_code_scanning_capc %} in repositories @@ -221,23 +235,28 @@ If you’re using a phased approach to roll out GHAS, we recommend enabling {% d If you’re not planning on a phased rollout approach and want to enable code scanning for many repositories, you may want to script the process. -For an example of a script that opens pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +For an example of a script that opens pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. ### Step 4: Run code scans and review your results -With code scanning enabled in the necessary repositories, you're ready to help your development team(s) understand how to run code scans and reports, view reports, and process results. +With code scanning enabled in the necessary repositories, you're ready to help your +development team(s) understand how to run code scans and reports, view reports, and process results. #### {% data variables.product.prodname_code_scanning_capc %} -With code scanning, you can find vulnerabilities and errors in your project's code on GitHub, as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts. +With code scanning, you can find vulnerabilities and errors in your project's code on GitHub, +as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts. -When code scanning identifies a problem in a pull request, you can review the highlighted code and resolve the alert. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de extracción](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)". +When code scanning identifies a problem in a pull request, you can review the highlighted +code and resolve the alert. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)." -If you have write permission to a repository you can manage code scanning alerts for that repository. With write permission to a repository, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your repository's code. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)". +If you have write permission to a repository you can manage code scanning alerts for that +repository. With write permission to a repository, you can view, fix, dismiss, or delete alerts for potential +vulnerabilities or errors in your repository's code. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)." #### Generate reports of {% data variables.product.prodname_code_scanning %} alerts -If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. Para obtener más información, consulta la "[API del {% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)". +If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. For more information, see the "[{% data variables.product.prodname_code_scanning_capc %} API](/rest/reference/code-scanning)." For an example of how to use the {% data variables.product.prodname_code_scanning_capc %} API, see the [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample) repository. @@ -245,7 +264,7 @@ For an example of how to use the {% data variables.product.prodname_code_scannin When running initial code scans, you may find that no results are found or that an unusual number of results are returned. You may want to adjust what is flagged in future scans. -Para obtener más información, consulta la sección "[Configurar el escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)". +For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)." If your company wants to use other third-party code analysis tools with GitHub code scanning, you can use actions to run those tools within GitHub. Alternatively, you can upload results, generated by third-party tools as SARIF files, to code scanning. For more information, see "[Integrating with code scanning](/code-security/code-scanning/integrating-with-code-scanning)." @@ -267,19 +286,15 @@ To learn how to view and close alerts for secrets checked into your repository, GitHub helps you avoid using third-party software that contains known vulnerabilities. We provide the following tools for removing and avoiding vulnerable dependencies. -| Dependency Management Tool | Descripción | -| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Dependabot Alerts | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects vulnerable dependencies. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)". | -| Dependency Graph | La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Te muestra los ecosistemas y paquetes de los cuales depende tu base de código (sus dependencias) y los repositorios y paquetes que dependen de tu proyecto (sus dependencias). Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)". |{% ifversion ghes > 3.1 or ghec %} -| Dependency Review | Si una solicitud de cambios contiene cambios a las dependencias, puedes ver un resumen de lo que ha cambiado y si es que existen vulnerabilidades conocidas en cualquiera de estas dependencias. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." |{% endif %} {% ifversion ghec %} -| Dependabot Security Updates | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." | -| Dependabot Version Updates | Dependabot can be used to keep the packages you use updated to the latest versions. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". | {% endif %} +| Dependency Management Tool | Description | +|----|----| +| Dependabot Alerts | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects vulnerable dependencies. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." | +| Dependency Graph | The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." |{% ifversion ghes > 3.1 or ghec %} +| Dependency Review | If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." | {% endif %} {% ifversion ghec or ghes > 3.2 %} +| Dependabot Security Updates | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." | +| Dependabot Version Updates | Dependabot can be used to keep the packages you use updated to the latest versions. For more information, see "[About Dependabot version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." | {% endif %} -{% note %} - -**Note:** Dependabot security updates and version updates are currently only available for {% data variables.product.prodname_ghe_cloud %} and will be available for {% data variables.product.prodname_ghe_server %} as outlined in our [public roadmap](https://github.com/github/roadmap). - -{% endnote %} +{% data reusables.dependabot.beta-security-and-version-updates-onboarding %} ### Step 8: Establish a remediation process @@ -303,7 +318,8 @@ You can learn more about [CodeQL queries](https://codeql.github.com/docs/writing All throughout the pilot phase, it’s essential to create and maintain high-quality internal documentation of the infrastructure and process changes made within your company, as well as learnings from the pilot process and configuration changes made as your team(s) progress throughout the rollout and implementation process. -Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process. Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s). +Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process. +Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s). Good documentation doesn’t end when rollout and implementation are complete. The most helpful documentation is actively updated and evolves as your teams expand their experience using GHAS and as their needs grow. @@ -358,7 +374,8 @@ Based on what you learned from your pilot project(s), update the rollout plan yo {% note %} {% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 3 may -last anywhere from 2 weeks to multiple months. This range can vary largely depending on your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc. +last anywhere from 2 weeks to multiple months. This range can vary largely depending on +your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc. {% endnote %} @@ -383,11 +400,11 @@ To help support your teams, here's a recap of relevant GitHub documentation. For documentation on how to enable GHAS, see: - "[Enabling Advanced Security features](/get-started/learning-about-github/about-github-advanced-security)" - - "[Administrar la seguridad y la configuración de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" - - "[Administrar la configuración de seguridad y de análisis para tu organización](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" + - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" + - "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" For documentation on how to migrate to GitHub, see: - - "[Importar código fuente a GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)" + - "[Importing source code to GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)" For documentation on getting started with GitHub, see: - "[Get started](/get-started)" diff --git a/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index 13cb632c5d..d32b69a028 100644 --- a/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Habilitar la Seguridad Avanzada de GitHub para tu empresa -shortTitle: Habilitar la Seguridad Avanzada de GitHub -intro: 'Puedes configurar {% data variables.product.product_name %} para que incluya la {% data variables.product.prodname_GH_advanced_security %}. Esto proporciona características adicionales que ayudan a los usuarios a encontrar y solucionar problemas de seguridad en su código.' +title: Enabling GitHub Advanced Security for your enterprise +shortTitle: Enabling GitHub Advanced Security +intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.' product: '{% data reusables.gated-features.ghas %}' versions: ghes: '*' @@ -14,81 +14,84 @@ topics: - Security --- -## Acerca de habilitar la {% data variables.product.prodname_GH_advanced_security %} +## About enabling {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.ghas-helps-developers %} {% ifversion ghes > 3.0 %} -Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} para tu empresa, los administradores de repositorio de todas las organizaciones pueden habilitar las características a menos de que configures una política para restringir el acceso. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)". +When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)." {% else %} -Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} para tu empresa, los administradores de repositorio en todas las organizaciones pueden habilitar las características. {% ifversion ghes = 3.0 %}Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración y análisis de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} +When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% ifversion ghes = 3.0 %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} {% endif %} {% ifversion ghes %} For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying GitHub Advanced Security in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." {% endif %} -## Prerequisitos para habilitar la {% data variables.product.prodname_GH_advanced_security %} +## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %} -1. Mejora tu licencia para que {% data variables.product.product_name %} incluya la {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} Para obtener más información sobre el licenciamiento, consulta la sección "[Acerca de la facturación de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".{% endif %} -2. Descarga el archivo de licencia nuevo. Paa obtener más información, consulta la sección "[Descargar tu licencia para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". -3. Carga el archivo de licencia nuevo en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Cargar una licencia nueva en {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% ifversion ghes %} -4. Revisa los prerequisitos para las características que piensas habilitar. +1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} +2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." +3. Upload the new license file to {% data variables.product.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %} +4. Review the prerequisites for the features you plan to enable. - - {% data variables.product.prodname_code_scanning_capc %}, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} para tu aplicativo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)". - - {% data variables.product.prodname_secret_scanning_caps %}, consulta la sección "[Configurar el {% data variables.product.prodname_secret_scanning %} para tu aplicativo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)".{% endif %} - - {% data variables.product.prodname_dependabot %}, Consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)". + - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)." + - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %} + - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." -## Verificar si tu licencia incluye a la {% data variables.product.prodname_GH_advanced_security %} +## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} {% ifversion ghes > 3.0 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Si tu licencia incluye a la {% data variables.product.prodname_GH_advanced_security %}, la página de licencia incluirá una sección que muestra los detalles de uso actuales. ![Sección de {% data variables.product.prodname_GH_advanced_security %} de la licencia empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) +1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. +![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) {% endif %} {% ifversion ghes = 3.0 %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. Si tu licencia incluye la {% data variables.product.prodname_GH_advanced_security %}, habrá una entrada de **{% data variables.product.prodname_advanced_security %}** en la barra lateral izquierda. ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) +1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. +![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) {% data reusables.enterprise_management_console.advanced-security-license %} {% endif %} -## Habilitar e inhabilitar las característcicas de la {% data variables.product.prodname_GH_advanced_security %} +## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features {% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %} -1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Seguridad{% endif %}", selecciona las características que quieras habilitar y deselecciona cualquier característica que quieras inhabilitar. +1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," select the features that you want to enable and deselect any features you want to disable. {% ifversion ghes > 3.1 %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %} -1. Debajo de "{% data variables.product.prodname_advanced_security %}", da clic en **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} +1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**. +![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} -Cuando {% data variables.product.product_name %} termina de reiniciarse, estás listo para configurar cualquier recurso adicional que se requiera para las características recién habilitadas. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_code_scanning %} en tu aplicativo](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." +When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." -## Habilitar o inhabilitar las características de la {% data variables.product.prodname_GH_advanced_security %} a través del shell administrativo (SSH) +## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH) -Puedes habilitar o inhabilitar las características mediante programación en {% data variables.product.product_location %}. Para obtener más información acerca de las utilidades del shell administrativo y de la línea de comandos para {% data variables.product.prodname_ghe_server %}, consulta las secciones "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[Utilidades de la línea de comandos](/admin/configuration/command-line-utilities#ghe-config)". +You can enable or disable features programmatically on {% data variables.product.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)." -Por ejemplo, puedes habilitar cualquier característica de {% data variables.product.prodname_GH_advanced_security %} con tus herramientas de infraestructura-como-código cuando despliegas una instancia para hacer pruebas o para recuperación de desastres. +For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery. -1. SSH en {% data variables.product.product_location %}. -1. Habilita las características de {% data variables.product.prodname_GH_advanced_security %}. +1. SSH into {% data variables.product.product_location %}. +1. Enable features for {% data variables.product.prodname_GH_advanced_security %}. - - Para habilitar el {% data variables.product.prodname_code_scanning_capc %}, ingresa los siguientes comandos. + - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands. ```shell ghe-config app.minio.enabled true ghe-config app.code-scanning.enabled true ``` - - Para habilitar el {% data variables.product.prodname_secret_scanning_caps %}, ingresa el siguiente comando. + - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command. ```shell ghe-config app.secret-scanning.enabled true ``` - - Para habilitar el {% data variables.product.prodname_dependabot %}, ingresa el siguiente {% ifversion ghes > 3.1 %}comando{% else %}comandos{% endif %}. + - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. {% ifversion ghes > 3.1 %}```shell ghe-config app.dependency-graph.enabled true ``` @@ -96,18 +99,18 @@ Por ejemplo, puedes habilitar cualquier característica de {% data variables.pro ghe-config app.github.dependency-graph-enabled true ghe-config app.github.vulnerability-alerting-and-settings-enabled true ```{% endif %} -2. Opcionalmente, inhabilita las características de {% data variables.product.prodname_GH_advanced_security %}. +2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. - - Para inhabilitar el {% data variables.product.prodname_code_scanning %}, ingresa los siguientes comandos. + - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. ```shell ghe-config app.minio.enabled false ghe-config app.code-scanning.enabled false ``` - - Para inhabilitar el {% data variables.product.prodname_secret_scanning %}, ingresa el siguiente comando. + - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command. ```shell ghe-config app.secret-scanning.enabled false ``` - - Para inhabilitar el {% data variables.product.prodname_dependabot %}, ingresa el siguiente {% ifversion ghes > 3.1 %}comando{% else %}comandos{% endif %}. + - To disable {% data variables.product.prodname_dependabot_alerts %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. {% ifversion ghes > 3.1 %}```shell ghe-config app.dependency-graph.enabled false ``` @@ -115,7 +118,7 @@ Por ejemplo, puedes habilitar cualquier característica de {% data variables.pro ghe-config app.github.dependency-graph-enabled false ghe-config app.github.vulnerability-alerting-and-settings-enabled false ```{% endif %} -3. Aplica la configuración +3. Apply the configuration. ```shell ghe-config-apply ``` diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md index fe90ebe6b8..f47653013e 100644 --- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md +++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md @@ -1,5 +1,5 @@ --- -title: Usar LDAP +title: Using LDAP redirect_from: - /enterprise/admin/articles/configuring-ldap-authentication/ - /enterprise/admin/articles/about-ldap-authentication/ @@ -9,7 +9,7 @@ redirect_from: - /enterprise/admin/user-management/using-ldap - /enterprise/admin/authentication/using-ldap - /admin/authentication/using-ldap -intro: 'LDAP te permite autenticar el {% data variables.product.prodname_ghe_server %} en tus cuentas existentes y administrar de manera centralizada el acceso a los repositorios. LDAP es un protocolo de aplicación popular para acceder a servicios de información de directorios y mantenerlos, y uno de los protocolos más comunes que se usan para integrar software de terceros con directorios de usuarios de empresas grandes.' +intro: 'LDAP lets you authenticate {% data variables.product.prodname_ghe_server %} against your existing accounts and centrally manage repository access. LDAP is a popular application protocol for accessing and maintaining directory information services, and is one of the most common protocols used to integrate third-party software with large company user directories.' versions: ghes: '*' type: how_to @@ -19,12 +19,11 @@ topics: - Enterprise - Identity --- - {% data reusables.enterprise_user_management.built-in-authentication %} -## Servicios LDAP admitidos +## Supported LDAP services -El {% data variables.product.prodname_ghe_server %} se integra con los siguientes servicios LDAP: +{% data variables.product.prodname_ghe_server %} integrates with these LDAP services: * Active Directory * FreeIPA @@ -33,7 +32,7 @@ El {% data variables.product.prodname_ghe_server %} se integra con los siguiente * Open Directory * 389-ds -## Consideraciones sobre el nombre de usuario con LDAP +## Username considerations with LDAP {% data reusables.enterprise_management_console.username_normalization %} @@ -42,150 +41,153 @@ El {% data variables.product.prodname_ghe_server %} se integra con los siguiente {% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %} -## Configurar LDAP con {% data variables.product.product_location %} +## Configuring LDAP with {% data variables.product.product_location %} -Una vez configurado LDAP, los usuarios podrán iniciar sesión en tu instancia con sus credenciales LDAP. Cuando los usuarios inician sesión por primera vez, sus nombres de perfil, direcciones de correo electrónico y claves SSH se establecen con los atributos de LDAP desde tu directorio. +After you configure LDAP, users will be able to sign into your instance with their LDAP credentials. When users sign in for the first time, their profile names, email addresses, and SSH keys will be set with the LDAP attributes from your directory. -Cuando configuras el acceso de LDAP para los usuarios a través de {% data variables.enterprise.management_console %}, tus licencias de usuario no se utilizarán sino hasta que los usuarios ingresen en tu instancia por primera vez. Sin embargo, si creas una cuenta manualmente utilizando la configuración de administrador para el sitio, esta licencia de usuario se tomará en cuenta. +When you configure LDAP access for users via the {% data variables.enterprise.management_console %}, your user licenses aren't used until the first time a user signs in to your instance. However, if you create an account manually using site admin settings, the user license is immediately accounted for. {% warning %} -**Advertencia:** Antes de configurar LDAP en {% data variables.product.product_location %}, asegúrate de que tu servicio LDAP admita resultados paginados. +**Warning:** Before configuring LDAP on {% data variables.product.product_location %}, make sure that your LDAP service supports paged results. {% endwarning %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. En "Authentication" (Autenticación), selecciona **LDAP**. ![Seleccionar LDAP](/assets/images/enterprise/management-console/ldap-select.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación autenticación integrada LDAP](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) -5. Agrega tus parámetros de configuración. +3. Under "Authentication", select **LDAP**. +![LDAP select](/assets/images/enterprise/management-console/ldap-select.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select LDAP built-in authentication checkbox](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) +5. Add your configuration settings. -## Atributos de LDAP -Usa estos atributos para terminar de configurar LDAP para {% data variables.product.product_location %}. +## LDAP attributes +Use these attributes to finish configuring LDAP for {% data variables.product.product_location %}. -| Nombre del atributo | Type | Descripción | -| --------------------------------------------------------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Host` | Requerido | El host LDAP, p. ej. `ldap.example.com` o `10.0.0.30`. Si el nombre del host solo está disponible desde tu red interna, es posible que primero debas configurar el DNS de {% data variables.product.product_location %} para que pueda resolver el nombre del host usando tus servidores de nombres internos. | -| `Port (Puerto)` | Requerido | El puerto que están escuchando los servicios LDAP. Los ejemplos incluyen: 389 y 636 (para LDAPS). | -| `Encryption (Cifrado)` | Requerido | El método de cifrado usado para garantizar las comunicaciones con el servidor LDAP. Los ejemplos incluyen el normal (sin cifrado), el SSL/LDAPS (cifrado desde el principio) y el StartTLS (se actualiza a comunicación cifrada una vez que se conecta). | -| `Usuario de búsqueda de dominio` | Opcional | El usuario LDAP que busca a otros usuarios que iniciaron sesión, para permitir la autenticación. Esto suele ser una cuenta de servicio creada específicamente para integraciones de terceros. Usa un nombre certificado completo, como `cn=Administrator,cn=Users,dc=Example,dc=com`. Con Active Directory, también puedes usar la sintaxis `[DOMAIN]\[USERNAME]` (p. ej.,`WINDOWS\Administrator`) para el usuario de búsqueda de dominio. | -| `Domain search password (Contraseña de búsqueda de dominio)` | Opcional | La contraseña para el usuario de búsqueda de dominio. | -| `Grupo de administradores` | Opcional | Los usuarios de este grupo son promovidos a administradores del sitio cuando inician sesión en tu aparato. Si no configuras un Grupo de administradores LDAP, la primera cuenta de usuario LDAP que inicie sesión en tu aparato será promovida automáticamente a administrador del sitio. | -| `Domain base (Base de dominio)` | Requerido | El `Nombre Distintivo` (DN) completamente calificado de un subárbol LDAP que quieras buscar para usuarios y grupos. Puedes agregar tantos como quieras; sin embargo, cada grupo debe estar definido en la misma base de dominio que los usuarios que le pertenecen. Si especificas grupos de usuarios con restricciones, solo los usuarios que pertenecen a esos grupo estarán al alcance. Te recomendamos que especifiques el primer nivel de tu árbol de directorios LDAP como tu base de dominio y que uses grupos de usuarios con restricciones para controlar el acceso. | -| `Restricted user groups (Grupos de usuarios con restricciones)` | Opcional | Si se especifica, solo los usuarios de estos grupos tendrán permiso para iniciar sesión. Solo necesitas especificar los nombres comunes (CN) de los grupos y puedes agregar tantos grupos como quieras. Si no se especifica ningún grupo, *todos* los usuarios dentro del alcance de la base de dominio especificada podrán iniciar sesión en tu instancia del {% data variables.product.prodname_ghe_server %}. | -| `User ID (Identificación de usuario)` | Requerido | El atributo de LDAP que identifica al usuario LDAP que intenta una autenticación. Una vez que se establece una asignación, los usuarios pueden modificar sus nombres de usuario del {% data variables.product.prodname_ghe_server %}. El campo debería ser `sAMAccountName` para la mayoría de las instalaciones de Active Directory, pero puede ser `uid` para otras soluciones LDAP, como OpenLDAP. El valor predeterminado es `uid`. | -| `Nombre de perfil` | Opcional | El nombre que aparecerá en la página de perfil del {% data variables.product.prodname_ghe_server %} del usuario. A menos que la sincronización LDAP esté activada, los usuarios pueden modificar sus nombres de perfil. | -| `Emails (Correos electrónicos)` | Opcional | Las direcciones de correo electrónico para la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. | -| `SSH keys (Claves SSH)` | Opcional | Las claves SSH públicas vinculadas a la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. Las claves deben ser en formato OpenSSH. | -| `Claves GPG` | Opcional | Las claves GPG vinculadas a la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. | -| `Disable LDAP authentication for Git operations (Desactivar la autenticación LDAP para las operaciones de Git)` | Opcional | Si está seleccionado, [desactiva](#disabling-password-authentication-for-git-operations) la posibilidad del usuario de usar contraseñas LDAP para autenticar las operaciones de Git. | -| `Enable LDAP certificate verification (Activar la verificación de certificado LDAP)` | Opcional | Si está seleccionado, [activa](#enabling-ldap-certificate-verification) la verificación de certificado LDAP. | -| `Synchronization (Sincronización)` | Opcional | Si está seleccionado, [activa](#enabling-ldap-sync) la sincronización LDAP. | +| Attribute name | Type | Description | +|--------------------------|----------|-------------| +| `Host` | Required | The LDAP host, e.g. `ldap.example.com` or `10.0.0.30`. If the hostname is only available from your internal network, you may need to configure {% data variables.product.product_location %}'s DNS first so it can resolve the hostname using your internal nameservers. | +| `Port` | Required | The port the host's LDAP services are listening on. Examples include: 389 and 636 (for LDAPS). | +| `Encryption` | Required | The encryption method used to secure communications to the LDAP server. Examples include plain (no encryption), SSL/LDAPS (encrypted from the start), and StartTLS (upgrade to encrypted communication once connected). | +| `Domain search user` | Optional | The LDAP user that looks up other users that sign in, to allow authentication. This is typically a service account created specifically for third-party integrations. Use a fully qualified name, such as `cn=Administrator,cn=Users,dc=Example,dc=com`. With Active Directory, you can also use the `[DOMAIN]\[USERNAME]` syntax (e.g. `WINDOWS\Administrator`) for the domain search user with Active Directory. | +| `Domain search password` | Optional | The password for the domain search user. | +| `Administrators group` | Optional | Users in this group are promoted to site administrators when signing into your appliance. If you don't configure an LDAP Administrators group, the first LDAP user account that signs into your appliance will be automatically promoted to a site administrator. | +| `Domain base` | Required | The fully qualified `Distinguished Name` (DN) of an LDAP subtree you want to search for users and groups. You can add as many as you like; however, each group must be defined in the same domain base as the users that belong to it. If you specify restricted user groups, only users that belong to those groups will be in scope. We recommend that you specify the top level of your LDAP directory tree as your domain base and use restricted user groups to control access. | +| `Restricted user groups` | Optional | If specified, only users in these groups will be allowed to log in. You only need to specify the common names (CNs) of the groups, and you can add as many groups as you like. If no groups are specified, *all* users within the scope of the specified domain base will be able to sign in to your {% data variables.product.prodname_ghe_server %} instance. | +| `User ID` | Required | The LDAP attribute that identifies the LDAP user who attempts authentication. Once a mapping is established, users may change their {% data variables.product.prodname_ghe_server %} usernames. This field should be `sAMAccountName` for most Active Directory installations, but it may be `uid` for other LDAP solutions, such as OpenLDAP. The default value is `uid`. | +| `Profile name` | Optional | The name that will appear on the user's {% data variables.product.prodname_ghe_server %} profile page. Unless LDAP Sync is enabled, users may change their profile names. | +| `Emails` | Optional | The email addresses for a user's {% data variables.product.prodname_ghe_server %} account. | +| `SSH keys` | Optional | The public SSH keys attached to a user's {% data variables.product.prodname_ghe_server %} account. The keys must be in OpenSSH format. | +| `GPG keys` | Optional | The GPG keys attached to a user's {% data variables.product.prodname_ghe_server %} account. | +| `Disable LDAP authentication for Git operations` | Optional |If selected, [turns off](#disabling-password-authentication-for-git-operations) users' ability to use LDAP passwords to authenticate Git operations. | +| `Enable LDAP certificate verification` | Optional |If selected, [turns on](#enabling-ldap-certificate-verification) LDAP certificate verification. | +| `Synchronization` | Optional |If selected, [turns on](#enabling-ldap-sync) LDAP Sync. | -### Desactivar la autenticación de contraseña para las operaciones de Git +### Disabling password authentication for Git operations -Selecciona **Disable username and password authentication for Git operations** (Desactivar la autenticación de nombre de usuario y contraseña para las operaciones de Git) en los parámetros de tu LDAP para implementar el uso de los tokens de acceso personal o las claves SSH para el acceso a Git, que pueden ayudarte a prevenir que tu servidor se sobrecargue de solicitudes de autenticación LDAP. Recomendamos esta configuración, ya que un servidor LDAP de respuesta lenta, en especial combinado con una gran cantidad de solicitudes debido al sondeo, suele ser una causa de problemas e interrupciones. +Select **Disable username and password authentication for Git operations** in your LDAP settings to enforce use of personal access tokens or SSH keys for Git access, which can help prevent your server from being overloaded by LDAP authentication requests. We recommend this setting because a slow-responding LDAP server, especially combined with a large number of requests due to polling, is a frequent source of performance issues and outages. -![Desactivar la casilla de verificación autenticación de contraseña LDAP](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) +![Disable LDAP password auth for Git check box](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) -Cuando se selecciona esta opción, si un usuario intenta usar una contraseña para las operaciones de Git a través de la línea de comando, recibirá un mensaje de error que dice: `La autenticación de contraseña no está permitida para las operaciones de Git. Debes usar un token de acceso personal.` +When this option is selected, if a user tries to use a password for Git operations via the command line, they will receive an error message that says, `Password authentication is not allowed for Git operations. You must use a personal access token.` -### Activar la verificación de certificado LDAP +### Enabling LDAP certificate verification -Selecciona **Enable LDAP certificate verification** (Activar verificación de certificado LDAP) en tus parámetros LDAP para validar el certificado del servidor LDAP que usas con TLS. +Select **Enable LDAP certificate verification** in your LDAP settings to validate the LDAP server certificate you use with TLS. -![Casilla de verificación de certificado LDAP](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) +![LDAP certificate verification box](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) -Cuando se selecciona esta opción, el certificado se valida para garantizar que: -- Si el certificado contiene al menos un nombre alternativo del firmante (SAN), uno de los SAN coincida con el nombre del host de LDAP. De lo contrario, que el nombre común (CN) coincida con el nombre del host de LDAP. -- El certificado no haya vencido. -- El certificado esté firmado por una entidad de certificación (CA) de confianza. +When this option is selected, the certificate is validated to make sure: +- If the certificate contains at least one Subject Alternative Name (SAN), one of the SANs matches the LDAP hostname. Otherwise, the Common Name (CN) matches the LDAP hostname. +- The certificate is not expired. +- The certificate is signed by a trusted certificate authority (CA). -### Activar la sincronización LDAP +### Enabling LDAP Sync {% note %} -**Nota:** Los equipos que utilizan sincronizaciòn de LDAP se limitan a un màximo de 1499 miembros. +**Note:** Teams using LDAP Sync are limited to a maximum 1499 members. {% endnote %} -La sincronización LDAP te permite sincronizar usuarios y miembros del equipo del {% data variables.product.prodname_ghe_server %} con tus grupos LDAP establecidos. Esto te permite establecer un control de acceso basado en roles para los usuarios desde tu servidor LDAP, en lugar de hacerlo de forma manual dentro del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Crear equipos](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)". +LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)." -Para activar la sincronización LDAP, en tus parámetros LDAP, selecciona **Synchronize Emails** (Sincronizar correos electrónicos), **Synchronize SSH Keys** (Sincronizar claves SSH) o **Synchronize GPG Keys** (Sincronizar claves GPG). +To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** . -![Casilla de verificación de Sincronización](/assets/images/enterprise/management-console/ldap-synchronize.png) +![Synchronization check box](/assets/images/enterprise/management-console/ldap-synchronize.png) -Una vez que actives la sincronización LDAP, se ejecutará un trabajo de sincronización en el intervalo de tiempo especificado para realizar las siguientes operaciones en cada cuenta de usuario: +After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account: -- Si has permitido la autenticación integrada para usuarios externos a tu proveedor de identidad, y el usuario está usando la autenticación integrada, pasa al siguiente usuario. -- Si no existe una asignación LDAP para el usuario, intenta asignar el usuario a una entrada LDAP en el directorio. Si el usuario no se puede asignar a una entrada LDAP, suspéndelo y pasa al siguiente usuario. -- Si hay una asignación LDAP y falta la entrada LDAP correspondiente en el directorio, suspende el usuario y pasa al siguiente usuario. -- Si la entrada LDAP correspondiente se marcó como desactivada, y el usuario aún no se suspendió, suspéndelo y pasa al siguiente usuario. -- Si la entrada LDAP correspondiente no se marcó como desactivada, el usuario está suspendido y _Reactivate suspended users_ (Reactivar usuarios suspendidos) está activado en el centro de administración, anula la suspensión del usuario. -- Si la entrada LDAP correspondiente incluye un atributo `name`, actualiza el nombre de perfil del usuario. -- Si la entrada LDAP correspondiente está en el grupo de administradores, promueve al usuario a administrador del sitio. -- Si la entrada LDAP correspondiente no está en el grupo de administradores, degrada al usuario a una cuenta normal. -- Si un campo de usuario LDAP está definido para correos electrónicos, sincroniza los parámetros del correo electrónico del usuario con la entrada LDAP. Establece la primera entrada `mail` LDAP como el correo electrónico principal. -- Si un campo de usuario LDAP está definido para claves públicas SSH, sincroniza las claves SSH públicas del usuario con la entrada LDAP. -- Si un campo de usuario LDAP está definido para claves GPG, sincroniza las claves GPG del usuario con la entrada LDAP. +- If you've allowed built-in authentication for users outside your identity provider, and the user is using built-in authentication, move on to the next user. +- If no LDAP mapping exists for the user, try to map the user to an LDAP entry in the directory. If the user cannot be mapped to an LDAP entry, suspend the user and move on to the next user. +- If there is an LDAP mapping and the corresponding LDAP entry in the directory is missing, suspend the user and move on to the next user. +- If the corresponding LDAP entry has been marked as disabled and the user is not already suspended, suspend the user and move on to the next user. +- If the corresponding LDAP entry is not marked as disabled, and the user is suspended, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user. +- If the corresponding LDAP entry includes a `name` attribute, update the user's profile name. +- If the corresponding LDAP entry is in the Administrators group, promote the user to site administrator. +- If the corresponding LDAP entry is not in the Administrators group, demote the user to a normal account. +- If an LDAP User field is defined for emails, synchronize the user's email settings with the LDAP entry. Set the first LDAP `mail` entry as the primary email. +- If an LDAP User field is defined for SSH public keys, synchronize the user's public SSH keys with the LDAP entry. +- If an LDAP User field is defined for GPG keys, synchronize the user's GPG keys with the LDAP entry. {% note %} -**Nota**: Las entradas LDAP solo pueden estar marcadas como desactivadas si usas Active Directory y el atributo `userAccountControl` está presente y marcado con `ACCOUNTDISABLE`. +**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. {% endnote %} -También se ejecutará un trabajo de sincronización en el intervalo de tiempo especificado para realizar las siguientes operaciones en cada equipo que haya sido asignado a un grupo LDAP: +A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group: -- Si se eliminó el grupo LDAP correspondiente de un equipo, elimina todos los miembros del equipo. -- Si las entradas de miembros LDAP se eliminaron del grupo LDAP, elimina los usuarios correspondientes del equipo. Si como resultado el usuario pierde acceso a algún repositorio, elimina toda bifurcación privada que el usuario tenga de esos repositorios. -- Si las entradas de miembros LDAP se agregaron al grupo LDAP, agrega los usuarios correspondientes al equipo. Si como resultado el usuario recupera el acceso a algún repositorio, restablece toda bifurcación privada de los repositorios que haya sido eliminada debido a que el usuario perdió acceso en los últimos 90 días. +- If a team's corresponding LDAP group has been removed, remove all members from the team. +- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories. +- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% warning %} -**Advertencia de seguridad:** +**Security Warning:** -Cuando la sincronización LDAP está activada, los administradores del sitio y los propietarios de la organización pueden buscar en el directorio LDAP los grupos a los cuales asignar el equipo. +When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to. -Esto posibilita divulgar información organizativa confidencial a contratistas u otros usuarios sin privilegios, incluidos los siguientes: +This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including: -- La existencia de grupos LDAP específicos visibles para el *Usuario de búsqueda de dominio*. -- Los miembros del grupo LDAP que tienen cuentas de usuario del {% data variables.product.prodname_ghe_server %}, que se divulga cuando se crea un equipo sincronizado con ese grupo LDAP. +- The existence of specific LDAP Groups visible to the *Domain search user*. +- Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group. -Si no se desea divulgar dicha información, su empresa u organización debe restringir los permisos del *Usuario de búsqueda de dominio* en la consola de administración. Si no es posible aplicar dicha restricción, comuníquese con el {% data variables.contact.contact_ent_support %}. +If disclosing such information is not desired, your company or organization should restrict the permissions of the configured *Domain search user* in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}. {% endwarning %} -### Clases de objetos del grupo LDAP admitidas +### Supported LDAP group object classes -El {% data variables.product.prodname_ghe_server %} admite estas clases de objetos del grupo LDAP. Los grupos se pueden anidar. +{% data variables.product.prodname_ghe_server %} supports these LDAP group object classes. Groups can be nested. -- `grupo` +- `group` - `groupOfNames` - `groupOfUniqueNames` - `posixGroup` -## Ver y crear usuarios LDAP +## Viewing and creating LDAP users -Puedes ver la lista completa de usuarios LDAP que tienen acceso a tu instancia y aprovisionar nuevos usuarios. +You can view the full list of LDAP users who have access to your instance and provision new users. {% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} -3. En la barra lateral izquierda, haz clic en **LDAP users** (Usuarios LDAP). ![Pestaña LDAP users (Usuarios LDAP)](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) -4. Para buscar un usuario, escribe un nombre de usuario completo o parcial y haz clic en **Search** (Buscar). Se mostrarán los usuarios existentes en los resultados de búsqueda. Si un usuario no existe, haz clic en **Create** (Crear) para aprovisionar la nueva cuenta de usuario. ![Búsqueda LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-search.png) +3. In the left sidebar, click **LDAP users**. +![LDAP users tab](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) +4. To search for a user, type a full or partial username and click **Search**. Existing users will be displayed in search results. If a user doesn’t exist, click **Create** to provision the new user account. +![LDAP search](/assets/images/enterprise/site-admin-settings/ldap-users-search.png) -## Actualizar cuentas LDAP +## Updating LDAP accounts -A menos que [la sincronización LDAP esté activada](#enabling-ldap-sync), las modificaciones de las cuentas LDAP no se sincronizan automáticamente con el {% data variables.product.prodname_ghe_server %}. +Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}. -* Para usar un nuevo grupo de administración LDAP, los usuarios deben ser promovidos y degradados de forma manual en el {% data variables.product.prodname_ghe_server %} para reflejar las modificaciones en LDAP. -* Para agregar o eliminar cuentas LDAP de los grupos de administración LDAP, [promueve o degrada las cuentas en el {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator). -* Para eliminar las cuentas LDAP, [suspende las cuentas del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users). +* To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP. +* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator). +* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users). -### Sincronizar cuentas LDAP de forma manual +### Manually syncing LDAP accounts {% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} @@ -193,12 +195,13 @@ A menos que [la sincronización LDAP esté activada](#enabling-ldap-sync), las m {% data reusables.enterprise_site_admin_settings.click-user %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -5. En "LDAP", haz clic en **Sync now** (Sincronizar ahora) para actualizar de forma manual la cuenta con los datos de tu servidor LDAP. ![Botón LDAP sync now (Sincronizar LDAP ahora)](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) +5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server. +![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) -También puedes [utilizar la API para activar una sincronización manual](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap). +You can also [use the API to trigger a manual sync](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap). -## Revocar acceso a {% data variables.product.product_location %} +## Revoking access to {% data variables.product.product_location %} -Si [la sincronización LDAP está activada](#enabling-ldap-sync), al eliminar las credenciales LDAP de un usuario, se suspenderá su cuenta hasta la siguiente ejecución de sincronización. +If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run. -Si la sincronización LDAP **no** está activada, debes suspender de forma manual la cuenta del {% data variables.product.prodname_ghe_server %} después de eliminar las credenciales LDAP. Para obtener más información, consulta [Suspender y anular suspensión de usuarios](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)". +If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)". diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md index 17007bdb3d..d92f270477 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Configurar tu empresa -intro: 'Después de que {% data variables.product.product_name %} se encuentre listo y funcionando, puedes configurar tu empresa de acuerdo con las necesidades de tu organización.' +title: Configuring your enterprise +intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.' redirect_from: - /enterprise/admin/guides/installation/basic-configuration/ - /enterprise/admin/guides/installation/administrative-tools/ @@ -34,6 +34,7 @@ children: - /restricting-network-traffic-to-your-enterprise - /configuring-github-pages-for-your-enterprise - /configuring-the-referrer-policy-for-your-enterprise -shortTitle: Configurar tu empresa + - /configuring-custom-footers +shortTitle: Configure your enterprise --- diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md index 5ad52dad91..983821794c 100644 --- a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md @@ -20,8 +20,7 @@ topics: - Dependency graph - Dependabot --- - -## Acerca de las alertas para las dependencias vulnerables en {% data variables.product.product_location %} +## About alerts for vulnerable dependencies on {% data variables.product.product_location %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -34,9 +33,9 @@ For more information about these features, see "[About the dependency graph](/gi ### About synchronization of data from the {% data variables.product.prodname_advisory_database %} -{% data reusables.repositories.tracks-vulnerabilities %} +{% data reusables.repositories.tracks-vulnerabilities %} -You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. También puedes elegir sincronizar manualmente los datos de vulnerabilidad en cualquier momento. No se han cargado códigos o información sobre el código desde {% data variables.product.product_location %} hasta {% data variables.product.prodname_dotcom_the_website %}. +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. ### About generation of {% data variables.product.prodname_dependabot_alerts %} @@ -44,68 +43,76 @@ If you enable vulnerability detection, when {% data variables.product.product_lo ## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.product_location %} -### Prerrequisitos +### Prerequisites For {% data variables.product.product_location %} to detect vulnerable dependencies and generate {% data variables.product.prodname_dependabot_alerts %}: -- Debes conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae-next %}For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."{% endif %} +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae-next %}For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."{% endif %} {% ifversion ghes %}- You must enable the dependency graph service.{% endif %} - You must enable vulnerability scanning. {% ifversion ghes %} {% ifversion ghes > 3.1 %} -Puedes habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %} o del shell administrativo. Te recomendamos que sigas la ruta de la {% data variables.enterprise.management_console %} a menos de que {% data variables.product.product_location %} utilice clústering. +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. -### Habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %} +### Enabling the dependency graph via the {% data variables.enterprise.management_console %} {% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Debajo de "Seguridad", haz clic en **Gráfica de dependencias**. ![Casilla de verificación para habilitar o inhabilitar la gráfica de dependencias](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +1. Under "Security," click **Dependency graph**. +![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} -1. Da clic en **Visitar tu instancia**. +1. Click **Visit your instance**. -### Habilitar la gráfica de dependencias a través del shell administrativo +### Enabling the dependency graph via the administrative shell {% endif %}{% ifversion ghes < 3.2 %} -### Habilitar la gráfica de dependencias +### Enabling the dependency graph {% endif %} {% data reusables.enterprise_site_admin_settings.sign-in %} -1. En el shell administrativo, habilita la gráfica de dependencias en {% data variables.product.product_location %}: +1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: ``` shell $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} ``` {% note %} - **Nota**: Para obtener más información acerca de cómo habilitar el acceso al shell administrativo por SSH, consulta la sección "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)". + **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." {% endnote %} -1. Aplica la configuración +1. Apply the configuration. ```shell $ ghe-config-apply ``` -1. Regresa a {% data variables.product.prodname_ghe_server %}. +1. Return to {% data variables.product.prodname_ghe_server %}. {% endif %} -### Habilitar {% data variables.product.prodname_dependabot_alerts %} +### Enabling {% data variables.product.prodname_dependabot_alerts %} {% ifversion ghes %} -Antes de habilitar {% data variables.product.prodname_dependabot_alerts %} para tu instancia, necesitas habilitar la gráfica de dependencias. Para obtener más información, consulta la sección anterior. +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**. ![Menú desplegable para habilitar el escaneo de repositorios para buscar vulnerabilidades](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) +1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**. + ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) {% tip %} - - **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. Después de algunos días, puedes habilitar las notificaciones para recibir las {% data variables.product.prodname_dependabot_alerts %} como de costumbre. + + **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual. {% endtip %} -## Ver las dependencias vulnerables en {% data variables.product.product_location %} +{% ifversion fpt or ghec or ghes > 3.2 %} +When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." +{% endif %} -Puedes ver todas las vulnerabilidades en {% data variables.product.product_location %} y sincronizar en forma manual los datos de vulnerabilidad desde {% data variables.product.prodname_dotcom_the_website %} para actualizar la lista. +## Viewing vulnerable dependencies on {% data variables.product.product_location %} + +You can view all vulnerabilities in {% data variables.product.product_location %} and manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. En la barra lateral izquierda, haz clic en **Vulnerabilities** (Vulnerabilidades). ![Pestaña de vulnerabilidades de la barra lateral del administrador del sitio](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) -3. Para sincronizar los datos de vulnerabilidades, haz clic en **Sync Vulnerabilities now** (Sincronizar vulnerabilidades ahora). ![Botón de Sincronizar vulnerabilidades ahora](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) +2. In the left sidebar, click **Vulnerabilities**. + ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. To sync vulnerability data, click **Sync Vulnerabilities now**. + ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md index 3a5e6966f1..ce17d8a050 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md @@ -1,6 +1,6 @@ --- -title: Acerca de la Replicación geográfica -intro: 'La Replicación geográfica en {% data variables.product.prodname_ghe_server %} utiliza múltiples réplicas activas para responder las solicitudes de los centros de datos distribuidos geográficamente.' +title: About geo-replication +intro: 'Geo-replication on {% data variables.product.prodname_ghe_server %} uses multiple active replicas to fulfill requests from geographically distributed data centers.' redirect_from: - /enterprise/admin/installation/about-geo-replication - /enterprise/admin/enterprise-management/about-geo-replication @@ -12,24 +12,25 @@ topics: - Enterprise - High availability --- +Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London. -Contar con múltiples réplicas puede permitir una menor distancia a la réplica más cercana. Por ejemplo, una organización con oficinas en San Francisco, Nueva York y Londres podrían ejecutar el aparato principal en un centro de datos cercano a Nueva York y dos réplicas en centros de datos cercanos a San Francisco y Londres. Al usar DNS con información de geolocalización, se puede dirigir a los usuarios al servidor disponible más cercano para que accedan a los datos más rápido. Designar como principal el aparato cercano a Nueva York ayuda a reducir la latencia entre los hosts, a diferencia de si se designa como principal el aparato cercano a San Francisco, que tiene mayor latencia con Londres. +The active replica proxies requests that it can't process itself to the primary instance. The replicas function as a point of presence terminating all SSL connections. Traffic between hosts is sent through an encrypted VPN connection, similar to a two-node high availability configuration without geo-replication. -Los proxies de la réplica activa solicitan que no se pueda procesar esta misma para la instancia principal. Las réplicas funcionan como un punto de presencia al terminar todas las conexiones SSL. El tráfico entre los servidores se envía a través de una conexión VPN encriptada, similar a una configuración de dos nodos de alta disponibilidad sin replicación geográfica. +Git requests and specific file server requests, such as LFS and file uploads, can be served directly from the replica without loading any data from the primary. Web requests are always routed to the primary, but if the replica is closer to the user the requests are faster due to the closer SSL termination. -Las solicitudes de Git y las solicitudes de archivos específicos a los servidores, tales como LFS y cargas de archivos, pueden servirse directamente de la réplica sin cargar ningún dato desde el primario. Las solicitudes web siempre se enrutan hacia el principal, pero si la réplica está más cerca del usuario, las solicitudes son más rápidas porque la terminación SSL está más cerca. +Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), is required for geo-replication to work seamlessly. The hostname for the instance should resolve to the replica that is closest to the user's location. -Se solicita un DNS geográfico, como [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), para que la replicación geográfica funcione sin problemas. El nombre del host para la instancia se debe resolver con la réplica más cercana a la ubicación del usuario. +## Limitations -## Limitaciones +Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes is limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. {% ifversion ghes > 3.2 %}To reduce the latency and bandwidth caused by distributed teams and large CI farms without impacting write throughput, you can configure repository caching instead. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."{% endif %} -Escribir solicitudes para la réplica exige que se envíen los datos al principal y a todas las réplicas. Esto significa que el rendimiento de todos los escritos se limita de acuerdo con la replica más lenta, aunque las geo-replicas nuevas pueden poblar la mayoría de sus datos desde geo-replicas existentes co-ubicadas, en vez de desde el primario. La replicación geográfica no le agregará capacidad a una instancia de {% data variables.product.prodname_ghe_server %} ni resolverá problemas de rendimiento relacionados con recursos de CPU o de memoria insuficientes. Si el aparato principal está fuera de línea, las réplicas activas no podrán atender ninguna solicitud de lectura o escritura. +Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests. {% data reusables.enterprise_installation.replica-limit %} -## Monitorear la configuración de una replicación geográfica +## Monitoring a geo-replication configuration {% data reusables.enterprise_installation.monitoring-replicas %} -## Leer más -- "[Crear réplicas de replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" +## Further reading +- "[Creating geo-replication replicas](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md index 00abf328e5..c5ad5e0895 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md @@ -1,6 +1,6 @@ --- -title: Acerca de la configuración de alta disponibilidad -intro: 'En una configuración de alta disponibilidad, un aparato secundario {% data variables.product.prodname_ghe_server %} totalmente redundante se mantiene en sincronización con el aparato principal mediante la replicación de todos los almacenes de datos importantes.' +title: About high availability configuration +intro: 'In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores.' redirect_from: - /enterprise/admin/installation/about-high-availability-configuration - /enterprise/admin/enterprise-management/about-high-availability-configuration @@ -12,116 +12,116 @@ topics: - Enterprise - High availability - Infrastructure -shortTitle: Acerca de la configuración de HA +shortTitle: About HA configuration --- +When you configure high availability, there is an automated setup of one-way, asynchronous replication of all datastores (Git repositories, MySQL, Redis, and Elasticsearch) from the primary to the replica appliance. -Cuando configuras la alta disponibilidad, hay una configuración automática unidireccional, una replicación asincrónica de todos los almacenes de datos (repositorios de Git, MySQL, Redis y Elasticsearch) desde el aparato principal hacia la réplica. - -{% data variables.product.prodname_ghe_server %} admite una configuración activa/pasiva, en la que el aparato réplica se ejecuta como en un modo de espera con los servicios de base de datos ejecutándose en modo de replicación, pero con los servicios de aplicación detenidos. +{% data variables.product.prodname_ghe_server %} supports an active/passive configuration, where the replica appliance runs as a standby with database services running in replication mode but application services stopped. {% data reusables.enterprise_installation.replica-limit %} -## Escenarios de fallas específicas +## Targeted failure scenarios -Utiliza la configuración de alta disponibilidad para la protección contra lo siguiente: +Use a high availability configuration for protection against: {% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %} -Una configuración de alta disponibilidad no es una buena solución para lo siguiente: +A high availability configuration is not a good solution for: - - **Escalar**. Mientras que puede distribuir el tráfico geográficamente utilizando la replicación geográfica, el rendimiento de las escrituras queda limitado a la velocidad y la disponibilidad del aparato principal. Para obtener más informació, consulta "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." - - **Generar copias de seguridad de tu aparato principal**. Una réplica de alta disponibilidad no reemplaza las copias de seguridad externas en tu plan de recuperación ante desastres. Algunas formas de corrupción o pérdida de datos se pueden replicar de inmediato desde el aparato principal hacia la réplica. Para asegurar una reversión segura a un estado antiguo estable, debes realizar copias de seguridad de rutina con instantáneas históricas. - - **Actualizaciones del tiempo de inactividad en cero**. Para evitar la pérdida de datos y las situaciones de cerebro dividido en escenarios de promoción controlados, coloca el aparato principal en el modo de mantenimiento y espera a que se completen todas las escrituras entes de promover la réplica. + - **Scaling-out**. While you can distribute traffic geographically using geo-replication, the performance of writes is limited to the speed and availability of the primary appliance. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %} + - **CI/CD load**. If you have a large number of CI clients that are geographically distant from your primary instance, you may benefit from configuring a repository cache. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."{% endif %} + - **Backing up your primary appliance**. A high availability replica does not replace off-site backups in your disaster recovery plan. Some forms of data corruption or loss may be replicated immediately from the primary to the replica. To ensure safe rollback to a stable past state, you must perform regular backups with historical snapshots. + - **Zero downtime upgrades**. To prevent data loss and split-brain situations in controlled promotion scenarios, place the primary appliance in maintenance mode and wait for all writes to complete before promoting the replica. -## Estrategias de conmutación por error del tráfico de red +## Network traffic failover strategies -Durante la conmutación por error, debes configurar por separado y administrar el tráfico de red de redireccionamiento desde el aparato principal hacia la réplica. +During failover, you must separately configure and manage redirecting network traffic from the primary to the replica. -### Conmutación por error de DNS +### DNS failover -Con la conmutación por error de DNS, utiliza valores TTL cortos en los registros DNS que se dirijan al aparato principal {% data variables.product.prodname_ghe_server %}. Recomendamos un TTL de entre 60 segundos y cinco minutos. +With DNS failover, use short TTL values in the DNS records that point to the primary {% data variables.product.prodname_ghe_server %} appliance. We recommend a TTL between 60 seconds and five minutes. -Durante la conmutación por error, debes colocar el aparato principal en modo de mantenimiento y redirigir sus registros DNS hacia la dirección IP del aparato réplica. El tiempo necesario para redirigir el tráfico desde el aparato principal hacia la réplica dependerá de la configuración TTL y del tiempo necesario para actualizar los registros DNS. +During failover, you must place the primary into maintenance mode and redirect its DNS records to the replica appliance's IP address. The time needed to redirect traffic from primary to replica will depend on the TTL configuration and time required to update the DNS records. -Si estás utilizando la replicación geográfica, debes configurar Geo DNS en tráfico directo hacia la réplica más cercana. Para obtener más informació, consulta "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." +If you are using geo-replication, you must configure Geo DNS to direct traffic to the nearest replica. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." -### Balanceador de carga +### Load balancer {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %} -Durante la conmutación por error, debes colocar el aparato principal en el modo de mantenimiento. Puedes configurar el balanceador de carga para que detecte automáticamente cuando la réplica se haya promovido a principal, o puede que se requiera un cambio de configuración manual. Debes promover manualmente la réplica a principal antes de que responda al tráfico de usuarios. Para obtener más información, consulta "[Utilizar {% data variables.product.prodname_ghe_server %} con un balanceador de carga](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)." +During failover, you must place the primary appliance into maintenance mode. You can configure the load balancer to automatically detect when the replica has been promoted to primary, or it may require a manual configuration change. You must manually promote the replica to primary before it will respond to user traffic. For more information, see "[Using {% data variables.product.prodname_ghe_server %} with a load balancer](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)." {% data reusables.enterprise_installation.monitoring-replicas %} -## Utilidades para la administración de la replicación +## Utilities for replication management -Para administrar la replicación en {% data variables.product.prodname_ghe_server %}, haz uso de estas utilidades de la línea de comando conectándote al aparato réplica con SSH. +To manage replication on {% data variables.product.prodname_ghe_server %}, use these command line utilities by connecting to the replica appliance using SSH. ### ghe-repl-setup -El comando `ghe-repl-setup` coloca un aparato {% data variables.product.prodname_ghe_server %} en modo de espera de réplica. +The `ghe-repl-setup` command puts a {% data variables.product.prodname_ghe_server %} appliance in replica standby mode. - - Un tunel de VPN de WireGuard cifrado se configura para establecer la comunicación entre los dos aplicativos. - - Se configuran los servicios de bases de datos para la replicación y se inician. - - Se inhabilitan los servicios de aplicaciones. Los intentos de acceder al aparato réplica por HTTP, Git u otros protocolos compatibles generarán una página de mantenimiento o un mensaje de error de "aparato en modo réplica". + - An encrypted WireGuard VPN tunnel is configured for communication between the two appliances. + - Database services are configured for replication and started. + - Application services are disabled. Attempts to access the replica appliance over HTTP, Git, or other supported protocols will result in an "appliance in replica mode" maintenance page or error message. ```shell admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1 -Verificar la conectividad ssh con 169.254.1.1 ... -Comprobación de conexión exitosa. -Configurando la replicación de base de datos en oposición al principal... +Verifying ssh connectivity with 169.254.1.1 ... +Connection check succeeded. +Configuring database replication against primary ... Success: Replica mode is configured against 169.254.1.1. To disable replica mode and undo these changes, run `ghe-repl-teardown'. -Ejecuta `ghe-repl-start' para comenzar la replicación en oposición al principal recientemente configurado. +Run `ghe-repl-start' to start replicating against the newly configured primary. ``` ### ghe-repl-start -El comando `ghe-repl-start` inicia la replicación activa de todos los almacenes de datos. +The `ghe-repl-start` command turns on active replication of all datastores. ```shell admin@169-254-1-2:~$ ghe-repl-start Starting MySQL replication ... -Iniciando la replicación de Redis... -Iniciando la replicación de ElasticSearch... -Iniciando la replicación de Páginas... -Iniciando la replicación de Git... -Exitoso: La replicación se está ejecutando para todos los servicios. -Utiliza `ghe-repl-status' para monitorear el estado y el progreso de la replicación. +Starting Redis replication ... +Starting Elasticsearch replication ... +Starting Pages replication ... +Starting Git replication ... +Success: replication is running for all services. +Use `ghe-repl-status' to monitor replication health and progress. ``` ### ghe-repl-status -El comando `ghe-repl-status` muestra un estado de `OK`, `ADVERTENCIA` o `CRÍTICO` para cada corriente de replicación de almacén de datos. Cuando cualquiera de los canales de replicación está en estado `ADVERTENCIA`, el comando se cerrará con el código `1`. Del mismo modo, cuando cualquiera de los canales esté en un estado `CRÍTICO`, el comando se cerrará con el código `2`. +The `ghe-repl-status` command returns an `OK`, `WARNING` or `CRITICAL` status for each datastore replication stream. When any of the replication channels are in a `WARNING` state, the command will exit with the code `1`. Similarly, when any of the channels are in a `CRITICAL` state, the command will exit with the code `2`. ```shell admin@169-254-1-2:~$ ghe-repl-status -OK: replicación de mysql en sinc -OK: la replicación de redis está en sinc -OK: la agrupación de elasticsearch está en sinc -OK: los datos de git están en sinc (10 repos, 2 wikis, 5 gists) -OK: los datos de páginas están en sinc +OK: mysql replication in sync +OK: redis replication is in sync +OK: elasticsearch cluster is in sync +OK: git data is in sync (10 repos, 2 wikis, 5 gists) +OK: pages data is in sync ``` -Las opciones `-v` y `-vv` dan detalles sobre cada uno de los estados de replicación de almacén de datos: +The `-v` and `-vv` options give details about each datastore's replication state: ```shell $ ghe-repl-status -v -OK: replicación de mysql en sinc - | IO en ejecución: Sí, SQL en ejecución: Sí, Demora: 0 +OK: mysql replication in sync + | IO running: Yes, SQL running: Yes, Delay: 0 -OK: la replicación de redis está en sinc +OK: redis replication is in sync | master_host:169.254.1.1 | master_port:6379 | master_link_status:up | master_last_io_seconds_ago:3 | master_sync_in_progress:0 -OK: la agrupación de elasticsearch está en sinc +OK: elasticsearch cluster is in sync | { | "cluster_name" : "github-enterprise", | "status" : "green", - | "timed_out" : falso, + | "timed_out" : false, | "number_of_nodes" : 2, | "number_of_data_nodes" : 2, | "active_primary_shards" : 12, @@ -131,58 +131,58 @@ OK: la agrupación de elasticsearch está en sinc | "unassigned_shards" : 0 | } -OK: los datos de git están en sinc (366 repos, 31 wikis, 851 gists) - | TOTAL OK FALLA PENDIENTE CON DEMORA - | repositorios 366 366 0 0 0.0 +OK: git data is in sync (366 repos, 31 wikis, 851 gists) + | TOTAL OK FAULT PENDING DELAY + | repositories 366 366 0 0 0.0 | wikis 31 31 0 0 0.0 | gists 851 851 0 0 0.0 | total 1248 1248 0 0 0.0 -OK: los datos de páginas están en sinc - | Las páginas están en sinc +OK: pages data is in sync + | Pages are in sync ``` ### ghe-repl-stop -El comando `ghe-repl-stop` inhabilita temporalmente la replicación de todos los almacenes de datos y detiene los servicios de replicación. Para reanudar la replicación, utiliza el comando [ghe-repl-start](#ghe-repl-start). +The `ghe-repl-stop` command temporarily disables replication for all datastores and stops the replication services. To resume replication, use the [ghe-repl-start](#ghe-repl-start) command. ```shell admin@168-254-1-2:~$ ghe-repl-stop -Deteniendo la replicación de Páginas... -Deteniendo la replicación de Git... -Deteniendo la replicación de MySQL... -Deteniendo la replicación de Redis... -Deteniendo la replicación de ElasticSearch... -Exitoso: la replicación se detuvo para todos los servicios. +Stopping Pages replication ... +Stopping Git replication ... +Stopping MySQL replication ... +Stopping Redis replication ... +Stopping Elasticsearch replication ... +Success: replication was stopped for all services. ``` ### ghe-repl-promote -El comando `ghe-repl-promote` inhabilita la replicación y convierte el aparato réplica en principal. El aparato se configura con los mismos ajustes que el principal original y se habilitan todos los servicios. +The `ghe-repl-promote` command disables replication and converts the replica appliance to a primary. The appliance is configured with the same settings as the original primary and all services are enabled. {% data reusables.enterprise_installation.promoting-a-replica %} ```shell admin@168-254-1-2:~$ ghe-repl-promote -Habilitando el modo de mantenimiento en el aparato principal para evitar escrituras... -Deteniendo la replicación... - | Deteniendo la replicación de Páginas... - | Deteniendo la replicación de Git... - | Deteniendo la replicación de MySQL... - | Deteniendo la replicación de Redis... - | Deteniendo la replicación de ElasticSearch... - | Exitoso: la replicación se detuvo para todos los servicios. -Cambiando del modo réplica... - | Exitoso: se eliminó la configuración de la replicación. - | Ejecuta `ghe-repl-setup' para volver a habilitar el modo réplica. -Aplicando la configuración e iniciando los servicios... -Exitoso: la réplica se promovió a principal y ahora está aceptando solicitudes. +Enabling maintenance mode on the primary to prevent writes ... +Stopping replication ... + | Stopping Pages replication ... + | Stopping Git replication ... + | Stopping MySQL replication ... + | Stopping Redis replication ... + | Stopping Elasticsearch replication ... + | Success: replication was stopped for all services. +Switching out of replica mode ... + | Success: Replication configuration has been removed. + | Run `ghe-repl-setup' to re-enable replica mode. +Applying configuration and starting services ... +Success: Replica has been promoted to primary and is now accepting requests. ``` ### ghe-repl-teardown -El comando `ghe-repl-teardown` inhabilita el modo de replicación por completo, eliminando la configuración de la réplica. +The `ghe-repl-teardown` command disables replication mode completely, removing the replica configuration. -## Leer más +## Further reading -- "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)" +- "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)" diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md index 7a4e29a31c..e2c8c3a9ef 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md @@ -1,6 +1,6 @@ --- -title: Crear una réplica de alta disponibilidad -intro: 'En una configuración activa/pasiva, el aparato réplica es una copia redundante del aparato principal. Si el aparato principal falla, el modo de alta disponibilidad permite que la réplica actúe como aparato principal, lo que posibilita que la interrupción del servicio sea mínima.' +title: Creating a high availability replica +intro: 'In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption.' redirect_from: - /enterprise/admin/installation/creating-a-high-availability-replica - /enterprise/admin/enterprise-management/creating-a-high-availability-replica @@ -12,91 +12,81 @@ topics: - Enterprise - High availability - Infrastructure -shortTitle: Crear una réplica de HA +shortTitle: Create HA replica --- - {% data reusables.enterprise_installation.replica-limit %} -## Crear una réplica de alta disponibilidad +## Creating a high availability replica -1. Configurar un aparato {% data variables.product.prodname_ghe_server %} nuevo en la plataforma que desees. El aparato réplica debe espejar la CPU, la RAM y los ajustes de almacenamiento del aparato principal. Recomendamos que instales el aparato réplica en un entorno separado. El hardward subyacente, el software y los componentes de red deben estar aislados de los del aparato principal. Si estás usando un proveedor de nube, utiliza una región o zona separada. Para obtener más información, consulta ["Configurar una instancia {% data variables.product.prodname_ghe_server %}"](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance). -2. Desde un navegador, dirígete a la nueva dirección IP del aparato réplica y carga tu licencia de {% data variables.product.prodname_enterprise %}. -3. Establece una contraseña de administrador que coincida con la contraseña del aparato principal y continúa. -4. Haz clic en **Configure as Replica** (Configurar como réplica). ![Opciones de instalación con enlace para configurar tu nueva instancia como una réplica](/assets/images/enterprise/management-console/configure-as-replica.png) -5. En "Agregar nueva clave SSH", escribe tu clave SSH. ![Agrega la clave SSH](/assets/images/enterprise/management-console/add-ssh-key.png) -6. Haz clic en **Add key** (Agregar clave), luego haz clic en **Continue** (Continuar). -6. Conectarse a la dirección IP del aparato réplica usando SSH. +1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. For more information, see ["Setting up a {% data variables.product.prodname_ghe_server %} instance"](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance). +2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license. +{% data reusables.enterprise_installation.replica-steps %} +6. Connect to the replica appliance's IP address using SSH. ```shell $ ssh -p 122 admin@REPLICA IP ``` -7. Para generar un par de claves para la replicación, usa el comando `ghe-repl-setup` con la dirección IP del aparato principal y copia la clave pública que este devuelve. - ```shell - $ ghe-repl-setup PRIMARY IP - ``` +{% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} -9. Para verificar la conexión con la primaria y habilitar el modo de réplica para una nueva réplica, ejecuta nuevamente `ghe-repl-setup`. +9. To verify the connection to the primary and enable replica mode for the new replica, run `ghe-repl-setup` again. ```shell $ ghe-repl-setup PRIMARY IP ``` {% data reusables.enterprise_installation.replication-command %} -11. Para verificar el estado de cada canal de replicación del almacén de datos, utiliza el comando `ghe-repl-status`. - ```shell - $ ghe-repl-status - ``` +{% data reusables.enterprise_installation.verify-replication-channel %} -## Crear réplicas de replicación geográfica +## Creating geo-replication replicas -Esta configuración de ejemplo utiliza una réplica primaria y dos réplicas, que se encuentran en tres regiones geográficas diferentes. Aunque los tres nodos pueden estar en redes diferentes, se necesitan todos los nodos para que sean accesibles desde todos los demás nodos. Como mínimo, los puertos administrativos requeridos deben estar abiertos para todos los demás nodos. Para obtener más información acerca de los requisitos de puerto, consulta "[Puertos de red](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)." +This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)." -1. Crea la primera réplica de la misma manera en que lo harías para una configuración de dos nodos estándar ejecutando `ghe-repl-setup` en la primera réplica. +1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica. ```shell (replica1)$ ghe-repl-setup PRIMARY IP (replica1)$ ghe-repl-start ``` -2. Crea una segunda réplica y utiliza el comando `ghe-repl-setup --add`. La marca `--add` evita que sobrescriba la configuración de la replicación existente y agrega la nueva réplica a la configuración. +2. Create a second replica and use the `ghe-repl-setup --add` command. The `--add` flag prevents it from overwriting the existing replication configuration and adds the new replica to the configuration. ```shell (replica2)$ ghe-repl-setup --add PRIMARY IP (replica2)$ ghe-repl-start ``` -3. Predeterminadamente, las replicas se configuran en el mismo centro de datos, y ahora intentarán poblar los datos desde un nodo existente en el mismo centro de datos. Configura las réplicas para diferentes centros de datos estableciendo un valor diferente para la opción de centro de datos. Los valores específicos pueden ser los que tú quieras, siempre que sean diferentes entre sí. Ejecuta el comando `ghe-repl-node` en cada nodo y especifica el centro de datos. +3. By default, replicas are configured to the same datacenter, and will now attempt to seed from an existing node in the same datacenter. Configure the replicas for different datacenters by setting a different value for the datacenter option. The specific values can be anything you would like as long as they are different from each other. Run the `ghe-repl-node` command on each node and specify the datacenter. - En la primaria: + On the primary: ```shell (primary)$ ghe-repl-node --datacenter [PRIMARY DC NAME] ``` - En la primera réplica: + On the first replica: ```shell (replica1)$ ghe-repl-node --datacenter [FIRST REPLICA DC NAME] ``` - En la segunda réplica: + On the second replica: ```shell (replica2)$ ghe-repl-node --datacenter [SECOND REPLICA DC NAME] ``` {% tip %} - **Consejo:** puedes establecer las opciones `--datacenter` y `--active` al mismo tiempo. + **Tip:** You can set the `--datacenter` and `--active` options at the same time. {% endtip %} -4. Un nodo de réplica activo almacenará copias de los datos del aparato y responderá las solicitudes de usuario final. Un nodo inactivo almacenará copias de los datos del aparato, pero no podrá atender las solicitudes de usuario final. Habilita el modo activo usando la marca `--active` o el modo inactivo usando la marca `--inactive`. +4. An active replica node will store copies of the appliance data and service end user requests. An inactive node will store copies of the appliance data but will be unable to service end user requests. Enable active mode using the `--active` flag or inactive mode using the `--inactive` flag. - En la primera réplica: + On the first replica: ```shell (replica1)$ ghe-repl-node --active ``` - En la segunda réplica: + On the second replica: ```shell (replica2)$ ghe-repl-node --active ``` -5. Para aplicar la configuración, usa el comando `ghe-config-apply` en el principal. +5. To apply the configuration, use the `ghe-config-apply` command on the primary. ```shell (primary)$ ghe-config-apply ``` -## Configurar el DNS para replicación geográfica +## Configuring DNS for geo-replication -Configurar Geo DNS usando las direcciones IP de los nodos primarios y réplica. También puedes crear un DNS CNAME para el nodo principal (p. ej., `primary.github.example.com`) para acceder al nodo principal a través de SSH o hacerle una copia de seguridad a través de `backup-utils`. +Configure Geo DNS using the IP addresses of the primary and replica nodes. You can also create a DNS CNAME for the primary node (e.g. `primary.github.example.com`) to access the primary node via SSH or to back it up via `backup-utils`. -Para probarlo, puedes agregar entradas al archivo de `hosts` de la estación de trabajo local (por ejemplo, `/etc/hosts`). Estas entradas de ejemplo resolverán las solicitudes de `HOSTNAME` para `replica2`. Puedes apuntar a hosts específicos comentando en diferentes líneas. +For testing, you can add entries to the local workstation's `hosts` file (for example, `/etc/hosts`). These example entries will resolve requests for `HOSTNAME` to `replica2`. You can target specific hosts by commenting out different lines. ``` # HOSTNAME @@ -104,8 +94,8 @@ Para probarlo, puedes agregar entradas al archivo de `hosts` de la estación de HOSTNAME ``` -## Leer más +## Further reading -- "[Acerca de la configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)" -- "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" -- "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)" +- "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)" +- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" +- "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)" diff --git a/translations/es-ES/content/admin/enterprise-management/index.md b/translations/es-ES/content/admin/enterprise-management/index.md index 206c825144..176730b8e5 100644 --- a/translations/es-ES/content/admin/enterprise-management/index.md +++ b/translations/es-ES/content/admin/enterprise-management/index.md @@ -1,6 +1,6 @@ --- -title: 'Monitorear, administrar y actualizar tu empresa' -intro: 'Puedes monitorear tu aplicativo, mejorar a una versión nueva y configurar el agrupamiento o la disponibilidad alta' +title: 'Monitoring, managing, and updating your enterprise' +intro: 'You can monitor your appliance, upgrade to a newer version, and configure clustering or high availability' redirect_from: - /enterprise/admin/enterprise-management versions: @@ -12,6 +12,7 @@ children: - /updating-the-virtual-machine-and-physical-resources - /configuring-clustering - /configuring-high-availability -shortTitle: 'Monitorear, administrar & actualizar' + - /caching-repositories +shortTitle: 'Monitor, manage & update' --- diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 1b5a3b5b4f..865966574d 100644 --- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -1,6 +1,6 @@ --- -title: Actualizar el servidor de GitHub Enterprise -intro: 'Actualizar el {% data variables.product.prodname_ghe_server %} para obtener las funciones y las actualizaciones de seguridad más recientes.' +title: Upgrading GitHub Enterprise Server +intro: 'Upgrade {% data variables.product.prodname_ghe_server %} to get the latest features and security updates.' redirect_from: - /enterprise/admin/installation/upgrading-github-enterprise-server - /enterprise/admin/articles/upgrading-to-the-latest-release/ @@ -20,220 +20,218 @@ type: how_to topics: - Enterprise - Upgrades -shortTitle: Mejorar el GHES +shortTitle: Upgrading GHES --- +## Preparing to upgrade -## Preparar para una actualización - -1. Determina una estrategia de actualización y elige una versión a la que actualizar. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." -3. Crea una copia de seguridad nueva de tu instancia principal con las {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta el archivo README.md en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). -4. Si estás actualizando con un paquete de actualización, programa una ventana de mantenimiento para los usuarios finales del {% data variables.product.prodname_ghe_server %}. Si estás usando un hotpatch, no se necesita el modo mantenimiento. +1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." +3. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). +4. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required. {% note %} - **Nota:** la ventana de mantenimiento depende del tipo de actualización que realices. Las actualizaciones que utilizan un hotpatch por lo general no necesitan una ventana de mantenimiento. A veces se necesita reiniciar; puedes hacerlo más tarde. Siguiendo el esquema de control de versiones de MAJOR.FEATURE.PATCH, los lanzamientos de patch que utilizan un paquete de actualización normalmente necesitan menos de cinco minutos de tiempo de inactividad. Los lanzamientos de funciones que incluyen migraciones de datos toman más tiempo dependiendo del desempeño del almacenamiento y de la cantidad de datos que se migran. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} {% data reusables.enterprise_installation.upgrade-hardware-requirements %} -## Tomar una instantánea +## Taking a snapshot -Una instantánea es un punto de verificación de una máquina virtual (VM) en un momento en el tiempo. Recomendamos firmemente tomar una instantánea antes de actualizar tu máquina virtual para que si falla una actualización, puedas revertir tu VM nuevamente a la instantánea. Si no estás actualizando a un nuevo lanzamiento de característica, debes tomar una instantánea de VM. Si estás actualizando a un nuevo lanzamiento de patch, puedes adjuntar el disco de datos existente. +A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk. -Hay dos tipos de instantáneas: +There are two types of snapshots: -- **Las instantáneas de VM** guardan el estado completo de tu VM, incluidos los datos del usuario y los datos de configuración. Este método de instantáneas requiere una gran cantidad de espacio de disco e insume mucho tiempo. -- **Las instantáneas de disco de datos** únicamente guardan tus datos de usuario. +- **VM snapshots** save your entire VM state, including user data and configuration data. This snapshot method requires a large amount of disk space and is time consuming. +- **Data disk snapshots** only save your user data. {% note %} - **Notas:** - - Algunas plataformas no permiten que tomes una instantánea solo de tu disco de datos. Para estas plataformas, necesitarás tomar una instantánea de tu VM completa. - - Si tu hipervisor no admite instantáneas de VM completas, debes tomar una instantánea de tu disco raíz y de tu disco de datos en rápida sucesión. + **Notes:** + - Some platforms don't allow you to take a snapshot of just your data disk. For these platforms, you'll need to take a snapshot of the entire VM. + - If your hypervisor does not support full VM snapshots, you should take a snapshot of the root disk and data disk in quick succession. {% endnote %} -| Plataforma | Método de instantánea | URL de documentación de instantánea | -| --------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Amazon AWS | Disco | | -| Azure | VM | | -| Hyper-V | VM | | -| Google Compute Engine | Disco | | -| VMware | VM | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) | -| XenServer | VM | | +| Platform | Snapshot method | Snapshot documentation URL | +|---|---|---| +| Amazon AWS | Disk | +| Azure | VM | +| Hyper-V | VM | +| Google Compute Engine | Disk | +| VMware | VM | {% ifversion ghes < 3.3 %} +| XenServer | VM | {% endif %} -## Actualizar con un hotpatch +## Upgrading with a hotpatch -{% data reusables.enterprise_installation.hotpatching-explanation %} Utilizando la {% data variables.enterprise.management_console %}, puedes instalar un hotpatch de forma inmediata o programar la instalación para más tarde. Puedes utilizar el shell administrativo para instalar un hotpatch con la herramienta `ghe-upgrade`. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." +{% data reusables.enterprise_installation.hotpatching-explanation %} Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." {% note %} -**{% ifversion ghes %}Notas{% else %}Nota{% endif %}**: +**{% ifversion ghes %}Notes{% else %}Note{% endif %}**: {% ifversion ghes %} -- Si {% data variables.product.product_location %} está ejecutando una compilación candidata a lanzamiento, no puedes actualizarla con un hotpatch. +- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. -- {% endif %}No hay disponibilidad para instalar un parche utilizando la {% data variables.enterprise.management_console %} en los ambientes de clúster. Para instalar un parche en un entorno de agrupación, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." +- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." {% endnote %} -### Actualizar un aparato único con un hotpatch +### Upgrading a single appliance with a hotpatch -#### Instalar un hotpatch utilizando la {% data variables.enterprise.management_console %} +#### Installing a hotpatch using the {% data variables.enterprise.management_console %} -1. Habilitar actualizaciones automáticas. Para obtener más información, consulta "[Habilitar actualizaciones automáticas](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." +1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)." {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.updates-tab %} -4. Cuando se ha descargado un nuevo hotpatch, utiliza el menú desplegable del paquete de instalación: - - Para instalar de forma inmediata, selecciona **Now (Ahora)**: - - Para instalarlo más tarde, selecciona una fecha posterior. ![Menú desplegable de fecha de instalación de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png) -5. Da clic en **Instalar**. ![Botón de instalación de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png) +4. When a new hotpatch has been downloaded, use the Install package drop-down menu: + - To install immediately, select **Now**: + - To install later, select a later date. + ![Hotpatch installation date dropdown](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png) +5. Click **Install**. + ![Hotpatch install button](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png) -#### Instalar un hotpatch utilizando un shell administrativo +#### Installing a hotpatch using the administrative shell {% data reusables.enterprise_installation.download-note %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copia el URL para obtener el paquete de actualización (*.hpkg* file). +2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copy the URL for the upgrade hotpackage (*.hpkg* file). {% data reusables.enterprise_installation.download-package %} -4. Ejecuta el comando `ghe-upgrade` utilizando el nombre del archivo del paquete: +4. Run the `ghe-upgrade` command using the package file name: ```shell admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg *** verifying upgrade package signature... ``` -5. Si se requiere un reinicio para las actualizaciones de kernel, MySQL, Elasticsearch u otros programas, el script de actualización de hotpatch te avisa. +5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you. -### Actualizar un aparato que tiene instancias de réplica utilizando un hotpatch +### Upgrading an appliance that has replica instances using a hotpatch {% note %} -**Nota**: si estás instalando un hotpatch, no necesitas entrar en modo de mantenimiento o detener la replicación. +**Note**: If you are installing a hotpatch, you do not need to enter maintenance mode or stop replication. {% endnote %} -Los aparatos configurados para alta disponibilidad y de replicación geográfica utilizan instancias de réplica además de las instancias principales. Para actualizar estos aparatos, necesitarás actualizar tanto la instancia principal y todas las instancias de réplica, una a la vez. +Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time. -#### Actualizar la instancia principal +#### Upgrading the primary instance -1. Actualiza la instancia principal siguiendo las instrucciones en "[Instalar un hotpatch utilizando el shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)." +1. Upgrade the primary instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." -#### Actualizar una instancia de réplica +#### Upgrading a replica instance {% note %} -**Nota:** si estás ejecutando múltiples instancias de réplica como parte de la replicación geográfica, repite este procedimiento para cada instancia de réplica, una a la vez. +**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time. {% endnote %} -1. Mejora la instancia de répica siguiendo las instrucciones en "[Instalar un hotpatch utilizando el shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)". Si estás utilizando varias replicas para la replicación geográfica, deberás repetir este procedimiento para actualizar cada réplica una a la vez. +1. Upgrade the replica instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time. {% data reusables.enterprise_installation.replica-ssh %} {% data reusables.enterprise_installation.replica-verify %} -## Actualizar con un paquete de actualización +## Upgrading with an upgrade package -Al mismo tiempo que puedes utilizar un hotpatch para actualizar al lanzamiento de patch más reciente dentro de una serie de características, debes utilizar un paquete de actualización para actualizar a un lanzamiento de característica más nuevo. Por ejemplo para actualizar de `2.11.10` a `2.12.4` debes utilizar un paquete de actualización ya que están en series de características diferentes. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." +While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." -### Actualizar un aparato único con un paquete de actualización +### Upgrading a single appliance with an upgrade package {% data reusables.enterprise_installation.download-note %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Selecciona la plataforma adecuada y copia el URL para obtener el paquete de actualización (*.pkg* file). +2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Select the appropriate platform and copy the URL for the upgrade package (*.pkg* file). {% data reusables.enterprise_installation.download-package %} -4. Habilita el modo mantenimiento y espera que se completen todos los procesos activos en la instancia del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% note %} - **Nota**: cuando se actualiza el aparato primario en una configuración de alta disponibilidad, el aparato debería estar ya en modo mantenimiento si estás siguiendo las instrucciones en "[Actualizar la instancia primaria](#upgrading-the-primary-instance)." + **Note**: When upgrading the primary appliance in a High Availability configuration, the appliance should already be in maintenance mode if you are following the instructions in "[Upgrading the primary instance](#upgrading-the-primary-instance)." {% endnote %} -5. Ejecuta el comando `ghe-upgrade` utilizando el nombre del archivo del paquete: +5. Run the `ghe-upgrade` command using the package file name: ```shell admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg *** verifying upgrade package signature... ``` -6. Confirma que te gustaría continuar con la actualización y reinicia después de que se verifique la firma del paquete. El nuevo sistema de archivos raíz escribe en la segunda partición y la instancia de forma automática se reinicia en modo mantenimiento: +6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode: ```shell - *** aplicando actualización... + *** applying update... This package will upgrade your installation to version version-number Current root partition: /dev/xvda1 [version-number] Target root partition: /dev/xvda2 - Proceed with installation? [s/N] + Proceed with installation? [y/N] ``` -7. Para las actualizaciones de aparato único, deshabilita el modo mantenimiento para que los usuarios puedan utilizar {% data variables.product.product_location %}. +7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.product.product_location %}. {% note %} - **Nota**: cuando se actualizan aparatos en configuración de alta disponibilidad, deberías mantener el modo mantenimiento hasta que hayas actualizado todas las réplicas y la replicación esté en curso. Para obtener más información, consulta "[Actualizar una instancia de réplica](#upgrading-a-replica-instance)." + **Note**: When upgrading appliances in a High Availability configuration you should remain in maintenance mode until you have upgraded all of the replicas and replication is current. For more information, see "[Upgrading a replica instance](#upgrading-a-replica-instance)." {% endnote %} -### Actualizar un aparato que tiene instancias de réplica utilizando un paquete de actualización +### Upgrading an appliance that has replica instances using an upgrade package -Los aparatos configurados para alta disponibilidad y de replicación geográfica utilizan instancias de réplica además de las instancias principales. Para actualizar estos aparatos, necesitarás actualizar tanto la instancia principal y todas las instancias de réplica, una a la vez. +Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time. -#### Actualizar la instancia principal +#### Upgrading the primary instance {% warning %} -**Advertencia:** Cuando se detiene una replicación, si falla la primaria, se perderá cualquier trabajo que se realice antes de que la réplica esté actualizada y comience nuevamente la replicación. +**Warning:** When replication is stopped, if the primary fails, any work that is done before the replica is upgraded and the replication begins again will be lost. {% endwarning %} -1. En la instancia primaria, habilita el modo mantenimiento y espera a que se completen todos los procesos activos. Para obtener más información, consulta "[Habilitar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." +1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." {% data reusables.enterprise_installation.replica-ssh %} -3. En la instancia de réplica, o en todas las instancias de réplica si estás ejecutando múltiples instancias de réplica como parte de una replicación geográfica, ejecuta `ghe-repl-stop` para detener la replicación. -4. Actualiza la instancia primaria siguiendo las instrucciones en "[Actualizar un aparato único con un paquete de actualización](#upgrading-a-single-appliance-with-an-upgrade-package)." +3. On the replica instance, or on all replica instances if you're running multiple replica instances as part of geo-replication, run `ghe-repl-stop` to stop replication. +4. Upgrade the primary instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." -#### Actualizar una instancia de réplica +#### Upgrading a replica instance {% note %} -**Nota:** si estás ejecutando múltiples instancias de réplica como parte de la replicación geográfica, repite este procedimiento para cada instancia de réplica, una a la vez. +**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time. {% endnote %} -1. Actualiza la instancia de la réplica siguiendo las instrucciones en la sección "[Mejorar un solo aplicativo con un paquete de mejora](#upgrading-a-single-appliance-with-an-upgrade-package)". Si estás utilizando varias replicas para la replicación geográfica, deberás repetir este procedimiento para actualizar cada réplica una a la vez. +1. Upgrade the replica instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time. {% data reusables.enterprise_installation.replica-ssh %} {% data reusables.enterprise_installation.replica-verify %} {% data reusables.enterprise_installation.start-replication %} -{% data reusables.enterprise_installation.replication-status %} Si el comando devuelve `La replicación no se está ejecutando`, la replicación puede estar comenzando. Espera alrededor de un minuto antes de volver a ejecutar `ghe-repl-status`. +{% data reusables.enterprise_installation.replication-status %} If the command returns `Replication is not running`, the replication may still be starting. Wait about one minute before running `ghe-repl-status` again. {% note %} - **Nota:** mientras la resincronización está en progreso, `ghe-repl-status` puede devolver mensajes esperados que indiquen que la replicación está de forma subyacente. - Por ejemplo: `CRITICO: la replicación de git está de forma subyacente de la primaria por más de 1007 repositorios o gists` + **Note:** While the resync is in progress `ghe-repl-status` may return expected messages indicating that replication is behind. + For example: `CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists` {% endnote %} - Si `ghe-repl-status` no devuelve `OK`, sigue los pasos de abajo para iniciar la replicación de forma manual. + If `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." + +6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.product.product_location %}. - 1. En la instancia de réplica, ejecuta nuevamente `ghe-repl-setup `. - {% data reusables.enterprise_installation.start-replication %} - {% data reusables.enterprise_installation.replication-status %} -6. Cuando hayas completado la actualización de la última réplica, y se haya completado la resincronización, deshabilita el modo mantenimiento para que los usuarios puedan utilizar {% data variables.product.product_location %}. +## Restoring from a failed upgrade -## Restaurar desde una actualización fallida +If an upgrade fails or is interrupted, you should revert your instance back to its previous state. The process for completing this depends on the type of upgrade. -Si una actualización falla o se interrumpe, deberías revertir tu instancia a su estado anterior. El proceso para completar esto depende del tipo de actualización. +### Rolling back a patch release -### Revertir un lanzamiento de patch +To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} -Para volver a lanzar una versión de parche, usa el comando `ghe-upgrade` con el comando `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} +For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)." -Para obtener más información, consulta "[Herramientas de línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)." +### Rolling back a feature release -### Revertir un lanzamiento de característica - -Para revertir un lanzamiento de característica, restaura desde una instantánea de VM para garantizar que las particiones raíz y de datos estén en un estado consistente. Para obtener más información, consulta "[Tomar una instantánea](#taking-a-snapshot)." +To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)." {% ifversion ghes %} -## Leer más +## Further reading -- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" {% endif %} diff --git a/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md b/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md index 2137e6d00b..c13b7e3a23 100644 --- a/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md +++ b/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md @@ -1,6 +1,6 @@ --- -title: Acerca del soporte de GitHub Enterprise -intro: '{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas que se presenten en {% data variables.product.product_name %}.' +title: About GitHub Enterprise Support +intro: '{% data variables.contact.github_support %} can help you troubleshoot issues that arise on {% data variables.product.product_name %}.' redirect_from: - /enterprise/admin/enterprise-support/about-github-enterprise-support - /admin/enterprise-support/about-github-enterprise-support @@ -11,84 +11,83 @@ type: overview topics: - Enterprise - Support -shortTitle: Soporte para GitHub Enterprise +shortTitle: GitHub Enterprise Support --- - {% note %} -**Nota**: {% data reusables.support.data-protection-and-privacy %} +**Note**: {% data reusables.support.data-protection-and-privacy %} {% endnote %} -## Acerca de {% data variables.contact.enterprise_support %} +## About {% data variables.contact.enterprise_support %} -{% data variables.product.product_name %} incluye {% data variables.contact.enterprise_support %} en inglés{% ifversion ghes %} y japonés{% endif %}. +{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% ifversion ghes %} and Japanese{% endif %}. {% ifversion ghes %} -Puedes contactar al {% data variables.contact.enterprise_support %} a través del {% data variables.contact.contact_enterprise_portal %} para obtener ayuda con: - - Instalar y usar {% data variables.product.product_name %} - - Inspeccionar y verificar las causas de errores sospechados +You can contact {% data variables.contact.enterprise_support %} through {% data variables.contact.contact_enterprise_portal %} for help with: + - Installing and using {% data variables.product.product_name %} + - Identifying and verifying the causes of suspected errors -Adicionalmente a los beneficios de {% data variables.contact.enterprise_support %}, el soporte de {% data variables.contact.premium_support %} para {% data variables.product.product_name %} te ofrece: - - Soporte técnico por escrito a través del portal de soporte de 24 horas por día, los 7 días de la semana - - Soporte técnico telefónico las 24 horas del día, los 7 días de la semana - - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados. - - Ingenieros de Confianza para el Cliente - - Acceso a contenido prémium. - - Revisiones de estado programadas. - - Horas administrativas administradas +In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} support for {% data variables.product.product_name %} offers: + - Written support through our support portal 24 hours per day, 7 days per week + - Phone support 24 hours per day, 7 days per week + - A Service Level Agreement (SLA) with guaranteed initial response times + - Customer Reliability Engineers + - Access to premium content + - Scheduled health checks + - Managed Admin hours {% endif %} {% ifversion ghes %} -Para obtener más información, consulta "[Acerca de{% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". +For more information, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)." {% endif %} {% data reusables.support.scope-of-support %} -## Ponerte en contacto con {% data variables.contact.enterprise_support %} +## Contacting {% data variables.contact.enterprise_support %} {% ifversion ghes %} -{% data reusables.support.zendesk-deprecation %} +{% data reusables.support.zendesk-old-tickets %} {% endif %} -Puedes contactar a {% data variables.contact.enterprise_support %} a través del {% ifversion ghes %}{% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} del {% data variables.contact.ae_azure_portal %}{% endif %} para reportar los problemas por escrito. Para obtener más información, consulta la sección "[Recibir ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". +You can contact {% data variables.contact.enterprise_support %} through {% ifversion ghes %}{% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} the {% data variables.contact.ae_azure_portal %}{% endif %} to report issues in writing. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." {% ifversion ghes %} -## Horas de operación +## Hours of operation -### Soporte en inglés +### Support in English -Para cuestiones estándar no urgentes, ofrecemos soporte en inglés las 24 horas del día, 5 días a la semana, excepto fines de semana y feriados nacionales de EE.UU. El tiempo de respuesta estándar es 24 horas. +For standard non-urgent issues, we offer support in English 24 hours per day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 24 hours. -Para asuntos urgentes, estamos disponibles las 24 horas del día, 7 días a la semana, incluso en días feriados de EE.UU. +For urgent issues, we are available 24 hours per day, 7 days per week, even during national U.S. holidays. -### Soporte en japonés +### Support in Japanese -Para cuestiones no urgentes, el soporte en japonés se encuentra disponible de lunes a viernes, de 9:00 a.m. a 5:00 p.m. (hora estándar en Japón), excepto los feriados nacionales en Japón. Para cuestiones urgentes, ofrecemos apoyo en inglés 24 horas al día, 7 días por semana, incluso durante las vacaciones nacionales de EE.UU. +For non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays. -Para obtener una lista de los días feriados nacionales de EE. UU. Para conocer una lista de los feriados nacionales de EE. UU. y Japón observados por {% data variables.contact.enterprise_support %}, consulta el [Cronograma de feriados](#holiday-schedules)". +For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)." -## Cronograma de feriados +## Holiday schedules -Para asuntos urgentes, podemos ofrecerte ayudaeninglés 24 horas al día, 7 días por semana, incluyendo los días feriados de EE.UU. y Japón. +For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. and Japanese holidays. -### Feriados en los Estados Unidos +### Holidays in the United States -{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. {{ site.data.variables.contact.enterprise_support }} respeta estos días feriados en los EE.UU, aunque nuestro equipo de soporte global se encuentra disponible para atender tickets urgentes. +{% data variables.contact.enterprise_support %} observes these U.S. holidays, although our global support team is available to answer urgent tickets. {% data reusables.enterprise_enterprise_support.support-holiday-availability %} -### Feriados en Japón +### Holidays in Japan -{% data variables.contact.enterprise_support %} no proporciona soporte en idioma japonés desde el 28 de diciembre hasta el 3 de enero, así como en los días feriados listados en [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html). +{% data variables.contact.enterprise_support %} does not provide Japanese-language support on December 28th through January 3rd as well as on the holidays listed in [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html). {% data reusables.enterprise_enterprise_support.installing-releases %} {% endif %} -## Asignar una prioridad a un ticket de soporte +## Assigning a priority to a support ticket -Cuando contactas a {% data variables.contact.enterprise_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. +When you contact {% data variables.contact.enterprise_support %}, you can choose one of four priorities for the ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. {% data reusables.support.github-can-modify-ticket-priority %} @@ -98,14 +97,14 @@ Cuando contactas a {% data variables.contact.enterprise_support %}, puedes escog {% data reusables.support.ghae-priorities %} {% endif %} -## Resolver y cerrar tickets de soporte +## Resolving and closing support tickets {% data reusables.support.enterprise-resolving-and-closing-tickets %} -## Leer más +## Further reading {% ifversion ghes %} -- Sección 10 sobre soporte en el "[Acuerdo de licencia de {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/license)"{% endif %} -- "[recibir ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% ifversion ghes %} -- "[Prepararse para emitir un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} -- [Enviar un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)" +- Section 10 on Support in the "[{% data variables.product.prodname_ghe_server %} License Agreement](https://enterprise.github.com/license)"{% endif %} +- "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% ifversion ghes %} +- "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} +- "[Submitting a ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)" diff --git a/translations/es-ES/content/admin/enterprise-support/overview/about-support-for-advanced-security.md b/translations/es-ES/content/admin/enterprise-support/overview/about-support-for-advanced-security.md index 925dbe5be1..5260f23fe3 100644 --- a/translations/es-ES/content/admin/enterprise-support/overview/about-support-for-advanced-security.md +++ b/translations/es-ES/content/admin/enterprise-support/overview/about-support-for-advanced-security.md @@ -1,6 +1,6 @@ --- -title: Acerca del soporte para Advanced Security -intro: '{% data variables.contact.enterprise_support %} puede ayudarte a solucionar problemas que encuentras mientras usas {% data variables.product.prodname_advanced_security %}.' +title: About support for Advanced Security +intro: '{% data variables.contact.enterprise_support %} can help you troubleshoot issues you run into while using {% data variables.product.prodname_advanced_security %}.' redirect_from: - /enterprise/admin/enterprise-support/about-support-for-advanced-security - /admin/enterprise-support/about-support-for-advanced-security @@ -10,68 +10,67 @@ type: overview topics: - Enterprise - Support -shortTitle: Compatibilidad con la Seguridad Avanzada +shortTitle: Support for Advanced Security --- - {% note %} -**Nota**: {% data reusables.support.data-protection-and-privacy %} +**Note**: {% data reusables.support.data-protection-and-privacy %} {% endnote %} -## Acerca del soporte para {% data variables.product.prodname_advanced_security %} +## About support for {% data variables.product.prodname_advanced_security %} -{% data variables.product.prodname_advanced_security %} incluye {% data variables.contact.enterprise_support %} en inglés, por correo electrónico. +{% data variables.product.prodname_advanced_security %} includes {% data variables.contact.enterprise_support %} in English, by email. -## Alcance del soporte técnico +## Scope of support -Si tu solicitud de soporte técnico está fuera del alcance de lo que puede hacer nuestro equipo para ayudarte, podemos recomendarte los siguientes pasos para resolver el problema por fuera del {% data variables.contact.enterprise_support %}. Es probable que tu solicitud de soporte técnico esté fuera del alcance del {% data variables.contact.enterprise_support %} si se trata principalmente de lo siguiente: -- Integraciones de terceros -- Configuración del hardware -- Configuración de sistemas externos -- Proyectos de código abierto -- Creando proyectos o repositorios -- Diseño de cluster LGTM -- Crear o depurar el código de nuevas consultas para {% data variables.product.prodname_codeql %} +If your support request is outside of the scope of what our team can help you with, we may recommend next steps to resolve your issue outside of {% data variables.contact.enterprise_support %}. Your support request is possibly out of {% data variables.contact.enterprise_support %}'s scope if it's primarily about: +- Third party integrations +- Hardware setup +- Configuration of external systems +- Open source projects +- Building projects or repositories +- LGTM cluster design +- Writing or debugging new queries for {% data variables.product.prodname_codeql %} -Si no estás seguro de si el problema está fuera de nuestro alcance, abre un ticket y nos complacerá ayudarte a determinar la mejor manera de continuar. +If you're uncertain if the issue is out of scope, open a ticket and we're happy to help you determine the best way to proceed. -## Ponerte en contacto con {% data variables.contact.enterprise_support %} +## Contacting {% data variables.contact.enterprise_support %} -{% data reusables.support.zendesk-deprecation %} +{% data reusables.support.zendesk-old-tickets %} -Puedes ponerte en contacto con {% data variables.contact.enterprise_support %} a través de {% data variables.contact.contact_enterprise_portal %} para obtener ayuda: -- Instalar y usar {% data variables.product.prodname_advanced_security %} -- Identificar y verificar las causas de los errores soportados +You can contact {% data variables.contact.enterprise_support %} through the {% data variables.contact.contact_enterprise_portal %} for help with: +- Installing and using {% data variables.product.prodname_advanced_security %} +- Identifying and verifying the causes of supported errors -## Horas de operación +## Hours of operation -Ofrecemos soporte para {% data variables.product.prodname_advanced_security %} en Inglés 24 horas al día, 5 días a la semana, excluyendo fines de semana y días festivos en Estados Unidos. EE.UU. El tiempo de respuesta estándar es de 1 día hábil. +We offer support for {% data variables.product.prodname_advanced_security %} in English 24 hours per day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 1 business day. -## Cronograma de feriados +## Holiday schedule -{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. EE.UU. +{% data variables.contact.enterprise_support %} observes these U.S. holidays. {% data reusables.enterprise_enterprise_support.support-holiday-availability %} -## Instalando actualizaciones de {% data variables.product.prodname_advanced_security %} +## Installing {% data variables.product.prodname_advanced_security %} updates -Para asegurarse de que su instancia {% data variables.product.prodname_advanced_security %} es estable, debe instalar e implementar nuevas versiones cuando estén disponibles. Esto asegura que tengas las últimas características, modificaciones y mejoras así como cualquier actualización de las características, correcciones de código, parches u otras actualizaciones generales y correcciones para {% data variables.product.prodname_advanced_security %}. +To ensure that your {% data variables.product.prodname_advanced_security %} instance is stable, you must install and implement new releases when they are made available. This ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches, or other general updates and fixes to {% data variables.product.prodname_advanced_security %}. -## Asignar una prioridad a un ticket de soporte +## Assigning a priority to a support ticket -Cuando contactas a {% data variables.contact.enterprise_support %} para obtener ayuda con {% data variables.product.prodname_advanced_security %}, puedes escoger una de tres prioridades para el ticket: {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. +When you contact {% data variables.contact.enterprise_support %} for help with {% data variables.product.prodname_advanced_security %}, you can choose one of three priorities for the ticket: {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. {% data reusables.support.github-can-modify-ticket-priority %} -| Prioridad | Descripción | -|:-------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_advanced_security %} no funciona o se detiene o se ve gravemente afectado de tal manera que el usuario final no puede seguir utilizando el software razonablemente y no hay solución disponible para solucionar el problema. | -| {% data variables.product.support_ticket_priority_normal %} | {% data variables.product.prodname_advanced_security %} está funcionando de forma inconsistente, lo que provoca un deterioro de la productividad y el uso del usuario final. | -| {% data variables.product.support_ticket_priority_low %} | {% data variables.product.prodname_advanced_security %} funciona consistentemente, pero el usuario final solicita cambios menores en el software, tales como actualizaciones de documentación, defectos cosméticos o mejoras. | +| Priority | Description | +| :---: | --- | +| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_advanced_security %} is not functioning or is stopped or severely impacted such that the end user cannot reasonably continue use of the software and no workaround is available. | +| {% data variables.product.support_ticket_priority_normal %} | {% data variables.product.prodname_advanced_security %} is functioning inconsistently, causing impaired end user usage and productivity. | +| {% data variables.product.support_ticket_priority_low %} | {% data variables.product.prodname_advanced_security %} is functioning consistently, but the end user requests minor changes in the software, such as documentation updates, cosmetic defects, or enhancements.| -## Resolver y cerrar tickets de soporte +## Resolving and closing support tickets {% data reusables.support.enterprise-resolving-and-closing-tickets %} diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md index c5cc5fe957..70b1836838 100644 --- a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md +++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md @@ -1,6 +1,6 @@ --- -title: Obtener soporte de GitHub -intro: 'Contacta a {% data variables.contact.enterprise_support %} utilizando la {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} o {% endif %} el portal de soporte.' +title: Reaching GitHub Support +intro: 'Contact {% data variables.contact.enterprise_support %} using the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.' redirect_from: - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/ - /enterprise/admin/enterprise-support/reaching-github-support @@ -12,49 +12,47 @@ topics: - Enterprise - Support --- +## Using automated ticketing systems -## Usar sistemas de tickets automatizado +Though we'll do our best to respond to automated support requests, we typically need more information than an automated ticketing system can give us to solve your issue. Whenever possible, please initiate support requests from a person or machine that {% data variables.contact.enterprise_support %} can interact with. For more information, see "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)." -Si bien haremos todo lo mejor por responder a solicitudes de soporte automatizado, habitualmente necesitamos más información que un sistema de tickets automatizado que nos permita resolver tu problema. Siempre que sea posible, inicia las solicitudes de soporte de una persona o una máquina con la que {% data variables.contact.enterprise_support %} pueda interactuar. Para obtener más información, consulta "[Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". +## Contacting {% data variables.contact.enterprise_support %} -## Ponerte en contacto con {% data variables.contact.enterprise_support %} +{% data reusables.support.zendesk-old-tickets %} -{% data reusables.support.zendesk-deprecation %} - -Los clientes de {% data variables.contact.enterprise_support %} pueden abrir un ticket de soporte utilizando la {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} o el {% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} el {% data variables.contact.contact_ae_portal %}{% endif %}. Marca la prioridad del ticket como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. Para obtener más información, consulta la sección "[Asignar una prioridad al ticket de soporte](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)" y "[Emitir un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". - -## Ponerte en contacto con {% data variables.contact.enterprise_support %} +{% data variables.contact.enterprise_support %} customers can open a support ticket using the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} the {% data variables.contact.contact_ae_portal %}{% endif %}. For more information, see "[Submitting a ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)." {% ifversion ghes %} -### Ver tickets de soporte anteriores -Puedes usar el {% data variables.contact.enterprise_portal %} para ver tickets de soporte anteriores. +## Contacting {% data variables.contact.premium_support %} -1. Navegar por el {% data variables.contact.contact_enterprise_portal %}. -2. Da clic en **Mist tickets**. ![Ver los tickets emitidos anteriormente](/assets/images/enterprise/support/view-past-tickets.png) +{% data variables.contact.enterprise_support %} customers can open a support ticket using the {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}. Mark its priority as {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. For more information, see "[Assigning a priority to a support ticket](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server#assigning-a-priority-to-a-support-ticket)" and "[Submitting a ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)." -## Comunicarse con {% data variables.contact.premium_support %} +### Viewing past support tickets -Los clientes de {% data variables.contact.enterprise_support %} pueden abrir un ticket de soporte mediante {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o {% data variables.contact.contact_enterprise_portal %}. Marca su prioridad como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. Para obtener más información, consulta la sección "[Asignar una prioridad al ticket de soporte](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server#assigning-a-priority-to-a-support-ticket)" y "[Emitir un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". +You can use the {% data variables.contact.enterprise_portal %} to view past support tickets. + +1. Navigate to the {% data variables.contact.contact_enterprise_portal %}. +2. Click **My tickets**. {% endif %} -## Contacto de ventas +## Contacting sales -Para las preguntas relacionadas con precios, licenciamiento, renovaciones, cotizaciones, pagos y otras relacionadas, contacta a {% data variables.contact.contact_enterprise_sales %} o llama al [+1 (877) 448-4820](tel:+1-877-448-4820). +For pricing, licensing, renewals, quotes, payments, and other related questions, contact {% data variables.contact.contact_enterprise_sales %} or call [+1 (877) 448-4820](tel:+1-877-448-4820). {% ifversion ghes %} -## Contacto de capacitación +## Contacting training -Para conocer más sobre las opciones de capacitación, incluida la capacitación personalizada, consulta el sitio de capacitación de [{% data variables.product.company_short %}](https://services.github.com/). +To learn more about training options, including customized trainings, see [{% data variables.product.company_short %}'s training site](https://services.github.com/). {% note %} -**Nota:** La capacitación está incluida en el {% data variables.product.premium_plus_support_plan %}. Para obtener más información, consulta "[Acerca de{% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". +**Note:** Training is included in the {% data variables.product.premium_plus_support_plan %}. For more information, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)." {% endnote %} {% endif %} -## Leer más +## Further reading -- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" -- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". +- "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" +- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)." diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md index e7cd119ee0..71e3b2a771 100644 --- a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md +++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md @@ -1,6 +1,6 @@ --- -title: Envío de ticket -intro: 'Puedes emitir un ticket de soporte utilizando la {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o el portal de soporte {% elsif ghae %}{% data variables.contact.ae_azure_portal %}{% endif %}.' +title: Submitting a ticket +intro: 'You can submit a support ticket using {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the support portal{% elsif ghae %}{% data variables.contact.ae_azure_portal %}{% endif %}.' redirect_from: - /enterprise/admin/enterprise-support/submitting-a-ticket - /admin/enterprise-support/submitting-a-ticket @@ -12,76 +12,65 @@ topics: - Enterprise - Support --- - -## Acerca del envío de tickets +## About submitting a ticket {% ifversion ghae %} -Puedes emitir un ticket de soporte con {% data variables.product.prodname_ghe_managed %} desde el {% data variables.contact.ae_azure_portal %}. +You can submit a ticket for support with {% data variables.product.prodname_ghe_managed %} from the {% data variables.contact.ae_azure_portal %}. {% endif %} -Antes de enviar un ticket, deberías recopilar información útil para {% data variables.contact.github_support %} y elegir una persona de contacto. Para obtener más información, consulta "[Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". +Before submitting a ticket, you should gather helpful information for {% data variables.contact.github_support %} and choose a contact person. For more information, see "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)." {% ifversion ghes %} -Después de enviar una solicitud de soporte e información de diagnóstico opcional, {% data variables.contact.github_support %} puede solicitarte que descargues y compartas un paquete de soporte con nosotros. Para obtener más información, consulta "[Proporcionar datos a {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)". +After submitting your support request and optional diagnostic information, {% data variables.contact.github_support %} may ask you to download and share a support bundle with us. For more information, see "[Providing data to {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)." -## Emitir un ticket utilizando el {% data variables.contact.enterprise_portal %} +## Submitting a ticket using the {% data variables.contact.enterprise_portal %} -{% data reusables.support.zendesk-deprecation %} +{% data reusables.support.zendesk-old-tickets %} -1. Navegar por el {% data variables.contact.contact_enterprise_portal %}. -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} +To submit a ticket about {% data variables.product.product_location_enterprise %}, you must be an owner, billing manager, or member with support entitlement. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." -## Emitir un ticket utilizando tu cuenta empresarial +If you cannot sign in to your account on {% data variables.product.prodname_dotcom_the_website %} or do not have support entitlement, you can still submit a ticket by providing your license or a diagnostics file from your server. -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} -{% data reusables.enterprise-accounts.settings-tab %} -3. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) -4. Debajo de "Ayuda de {% data variables.product.prodname_enterprise %}", da clic en **Portal de {% data variables.contact.enterprise_support %}**. ![Enlace para navegar al sitio de soporte empresarial](/assets/images/enterprise/support/enterprise-support-link.png) -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} +1. Navigate to the {% data variables.contact.contact_support_portal %}. +{% data reusables.support.submit-a-ticket %} -## Enviar un ticket mediante el {% data variables.product.product_name %} {% data variables.enterprise.management_console %} +## Submitting a ticket using the {% data variables.product.product_name %} {% data variables.enterprise.management_console %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} {% data reusables.enterprise_management_console.support-link %} -5. Si deseas incluir los diagnósticos con tu ticket de soporte, en "Diagnostics" (Diagnóstico), haz clic en **Download diagnostic info** (Descargar información de diagnóstico) y guarda el archivo localmente. Adjuntarás este archivo a tu ticket de soporte posteriormente. ![Botón para descargar información de diagnóstico](/assets/images/enterprise/support/download-diagnostics-info-button.png) -6. En "Open Support Request" (Abrir solicitud de soporte", haz clic en **New support request** (Nueva solicitud de soporte). ![Botón para abrir una solicitud de soporte](/assets/images/enterprise/management-console/open-support-request.png) -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -14. Para incluir los diagnósticos con tu ticket de soporte, haz clic en **Add file** (Agregar archivo), luego adjunta el archivo de diagnóstico que descargaste. ![Añadir botón de archivo](/assets/images/enterprise/support/support-ticket-add-file.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} -7. Haz clic en **Submit** (enviar). +5. If you'd like to include diagnostics with your support ticket, Under "Diagnostics", click **Download diagnostic info** and save the file locally. You'll attach this file to your support ticket later. + ![Button to download diagnostics info](/assets/images/enterprise/support/download-diagnostics-info-button.png) +6. To complete your ticket and display the {% data variables.contact.enterprise_portal %}, under "Open Support Request", click **New support request**. + ![Button to open a support request](/assets/images/enterprise/management-console/open-support-request.png) +{% data reusables.support.submit-a-ticket %} {% endif %} {% ifversion ghae %} -## Prerrequisitos +## Prerequisites -Para emitir un ticket para {% data variables.product.prodname_ghe_managed %} en el {% data variables.contact.ae_azure_portal %}, debes proporcionar la ID para tu suscripción de {% data variables.product.prodname_ghe_managed %} en Azure a tu Administrador de Cuentas y Satisfacción del Cliente (CSAM, por sus siglas en inglés) en Microsoft. +To submit a ticket for {% data variables.product.prodname_ghe_managed %} in the {% data variables.contact.ae_azure_portal %}, you must provide the ID for your {% data variables.product.prodname_ghe_managed %} subscription in Azure to your Customer Success Account Manager (CSAM) at Microsoft. -## Enviar un ticket mediante el {% data variables.contact.ae_azure_portal %} +## Submitting a ticket using the {% data variables.contact.ae_azure_portal %} -Los clientes comerciales pueden emitir una solicitud de soporte en el {% data variables.contact.contact_ae_portal %}. Los clientes de gobierno deben utilizar el [portal de Azure para clientes de gobierno](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade). Para obtener más información, consulta la sección [Crear una solicitud de soporte de Azure](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) en los documentos de Microsoft. +Commercial customers can submit a support request in the {% data variables.contact.contact_ae_portal %}. Government customers should use the [Azure portal for government customers](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade). For more information, see [Create an Azure support request](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) in the Microsoft Docs. -## Solución de problemas en el {% data variables.contact.ae_azure_portal %} +## Troubleshooting problems in the {% data variables.contact.ae_azure_portal %} -{% data variables.product.company_short %} no puede solucionar los problemas de acceso y de suscripción en el portal de Azure. Para obtener ayuda con el protal de Azure, contacta a tu CSAM en Microsoft para revisar la siguiente información. +{% data variables.product.company_short %} is unable to troubleshoot access and subscription issues in the Azure portal. For help with the Azure portal, contact your CSAM at Microsoft or review the following information. -- Si no puedes iniciar sesión en el portal de Azure, consulta la sección [Solución de problemas para el inicio de sesión en las suscripciones de Azure](https://docs.microsoft.com/en-US/azure/cost-management-billing/manage/troubleshoot-sign-in-issue) en los Documentos de Microsoft o [envía una solicitud directamente](https://support.microsoft.com/en-us/supportrequestform/84faec50-2cbc-9b8a-6dc1-9dc40bf69178). +- If you cannot sign into the Azure portal, see [Troubleshoot Azure subscription sign-in issues](https://docs.microsoft.com/en-US/azure/cost-management-billing/manage/troubleshoot-sign-in-issue) in the Microsoft Docs or [submit a request directly](https://support.microsoft.com/en-us/supportrequestform/84faec50-2cbc-9b8a-6dc1-9dc40bf69178). -- Si puedes iniciar sesión en el portal de Azure, pero no puedes emitir un ticket para {% data variables.product.prodname_ghe_managed %}, revisa los prerequisitos para emitir un ticket. Para obtener más información, consulta la sección "[Prerrequisitos](#prerequisites)". +- If you can sign into the Azure portal but you cannot submit a ticket for {% data variables.product.prodname_ghe_managed %}, review the prerequisites for submitting a ticket. For more information, see "[Prerequisites](#prerequisites)". {% endif %} -## Leer más +## Further reading -- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% ifversion ghes %} -- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)".{% endif %} +- "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% ifversion ghes %} +- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)."{% endif %} diff --git a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md index ad45cb6627..3e1182668d 100644 --- a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Solucionar problemas en las GitHub Actions de tu empresa -intro: 'Solucionar problemas comunes que ocurren cuando se utilizan {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}.' +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' versions: ghes: '*' @@ -11,69 +11,68 @@ topics: - Troubleshooting redirect_from: - /admin/github-actions/troubleshooting-github-actions-for-your-enterprise -shortTitle: Solucionar problemas de las GitHub Actions +shortTitle: Troubleshoot GitHub Actions --- +## Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} -## Configurar los ejecutores auto-hospedados cuando utilizas un certificado auto-firmado para {% data variables.product.prodname_ghe_server %} +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." -{% data reusables.actions.enterprise-self-signed-cert %} Para obtener más información, consulta la sección "[Configurar TLS](/admin/configuration/configuring-tls)". +### Installing the certificate on the runner machine -### Instalar el certificado en la máquina ejecutora +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. -Para que un ejecutor auto-hospedado se conecte a {% data variables.product.prodname_ghe_server %} utilizando un certificado auto-firmado, debes instalarlo en la máquina ejecutora para que la seguridad de la conexión se fortalezca. +For the steps required to install a certificate, refer to the documentation for your runner's operating system. -Para encontrar los pasos necesarios para instalar un certificado, refiérete a la documentación del sistema operativo de tu ejecutor. +### Configuring Node.JS to use the certificate -### Configurar Node.JS para utilizar el certificado +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. -La mayoría de las acciones se escriben en JavaScript y se ejecutan utilizando Node.js, lo cual no utiliza el almacenamiento del certificado del sistema operativo. Para que la aplicación ejecutora auto-hospedada utilice el certificado, debes configurar la variable de ambiente `NODE_EXTRA_CA_CERTS` en la máquina ejecutora. +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. -Puedes configurar la variable de ambiente como una variable de ambiente de sistema, o declararla en un archivo que se llame _.env_ en el directorio de aplicaciones del ejecutor auto-hospedado. - -Por ejemplo: +For example: ```shell NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt ``` -Las variables de ambiente se leen cuando la aplicación ejecutora auto-hospedada inicia, así que debes configurar la variable de ambiente antes de configurar o iniciar la aplicación ejecutora auto-hospedada. Si cambia la configuración de tu certificado, debes reiniciar la aplicación ejecutora auto-hospedada. +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. -### Configurar los contenedores de Docker para que utilicen el certificado +### Configuring Docker containers to use the certificate -Si utilizas las acciones de contenedor de Docker o los contenedores de servicio en tus flujos de trabajo, puede que también necesites instalar el certificado en tu imagen de Docker adicionalmente a configurar la variable de ambiente anterior. +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. -## Configurar los ajustes de proxy HTTP para {% data variables.product.prodname_actions %} +## Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} {% data reusables.actions.enterprise-http-proxy %} -Si estos ajustes no se configuran adecuadamente, podrías recibir errores tales como `Resource unexpectedly moved to https://` cuando ajustes o cambies tu configuración de {% data variables.product.prodname_actions %}. +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. -## Los ejecutores no se conectan a {% data variables.product.prodname_ghe_server %} después de cambiar el nombre de host +## Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname -Si cambias el nombre de host de {% data variables.product.product_location %}, los ejecutores auto-hospedados no podrán conectarse al nombre de host antiguo y no podrán ejecutar ningún job. +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. -Necesitarás actualizar la configuración de tus ejecutores auto-hospedados para utilizar el nuevo nombre de host para {% data variables.product.product_location %}. Cada ejecutor auto-hospedado necesitará alguno de los siguientes procedimientos: +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: -* En el directorio de la aplicación ejecutora auto-hospedada, edita los archivos `.runner` y `.credentials` para reemplazar todas las menciones del nombre de host antiguo con el nuevo, posteriormente, reinicia la aplicación ejecutora auto-hospedada. -* Elimina al ejecutor de {% data variables.product.prodname_ghe_server %} utilizando la IU, y vuelve a agregarlo. Para obtener más información, consulta "[Eliminar ejecutores autoalojados](/actions/hosting-your-own-runners/removing-self-hosted-runners) y [Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -## Jobs atorados y límites de CPU y de memoria de las {% data variables.product.prodname_actions %} +## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits -{% data variables.product.prodname_actions %} se compone de varios servicios que se ejecutan en {% data variables.product.product_location %}. Predeterminadamente, estos servicios se configuran con límites predeterminados de CPU y de memoria que deberían funcionar con la mayoría de las instancias. Sin embargo, los usuarios asiduos de {% data variables.product.prodname_actions %} podrían encesitar ajustar esta configuración. +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. -Puede que estés llegando a los límites de CPU o de memoria si notas que los jobs no están iniciando (aún si hay ejecutores inactivos), o si el progreso del job no se actualiza o cambia en la IU. +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. -### 1. Verifica el uso total de memoria y CPU en la consola de administración +### 1. Check the overall CPU and memory usage in the management console -Accede a la consola de administración y utiliza el tablero de monitoreo para inspeccionar las gráficas del total de memoria y de CPU debajo de "Salud del Sistema". Para obtener más información, consulta la sección "[Acceder al tablero de monitoreo](/admin/enterprise-management/accessing-the-monitor-dashboard)". +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." -Si la "Salud del sistema" para el uso total de CPU es cercano a 100%, o si ya no hay memoria disponible restante, entonces {% data variables.product.product_location %} se está ejecutando al total de su capacidad y necesita escalarse. Para obtener más información, consulta "[Aumentar los recursos de memoria o la CPU](/admin/enterprise-management/increasing-cpu-or-memory-resources)." +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." -### 2. Verifica el uso de CPU y memoria de los jobs nómadas en la consola de administración +### 2. Check the Nomad Jobs CPU and memory usage in the management console -Si la "Salud del sistema" para el uso total de CPU y memoria están bien, desplázate a la parte inferior de la página, hacia la sección de "Jobs nómadas", y revisa las g´raficas de "Valor porcentual de CPU" y de "Uso de memoria". +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. -Cada sección en estas gráficas corresponde a un servicio. Para los servicios de {% data variables.product.prodname_actions %}, busca: +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: * `mps_frontend` * `mps_backend` @@ -82,18 +81,18 @@ Cada sección en estas gráficas corresponde a un servicio. Para los servicios d * `actions_frontend` * `actions_backend` -Si cualquiera de estos servicios estan cerca de o en 100% de uso de CPU, o si la memoria está cerca de su límite (2 GB, predeterminadamente), entonces el recurso de asignación para estos servicios podría necesitar un aumento. Toma nota de cuáles de los servicios antes descritos están cerca de o en su límite. +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. -### 3. Incrementa la asignación de recursos para los servicios en su límite +### 3. Increase the resource allocation for services at their limit -1. Ingresa en el shell administrativo utilizando SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." -1. Ejecuta el siguiente comando para ver qué recursos se encuentran disponibles para su asignación: +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Run the following command to see what resources are available for allocation: ```shell nomad node status -self ``` - En la salida, encuentra la sección de "Recursos asignados". Se debe ver similar al siguiente ejemplo: + In the output, find the "Allocated Resources" section. It looks similar to the following example: ``` Allocated Resources @@ -101,25 +100,25 @@ Si cualquiera de estos servicios estan cerca de o en 100% de uso de CPU, o si la 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB ``` - Para la memoria y el CPU, esta muestra cuánto se asigna al **total** de **todos** los servicios (el valor de la izquierda) y cuánto queda disponible (el valor de la derecha). En el ejemplo anterior, hay 23 GiB de memoria asignada de los 32 GiB totales. Esto significa que hay 9 GiB de memoria disponibles para asignar. + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. {% warning %} - **Advertencia:** Ten cuidado de no asignar más del total de los recursos disponibles o los servicios no podrán iniciar. + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. {% endwarning %} -1. Cambia el directorio a `/etc/consul-templates/etc/nomad-jobs/actions`: +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: ```shell cd /etc/consul-templates/etc/nomad-jobs/actions ``` - En este directorio hay tres archivos que corresponden a los servicios de {% data variables.product.prodname_actions %} descritos anteriormente: + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: * `mps.hcl.ctmpl` * `token.hcl.ctmpl` * `actions.hcl.ctmpl` -1. Para los servicios en los que identificaste una necesidad de ajuste, abre el archivo correspondiente y ubica el grupo `resources` que se ve como el siguiente ejemplo: +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: ``` resources { @@ -131,9 +130,9 @@ Si cualquiera de estos servicios estan cerca de o en 100% de uso de CPU, o si la } ``` - Los valores están en MHz para los recursos de CPU y en MB para los recursos de memoria. + The values are in MHz for CPU resources, and MB for memory resources. - Por ejemplo, para incrementar los límites de recursos en el ejemplo anterior a 1 GHz para el CPU y 4 GB de memoria, cámbialos a: + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: ``` resources { @@ -144,8 +143,38 @@ Si cualquiera de estos servicios estan cerca de o en 100% de uso de CPU, o si la } } ``` -1. Guarda el cambio y sal del archivo. -1. Ejecuta `ghe-config-apply` para aplicar los cambios. +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. - Cuando ejecutes `ghe-config-apply`, si ves una salida como `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, entonces el cambio seguramente sobreasignó recursos de CPU o de memoria. Si esto sucede, edita los archivos de configuración nuevamente y baja los recursos de CPU o de memoria y luego vuelve a ejecutar `ghe-config-apply`. -1. Después de aplicar la configuración, ejecuta `ghe-actions-check` para verificar que los servicios de {% data variables.product.prodname_actions %} estén operando. + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. + +{% ifversion fpt or ghec or ghes > 3.2 %} +## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows + +{% data reusables.dependabot.beta-security-and-version-updates %} + +After you set up {% data variables.product.prodname_dependabot %} updates for {% data variables.product.product_location %}, you may see failures when existing workflows are triggered by {% data variables.product.prodname_dependabot %} events. + +By default, {% data variables.product.prodname_actions %} workflow runs that are triggered by {% data variables.product.prodname_dependabot %} from `push`, `pull_request`, `pull_request_review`, or `pull_request_review_comment` events are treated as if they were opened from a repository fork. Unlike workflows triggered by other actors, this means they receive a read-only `GITHUB_TOKEN` and do not have access to any secrets that are normally available. This will cause any workflows that attempt to write to the repository to fail when they are triggered by {% data variables.product.prodname_dependabot %}. + +There are three ways to resolve this problem: + +1. You can update your workflows so that they are no longer triggered by {% data variables.product.prodname_dependabot %} using an expression like: `if: github.actor != 'dependabot[bot]'`. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +2. You can modify your workflows to use a two-step process that includes `pull_request_target` which does not have these limitations. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)." +3. You can provide workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and allow the `permissions` term to increase the default scope of the `GITHUB_TOKEN`. For more information, see "[Providing workflows triggered by{% data variables.product.prodname_dependabot %} access to secrets and increased permissions](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)" below. + +### Providing workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and increased permissions + +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. To remove the limitations on workflows triggered by {% data variables.product.prodname_dependabot %} on {% data variables.product.product_location %}, use the following command. + ``` shell + $ ghe-config app.actions.disable-dependabot-enforcement true + ``` +1. Apply the configuration. + ```shell + $ ghe-config-apply + ``` +1. Return to {% data variables.product.prodname_ghe_server %}. + +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md deleted file mode 100644 index 484ef9f556..0000000000 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: Iniciar con GitHub Actions para GitHub Enterprise Server -shortTitle: Comenzar con Acciones de GitHub -intro: 'Aprende cómo habilitar y configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} por primera vez.' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -redirect_from: - - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server -versions: - ghes: '*' -type: how_to -topics: - - Actions - - Enterprise ---- - -{% data reusables.actions.enterprise-beta %} - -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% ifversion ghes %} - -Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_server %} para utilizar {% data variables.product.prodname_actions %}. Esto cubre los requisitos de hardware y software, presenta las opciones de almacenamiento y describe las políticas de administración de seguridad. - -{% endif %} - -## Revisar las consideraciones de hardware - -{% ifversion ghes = 3.0 %} - -{% note %} - -**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." - -{% endnote %} - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -Los recursos de CPU y de memoria que están disponibles para {% data variables.product.product_location %} determinan el rendimiento máximo de jobs para {% data variables.product.prodname_actions %}. - -Las pruebas internas de {% data variables.product.company_short %} demostraron el siguiente rendimiento máximo para las instancias de {% data variables.product.prodname_ghe_server %} con un rango de CPU y configuraciones de memoria. Puede que vas rendimientos diferentes dependiendo de los niveles generales de actividad en tu instancia. - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -Los recursos de memoria y CPU que {% data variables.product.product_location %} tiene disponibles determinan la cantidad de jobs que se pueden ejecutar simultáneamente sin pérdida de rendimiento. - -La cantidad máxima de ejecución simultánea de jobs sin pérdida de rendimiento depende de factores tales como la duración de los jobs, el uso de artefactos, la cantidad de repositorios ejecutando acciones y qué tanto trabajo adicional sin relación a las acciones ejecuta tu instancia. Las pruebas internas en GitHub demostraron los siguientes objetivos de rendimiento para GitHub Enterprise Server en un rango de configuraciones de memoria y CPU: - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -| vCPU | Memoria | Rendimiento máximo del job | -|:---- |:------- |:-------------------------- | -| 4 | 32 GB | Demo o pruebas leves | -| 8 | 64 GB | 25 puestos de trabajo | -| 16 | 160 GB | 35 puestos de trabajo | -| 32 | 256 GB | 100 puestos de trabajo | - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -| vCPU | Memoria | Simultaneidad máxima* | -|:---- |:------- |:----------------------- | -| 32 | 128 GB | 1500 puestos de trabajo | -| 64 | 256 GB | 1900 puestos de trabajo | -| 96 | 384 GB | 2200 puestos de trabajo | - -*La simultaneidad máxima se midió utilizando repositorios múltiples, una duración de los jobs de aproximadamente 10 minutos y 10 MB de cargas de artefactos. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia. - -{%- endif %} - -If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. Para obtener más información acerca de cómo monitorear la capacidad y rendimiento de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Monitorear tu aplicativo](/admin/enterprise-management/monitoring-your-appliance)". - -Para obtener más información acerca de los requisitos mínimos de {% data variables.product.product_location %}, consulta las consideraciones de hardware para la plataforma de tu instancia. - -- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) -- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) -- [Plataforma de Google Cloud](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) -- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) -- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) -- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) -- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) - -{% data reusables.enterprise_installation.about-adjusting-resources %} - -## Requisitos de almacenamiento externo - -Para habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, debes tener acceso al almacenamiento externo de blobs. - -{% data variables.product.prodname_actions %} utiliza el almacenamiento de blobs para almacenar artefactos que se generan con las ejecuciones de flujo de trabajo, tales como las bitácoras de flujo de trabajo y los artefactos de compilaciones que sube el usuario. La cantidad de almacenamiento requerida dependerá de tu uso de {% data variables.product.prodname_actions %}. Sólo se admite una sola configuración de almacenamiento externo y no puedes utilizar varios proveedores de almacenamiento al mismo tiempo. - -{% data variables.product.prodname_actions %} es compatible con estos proveedores de almacenamiento: - -* Azure Blob storage -* Amazon S3 -* S3-compatible MinIO Gateway para NAS - -{% note %} - -**Nota:** Estos son los únicos proveedores de almacenamiento compatibles con {% data variables.product.company_short %} y sobre los que éste puede proporcionar asistencia. Es muy poco probable que otros proveedores de almacenamiento de S3 compatibles con la API funcionen, debido a las diferencias de la API de S3. [Contáctanos](https://support.github.com/contact) para solicitar soporte para proveedores de almacenamiento adicionales. - -{% endnote %} - -## Consideraciones de las conexiones - -{% data reusables.actions.proxy-considerations %} Para obtener más información sobre cómo utilizar un proxy con {% data variables.product.prodname_ghe_server %}, consulta la sección "[Configurar un servidor proxy saliente](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)". - -{% ifversion ghes %} - -## Habilitar las {% data variables.product.prodname_actions %} con tu proveedor de almacenamiento - -Sigue uno de los procedimientos siguientes para habilitar las {% data variables.product.prodname_actions %} con el proveedor de almacenamiento de tu elección: - -* [Habilitar las GitHub Actions con el almacenamiento de Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) -* [Habilitar las GitHub Actions con el almacenamiento de Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) -* [Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) - -## Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa - -Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". - -## Agrega ejecutores auto-hospedados - -{% data reusables.actions.enterprise-github-hosted-runners %} - -Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." - -## Administrar qué acciones pueden utilizarse en tu empresa - -Puedes controlar las acciones que pueden utilizar tus usuarios en tu empresa. Esto incluye el configurar {% data variables.product.prodname_github_connect %} para el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %}, o sincronizar las acciones de {% data variables.product.prodname_dotcom_the_website %} manualmente. - -Para obtener más información, consulta la sección "[Acerca de utilizar las acciones en tu empresa](/admin/github-actions/about-using-actions-in-your-enterprise)". - -## Fortalecimiento de seguridad general para las {% data variables.product.prodname_actions %} - -Si quieres aprender más acerca de las prácticas de seguridad para {% data variables.product.prodname_actions %}, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". - -{% endif %} - -## Nombres reservados - -Cuando habilitas las {% data variables.product.prodname_actions %} para tu empresa, se crean dos organizaciones: `github` y `actions`. Si tu empresa utiliza el nombre de organización `github`, `github-org` (o `github-github-org` si `github-org` también se está utilizando) se utilizará en su lugar. Si tu empresa ya utiliza el nombre de organización `actions`, `github-actions` (or `github-actions-org` si `github-actions` también se está utilizando) se utilizará en su lugar. Una vez que se habiliten las acciones, ya no podrás utilizar estos nombres. diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 11742dab75..ee0f477635 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -1,15 +1,15 @@ --- -title: Habilitar GitHub Actions para GitHub Enterprise Server -intro: 'Aprende cómo configurar el almacenamiento y habilita las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}.' +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' versions: ghes: '*' topics: - Enterprise children: - - /getting-started-with-github-actions-for-github-enterprise-server - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage -shortTitle: Habiligar GitHub Actions + - /setting-up-dependabot-updates +shortTitle: Enable GitHub Actions --- diff --git a/translations/es-ES/content/admin/github-actions/index.md b/translations/es-ES/content/admin/github-actions/index.md index ba1bb5a1da..808fdae5b0 100644 --- a/translations/es-ES/content/admin/github-actions/index.md +++ b/translations/es-ES/content/admin/github-actions/index.md @@ -1,19 +1,21 @@ --- -title: Administrar GitHub Actions para tu empresa -intro: 'Habilita las {% data variables.product.prodname_actions %} en {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, y administra las políticas y configuraciones de {% data variables.product.prodname_actions %}.' +title: Managing GitHub Actions for your enterprise +intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, and manage {% data variables.product.prodname_actions %} policies and settings.' redirect_from: - /enterprise/admin/github-actions versions: + ghec: '*' ghes: '*' ghae: '*' topics: - Enterprise children: + - /getting-started-with-github-actions-for-your-enterprise - /using-github-actions-in-github-ae - /enabling-github-actions-for-github-enterprise-server - /managing-access-to-actions-from-githubcom - /advanced-configuration-and-troubleshooting -shortTitle: Administrar las GitHub Actions +shortTitle: Manage GitHub Actions --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index ea73f6bdd7..3470da6098 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -1,6 +1,6 @@ --- -title: Habilitar el acceso automático a las acciones de GitHub.com utilizando GitHub Connect -intro: 'Para permitir que las {% data variables.product.prodname_actions %} en tu empresa utilicen acciones de {% data variables.product.prodname_dotcom_the_website %}, puedes conectar tu instancia empresarial a {% data variables.product.prodname_ghe_cloud %}.' +title: Enabling automatic access to GitHub.com actions using GitHub Connect +intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.' permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.' redirect_from: - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect @@ -13,20 +13,25 @@ topics: - Actions - Enterprise - GitHub Connect -shortTitle: Utilizar GitHub Connect para las acciones +shortTitle: Use GitHub Connect for actions --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} + +## About automatic access to {% data variables.product.prodname_dotcom_the_website %} actions + +By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). + +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." + +To use actions from {% data variables.product.prodname_dotcom_the_website %}, your self-hosted runners must be able to download public actions from `api.github.com`. + +## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions + {% data reusables.actions.enterprise-github-connect-warning %} -Predeterminadamente, los flujos de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.product_name %} no pueden utilizar las acciones directamente desde {% data variables.product.prodname_dotcom_the_website %} o desde [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). - -Para que todas las acciones de {% data variables.product.prodname_dotcom_the_website %} se hagan disponibles para tu instancia empresarial, puedes utilizar {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %}. Para encontrar otras formas de acceder a las acciones desde {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Acerca de utilizar las acciones en tu empresa](/admin/github-actions/about-using-actions-in-your-enterprise)". - -## Habilitar el acceso automático a todas las acciones de {% data variables.product.prodname_dotcom_the_website %} - -Antes de habilitar el acceso para todas las acciones desde {% data variables.product.prodname_dotcom_the_website %} en tu instancia empresarial, debes conectar a tu empresa con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Conectar empresa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% data reusables.enterprise-accounts.access-enterprise %} {%- ifversion ghes < 3.1 %} @@ -34,8 +39,34 @@ Antes de habilitar el acceso para todas las acciones desde {% data variables.pro {%- endif %} {% data reusables.enterprise-accounts.github-connect-tab %} {%- ifversion ghes > 3.0 or ghae %} -1. Debajo de "Los usuarios pueden utilizar acciones de GitHub.com en las ejecuciones de flujo de trabajo", utiliza el menú desplegable y selecciona **Habilitado**. ![Menú desplegable a las acciones de GitHub.com en las ejecuciones de flujo de trabajo](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. + ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) {%- else %} -1. Debajo de "El servidor puede utilizar acciones de GitHub.com en las ejecuciones de flujo de trabajo", utiliza el menú desplegable y selecciona **Habilitado**. ![Menú desplegable a las acciones de GitHub.com en las ejecuciones de flujo de trabajo](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. + ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) {%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} + +{% ifversion ghes > 3.2 or ghae-issue-4815 %} + +## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} + +When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.product.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}. + +Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} blocks the potential for a man-in-the-middle attack by a malicious user with access to {% data variables.product.product_location %}. When an action on {% data variables.product.prodname_dotcom_the_website %} is used for the first time, that namespace is retired in {% data variables.product.product_location %}. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on {% data variables.product.prodname_dotcom_the_website %}. This ensures that when a workflow runs, the intended action is always run. + +After using an action from {% data variables.product.prodname_dotcom_the_website %}, if you want to create an action in {% data variables.product.product_location %} with the same name, first you need to make the namespace for that organization and repository available. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. In the left sidebar, under **Site admin** click **Retired namespaces**. +3. Locate the namespace that you want use in {% data variables.product.product_location %} and click **Unretire**. + ![Unretire namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) +4. Go to the relevant organization and create a new repository. + + {% tip %} + + **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository. + + {% endtip %} + +{% endif %} diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 85c293ca72..aca31e0e64 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -1,6 +1,6 @@ --- -title: Sincronizar manualmente las acciones de GitHub.com -intro: 'Para los usuarios que necesiten acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar las acciones específicas a tu empresa.' +title: Manually syncing actions from GitHub.com +intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.' redirect_from: - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom - /admin/github-actions/manually-syncing-actions-from-githubcom @@ -11,7 +11,7 @@ type: tutorial topics: - Actions - Enterprise -shortTitle: Sincronziar acciones manualmente +shortTitle: Manually sync actions --- {% data reusables.actions.enterprise-beta %} @@ -22,31 +22,39 @@ shortTitle: Sincronziar acciones manualmente {% ifversion ghes or ghae-next %} -El acercamiento recomendado para habilitar el acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %} es habilitar el acceso automático para todas las acciones. Puedes hacer esto si utilizas {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." -Sin embargo, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes{% else %}Puedes{% endif %} seguir esta guía para utilizar la herramienta [`actions-sync`](https://github.com/actions/actions-sync) de código abierto de {% data variables.product.company_short %} para sincronizar los repositorios de acciones individuales desde {% data variables.product.prodname_dotcom_the_website %} hacia tu empresa. +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. -## Acerca de la herramienta `actions-sync` +## About the `actions-sync` tool -La herramienta `actions-sync` debe ejecutarse en una máquina que pueda acceder a la API de {% data variables.product.prodname_dotcom_the_website %} y a la API de tu instancia de {% data variables.product.product_name %}. La máquina no necesita estar conectada a ambas al mismo tiempo. +The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time. -Si tu máquina tiene acceso a ambos sistemas al mismo tiempo, puedes hacer la sincronización con un simple comando de `actions-sync sync`. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`. +If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. -La herramienta `actions-sync` solo puede descargar acciones de {% data variables.product.prodname_dotcom_the_website %} que estén almacenadas en repositorios públicos. +The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -## Prerrequisitos +{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% note %} -* Antes de utilizar la herramienta `actions-sync`, debes asegurarte de que todas las organizaciones de destino ya existan en tu empresa. El siguiente ejemplo demuestra cómo sincronizar acciones a una organización que se llama `synced-actions`. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". -* Debes crear un token de acceso personal (PAT) en tu empresa que pueda crear y escribir en los repositorios de las organizaciones destino. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".{% ifversion ghes %} -* Si quieresSi quieres sincronizar las acciones incluidas en la organización `actions` en {% data variables.product.product_location %}, debes ser un propietario de la organización `actions`. +**Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + +{% endnote %} +{% endif %} + +## Prerequisites + +* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." +* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. {% note %} - - **Nota:** Predeterminadamente, incluso los administradores de sitio no son propietarios de la organización empaquetada `actions`. - + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + {% endnote %} - Los administradores de sitio pueden utilizar el comando `ghe-org-admin-promote` en el shell administrativo para promover a un usuario para que sea propietario de la organización empaquetada `actions`. Para obtener más información, consulta la sección "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)". + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." ```shell ghe-org-admin-promote -u USERNAME -o actions @@ -63,7 +71,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac {% endnote %} 1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system. -1. Crea un directorio para almacenar los archivos de caché para la herramienta. +1. Create a directory to store cache files for the tool. 1. Run the `actions-sync sync` command: ```shell @@ -74,20 +82,20 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac --repo-name "actions/stale:synced-actions/actions-stale" ``` - El comando anterior utiliza los siguientes argumentos: - - * `--cache-dir`: El directorio del caché en la máquina que ejecuta el comando. - * `--destination-token`: Un token de acceso personal para la instancia empresarial de destino. - * `--destination-url`: La URL de la instancia empresarial de destino. - * `--repo-name`: El repositorio de acción a sincronizar. Esto adopta el formato de `owner/repository:destination_owner/destination_repository`. - - * El ejemplo anterior sincroniza el repositorio [`actions/stale`](https://github.com/actions/stale) con el repositorio `synced-actions/actions-stale` en la instancia empresarial de destino. Debes crear la organización denominada `synced-actions` en tu empresa antes de ejecutar el comando anterior. - * Si omites el `:destination_owner/destination_repository`, la herramienta utilizará el nombre de propietario y de repositorio originales para tu empresa. Antes de ejecutar el comando, debes crear una organización nueva en tu empresa, la cual empate con el nombre de propietario de la acción. Considera utilizar una organización central para almacenar las acciones sincronizadas en tu empresa, ya que esto significa que no necesitarás crear varias organizaciones nuevas si sincronizas las acciones de propietarios diferentes. - * Puedes sincronizar varias acciones si reemplazas el parámetro `--repo-name` con `--repo-name-list` o con `--repo-name-list-file`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#actions-sync). -1. Después de que se haya creado el repositorio de acción en tu empresa, las personas en tu empresa pueden utilizar el repositorio de destino para referenciar la acción en sus flujos de trabajo. Para la acción de ejemplo que se muestra a continuación: + The above command uses the following arguments: + * `--cache-dir`: The cache directory on the machine running the command. + * `--destination-token`: A personal access token for the destination enterprise instance. + * `--destination-url`: The URL of the destination enterprise instance. + * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`. + + * The above example syncs the [`actions/stale`](https://github.com/actions/stale) repository to the `synced-actions/actions-stale` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command. + * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners. + * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync). +1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above: + ```yaml uses: synced-actions/actions-stale@v1 ``` - Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)". + For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)." diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 6c9009a9fd..a4e9e42420 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -1,6 +1,6 @@ --- -title: Utilizar la última versión de las acciones empaquetadas oficiales -intro: 'Puedes actualizar las acciones que vienen en paquete para tu empresa o utilizarlas directamente desde {% data variables.product.prodname_dotcom_the_website %}.' +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: next @@ -11,34 +11,47 @@ topics: - GitHub Connect redirect_from: - /admin/github-actions/using-the-latest-version-of-the-official-bundled-actions -shortTitle: Utilizar las acciones empaquetadas más recientes +shortTitle: Use the latest bundled actions --- - {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -Tu instancia empresarial incluye varias acciones integradas que puedes utilizar en tus flujos de trabajo. Para obtener más información sobre las acciones en paquete, consulta la sección "[Acciones oficiales que vienen en paquete con tu instancia empresarial](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)". +Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." -Estas acciones que vienen en paquete son una captura de un punto en el tiempo de las acciones oficiales que se encuentran en https://github.com/actions, así que podría haber versiones nuevas disponibles de estas. Puedes utilizar la herramienta de `actions-sync` para actualizar estas acciones o puedes configurar {% data variables.product.prodname_github_connect %} para permitir el acceso a las últimas acciones en {% data variables.product.prodname_dotcom_the_website %}. Estas opciones se describen en las siguietnes secciones. +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections. -## Utilizar `actions-sync` para actualizar las acciones que vienen en paquete +## Using `actions-sync` to update the bundled actions -Para actualizar las acciones que vienen en paquete, puedes utilizar la herramienta `actions-sync` para actualizar esta captura. Para obtener más información sobre cómo utilizar `actions-sync`, consulta la sección "[Sincronizar manualmente las acciones desde {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)". +To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." -## Utilizar {% data variables.product.prodname_github_connect %} para acceder a las últimas acciones +## Using {% data variables.product.prodname_github_connect %} to access the latest actions -Puedes utilizar {% data variables.product.prodname_github_connect %} para permitir que {% data variables.product.product_name %} utilice acciones desde {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." -Una vez que se configura {% data variables.product.prodname_github_connect %}, puedes utilizar la versión más reciente de una acción si borras su repositorio local en la organización `actions` en tu instancia. Por ejemplo, si tu instancia empresarial está utilizando la acción `actions/checkout@v1` y necesitas utilizar `actions/checkout@v2`, el cual no está disponible en esta, lleva a cabo los siguietnes pasos para que puedas utilizar la acción más reciente de `checkout` desde {% data variables.product.prodname_dotcom_the_website %}: +Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. Desde una cuenta de propietario de empresa en {% data variables.product.product_name %}, navega al repositorio que quieras borrar desde la organización *actions* (en este `checkout` de ejemplo). -1. Predeterminadamente, los administradores de sitio no son propietarios de la organización integrada de *actions*. Para obtener el acceso requerido para borrar el repositorio `checkout`, debes utilizar las herramientas de administrador de sitio. Haz clic en {% octicon "rocket" aria-label="The rocket ship" %} en la esquina superior derecha de cualquier página de este repositorio. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) -1. Haz clic en {% octicon "shield-lock" %} **Seguridad** para ver el resumen de seguridad del repositorio. ![Asegurar el repositorio del repositorio](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) -1. Debajo de "Acceso privilegiado", haz clic en **Desbloquear**. ![Botón de desbloquear](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) -1. Debajo de **Razón**, teclea una razón para desbloquear el repositorio y luego haz clic en **Desbloquear**. ![Diálogo de confirmación](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) -1. Ahora que el repositorio se desbloqueó, puedes salir de las páginas de administrador de sitio y borrar el repositorio dentro de la organización `actions`. En la parte superior de la página, haz clic en el nombre de repositorio, que en este ejemplo es **checkout**, para regresar a la página de resumen. ![Enlace de nombre de repositorio](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) -1. Debajo de "Información de repositorio", haz clic en **Ver código** para salir de las páginas de administrador del sitio y que se muestre el repositorio `checkout`. -1. Borra el repositorio `checkout` dentro de la organización `actions`. Para obtener más información sobre cómo borrar un repositorio, consulta la sección "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)". ![Enlace de ver código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) -1. Configura el YAML de tu flujo de trabajo para que utilice `actions/checkout@v2`. -1. Cada vez que se ejecute tu flujo de trabajo, el ejecutor utilizará la versión `v2` de `actions/checkout` desde {% data variables.product.prodname_dotcom_the_website %}. +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. + ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. + ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. + ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. + ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. + ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." + ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) +1. Configure your workflow's YAML to use `actions/checkout@v2`. +1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. + + {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% note %} + + **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + + {% endnote %} + {% endif %} diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md deleted file mode 100644 index c655d177ec..0000000000 --- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Comenzar con las GitHub Actions para GitHub AE -shortTitle: Comenzar con Acciones de GitHub -intro: 'Aprende a configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}.' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -versions: - ghae: '*' -type: how_to -topics: - - Actions - - Enterprise -redirect_from: - - /admin/github-actions/getting-started-with-github-actions-for-github-ae ---- - -{% data reusables.actions.ae-beta %} - -Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_managed %} para utilizar {% data variables.product.prodname_actions %}. - -## Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa - -Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". - -## Agregar ejecutores - -{% note %} - -**Nota:** Para agregar {% data variables.actions.hosted_runner %} a {% data variables.product.prodname_ghe_managed %}, tendrás que contactar al soporte de {% data variables.product.prodname_dotcom %}. - -{% endnote %} - -Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores a nivel de empresa, organización o repositorio. Para obtener más información, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)". - - -## Fortalecimiento de seguridad general para las {% data variables.product.prodname_actions %} - -Si quieres aprender más acerca de las prácticas de seguridad para {% data variables.product.prodname_actions %}, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md index 2ec6a93766..ed67e364c7 100644 --- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md +++ b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md @@ -1,11 +1,10 @@ --- -title: Utilizar GitHub Actions en GitHub AE -intro: 'Aprende cómo configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}.' +title: Using GitHub Actions in GitHub AE +intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' versions: ghae: '*' children: - - /getting-started-with-github-actions-for-github-ae - /using-actions-in-github-ae -shortTitle: Utilizar las acciones en GitHub AE +shortTitle: Use Actions in GitHub AE --- diff --git a/translations/es-ES/content/admin/guides.md b/translations/es-ES/content/admin/guides.md index 688512274d..6eee293a97 100644 --- a/translations/es-ES/content/admin/guides.md +++ b/translations/es-ES/content/admin/guides.md @@ -1,7 +1,7 @@ --- -title: Guías de Github Enterprise -shortTitle: Guías -intro: 'Aprende cómo incrementar la productividad de desarrollador y calidad de código con {% data variables.product.product_name %}.' +title: GitHub Enterprise guides +shortTitle: Guides +intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -9,14 +9,15 @@ versions: ghes: '*' ghae: '*' learningTracks: + - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' - '{% ifversion ghae %}get_started_with_github_ae{% endif %}' - '{% ifversion ghes %}deploy_an_instance{% endif %}' - '{% ifversion ghes %}upgrade_your_instance{% endif %}' + - adopting_github_actions_for_your_enterprise - '{% ifversion ghes %}increase_fault_tolerance{% endif %}' - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}' - - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' includeGuides: - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - /admin/authentication/changing-authentication-methods @@ -134,5 +135,6 @@ includeGuides: - /admin/user-management/removing-users-from-teams-and-organizations - /admin/user-management/requiring-two-factor-authentication-for-an-organization - /admin/user-management/suspending-and-unsuspending-users + - /admin/overview/creating-an-enterprise-account --- diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md index fd77d7897a..cf364b8e3a 100644 --- a/translations/es-ES/content/admin/index.md +++ b/translations/es-ES/content/admin/index.md @@ -1,6 +1,6 @@ --- -title: Documentación para administradores empresariales -shortTitle: Administradores empresariales +title: Enterprise administrator documentation +shortTitle: Enterprise administrators intro: 'Documentation and guides for enterprise administrators{% ifversion ghes %}, system administrators,{% endif %} and security specialists who {% ifversion ghes %}deploy, {% endif %}configure{% ifversion ghes %},{% endif %} and manage {% data variables.product.product_name %}.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account @@ -101,6 +101,7 @@ featuredLinks: - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}' - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}' - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}' + - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}' - /admin/enterprise-support/about-github-enterprise-support layout: product-landing versions: diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md index 22584c5484..1be5214e08 100644 --- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md +++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md @@ -1,63 +1,63 @@ --- -title: Instalar el servidor de GitHub Enterprise en XenServer -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en XenServer, debes implementar la imagen de disco {% data variables.product.prodname_ghe_server %} a un servidor XenServer.' +title: Installing GitHub Enterprise Server on XenServer +intro: 'To install {% data variables.product.prodname_ghe_server %} on XenServer, you must deploy the {% data variables.product.prodname_ghe_server %} disk image to a XenServer host.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-xenserver/ - /enterprise/admin/installation/installing-github-enterprise-server-on-xenserver - /admin/installation/installing-github-enterprise-server-on-xenserver versions: - ghes: '*' + ghes: '<=3.2' type: tutorial topics: - Administrator - Enterprise - Infrastructure - Set up -shortTitle: Instalar en XenServer +shortTitle: Install on XenServer --- {% note %} - **Nota:** Se descontinuará la compatibilidad con {% data variables.product.prodname_ghe_server %} en XenServer desde {% data variables.product.prodname_ghe_server %} 3.3. Para obtener más información, consulta la sección de [notas de lanzamiento para {% data variables.product.prodname_ghe_server %} 3.1](/admin/release-notes#3.1.0) + **Note:** Support for {% data variables.product.prodname_ghe_server %} on XenServer will be discontinued in {% data variables.product.prodname_ghe_server %} 3.3. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.1 release notes](/admin/release-notes#3.1.0) {% endnote %} -## Prerrequisitos +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- Debes instalar el XenServer Hypervisor en la máquina que ejecutará tu máquina virtual (VM) {% data variables.product.prodname_ghe_server %}. Admitimos versiones 6.0 a 7.0. -- Recomendamos utilizar XenCenter Windows Management Console para la configuración inicial. Abajo se incluyen instrucciones utilizando XenCenter Windows Management Console. Para obtener más información, consulta la guía de Citrix "[Cómo descargar e instalar una nueva versión de XenCenter](https://support.citrix.com/article/CTX118531)." +- You must install the XenServer Hypervisor on the machine that will run your {% data variables.product.prodname_ghe_server %} virtual machine (VM). We support versions 6.0 through 7.0. +- We recommend using the XenCenter Windows Management Console for initial setup. Instructions using the XenCenter Windows Management Console are included below. For more information, see the Citrix guide "[How to Download and Install a New Version of XenCenter](https://support.citrix.com/article/CTX118531)." -## Consideraciones relativas al hardware +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## Descargar la imagen {% data variables.product.prodname_ghe_server %} +## Downloading the {% data variables.product.prodname_ghe_server %} image {% data reusables.enterprise_installation.enterprise-download-procedural %} {% data reusables.enterprise_installation.download-license %} {% data reusables.enterprise_installation.download-appliance %} -4. Selecciona {% data variables.product.prodname_dotcom %} local, después haz clic en **XenServer (VHD)**. -5. Para descargar tu archivo de licencia, haz clic en **Download license (Descargar licencia)**. +4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **XenServer (VHD)**. +5. To download your license file, click **Download license**. -## Crear la instancia {% data variables.product.prodname_ghe_server %} +## Creating the {% data variables.product.prodname_ghe_server %} instance {% data reusables.enterprise_installation.create-ghe-instance %} -1. En XenCenter, importa la imagen {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, consulta la guía de XenCenter "[Importar imágenes de disco](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)." - - Para el paso "Enable Operating System Fixup (Habilitar Ajuste del sistema en funcionamiento)", selecciona **Don't use Operating System Fixup (No usar Ajuste del sistema en funcionamiento)**. - - Deja la VM apagada cuando hayas finalizado. -{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obtener instrucciones, consulta la guía de XenCenter "[Agregar discos virtuales](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)." +1. In XenCenter, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the XenCenter guide "[Import Disk Images](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)." + - For the "Enable Operating System Fixup" step, select **Don't use Operating System Fixup**. + - Leave the VM powered off when you're finished. +{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the XenCenter guide "[Add Virtual Disks](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)." -## Configurar la instancia de {% data variables.product.prodname_ghe_server %} +## Configuring the {% data variables.product.prodname_ghe_server %} instance {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -## Leer más +## Further reading -- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} -- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md index e025ad377e..fae7b08ba4 100644 --- a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md +++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- -title: Acerca de las cuentas de empresa -intro: 'Con {% data variables.product.product_name %}, puedes utilizar una cuenta empresarial para {% ifversion ghec %}habilitar la colaboración entre tus organizaciones, mientras que proporcionas{% elsif ghes or ghae %}dar{% endif %} a los administradores un punto único de visibilidad y administración.' +title: About enterprise accounts +intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion ghec %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.' redirect_from: - /articles/about-github-business-accounts/ - /articles/about-enterprise-accounts @@ -20,81 +20,83 @@ topics: - Fundamentals --- -## Acerca de las cuentas empresariales en {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} +## About enterprise accounts on {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} {% ifversion ghec %} -Tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} te permite administrar organizaciones múltiples. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. +Your enterprise account on {% data variables.product.prodname_dotcom_the_website %} allows you to manage multiple organizations. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}. {% elsif ghes or ghae %} -La cuenta empresarial en {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} te permite administrar las organizaciones{% ifversion ghes %} en{% elsif ghae %} que pertenecen a{% endif %} tu {% ifversion ghes %}instancia de {% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa{% endif %}. +The enterprise account on {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} allows you to manage the organizations{% ifversion ghes %} on{% elsif ghae %} owned by{% endif %} your {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise{% endif %}. {% endif %} -Las organizaciones son cuentas compartidas en donde los miembros de las empresas pueden colaborar a través de muchos proyectos al mismo tiempo. Los propietarios de la organización pueden administrar el acceso a los datos y proyectos de esta con seguridad y características administrativas sofisticadas. Para obtener más información, consulta la sección {% ifversion ghec %}"[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)".{% elsif ghes or ghae %}"[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)" y "[Administrar usuarios, organizaciones y repositorios](/admin/user-management)".{% endif %} +Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion ghec %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %} {% ifversion ghec %} -Los propietarios de las empresas pueden crear organizaciones y enlazarlas a la empresa. Alternatively, you can invite an existing organization to join your enterprise account. Después de que agregues organizaciones a tu cuenta empresarial, puedes administrar y requerir políticas para dichas organizaciones. Las opciones de cumplimiento específicas varían según el parámetro, generalmente, puedes elegir implementar una política única para cada organización en tu cuenta de empresa o puedes permitirle a los propietarios configurar la política en el nivel de organización. For more information, see "[Setting policies for your enterprise](/admin/policies)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for your enterprise](/admin/policies)." + +{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." {% elsif ghes or ghae %} -Para obtener más información sobre la administración de políticas para tu cuenta empresarial, consulta la sección "[Configurar las políticas de tu empresa](/admin/policies)". +For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)." {% endif %} -## Acerca de la administración de tu cuenta empresarial +## About administration of your enterprise account {% ifversion ghes or ghae %} -Desde tu cuenta empresarial en {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}una instancia de {% data variables.product.prodname_ghe_server %}{% endif %}, los administradores pueden ver la membrecía empresrial y administrar lo siguiente para la instancia de {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa en {% data variables.product.prodname_ghe_managed %}{% endif %}. +From your enterprise account on {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.prodname_ghe_server %} instance{% endif %}, administrators can view enterprise membership and manage the following for the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %}. {% ifversion ghes %} -- Uso de licencia{% endif %} -- Seguridad ({% ifversion ghae %}inicio de sesión único, listas de IP permitidas, {% endif %}autoridades de certificados SSH, autenticación bifactorial) -- Políticas empresariales para las organizaciones que pertenezcan a la cuenta empresarial +- License usage{% endif %} +- Security ({% ifversion ghae %}single sign-on, IP allow lists, {% endif %}SSH certificate authorities, two-factor authentication) +- Enterprise policies for organizations owned by the enterprise account {% endif %} {% ifversion ghes %} -### Acerca de la administración de tu cuenta empresarial en {% data variables.product.prodname_ghe_cloud %} +### About administration of your enterprise account on {% data variables.product.prodname_ghe_cloud %} {% endif %} -{% ifversion ghec or ghes %}Cuando pruebas o compras {% data variables.product.prodname_enterprise %}, también {% ifversion ghes %} puedes{% endif %} crear una cuenta empresarial para {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}. Los administradores de la cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} pueden ver la membrecía y administrar lo siguiente para la cuenta empresarial{% ifversion ghes %} en {% data variables.product.prodname_dotcom_the_website %}{% endif %}. +{% ifversion ghec or ghes %}When you try or purchase {% data variables.product.prodname_enterprise %}, you can{% ifversion ghes %} also{% endif %} create an enterprise account for {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. Administrators for the enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view membership and manage the following for the enterprise account{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. -- Facturación y uso (Servicios en {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, licencias de usuario) -- Seguridad (Inicio de sesión único, listas de IP permitidas, autoridades de certificados SSH, autenticación bifactorial) -- Políticas empresariales para las organizaciones que pertenezcan a la cuenta empresarial +- Billing and usage (services on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, user licenses) +- Security (single sign-on, IP allow lists, SSH certificate authorities, two-factor authentication) +- Enterprise policies for organizations owned by the enterprise account -Si utilizas tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %}, también puedes administrar lo siguiente para {% data variables.product.prodname_ghe_server %} desde tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}. +If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you can also manage the following for {% data variables.product.prodname_ghe_server %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. -- Facturación y uso de las instancias de {% data variables.product.prodname_ghe_server %} -- Solicitudes y paquetes de soporte compartidos con {% data variables.contact.enterprise_support %} +- Billing and usage for {% data variables.product.prodname_ghe_server %} instances +- Requests and support bundle sharing with {% data variables.contact.enterprise_support %} -También puedes conectar la cuenta empresarial en {% data variables.product.product_location_enterprise %} a tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} para ver los detalles de uso de licencia para tu suscripción de {% data variables.product.prodname_enterprise %} desde {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} +You can also connect the enterprise account on {% data variables.product.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} -Para obtener más información acerca de las diferencias entre {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}, consulta la sección "[ productos de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)". {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} +For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} {% endif %} {% ifversion ghec %} -## Acerca de {% data variables.product.prodname_emus %} +## About {% data variables.product.prodname_emus %} {% data reusables.enterprise-accounts.emu-short-summary %} {% endif %} -## Acerca de la facturación para tu cuenta empresarial +## About billing for your enterprise account -La factura de tu cuenta empresarial incluye el costo mensual de cada miembro de ella. The bill includes {% ifversion ghec %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}additional paid services for your enterprise{% ifversion ghec %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. +The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion ghec %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}additional paid services for your enterprise{% ifversion ghec %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. {% ifversion ghec %} -Para obtener más información sobre la facturación de tu suscripción de {% data variables.product.prodname_ghe_cloud %}, consulta las secciones "[Ver la suscripción y el uso de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" y "[Acerca de la facturación de tu empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". +For more information about billing for your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." {% elsif ghes %} @@ -108,10 +110,10 @@ For more information about billing for {% ifversion ghec %}{% data variables.pro {% ifversion ghec %} -{% data variables.product.prodname_enterprise %} ofrece opciones de despliegue. Adicionalmente a las {% data variables.product.prodname_ghe_cloud %}, puedes utilizar {% data variables.product.prodname_ghe_server %} para hospedar trabajo de desarrollo para tu empresa en tu centro de datos o proveedor compatible en la nube. {% endif %}Los propietarios empresariales en {% data variables.product.prodname_dotcom_the_website %} pueden utilizar una cuenta empresarial para administrar el pago y el licenciamiento de las instancias de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta las secciones "[ productos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products#github-enterprise)" y "[Administrar tu licencia para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". +{% data variables.product.prodname_enterprise %} offers two deployment options. In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or supported cloud provider. {% endif %}Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can use an enterprise account to manage payment and licensing for {% data variables.product.prodname_ghe_server %} instances. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)" and "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." {% endif %} -## Leer más +## Further reading -- "[Cuentas empresariales](/graphql/guides/managing-enterprise-accounts)" en la documentación de la API de GraphQL +- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation diff --git a/translations/es-ES/content/admin/overview/index.md b/translations/es-ES/content/admin/overview/index.md index 974faceaa9..f947bc951e 100644 --- a/translations/es-ES/content/admin/overview/index.md +++ b/translations/es-ES/content/admin/overview/index.md @@ -1,6 +1,6 @@ --- -title: Resumen -intro: 'Puedes aprender sobre {% data variables.product.product_name %} y administrar cuentas de{% ifversion ghes %} y accesos, licencias, y{% endif %} facturación.' +title: Overview +intro: 'You can learn about {% data variables.product.product_name %} and manage{% ifversion ghes %} accounts and access, licenses, and{% endif %} billing.' redirect_from: - /enterprise/admin/overview versions: @@ -14,6 +14,6 @@ children: - /about-enterprise-accounts - /system-overview - /about-the-github-enterprise-api + - /creating-an-enterprise-account --- - -Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). +For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md index cd358faa99..de67c4ae7c 100644 --- a/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md +++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md @@ -1,6 +1,6 @@ --- -title: Habilitar los GitHub Packages con MinIO -intro: 'Configura el {% data variables.product.prodname_registry %} con MinIO como tu almacenamiento externo.' +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' versions: ghes: '*' type: tutorial @@ -8,21 +8,23 @@ topics: - Enterprise - Packages - Storage -shortTitle: Habilitar los paquetes con MinIO +shortTitle: Enable Packages with MinIO --- {% warning %} -**Advertencias:** -- Es crítico que configures las políticas de acceso restrictivo que necesites para tu bucket de almacenamiento, ya que {% data variables.product.company_short %} no aplica permisos de objeto específicos o listas de control de acceso adicionales (ACLs) a tu configuración de bucket de almacenamiento. Por ejemplo, si haces a tu bucket público, el público general en la internet podrá acceder a ellos. -- Te recomendamos utilizar un bucket dedicado para {% data variables.product.prodname_registry %}, separado de aquél que utilices para almacenar {% data variables.product.prodname_actions %}. -- Asegúrate de configurar el bucket que quieres utilizar en el futuro. No te recomendamos cambiar tu almacenamiento después de que comienzas a utilizar {% data variables.product.prodname_registry %}. +**Warnings:** +- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## Prerrequisitos -Antes de que puedas habilitar y configurar el {% data variables.product.prodname_registry %} en {% data variables.product.product_location_enterprise %}, necesitas preparar tu bucket de almacenamiento de MinIO. Para ayudarte a configurar el bucket de MinIO rápidamente y navegar a las opciones de personalización de MinIO, consulta la [Guía de inicio rápido para configurar tu bucket de almacenamiento de MinIO para el {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)". -Asegúrate que tu ID de clave de acceso y secreto de almacenamiento externo de MinIO tenga estos permisos: +## Prerequisites + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -31,9 +33,9 @@ Asegúrate que tu ID de clave de acceso y secreto de almacenamiento externo de M - `s3:DeleteObject` - `s3:ListBucket` -## Habilitar el {% data variables.product.prodname_registry %} con el almacenamiento externo de MinIO +## Enabling {% data variables.product.prodname_registry %} with MinIO external storage -Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. También debes tomar en cuenta que el almacenamiento de objetos de MinIO es compatible con la API de S3 y puedes ingresar los detalles del bucket de MinIO en vez de aquellos de AWS S3. +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -41,16 +43,16 @@ Although MinIO does not currently appear in the user interface under "Package St {% data reusables.package_registry.enable-enterprise-github-packages %} {% ifversion ghes %} -1. Debajo de "Almacenamiento de Paquetes", selecciona **Amazon S3**. -1. Ingresa tus detalles de bucket de almacenamiento de MinIO en la configuración de almacenamiento de AWS. - - **AWS Service URL:** La URL de hospedaje para tu bucket de MinIO. - - **AWS S3 Bucket:** El nombre de tu bucket de MinIO compatible con S3 dedicado para el {% data variables.product.prodname_registry %}. - - **AWS S3 Access Key** y **AWS S3 Secret Key**: Ingresa la ID de clave de acceso y clave secreta de MinIO para acceder a tu bucket. +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. - ![Cajas de entrada para los detalles de tu bucket de AWS S3](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} -## Pasos siguientes +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 471aeac372..8a68e62c4f 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,36 +14,46 @@ topics: - Administrator - Enterprise - Organizations -shortTitle: Agregar organizaciones +shortTitle: Add organizations --- -## Acerca de las organizaciones +## About organizations -Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. Para obtener más información, consulta "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings. -## Crear una organización en tu cuenta de empresa +You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -Las organizaciones nuevas que crees dentro de los parámetros de la cuenta de empresa se incluyen en la suscripción de la cuenta de empresa de {% data variables.product.prodname_ghe_cloud %}. +## Creating an organization in your enterprise account -Los propietarios de empresas que creen una organización que es propiedad de una cuenta de empresa se convierten automáticamente en los propietarios de la organización. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +New organizations you create within your enterprise account settings are included in your enterprise account's {% data variables.product.prodname_ghe_cloud %} subscription. + +Enterprise owners who create an organization owned by the enterprise account automatically become organization owners. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% data reusables.enterprise-accounts.access-enterprise %} -2. En la pestaña **Organizations** (Organizaciones), encima de la lista d elas organizaciones, haz clic en **New organization** (Organización nueva). ![Botón de la nueva organización](/assets/images/help/business-accounts/enterprise-account-add-org.png) -3. En "Organization name" (Nombre de la organización) escribe un nombre para tu organización. ![Campo para escribir el nombre de una organización nueva](/assets/images/help/business-accounts/new-organization-name-field.png) -4. Haz clic en **Create organization** (Crear organización). -5. En "Invite owners" (Invitar propietarios), escribe el nombre de usuario de una persona a la que te gustaría invitar para convertir en propietario de la organización, luego clic en **Invite** (Invitar). ![Campo de búsqueda del propietario de la organización y botón Invite (Invitar)](/assets/images/help/business-accounts/invite-org-owner.png) -6. Da clic en **Finalizar**. +2. On the **Organizations** tab, above the list of organizations, click **New organization**. + ![New organization button](/assets/images/help/business-accounts/enterprise-account-add-org.png) +3. Under "Organization name", type a name for your organization. + ![Field to type a new organization name](/assets/images/help/business-accounts/new-organization-name-field.png) +4. Click **Create organization**. +5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**. + ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png) +6. Click **Finish**. -## Invitar a una organización para que se una a tu cuenta empresarial +## Inviting an organization to join your enterprise account -Los propietarios de las empresas pueden invitar a las organizaciones existentes para que se unan a su cuenta empresarial. Si la organización que quieres invitar ya pertenece a otra empresa, no podrás emitir una invitación hasta que la empresa anterior deje la propiedad de esta. +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. {% data reusables.enterprise-accounts.access-enterprise %} -2. En la pestaña **Organizaciones**, sobre la lista de las organizaciones, haz clic en **Invitar organización**. ![Invitar a una organización](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) -3. Debajo de "Nombre de organización", comienza a teclear el nombre de la organización que quieras invitar y selecciónalo cuando se muestre en la lista desplegable. ![Buscar una organización](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) -4. Haz clic en **Invitar organización**. -5. Los propietarios de la organización recibirán un mensaje de correo electrónico invitándolos a unirse a la organización. Por lo menos el propietario necesita aceptar la invitación antes de que el proceso pueda continuar. Puedes cancelar o reenviar la invitación en cualquier momento antes de que un propietario la apruebe. ![Cancelar o reenviar](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) -6. Una vez que un propietario de la organización haya aprobado la invitación, puedes ver su estado en la lista de invitaciones pendientes. ![Invitación pendiente](/assets/images/help/business-accounts/enterprise-account-pending.png) -7. Haz clic en **Aprobar** para completar la transferencia o en **Cancelar** para cancelarla. ![Aprobar invitación](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. +![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. +![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. +![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. +![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. +![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md index 5b44b22eb7..52334965f2 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md @@ -1,6 +1,6 @@ --- -title: Crear equipos -intro: 'Los equipos les permiten a las organizaciones crear grupos de miembros y controlar el acceso a los repositorios. A los miembros del equipo se les pueden otorgar permisos de lectura, escritura o administración para repositorios específicos.' +title: Creating teams +intro: 'Teams give organizations the ability to create groups of members and control access to repositories. Team members can be granted read, write, or admin permissions to specific repositories.' redirect_from: - /enterprise/admin/user-management/creating-teams - /admin/user-management/creating-teams @@ -13,16 +13,15 @@ topics: - Teams - User account --- +Teams are central to many of {% data variables.product.prodname_dotcom %}'s collaborative features, such as team @mentions to notify appropriate parties that you'd like to request their input or attention. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -Los equipos son centrales para muchas de las características colaborativas de {% data variables.product.prodname_dotcom %}, como las @menciones del equipo para notificar a las partes correspondientes que les quieres solicitar su colaboración o atención. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +A team can represent a group within your company or include people with certain interests or expertise. For example, a team of accessibility experts on {% data variables.product.product_location %} could comprise of people from several different departments. Teams can represent functional concerns that complement a company's existing divisional hierarchy. -Un equipo puede representar a un grupo dentro de tu empresa o incluir personas con ciertos intereses o experiencia. Por ejemplo, un equipo de expertos en accesibilidad en {% data variables.product.product_location %} podría estar compuesto por personas de diferentes departamentos. Los equipos pueden representar inquietudes de carácter funcional que complementan la jerarquía divisional existente de una empresa. +Organizations can create multiple levels of nested teams to reflect a company or group's hierarchy structure. For more information, see "[About teams](/enterprise/{{ currentVersion }}/user/articles/about-teams/#nested-teams)." -Las organizaciones pueden crear varios niveles de equipos anidados para reflejar la estructura de jerarquía de una empresa o grupo. Para obtener más información, consulta "[Acerca de los equipos](/enterprise/{{ currentVersion }}/user/articles/about-teams/#nested-teams)". +## Creating a team -## Crear un equipo - -Una combinación prudente de equipos es una manera eficaz de controlar el acceso a los repositorios. Por ejemplo, si tu organización solo permite que tu equipo de ingeniería en lanzamientos suba código a la rama predeterminada de cualquier repositorio, puedes otorgar únicamente a este equipo el permiso de **administrador** para los repositorios de tu organización y darle al resto de los equipos permisos de **lectura**. +A prudent combination of teams is a powerful way to control repository access. For example, if your organization allows only your release engineering team to push code to the default branch of any repository, you could give only the release engineering team **admin** permissions to your organization's repositories and give all other teams **read** permissions. {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} @@ -33,27 +32,30 @@ Una combinación prudente de equipos es una manera eficaz de controlar el acceso {% data reusables.organizations.create-team-choose-parent %} {% data reusables.organizations.create_team %} -## Crear equipos con la sincronización LDAP activada +## Creating teams with LDAP Sync enabled -Las instancias que usan LDAP para la autenticación de usuarios pueden usar la sincronización LDAP para administrar los miembros de un equipo. Al poner el **Nombre Distintivo** (DN) del grupo en el campo **LDAP group** (Grupo LDAP), se le asignará un equipo a un grupo LDAP en tu servidor LDAP. Si usas la sincronización LDAP para administrar los miembros de un equipo, no podrás administrar tu equipo dentro de {% data variables.product.product_location %}. Cuando la sincronización LDAP está activada, el equipo asignado sincroniza sus miembros en segundo plano de manera periódica con el intervalo configurado. Para obtener más información, consulta "[Activar sincronización LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". +Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.product.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." + +You must be a site admin and an organization owner to create a team with LDAP sync enabled. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% warning %} -**Notas:** -- La sincronización LDAP solo administra la lista de miembros del equipo. Debes administrar los permisos y repositorios del equipo desde dentro del {% data variables.product.prodname_ghe_server %}. -- Si se elimina un grupo LDAP asignado a un DN, o si se borra un grupo LDAP, todos los miembros se eliminan del equipo sincronizado del {% data variables.product.prodname_ghe_server %}. Para solucionar esto, asigna el equipo a un nuevo DN, vuelve a agregar a los miembros del equipo y [sincroniza de forma manual la asignación](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#manually-syncing-ldap-accounts). -- Si se elimina a una persona de un repositorio cuando la sincronización LDAP está activada, perderá el acceso, pero sus bifurcaciones no se borrarán. Si se agrega a esa persona a un equipo con acceso al repositorio original de la organización dentro de los tres meses posteriores, en la siguiente sincronización, se reestablecerá automáticamente su acceso a las bifurcaciones. +**Notes:** +- LDAP Sync only manages the team's member list. You must manage the team's repositories and permissions from within {% data variables.product.prodname_ghe_server %}. +- If an LDAP group mapping to a DN is removed, such as if the LDAP group is deleted, then every member is removed from the synced {% data variables.product.prodname_ghe_server %} team. To fix this, map the team to a new DN, add the team members back, and [manually sync the mapping](/enterprise/admin/authentication/using-ldap#manually-syncing-ldap-accounts). +- When LDAP Sync is enabled, if a person is removed from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync. {% endwarning %} -1. Asegúrate de que [La sincronización LDAP esté activada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync). +1. Ensure that [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync). {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} -6. Busca el DN de un grupo LDAP al que asignar el equipo. Si no conoces el DN, escribe el nombre del grupo LDAP. El {% data variables.product.prodname_ghe_server %} buscará y completará automáticamente cualquier coincidencia. ![Asignar al DN del grupo LDAP](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) +6. Search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches. +![Mapping to the LDAP group DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) {% data reusables.organizations.team_description %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create-team-choose-parent %} diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md index d85eef03dd..f7a55c64ba 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Auditar a los usuarios a lo largo de tu empresa -intro: 'El tablero de bitácoras de auditoría muestra a los administradores de sitio las acciones que realizan todos los usuarios y organizaciones en toda la empresa durante los últimos 90 días, incluyendo detalles tales como quién realizó la acción, de qué acción se trata, y cuándo se llevó a cabo.' +title: Auditing users across your enterprise +intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. The audit log includes details such as who performed the action, what the action was, and when the action was performed.' redirect_from: - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/ - /enterprise/admin/user-management/auditing-users-across-your-instance @@ -16,105 +16,104 @@ topics: - Organizations - Security - User account -shortTitle: Auditar usuarios +shortTitle: Audit users --- +## Accessing the audit log -## Acceder al registro de auditoría +The audit log dashboard gives you a visual display of audit data across your enterprise. -El tablero de bitácoras de auditoría te proporciona una presentación visual de los datos de auditoría a lo largo de tu empresa. - -![Tablero de registro de auditoría en toda la instancia](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) +![Instance wide audit log dashboard](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -Dentro del mapa, puedes usar panorámica y zoom para ver eventos en todo el mundo. Mantén el puntero sobre un país para ver un recuento rápido de los eventos de ese país. +Within the map, you can pan and zoom to see events around the world. Hover over a country to see a quick count of events from that country. -## Buscar eventos a través de tu empresa +## Searching for events across your enterprise -La bitácora de auditoría lista la siguiente información sobre las acciones que se llevan a cabo dentro de tu empresa: +The audit log lists the following information about actions made within your enterprise: -* [El repositorio](#search-based-on-the-repository) en el cual una acción fue realizada. -* [El usuario](#search-based-on-the-user) que realizó la acción. -* [La organización](#search-based-on-the-organization) a la cual pertenece la acción. -* [La acción](#search-based-on-the-action-performed) que fue realizada. -* [El país](#search-based-on-the-location) en el que la acción fue realizada. -* [La fecha y la hora](#search-based-on-the-time-of-action) en que ocurrió la acción. +* [The repository](#search-based-on-the-repository) an action was performed in +* [The user](#search-based-on-the-user) who performed the action +* [Which organization](#search-based-on-the-organization) an action pertained to +* [The action](#search-based-on-the-action-performed) that was performed +* [Which country](#search-based-on-the-location) the action took place in +* [The date and time](#search-based-on-the-time-of-action) the action occurred {% warning %} -**Notas:** +**Notes:** -- Si bien no puedes utilizar texto para buscar entradas de auditoría, puedes crear consultas de búsqueda usando una variedad de filtros. {% data variables.product.product_name %} es compatible con muchos operadores para hacer búsquedas a través de {% data variables.product.product_name %}. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". -- Para buscar eventos de más de 90 días, usa el calificador `created`. +- While you can't use text to search for audit entries, you can construct search queries using a variety of filters. {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)." +- Audit records are available for the current month and every day of the previous six months. {% endwarning %} -### Búsqueda basada en el repositorio +### Search based on the repository -El calificador `repo` limita las acciones a un repositorio específico que le pertenece a tu organización. Por ejemplo: +The `repo` qualifier limits actions to a specific repository owned by your organization. For example: -* `repo:my-org/our-repo` encuentra todos los eventos que ocurrieron para el repositorio `our-repo` en la organización `my-org`. -* `repo:my-org/our-repo repo:my-org/another-repo` encuentra todos los eventos que ocurrieron tanto para los repositorios `our-repo` como `another-repo` en la organización `my-org`. -* `-repo:my-org/not-this-repo` excluye todos los eventos que ocurrieron para el repositorio `not-this-repo` en la organización `my-org`. +* `repo:my-org/our-repo` finds all events that occurred for the `our-repo` repository in the `my-org` organization. +* `repo:my-org/our-repo repo:my-org/another-repo` finds all events that occurred for both the `our-repo` and `another-repo` repositories in the `my-org` organization. +* `-repo:my-org/not-this-repo` excludes all events that occurred for the `not-this-repo` repository in the `my-org` organization. -Debes incluir el nombre de tu organización dentro del calificador `repo`; si buscas solo `repo:our-repo` no funcionará. +You must include your organization's name within the `repo` qualifier; searching for just `repo:our-repo` will not work. -### Búsqueda basada en el usuario +### Search based on the user -El calificador `actor` examina eventos basados en el miembro de tu organización que realizó la acción. Por ejemplo: +The `actor` qualifier scopes events based on the member of your organization that performed the action. For example: -* `actor:octocat` encuentra todos los eventos realizados por `octocat`. -* `actor:octocat actor:hubot` encuentra todos los eventos realizados tanto por `octocat` como por `hubot`. -* `-actor:hubot` excluye todos los eventos realizados por `hubot`. +* `actor:octocat` finds all events performed by `octocat`. +* `actor:octocat actor:hubot` finds all events performed by both `octocat` and `hubot`. +* `-actor:hubot` excludes all events performed by `hubot`. -Solo puedes usar un nombre de usuario {% data variables.product.product_name %}, no el nombre real de un individuo. +You can only use a {% data variables.product.product_name %} username, not an individual's real name. -### Búsqueda basada en la organización +### Search based on the organization -El calificador `org` limita las acciones a una organización específica. Por ejemplo: +The `org` qualifier limits actions to a specific organization. For example: -* `org:my-org` encuentra todos los eventos que ocurrieron para la organización `my-org`. -* `org:my-org action:team` encuentra todos los eventos del equipo realizados dentro de la organización `my-org`. -* `-org:my-org` excluye todos los eventos que ocurrieron para la organización `my-org`. +* `org:my-org` finds all events that occurred for the `my-org` organization. +* `org:my-org action:team` finds all team events performed within the `my-org` organization. +* `-org:my-org` excludes all events that occurred for the `my-org` organization. -### Búsqueda basada en la acción realizada +### Search based on the action performed -El calificador `action` busca los eventos específicos, agrupados dentro de categorías. Para obtener más información sobre los eventos asociados con estas categorías, consulta la sección "[Acciones auditadas](/admin/user-management/audited-actions)". +The `action` qualifier searches for specific events, grouped within categories. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)". -| Nombre de la categoría | Descripción | -| ---------------------- | ----------------------------------------------------------------------------------------------------- | -| `gancho` | Contiene todas las actividades relacionadas con los webhooks. | -| `org` | Contiene todas las actividades relacionadas con los miembros de la organización. | -| `repo` | Contiene todas las actividades relacionadas con los repositorios que le pertenecen a tu organización. | -| `equipo` | Contiene todas las actividades relacionadas con los equipos en tu organización. | +| Category name | Description +|------------------|------------------- +| `hook` | Contains all activities related to webhooks. +| `org` | Contains all activities related organization membership +| `repo` | Contains all activities related to the repositories owned by your organization. +| `team` | Contains all activities related to teams in your organization. -Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: +You can search for specific sets of actions using these terms. For example: -* `action:team` encuentra todos los eventos agrupados dentro de la categoría de equipo. -* `-action:billing` excluye todos los eventos en la categoría de facturación. +* `action:team` finds all events grouped within the team category. +* `-action:billing` excludes all events in the billing category. -Cada categoría tiene un conjunto de eventos asociados con los que puedes filtrar. Por ejemplo: +Each category has a set of associated events that you can filter on. For example: -* `action:team.create` encuentra todos los eventos donde se creó un equipo. -* `-action:billing.change_email` excluye todos los eventos donde se modificó el correo electrónico de facturación. +* `action:team.create` finds all events where a team was created. +* `-action:billing.change_email` excludes all events where the billing email was changed. -### Búsqueda basada en la ubicación +### Search based on the location -El calificador `country` filtra las acciones por el país de origen. -- Puedes utilizar un código corto de dos letras del país o el nombre completo. -- Los países con espacios en sus nombres deben encerrarse entre comillas. Por ejemplo: - * `country:de` encuentra todos los eventos ocurridos en Alemania. - * `country:Mexico` encuentra todos los eventos ocurridos en México. - * `country:"United States"` encuentra todos los eventos que ocurrieron en Estados Unidos. +The `country` qualifier filters actions by the originating country. +- You can use a country's two-letter short code or its full name. +- Countries with spaces in their name must be wrapped in quotation marks. For example: + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. -### Búsqueda basada en la fecha de acción +### Search based on the time of action -El calificador `created` filtra las acciones por la fecha en la que ocurrieron. -- Define fechas usando el formato `YYYY-MM-DD`-- es decir, año, seguido del mes, seguido del día. -- Las fechas admiten [ calificadores mayor que, menor que y rango](/enterprise/{{ currentVersion }}/user/articles/search-syntax). Por ejemplo: - * `created:2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014. - * `created:>=2014-07-01` encuentra todos los eventos ocurridos el 8 de julio de 2014 o posteriormente. - * `created:<=2014-07-01` encuentra todos los eventos ocurridos el 8 de julio de 2014 o anteriormente. - * `created:2014-07-01..2014-07-31` encuentra todos los eventos ocurridos en el mes de julio de 2014. +The `created` qualifier filters actions by the time they occurred. +- Define dates using the format of `YYYY-MM-DD`--that's year, followed by month, followed by day. +- Dates support [greater than, less than, and range qualifiers](/enterprise/{{ currentVersion }}/user/articles/search-syntax). For example: + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-01` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-01` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md index d535417259..477387bd1a 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Administrar los usuarios en tu empresa -intro: Puedes auditar la actividad de los usuarios y administrar sus configuraciones de usuario. +title: Managing users in your enterprise +intro: You can audit user activity and manage user settings. redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ @@ -26,12 +26,12 @@ children: - /viewing-people-in-your-enterprise - /viewing-and-managing-a-users-saml-access-to-your-enterprise - /auditing-users-across-your-enterprise + - /impersonating-a-user - /managing-dormant-users - /suspending-and-unsuspending-users - /placing-a-legal-hold-on-a-user-or-organization - /auditing-ssh-keys - /customizing-user-messages-for-your-enterprise - /rebuilding-contributions-data -shortTitle: Administrar usuarios +shortTitle: Manage users --- - diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index 064ec24f22..d482da22bc 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -1,13 +1,14 @@ --- -title: Administrar usuarios inactivos +title: Managing dormant users redirect_from: - /enterprise/admin/articles/dormant-users/ - /enterprise/admin/articles/viewing-dormant-users/ - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/ - /enterprise/admin/user-management/managing-dormant-users - /admin/user-management/managing-dormant-users -intro: 'Se considera una cuenta de usuario como durmiente si no ha tenido actividad por lo menos en todo un mes.{% ifversion ghes %} Puedes elegir suspender a los usuarios durmientes para liberar licencias de usuario.{% endif %}' +intro: '{% data reusables.enterprise-accounts.dormant-user-activity-threshold %}' versions: + ghec: '*' ghes: '*' ghae: '*' type: how_to @@ -16,38 +17,56 @@ topics: - Enterprise - Licensing --- +{% data reusables.enterprise-accounts.dormant-user-activity %} -"Actividad" incluye, entre otros: -- Iniciar sesión en {% data variables.product.product_name %}. -- Comentar en propuestas y en solicitudes de extracción. -- Crear, eliminar, observar y destacar repositorios. -- Subir confirmaciones.{% ifversion ghes or ghae %} -- Acceder a los recursos utilizando un token de acceso personal o llave de SSH.{% endif %} +{% ifversion ghes or ghae%} +## Viewing dormant users -## Visualizar usuarios inactivos - -Puedes ver una lista de todos los usuarios inactivos que no han sido suspendidos y que no son administradores del sitio. +{% data reusables.enterprise-accounts.viewing-dormant-users %} {% data reusables.enterprise_site_admin_settings.access-settings %} -3. En la barra lateral de la izquierda, haz clic en **Usuarios inactivos**. ![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %} -4. Para suspender todos los usuarios inactivos de esta lista, haz clic en **Suspender todos**, en la parte superior de la página. ![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %} +3. In the left sidebar, click **Dormant users**. +![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %} +4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**. +![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %} -## Determinar si un usuario está inactivo +## Determining whether a user account is dormant {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} -5. En la sección **Información del usuario**, un punto rojo con la palabra "Inactiva" indica que la cuenta del usuario está inactiva, y un punto verde con la palabra "Activa" indica que la cuenta del usuario está activa. ![Cuenta de usuario inactiva](/assets/images/enterprise/stafftools/dormant-user.png) ![Cuenta de usuario activa](/assets/images/enterprise/stafftools/active-user.png) +5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active. +![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png) +![Active user account](/assets/images/enterprise/stafftools/active-user.png) -## Configurar el umbral de inactividad +## Configuring the dormancy threshold {% data reusables.enterprise_site_admin_settings.dormancy-threshold %} {% data reusables.enterprise-accounts.access-enterprise %} -{% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} -{% else %} {% data reusables.enterprise-accounts.settings-tab %} -{% endif %} {% data reusables.enterprise-accounts.options-tab %} -4. En "Umbral de inactividad", usa el menú desplegable y haz clic en el umbral de inactividad deseado. ![Menú desplegable Umbral de inactividad](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png) +4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold. +![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png) + +{% endif %} + +{% ifversion ghec %} + +{% data reusables.enterprise-accounts.dormant-user-release-phase %} + +{% warning %} + +**Note:** During the private beta, ongoing improvements to the report download feature may limit its availability. + +{% endwarning %} + +## Downloading the dormant users report from your enterprise account + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %} +1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**. + ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png) + +{% endif %} diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index a4d207c0d5..477627f28a 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Visualizar a las personas en tu empresa -intro: 'Para auditar el acceso a los recursos que pertenezcan a tu empresa o al uso de licencias de usuario, los propietarios de la empresa pueden ver a cada administrador y miembro de la misma.' +title: Viewing people in your enterprise +intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account @@ -13,31 +13,35 @@ versions: ghae: '*' topics: - Enterprise -shortTitle: Visualizar a las personas en tu empresa +shortTitle: View people in your enterprise --- +## Viewing enterprise owners{% ifversion ghec %} and billing managers{% endif %} -## Visualizar a los propietarios{% ifversion ghec %} y gerentes de facturación de la empresa{% endif %} - -Puedes ver a los propietarios {% ifversion ghec %}y gerentes de facturación de la empresa, {% endif %}así como una lista de invitaciones pendientes para convertirse en propietarios{% ifversion ghec %} y gerentes de facturación. Puedes filtrar la lista de administradores de la empresa por rol{% endif %}. Puedes encontrar una persona específica al buscar por su nombre de usuario o nombre completo. +You can view enterprise owners {% ifversion ghec %} and billing managers, {% endif %}as well as a list of pending invitations to become owners{% ifversion ghec %} and billing managers. You can filter the list of enterprise administrators by role{% endif %}. You can find a specific person by searching for their username or full name. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %} -{% ifversion ghec %}1. Opcionalmente, para ver una lista de invitaciones pendientes, da clic en **_CANTIDAD_ pendientes**. - ![botón de "CANTIDAD pendientes" a la derecha de las opciones de búsqueda y de filtrado](/assets/images/help/enterprises/administrators-pending.png){% endif %} +{% ifversion ghec %}1. Optionally, to view a list of pending invitations, click **_NUMBER_ pending**. + !["NUMBER pending" button to the right of search and filter options](/assets/images/help/enterprises/administrators-pending.png){% endif %} -## Ver miembros y colaboradores externos +## Viewing members and outside collaborators -Puedes ver la cantidad de miembros y colaboradores externos pendientes. Puedes filtrar la lista de miembros por {% ifversion ghec %}despliegue ({% data variables.product.prodname_ghe_cloud %} o {% data variables.product.prodname_ghe_server %}),{% endif %} rol{% ifversion ghec %}, y{% else %} u{% endif %} organización. Puedes filtrar la lista de colaboradores externos por la visibilidad de los repositorios a los que el colaborador tiene acceso. Puedes encontrar una persona específica al buscar por su nombre de usuario o nombre que se muestra. +You can view the number of pending members and outside collaborators. You can filter the list of members by {% ifversion ghec %}deployment ({% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}),{% endif %} role{% ifversion ghec %}, and{% else %} or {% endif %} organization. You can filter the list of outside collaborators by the visibility of the repositories the collaborator has access to. You can find a specific person by searching for their username or display name. -Puedes ver {% ifversion ghec %}todas las organizaciones de {% data variables.product.prodname_ghe_cloud %} e instancias de {% data variables.product.prodname_ghe_server %} a las cuales pertenece un miembro, y {% endif %}a qué repositorios tiene acceso un colaborador externo{% ifversion ghec %}, {% endif %} dand clic en el nombre de una persona. +You can view {% ifversion ghec %}all the {% data variables.product.prodname_ghe_cloud %} organizations and {% data variables.product.prodname_ghe_server %} instances that a member belongs to, and {% endif %}which repositories an outside collaborator has access to{% ifversion ghec %}, {% endif %} by clicking on the person's name. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} -1. De manera opcional, para ver una lista de colaboradores externos en lugar de una lista de miembros, haz clic en **Outside collaborators (Colaboradores externos)**. ![Pestaña de colaboradores externos en la página de miembros de la organización](/assets/images/help/business-accounts/outside-collaborators-tab.png) -{% ifversion ghec %}1. Opcionalmente, para ver una lista de invitaciones pendientes, da clic en **_CANTIDAD_ pendientes**. - ![botón de "CANTIDAD pendientes" a la derecha de las opciones de búsqueda y de filtrado](/assets/images/help/enterprises/members-pending.png){% endif %} +1. Optionally, to view a list of outside collaborators rather than the list of members, click **Outside collaborators**. + ![Outside collaborators tab on the Organization members page](/assets/images/help/business-accounts/outside-collaborators-tab.png) +{% ifversion ghec %}1. Optionally, to view a list of pending invitations, click **_NUMBER_ pending**. + !["NUMBER pending" button to the right of search and filter options](/assets/images/help/enterprises/members-pending.png){% endif %} -## Leer más +## Viewing dormant users -- "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" +You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)." + +## Further reading + +- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md index d39cb84767..7154212cf8 100644 --- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md @@ -1,6 +1,6 @@ --- -title: Exportar datos de migración desde GitHub.com -intro: 'Puedes exportar los dtos de migración desde una organización en {% data variables.product.prodname_dotcom_the_website %} si utilizas la API para seleccionar los repositorios que deseas migrar y luego generas un archivo de migración que puedas importar en una instancia de {% data variables.product.prodname_ghe_server %}.' +title: Exporting migration data from GitHub.com +intro: 'You can export migration data from an organization on {% data variables.product.prodname_dotcom_the_website %} by using the API to select repositories to migrate, then generating a migration archive that you can import into a {% data variables.product.prodname_ghe_server %} instance.' redirect_from: - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com - /enterprise/admin/migrations/exporting-migration-data-from-githubcom @@ -17,76 +17,75 @@ topics: - API - Enterprise - Migration -shortTitle: Exportar datos desde GitHub.com +shortTitle: Export data from GitHub.com --- +## Preparing the source organization on {% data variables.product.prodname_dotcom %} -## Preparar la orgnanización origen en {% data variables.product.prodname_dotcom %} +1. Ensure that you have [owner permissions](/articles/permission-levels-for-an-organization/) on the source organization's repositories. -1. Asegúrate de tener [permisos de propietario](/articles/permission-levels-for-an-organization/) en los repositorios de la organización de origen. - -2. {% data reusables.enterprise_migrations.token-generation %} en {% data variables.product.prodname_dotcom_the_website %}. +2. {% data reusables.enterprise_migrations.token-generation %} on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise_migrations.make-a-list %} -## Exportar los repositorios de la organización +## Exporting the organization's repositories {% data reusables.enterprise_migrations.fork-persistence %} -Para exportar datos del repositorio desde {% data variables.product.prodname_dotcom_the_website %}, usa la API de Migraciones. +To export repository data from {% data variables.product.prodname_dotcom_the_website %}, use the Migrations API. -La API de Migraciones se encuentra actualmente en un período de previsualización, lo que significa que los puntos finales y los parámetros pueden cambiar en el futuro. Para acceder a la API de Migraciones, debes proporcionar un [tipo de medio](/rest/overview/media-types) personalizado en el encabezado `Accept` (Aceptar): `application/vnd.github.wyandotte-preview+json`. Los ejemplos a continuación incluyen el tipo de medio personalizado. +The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future. To access the Migrations API, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: `application/vnd.github.wyandotte-preview+json`. The examples below include the custom media type. -## Generar un archivo de migración +## Generating a migration archive {% data reusables.enterprise_migrations.locking-repositories %} -1. Notifica a los miembros de tu organización que harás una migración. La exportación puede durar varios minutos, en función de la cantidad de repositorios que se exporten. La migración completa, incluida la importación, puede durar varias horas. Por lo tanto, te recomendamos que hagas una prueba para determinar cuánto tiempo tomará el proceso completo. Para obtener más información, consulta "[Acerca de las migraciones](/enterprise/admin/migrations/about-migrations#types-of-migrations)". +1. Notify members of your organization that you'll be performing a migration. The export can take several minutes, depending on the number of repositories being exported. The full migration including import may take several hours so we recommend doing a trial run in order to determine how long the full process will take. For more information, see "[About Migrations](/enterprise/admin/migrations/about-migrations#types-of-migrations)." -2. Inicia una migración enviando una solicitud de `POST` a la terminal de migración. Necesitarás: - * Tu token de acceso para autenticación. - * Una [lista de los repositorios](/rest/reference/repos#list-organization-repositories) que deseas migrar: +2. Start a migration by sending a `POST` request to the migration endpoint. You'll need: + * Your access token for authentication. + * A [list of the repositories](/rest/reference/repos#list-organization-repositories) you want to migrate: ```shell - curl -H "Autorización: token GITHUB_ACCESS_TOKEN" -X POST \ - -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \ + -H "Accept: application/vnd.github.wyandotte-preview+json" \ -d'{"lock_repositories":true,"repositories":["orgname/reponame", "orgname/reponame"]}' \ https://api.github.com/orgs/orgname/migrations ``` - * Si deseas bloquear los repositorios antes de migrarlos, asegúrate de que `lock_repositories`esté establecido en `true` (true). Esto es altamente recomendable. - * Puedes excluir archivos adjuntos pasando `exclude_attachments: true` al punto final. {% data reusables.enterprise_migrations.exclude-file-attachments %} El tamaño final del archivo debe ser inferior a 20 GB. + * If you want to lock the repositories before migrating them, make sure `lock_repositories` is set to `true`. This is highly recommended. + * You can exclude file attachments by passing `exclude_attachments: true` to the endpoint. {% data reusables.enterprise_migrations.exclude-file-attachments %} The final archive size must be less than 20 GB. - Esta solicitud devuelve un `id` único que representa tu migración. Lo necesitarás para solicitudes posteriores a la API de Migraciones. + This request returns a unique `id` which represents your migration. You'll need it for subsequent calls to the Migrations API. -3. Envía una solicitud de `GET` al punto final del estado de la migración para extraer el estado de una migración. Necesitarás: - * Tu token de acceso para autenticación. - * El `id` único de la migración: +3. Send a `GET` request to the migration status endpoint to fetch the status of a migration. You'll need: + * Your access token for authentication. + * The unique `id` of the migration: ```shell - curl -H "Autorización: token GITHUB_ACCESS_TOKEN" \ - -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \ + -H "Accept: application/vnd.github.wyandotte-preview+json" \ https://api.github.com/orgs/orgname/migrations/id ``` - Una migración puede estar en uno de los siguientes estados: - * `pending` (pendiente), lo que significa que la migración aún no se ha iniciado. - * `exporting` (exportando), lo que significa que la migración está en curso. - * `exported` (exportada), lo que significa que la migración finalizó correctamente. - * `failed` (fallida), lo que significa que la migración falló. + A migration can be in one of the following states: + * `pending`, which means the migration hasn't started yet. + * `exporting`, which means the migration is in progress. + * `exported`, which means the migration finished successfully. + * `failed`, which means the migration failed. -4. Una vez que se haya exportado tu migración, descarga el archivo de migración enviando una solicitud de `GET` al punto final de descarga de migración. Necesitarás: - * Tu token de acceso para autenticación. - * El `id` único de la migración: +4. After your migration has exported, download the migration archive by sending a `GET` request to the migration download endpoint. You'll need: + * Your access token for authentication. + * The unique `id` of the migration: ```shell - curl -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ - -u GITHUB_USERNAME:GITHUB_ACCESS_TOKEN \ + curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \ + -H "Accept: application/vnd.github.wyandotte-preview+json" \ -L -o migration_archive.tar.gz \ https://api.github.com/orgs/orgname/migrations/id/archive ``` -5. El archivo de migración se elimina automáticamente después de siete días. Si prefieres eliminarlo antes, puedes enviar una solicitud `DELETE` al punto final de eliminación del archivo de migración. Necesitarás: - * Tu token de acceso para autenticación. - * El `id` único de la migración: +5. The migration archive is automatically deleted after seven days. If you would prefer to delete it sooner, you can send a `DELETE` request to the migration archive delete endpoint. You'll need: + * Your access token for authentication. + * The unique `id` of the migration: ```shell - curl -H "Autorización: token GITHUB_ACCESS_TOKEN" -X DELETE \ - -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ + -H "Accept: application/vnd.github.wyandotte-preview+json" \ https://api.github.com/orgs/orgname/migrations/id/archive ``` {% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md index 39e225bd8d..60bb98cb33 100644 --- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md +++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md @@ -1,6 +1,6 @@ --- -title: Acciones auditadas -intro: Puedes buscar el registro de auditoría para una gran variedad de acciones. +title: Audited actions +intro: You can search the audit log for a wide variety of actions. miniTocMaxHeadingLevel: 3 redirect_from: - /enterprise/admin/articles/audited-actions/ @@ -17,20 +17,27 @@ topics: - Security --- -## Autenticación +## Authentication -| Acción | Descripción | -| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | -| `oauth_access.create` | Un [Token de acceso de OAuth][] fue [generado][generate token] para la cuenta de un usuario. | -| `oauth_access.destroy` | Un [Token de acceso de OAuth][] se eliminó de la cuenta de un usuario. | -| `oauth_application.destroy` | Una [Aplicación de OAuth][] se eliminó de la cuenta de un usuario o de una organización. | -| `oauth_application.reset_secret` | Se restableció una [clave secreta de una aplicación de OAuth][]. | -| `oauth_application.transfer` | Una [aplicación de OAuth][] se transfirió de una cuenta de usuario o de organización a otra. | -| `public_key.create` | Una clave SSH se [agregó][add key] a una cuenta de usuario o una [llave de implementación][] se agregó a un repositorio. | -| `public_key.delete` | Una clave SSH se eliminó de una cuenta de usuario o una [llave de implementación][] se eliminó de un repositorio. | -| `public_key.update` | Se actualizó una llave SSH de una cuenta de usuario o una [llave de despliegue][] de un repositorio.{% ifversion ghes %} -| `two_factor_authentication.enabled` | [Se habilitó la autenticación de dos factores][2fa] para una cuenta de usuario. | -| `two_factor_authentication.disabled` | Se inhabilitó la [Autenticación bifactorial][2fa] para una cuenta de usuario.{% endif %} +Action | Description +------------------------------------ | ---------------------------------------- +`oauth_access.create` | An [OAuth access token][] was [generated][generate token] for a user account. +`oauth_access.destroy` | An [OAuth access token][] was deleted from a user account. +`oauth_application.destroy` | An [OAuth application][] was deleted from a user or organization account. +`oauth_application.reset_secret` | An [OAuth application][]'s secret key was reset. +`oauth_application.transfer` | An [OAuth application][] was transferred from one user or organization account to another. +`public_key.create` | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository. +`public_key.delete` | An SSH key was removed from a user account or a [deploy key][] was removed from a repository. +`public_key.update` | A user account's SSH key or a repository's [deploy key][] was updated.{% ifversion ghes %} +`two_factor_authentication.enabled` | [Two-factor authentication][2fa] was enabled for a user account. +`two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %} + + [add key]: /articles/adding-a-new-ssh-key-to-your-github-account + [deploy key]: /guides/managing-deploy-keys/#deploy-keys + [generate token]: /articles/creating-an-access-token-for-command-line-use + [OAuth access token]: /developers/apps/authorizing-oauth-apps + [OAuth application]: /guides/basics-of-authentication/#registering-your-app + [2fa]: /articles/about-two-factor-authentication {% ifversion ghes %} ## {% data variables.product.prodname_actions %} @@ -39,153 +46,159 @@ topics: {% endif %} -## Ganchos +## Hooks -| Acción | Descripción | -| --------------------- | --------------------------------------------------- | -| `hook.create` | Se agregó un enlace nuevo a un repositorio. | -| `hook.config_changed` | Se cambió la configuración de un enlace. | -| `hook.destroy` | Se eliminó un enlace. | -| `hook.events_changed` | Se cambiaron los eventos configurados de un enlace. | +Action | Description +--------------------------------- | ------------------------------------------- +`hook.create` | A new hook was added to a repository. +`hook.config_changed` | A hook's configuration was changed. +`hook.destroy` | A hook was deleted. +`hook.events_changed` | A hook's configured events were changed. -## Configuración de ajustes de empresa +## Enterprise configuration settings -| Acción | Descripción | -| ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes > 3.0 or ghae-next %} -| `business.advanced_security_policy_update` | Un adminsitrador de sitio crea, actualiza o elimina una política para la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".{% endif %} -| `business.clear_members_can_create_repos` | Un administrador de sitio elimina una restricción para la creación de repositorios en las organizciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes > 3.1 %} -| `business.referrer_override_enable` | Un administrador de sitio habilita la anulación de la política del referente. Para obtener más información, consulta la sección "[Configurar la política del referente para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)". | -| `business.referrer_override_disable` | Un administrador de sitio inhabilita la anulación de la política del referente. Para obtener más información, consulta la sección "[Configurar la política del referente para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".{% endif %} -| `business.update_member_repository_creation_permission` | Un administrador de sitio restringe la creación de repositorios en las organizaciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes %} -| `enterprise.config.lock_anonymous_git_access` | Un administrador de sitio bloquea el acceso de lectura anónima a Git para prevenir que los administradores de repositorio cambien dicha configuración para los repositorios de la empresa. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | -| `enterprise.config.unlock_anonymous_git_access` | Un administrador de sitio desbloquea el acceso de lectura anónima a Git para permitir que los administradores de repositorio cambien dicha configuración en los repositorios de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)".{% endif %} +Action | Description +----------------------------------------------- | -------------------------------------------{% ifversion ghes > 3.0 or ghae-next %} +`business.advanced_security_policy_update` | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."{% endif %} +`business.clear_members_can_create_repos` | A site admin clears a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes > 3.1 %} +`business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." +`business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %} +`business.update_member_repository_creation_permission` | A site admin restricts repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes %} +`enterprise.config.lock_anonymous_git_access` | A site admin locks anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." +`enterprise.config.unlock_anonymous_git_access` | A site admin unlocks anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %} {% ifversion ghae %} -## Listas de IP permitidas +## IP allow lists -| Nombre | Descripción | -| ------------------------------------------:| ----------------------------------------------------------------------------------------------------------------- | -| `ip_allow_list_entry.create` | Se agregó una dirección IP a una lista de IP permitidas. | -| `ip_allow_list_entry.update` | Se cambió una dirección IP o su descripción. | -| `ip_allow_list_entry.destroy` | Se borró una dirección IP de una lista de IP permitidas. | -| `ip_allow_list.enable` | Se habilitó una lista de IP permitidas. | -| `ip_allow_list.enable_for_installed_apps` | Se habilitó una lista de IP permitidas para las {% data variables.product.prodname_github_apps %} instaladas. | -| `ip_allow_list.disable` | Se inhabilitó una lista de IP permitidas. | -| `ip_allow_list.disable_for_installed_apps` | Se inhabilitó una lista de IP permitidas para las {% data variables.product.prodname_github_apps %} instaladas. | +Name | Description +------------------------------------:| ----------------------------------------------------------- +`ip_allow_list_entry.create` | An IP address was added to an IP allow list. +`ip_allow_list_entry.update` | An IP address or its description was changed. +`ip_allow_list_entry.destroy` | An IP address was deleted from an IP allow list. +`ip_allow_list.enable` | An IP allow list was enabled. +`ip_allow_list.enable_for_installed_apps` | An IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. +`ip_allow_list.disable` | An IP allow list was disabled. +`ip_allow_list.disable_for_installed_apps` | An IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. {% endif %} -## Problemas +## Issues -| Acción | Descripción | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `issue.update` | Cambió el texto del cuerpo de un problema (comentario inicial). | -| `issue_comment.update` | Cambió un comentario sobre un problema (diferente al inicial). | -| `issue.destroy` | Se eliminó un problema del repositorio. Para obtener más información, consulta la sección "[Borrar una propuesta](/github/managing-your-work-on-github/deleting-an-issue)". | +Action | Description +------------------------------------ | ----------------------------------------------------------- +`issue.update` | An issue's body text (initial comment) changed. +`issue_comment.update` | A comment on an issue (other than the initial one) changed. +`issue.destroy` | An issue was deleted from the repository. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)." -## Organizaciones +## Organizations -| Acción | Descripción | -| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org.async_delete` | Un usuario inició una tarea en segundo plano para eliminar una organización. | -| `org.delete` | Un job en segundo plano que inició un usuario ocasionó que una organización se borrara.{% ifversion not ghae %} -| `org.transform` | Una cuenta de usuario se convirtió en una organización. Para obtener más información, consulta la sección "[Convertir a un usuario en una organización](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)".{% endif %} +Action | Description +------------------ | ---------------------------------------------------------- +`org.async_delete` | A user initiated a background job to delete an organization. +`org.delete` | An organization was deleted by a user-initiated background job.{% ifversion not ghae %} +`org.transform` | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %} -## Solicitudes de cambios +## Pull requests -| Acción | Descripción| | :- | :- |{% ifversion ghes > 3.1 or ghae-next %} | `pull_request.create` | Se creó una solicitud de cambios. Para obtener más información, consulta la sección"[Crear una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.close` | Se cerró una solicitud de cambios sin haberse fusionado. Para obtener más información, consulta la sección "[Cerrar una solicitud de cambios](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)". | | `pull_request.reopen` | Se volvió a abrir una solicitud de cambios después de haberla cerrado previamente. | | `pull_request.merge` | Se fusionó una solicitud de cambios. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". | | `pull_request.indirect_merge` | Se consideró a una solicitud de cambios como fusionada porque las confirmaciones de esta se fusionaron en la rama destino. | | `pull_request.ready_for_review` | Se marcó a una solicitud de cambios como lista para revisión. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)". | | `pull_request.converted_to_draft` | Se convirtió a una solicitud de cambios en borrador. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)". | | `pull_request.create_review_request` | Se solicitó una revisión en una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.remove_review_request` | Se eliminó una solicitud de revisión de una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.submit` | Se emitió una revisión para una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.dismiss` | Se descartó una revisión en una solicitud de cambios. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | | `pull_request_review.delete` | Se eliminó una revisión en una solicitud de cambios. | | `pull_request_review_comment.create` | Se agregó un comentario de revisión a una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review_comment.update` | Se cambió un comentario de revisión en una solicitud de cambios. |{% endif %} | `pull_request_review_comment.delete` | Se borró un comentario de revisión en una solicitud de cambios. | +| Action | Description | +| :- | :- |{% ifversion ghes > 3.1 or ghae-next %} +| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | +| `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | +| `pull_request.reopen` | A pull request was reopened after previously being closed. | +| `pull_request.merge` | A pull request was merged. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." | +| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | +| `pull_request.ready_for_review` | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)." | +| `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." | +| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request_review.submit` | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." | +| `pull_request_review.delete` | A review on a pull request was deleted. | +| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %} +| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. | -## Ramas protegidas +## Protected branches -| Acción | Descripción | -| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ | -| `protected_branch.create` | La protección de rama está habilitada para una rama. | -| `protected_branch.destroy` | La protección de rama está inhabilitada para una rama. | -| `protected_branch.update_admin_enforced` | La protección de rama es obligatoria para los administradores de repositorios. | -| `protected_branch.update_require_code_owner_review` | Se atualiza la imposición de las revisiones requeridas de los propietarios del código en una rama. | -| `protected_branch.dismiss_stale_reviews` | El cumplimiento de las solicitudes de extracción en espera descartadas está actualizado para una rama. | -| `protected_branch.update_signature_requirement_enforcement_level` | El cumplimiento de la firma de confirmación obligatoria está actualizado para una rama. | -| `protected_branch.update_pull_request_reviews_enforcement_level` | El cumplimiento de la revisión obligatoria de solicitud de extracción está actualizado para una rama. | -| `protected_branch.update_required_status_checks_enforcement_level` | El cumplimiento de las verificaciones de estado obligatorias está actualizado para una rama. | -| `protected_branch.rejected_ref_update` | Se rechaza el intento de actualización de una rama. | -| `protected_branch.policy_override` | Un administrador de repositorios anula el requisito de protección de una rama. | +Action | Description +-------------------------- | ---------------------------------------------------------- +`protected_branch.create ` | Branch protection is enabled on a branch. +`protected_branch.destroy` | Branch protection is disabled on a branch. +`protected_branch.update_admin_enforced ` | Branch protection is enforced for repository administrators. +`protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review is updated on a branch. +`protected_branch.dismiss_stale_reviews ` | Enforcement of dismissing stale pull requests is updated on a branch. +`protected_branch.update_signature_requirement_enforcement_level ` | Enforcement of required commit signing is updated on a branch. +`protected_branch.update_pull_request_reviews_enforcement_level ` | Enforcement of required pull request reviews is updated on a branch. +`protected_branch.update_required_status_checks_enforcement_level ` | Enforcement of required status checks is updated on a branch. +`protected_branch.rejected_ref_update ` | A branch update attempt is rejected. +`protected_branch.policy_override ` | A branch protection requirement is overridden by a repository administrator. -## Repositorios +## Repositories -| Acción | Descripción | -| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.access` | La visbilidad de un repositorio cambió a privado{% ifversion ghes %}, público,{% endif %} o interno. | -| `repo.archived` | Se archivó un repositorio. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | -| `repo.add_member` | Se agregó un colaborador a un repositorio. | -| `repo.config` | Un administrador de sitio bloqueó los empujes forzados. Para obtener más información, consulta [Bloquear los empujes forzados para un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) para un repositorio. | -| `repo.create` | Se creó un repositorio. | -| `repo.destroy` | Se eliminó un repositorio. | -| `repo.remove_member` | Se eliminó un colaborador de un repositorio. | -| `repo.rename` | Se renombró un repositorio. | -| `repo.transfer` | Un usuario aceptó una solicitud para recibir un repositorio transferido. | -| `repo.transfer_start` | Un usuario envió una solicitud para transferir un repositorio a otro usuario u organización. | -| `repo.unarchived` | Un repositorio dejó de estar archivado. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".{% ifversion ghes %} -| `repo.config.disable_anonymous_git_access` | El acceso de lectura anónima de Git se encuentra inhabilitado para un repositorio. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | -| `repo.config.enable_anonymous_git_access` | El acceso de lectura anónima de Git se encuentra habilitado para un repositorio. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | -| `repo.config.lock_anonymous_git_access` | La configuración del acceso de lectura anónimo de Git para un repositorio está bloqueada, lo cual evita que los administradores de repositorios cambien (habiliten o deshabiliten) esta configuración. Para obtener más información, consulta la sección "[Prevenir que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | -| `repo.config.unlock_anonymous_git_access` | La configuración del acceso de lectura anónimo de Git para un repositorio está desbloqueada, lo cual permite que los administradores del repositorio cambien (habiliten o inhabiliten) esta configuración. Para obtener más información, consulta la sección "[Prevenir que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)".{% endif %} +Action | Description +--------------------- | ------------------------------------------------------- +`repo.access` | The visibility of a repository changed to private{% ifversion ghes %}, public,{% endif %} or internal. +`repo.archived` | A repository was archived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)." +`repo.add_member` | A collaborator was added to a repository. +`repo.config` | A site admin blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository. +`repo.create` | A repository was created. +`repo.destroy` | A repository was deleted. +`repo.remove_member` | A collaborator was removed from a repository. +`repo.rename` | A repository was renamed. +`repo.transfer` | A user accepted a request to receive a transferred repository. +`repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. +`repo.unarchived` | A repository was unarchived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% ifversion ghes %} +`repo.config.disable_anonymous_git_access`| Anonymous Git read access is disabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." +`repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." +`repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting is locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." +`repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting is unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %} -## Herramientas del admin del sitio +## Site admin tools -| Acción | Descripción | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------- | -| `staff.disable_repo` | Un administrador del sitio inhabilitó el acceso a un repositorio y a todas sus bifurcaciones. | -| `staff.enable_repo` | Un administrador del sitio volvió a habilitar el acceso a un repositorio y a todas sus bifurcaciones. | -| `staff.fake_login` | Un administrador del sitio inició sesión en {% data variables.product.product_name %} como otro usuario. | -| `staff.repo_unlock` | Un administrador del sitio desbloqueó (obtuvo acceso total de manera temporaria) uno de los repositorios privados del usuario. | -| `staff.unlock` | Un administrador del sitio desbloqueó (obtuvo acceso total de manera temporaria) todos los repositorios privados de un usuario. | +Action | Description +----------------------------- | ----------------------------------------------- +`staff.disable_repo` | A site admin disabled access to a repository and all of its forks. +`staff.enable_repo` | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %} +`staff.exit_fake_login` | A site admin ended an impersonation session on {% data variables.product.product_name %}. +`staff.fake_login` | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %} +`staff.repo_unlock` | A site admin unlocked (temporarily gained full access to) one of a user's private repositories. +`staff.unlock` | A site admin unlocked (temporarily gained full access to) all of a user's private repositories. -## Equipos +## Teams -| Acción | Descripción | -| ------------------------- | ----------------------------------------------------------------------------------------- | -| `team.create` | Se agregó una cuenta de usuario o repositorio a un equipo. | -| `team.delete` | A user account or repository was removed from a team.{% ifversion ghes or ghae %} -| `team.demote_maintainer` | Se bajó de categoría a un usuario de mantenedor de equipo a miembro de equipo.{% endif %} -| `team.destroy` | Se borró un equipo.{% ifversion ghes or ghae %} -| `team.promote_maintainer` | Se promovió a un usuario de miembro de equipo a mantenedor de equipo.{% endif %} +Action | Description +--------------------------------- | ------------------------------------------- +`team.create` | A user account or repository was added to a team. +`team.delete` | A user account or repository was removed from a team.{% ifversion ghes or ghae %} +`team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +`team.destroy` | A team was deleted.{% ifversion ghes or ghae %} +`team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} -## Usuarios +## Users -| Acción | Descripción | -| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `user.add_email` | Se agregó una dirección de correo electrónico a una cuenta de usuario. | -| `user.async_delete` | Se inició un job asincrónico para destruir una cuenta de usuario, lo cual finalmente activó a `user.delete`.{% ifversion ghes %} -| `user.change_password` | Un usuario cambió su contraseña.{% endif %} -| `user.create` | Se creó una cuenta de usuario nueva. | -| `user.delete` | Se destruyó una cuenta de usuario mediante una tarea asincrónica. | -| `user.demote` | Se disminuyó el nivel de un administrador del sitio a cuenta de usuario común. | -| `user.destroy` | Un usuario borró su cuenta, lo cual activó a `user.async_delete`.{% ifversion ghes %} -| `user.failed_login` | Un usuario intentó registrarse con un nombre de usuario, contraseña o código de autenticación de dos factores incorrecto. | -| `user.forgot_password` | Un usuario solicitó el restablecimiento de una contraseña a través de la página de inicio de sesión.{% endif %} -| `user.login` | Un usuario inició sesión.{% ifversion ghes or ghae %} -| `user.mandatory_message_viewed` | Un usuario vió un mensaje mandatorio (consulta "[Personalizar los mensajes de usuario](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obtener más detalles) | {% endif %} -| `user.promote` | Se ascendió una cuenta de usuario común a administrador del sitio. | -| `user.remove_email` | Se eliminó una dirección de correo electrónico de una cuenta de usuario. | -| `user.rename` | Se cambió un nombre de usuario. | -| `user.suspend` | Un administrador de sitio suspendió una cuenta de usuario.{% ifversion ghes %} -| `user.two_factor_requested` | Se solicitó a un usuario ingresar un código de autenticación bifactorial.{% endif %} -| `user.unsuspend` | Un administrador del sitió dejó de suspender una cuenta de usuario. | +Action | Description +--------------------------------- | ------------------------------------------- +`user.add_email` | An email address was added to a user account. +`user.async_delete` | An asynchronous job was started to destroy a user account, eventually triggering `user.delete`.{% ifversion ghes %} +`user.change_password` | A user changed his or her password.{% endif %} +`user.create` | A new user account was created. +`user.delete` | A user account was destroyed by an asynchronous job. +`user.demote` | A site admin was demoted to an ordinary user account. +`user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% ifversion ghes %} +`user.failed_login` | A user tried to sign in with an incorrect username, password, or two-factor authentication code. +`user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} +`user.login` | A user signed in.{% ifversion ghes or ghae %} +`user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +`user.promote` | An ordinary user account was promoted to a site admin. +`user.remove_email` | An email address was removed from a user account. +`user.rename` | A username was changed. +`user.suspend` | A user account was suspended by a site admin.{% ifversion ghes %} +`user.two_factor_requested` | A user was prompted for a two-factor authentication code.{% endif %} +`user.unsuspend` | A user account was unsuspended by a site admin. {% ifversion ghes > 3.1 or ghae-issue-1157 %} -## Flujos de trabajo +## Workflows {% data reusables.actions.actions-audit-events-workflow %} {% endif %} - - [add key]: /articles/adding-a-new-ssh-key-to-your-github-account - [llave de implementación]: /guides/managing-deploy-keys/#deploy-keys - [llave de despliegue]: /guides/managing-deploy-keys/#deploy-keys - [generate token]: /articles/creating-an-access-token-for-command-line-use - [Token de acceso de OAuth]: /developers/apps/authorizing-oauth-apps - [Aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app - [clave secreta de una aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app - [aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app - [2fa]: /articles/about-two-factor-authentication - [2fa]: /articles/about-two-factor-authentication diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index b30902f675..62f0449fb9 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -1,5 +1,5 @@ --- -title: Agregar una clave SSH nueva a tu cuenta de GitHub +title: Adding a new SSH key to your GitHub account intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to use your new (or existing) SSH key, you''ll also need to add the key to your account.' redirect_from: - /articles/adding-a-new-ssh-key-to-your-github-account @@ -12,14 +12,13 @@ versions: ghec: '*' topics: - SSH -shortTitle: Agregar una llave SSH nueva +shortTitle: Add a new SSH key --- - Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you should have: -* [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys) -* [Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) +* [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) +* [Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -After adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. Para obtener más información, consulta "[Alternar URL remota de HTTPS a SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)". +After adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. For more information, see "[Switching remote URLs from HTTPS to SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)." {% data reusables.ssh.key-type-support %} @@ -28,9 +27,9 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% include tool-switcher %} {% webui %} -1. Copia la llave SSH pública a tu portapapeles. +1. Copy the SSH public key to your clipboard. - Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ pbcopy < ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub @@ -39,16 +38,19 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% tip %} - **Sugerencia:** Si `pbcopy` no está funcionando, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. + **Tip:** If `pbcopy` isn't working, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard. {% endtip %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) -5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". -6. Pega tu clave en el campo "Key". ![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) -7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) +4. Click **New SSH key** or **Add SSH key**. + ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key.png) +5. In the "Title" field, add a descriptive label for the new key. For example, if you're using a personal Mac, you might call this key "Personal MacBook Air". +6. Paste your key into the "Key" field. + ![The key field](/assets/images/help/settings/ssh-key-paste.png) +7. Click **Add SSH key**. + ![The Add key button](/assets/images/help/settings/ssh-add-key.png) {% data reusables.user_settings.sudo-mode-popup %} {% endwebui %} @@ -61,9 +63,9 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% webui %} -1. Copia la llave SSH pública a tu portapapeles. +1. Copy the SSH public key to your clipboard. - Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ clip < ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub @@ -72,17 +74,21 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% tip %} - **Sugerencia:** Si `clip` no está funcionando, puedes ubicar la carpeta `.shh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. + **Tip:** If `clip` isn't working, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard. {% endtip %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) -5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". -6. Pega tu clave en el campo "Key". ![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) -7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) -8. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) +4. Click **New SSH key** or **Add SSH key**. + ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key.png) +5. In the "Title" field, add a descriptive label for the new key. For example, if you're using a personal Mac, you might call this key "Personal MacBook Air". +6. Paste your key into the "Key" field. + ![The key field](/assets/images/help/settings/ssh-key-paste.png) +7. Click **Add SSH key**. + ![The Add key button](/assets/images/help/settings/ssh-add-key.png) +8. If prompted, confirm your {% data variables.product.product_name %} password. + ![Sudo mode dialog](/assets/images/help/settings/sudo_mode_popup.png) {% endwebui %} @@ -93,9 +99,9 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% include tool-switcher %} {% webui %} -1. Copia la llave SSH pública a tu portapapeles. +1. Copy the SSH public key to your clipboard. - Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ cat ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub @@ -105,17 +111,21 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% tip %} - **Tip:** Como alternativa, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito y copiarlo a tu portapapeles. + **Tip:** Alternatively, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard. {% endtip %} - + {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) -5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". -6. Pega tu clave en el campo "Key". ![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) -7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) -8. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) +4. Click **New SSH key** or **Add SSH key**. + ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key.png) +5. In the "Title" field, add a descriptive label for the new key. For example, if you're using a personal Mac, you might call this key "Personal MacBook Air". +6. Paste your key into the "Key" field. + ![The key field](/assets/images/help/settings/ssh-key-paste.png) +7. Click **Add SSH key**. + ![The Add key button](/assets/images/help/settings/ssh-add-key.png) +8. If prompted, confirm your {% data variables.product.product_name %} password. + ![Sudo mode dialog](/assets/images/help/settings/sudo_mode_popup.png) {% endwebui %} @@ -125,22 +135,30 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% data reusables.cli.cli-learn-more %} -Para agergar una clave SSH a tu cuenta de GitHub, utiliza el subcomando `ssh-key add`, especificando tu llave pública. +Before you can use the {% data variables.product.prodname_cli %} to add an SSH key to your account, you must authenticate to the {% data variables.product.prodname_cli %}. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login) in the {% data variables.product.prodname_cli %} documentation. + +To add an SSH key to your GitHub account, use the `ssh-key add` subcommand, specifying your public key. ```shell gh ssh-key add key-file ``` -Para incluir un título para la clave nueva, utiliza el marcador `-t` o `--title`. +To include a title for the new key, use the `-t` or `--title` flag. ```shell gh ssh-key add key-file --title "personal laptop" ``` +If you generated your SSH key by following the instructions in "[Generating a new SSH key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)", you can add the key to your account with this command. + +```shell +gh ssh-key add ~/.ssh/id_ed25519.pub +``` + {% endcli %} {% ifversion fpt or ghec %} -## Leer más +## Further reading -- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" {% endif %} diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 7201dac51d..8abeaf8aae 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -1,6 +1,6 @@ --- -title: Generar una nueva clave SSH y agregarla al ssh-agent -intro: 'Una vez que has comprobado las claves SSH existentes, puedes generar una nueva clave SSH para usarla para la autenticación y luego agregarla al ssh-agent.' +title: Generating a new SSH key and adding it to the ssh-agent +intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.' redirect_from: - /articles/adding-a-new-ssh-key-to-the-ssh-agent/ - /articles/generating-a-new-ssh-key/ @@ -14,24 +14,23 @@ versions: ghec: '*' topics: - SSH -shortTitle: Generar una llave SSH nueva +shortTitle: Generate new SSH key --- +## About SSH key generation -## Acerca de la generación de llaves SSH - -Si todavía no tienes una llave SSH, debes generar una nueva para utilizarla para autenticación. Si no estás seguro si ya tienes una llave SSH, puedes verificar si hay llaves existentes. Para obtener más información, consulta la sección "[Verificar si hay llaves SSH existentes](/github/authenticating-to-github/checking-for-existing-ssh-keys)". +If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)." {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} -Si quieres utilizar una llave de seguridad de hardware para autenticarte en {% data variables.product.product_name %}, debes generar una llave SSH nueva para esta. Debes conectar tu llave de seguridad de hardware a tu computadora cuando te autentiques con el par de llaves. Para obtener más información, consulta las[notas de lanzamiento de OpenSSH 8.2](https://www.openssh.com/txt/release-8.2). +If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2). {% endif %} -Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, puedes agregar tu clave al agente SSH, el cual administrará tus claves SSH y recordará tu contraseña. +If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase. -## Generar una nueva clave SSH +## Generating a new SSH key {% data reusables.command_line.open_the_multi_os_terminal %} -2. Pega el siguiente texto, que sustituye tu dirección de correo electrónico en {% data variables.product.product_name %}. +2. Paste the text below, substituting in your {% data variables.product.product_name %} email address. {% ifversion ghae %} ```shell @@ -43,7 +42,7 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu ``` {% note %} - **Nota:** Si estás utilizando un sistema tradicional que no es compatible con el algoritmo Ed25519, utiliza: + **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: ```shell $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` @@ -51,11 +50,11 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu {% endnote %} {% endif %} - Esto crea una llave SSH utilizando el correo electrónico proporcionado como etiqueta. + This creates a new SSH key, using the provided email as a label. ```shell > Generating public/private algorithm key pair. ``` -3. Cuando se te indique "Ingresar un archivo donde guardar la clave", presiona Intro. Al hacerlo aceptas la ubicación predeterminada del archivo. +3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location. {% mac %} @@ -81,36 +80,36 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu {% endlinux %} -4. Donde se indica, escribe una contraseña segura. Para obtener más información, consulta la sección ["Trabajar con contraseñas de llaves SSH](/articles/working-with-ssh-key-passphrases)". +4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)." ```shell > Enter passphrase (empty for no passphrase): [Type a passphrase] > Enter same passphrase again: [Type passphrase again] ``` -## Agregar tu clave SSH al ssh-agent +## Adding your SSH key to the ssh-agent -Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves, debes haber verificado si habían llaves SSH existentes y haber generado una llave SSH nueva. Cuando agregues tu clave SSH al agente, usa el comando macOS `ssh-add` y no una aplicación instalada por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) o alguna otra fuente externa. +Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source. {% mac %} {% data reusables.command_line.start_ssh_agent %} -2. Si estás usando macOS Sierra 10.12.2 o una versión posterior, deberás modificar tu archivo `~/.ssh/config` para cargar las claves automáticamente en el ssh-agent y almacenar las contraseñas en tu keychain. +2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain. - * Primero, revisa si tu archivo `~/.ssh/config` existe en la ubicación predeterminada. + * First, check to see if your `~/.ssh/config` file exists in the default location. ```shell $ open ~/.ssh/config > The file /Users/you/.ssh/config does not exist. ``` - * Si el archivo no existe, créalo. + * If the file doesn't exist, create the file. ```shell $ touch ~/.ssh/config ``` - * Abre tu archivo `~/.ssh/config` y luego modifícalo para que contenga las siguientes líneas. Si tu llave SSH tiene un nombre o ruta diferentes que el código de ejemplo, modifica el nombre de archivo o ruta para que coincida con tu configuración actual. + * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup. ``` Host * @@ -121,20 +120,20 @@ Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves {% note %} - **Nota:** Si eliges no agregar una frase de acceso a tu llave, deberás omitir la línea `UseKeychain`. - + **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line. + {% endnote %} - + {% mac %} {% note %} - **Nota:** Si ves un error como este + **Note:** If you see an error like this ``` /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain ``` - y una línea de configuración adicional en tu sección `Host *`: + add an additional config line to your `Host *` section: ``` Host * @@ -143,20 +142,22 @@ Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves {% endnote %} {% endmac %} - -3. Agrega tu llave privada SSH al ssh-agent y almacena tu contraseña en tu keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} + +3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} - **Nota:** La opción `-K` es una versión estándar de Apple de `ssh-add`, que almacena la contraseña en tu keychain cuando agregas una llave SSH al ssh-agent. Si eliges no agregar una frase de acceso a tu llave, ejecuta el comando sin la opción `-K`. + **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. - Si no tienes instalada la versión estándar de Apple, puedes recibir un mensaje de error. Para obtener más información sobre cómo resolver este error, consulta "[Error: ssh-add: opción ilegal -- K](/articles/error-ssh-add-illegal-option-k)". + If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)." + + In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. {% endnote %} -4. Agrega la llave SSH a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)". +4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." {% endmac %} @@ -164,17 +165,17 @@ Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves {% data reusables.desktop.windows_git_bash %} -1. Verifica que el ssh-agent se esté ejecutando. Puedes utilizar las instrucciones de "Autolanzamiento del ssh-agent" que se encuentran en [Trabajar con frases de acceso de las llaves SSH](/articles/working-with-ssh-key-passphrases)" o iniciarlo manualmente: +1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 ``` -2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} +2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} -3. Agrega la llave SSH a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)". +3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." {% endwindows %} @@ -182,37 +183,37 @@ Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves {% data reusables.command_line.start_ssh_agent %} -2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} +2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} -3. Agrega la llave SSH a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)". +3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." {% endlinux %} {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} -## Generar una llave SSH nueva para una llave de seguridad de hardware +## Generating a new SSH key for a hardware security key -Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SSH o instalar un cliente SSH nuevo antes de generar una llave SSH nueva. Para obtener más información, consulta el "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)" +If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)." -1. Insterta tu clave de seguridad de hardware en tu computadora. +1. Insert your hardware security key into your computer. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Pega el siguiente texto, sustitutyendo la dirección de correo electrónico por tu cuenta de {% data variables.product.product_name %}. +3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}. ```shell $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` - + {% ifversion not ghae %} {% note %} - **Nota:** Si el comando falla y recibes el error `invalid format` o `feature not supported,` puede que estés utilizando una llave de seguridad de hardware que no sea compatible con el algoritmo Ed25519. En vez de esto, ingresa el siguiente comando. + **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. ```shell $ ssh-keygen -t ecdsa-sk -C "your_email@example.com" ``` {% endnote %} {% endif %} -4. Cuando se te solicite, pulsa el botón en tu llave de seguridad de hardware. -5. Cuando se te pida "Ingresar un archivo en donde se pueda guardar la llave", teclea Enter para aceptar la ubicación predeterminada. +4. When you are prompted, touch the button on your hardware security key. +5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location. {% mac %} @@ -238,19 +239,19 @@ Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SS {% endlinux %} -6. Cuando se te solicite teclear una contraseña, teclea **Enter**. +6. When you are prompted to type a passphrase, press **Enter**. ```shell > Enter passphrase (empty for no passphrase): [Type a passphrase] > Enter same passphrase again: [Type passphrase again] ``` -7. Agrega la llave SSH a tu cuenta en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)". +7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." {% endif %} -## Leer más +## Further reading -- "[Acerca de SSH](/articles/about-ssh)" -- Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)" +- "[About SSH](/articles/about-ssh)" +- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)" {%- ifversion fpt %} -- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" {%- endif %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md index b14508f4ef..7252e596e2 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md @@ -1,6 +1,6 @@ --- -title: Acerca de las URL anonimizadas -intro: 'Si cargas una imagen o video a {% data variables.product.product_name %}, la URL de estos medios se modificará para que tu información no se pueda rastrear.' +title: About anonymized URLs +intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.' redirect_from: - /articles/why-do-my-images-have-strange-urls/ - /articles/about-anonymized-image-urls @@ -14,33 +14,32 @@ topics: - Identity - Access management --- +To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://.githubusercontent.com/`, with different subdomains depending on how you uploaded the image. -Para alojar tus imágenes, {% data variables.product.product_name %} usa el [Camo del proyecto de código abierto](https://github.com/atmos/camo). Camo genera un proxy de URL anónimo para cada archivo que oculta los detalles de tu buscador y la información relacionada de otros usuarios. La URL inicia a `https://.githubusercontent.com/`, con subdominios diferentes dependiendo de cómo la cargues. +Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}. -También se asignan URL anonimizadas a los videos, las cuales tienen el mismo formato que las URL de imagen, pero no se procesan a través de Camo. Esto es porque {% data variables.product.prodname_dotcom %} no es compatible con videos hospedados externamente, así que la URL anonimizada es un enlace al video cargado que hospeda {% data variables.product.prodname_dotcom %}. +Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo. -Cualquiera que reciba tu URL anonimizada directa o indirectamente podrá ver tu imagen o video. Para mantener privados los archivos de medios sensibles, restríngelos a una red o servidor privado que requiere autenticación en vez de utilizar Camo. +## Troubleshooting issues with Camo -## Solución de problemas con Camo - -En circunstancias excepcionales, las imágenes procesadas mediante Camo podrían no aparecer en {% data variables.product.prodname_dotcom %}. Aquí presentamos algunos pasos que puedes tomar para determinar dónde está el problema. +In rare circumstances, images that are processed through Camo might not appear on {% data variables.product.prodname_dotcom %}. Here are some steps you can take to determine where the problem lies. {% windows %} {% tip %} -Los usuarios de Windows necesitarán usar PowerShell de Git (que está instalado junto a [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) o descargar [curl para Windows](http://curl.haxx.se/download.html). +Windows users will either need to use the Git PowerShell (which is installed alongside [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) or download [curl for Windows](http://curl.haxx.se/download.html). {% endtip %} {% endwindows %} -### Una imagen no aparece +### An image is not showing up -Si se muestra una imagen en tu buscador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar solicitarla localmente. +If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally. {% data reusables.command_line.open_the_multi_os_terminal %} -1. Solicita los encabezados de la imagen usando `curl`. +1. Request the image headers using `curl`. ```shell $ curl -I https://www.my-server.com/images/some-image.png > HTTP/2 200 @@ -50,20 +49,20 @@ Si se muestra una imagen en tu buscador pero no en {% data variables.product.pro > Server: Google Frontend > Content-Length: 6507 ``` -3. Verifica el valor de `Content-Type`. En este caso, es `image/x-png`. -4. Verifica ese tipo de contenido con [la lista de tipos admitidos por Camo](https://github.com/atmos/camo/blob/master/mime-types.json). +3. Check the value of `Content-Type`. In this case, it's `image/x-png`. +4. Check that content type against [the list of types supported by Camo](https://github.com/atmos/camo/blob/master/mime-types.json). -Si Camo no admite tu tipo de contenido, puedes probar varias acciones: - * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un tipo de contenido correcto para las imágenes. - * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio. - * Realiza una solicitud de extracción para que Camo agregue tu tipo de contenido a la lista. +If your content type is not supported by Camo, you can try several actions: + * If you own the server that's hosting the image, modify it so that it returns a correct content type for images. + * If you're using an external service for hosting images, contact support for that service. + * Make a pull request to Camo to add your content type to the list. -### Una imagen que cambió recientemente no se está actualizando +### An image that changed recently is not updating -Si recientemente modificaste una imagen y aparece en tu navegador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar restablecer la caché de la imagen. +If you changed an image recently and it's showing up in your browser but not {% data variables.product.prodname_dotcom %}, you can try resetting the cache of the image. {% data reusables.command_line.open_the_multi_os_terminal %} -1. Solicita los encabezados de la imagen usando `curl`. +1. Request the image headers using `curl`. ```shell $ curl -I https://www.my-server.com/images/some-image.png > HTTP/2 200 @@ -73,29 +72,29 @@ Si recientemente modificaste una imagen y aparece en tu navegador pero no en {% > Server: Jetty(8.y.z-SNAPSHOT) ``` -Verifica el valor de `Cache-Control`. En este ejemplo, no hay `Cache-Control`. En ese caso: - * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un `Cache-Control` de `no-cache` para las imágenes. - * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio. +Check the value of `Cache-Control`. In this example, there's no `Cache-Control`. In that case: + * If you own the server that's hosting the image, modify it so that it returns a `Cache-Control` of `no-cache` for images. + * If you're using an external service for hosting images, contact support for that service. - Si `Cache-Control` se *configura* como `no-cache`, contacta a {% data variables.contact.contact_support %} o busca ayuda en el {% data variables.contact.community_support_forum %}. + If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}. -### Eliminar una imagen desde la caché de Camo +### Removing an image from Camo's cache -Purgar la caché fuerza a cada usuario de {% data variables.product.prodname_dotcom %} a volver a solicitar la imagen, por lo que deberías usarla con mucha prudencia y solo en el caso de que los pasos anteriores no hayan funcionado. +Purging the cache forces every {% data variables.product.prodname_dotcom %} user to re-request the image, so you should use it very sparingly and only in the event that the above steps did not work. {% data reusables.command_line.open_the_multi_os_terminal %} -1. Purga la imagen usando `curl -X PURGE` en la URL de Camo. +1. Purge the image using `curl -X PURGE` on the Camo URL. ```shell $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223.... > {"status": "ok", "id": "216-8675309-1008701"} ``` -### Visualizar imágenes en redes privadas +### Viewing images on private networks -Si una imagen está siendo proporcionada desde una red privada o desde un servidor que requiere de autenticación, se puede ver mediante {% data variables.product.prodname_dotcom %}. De hecho, no puede ser vista por ningún usuario sin pedirle que se registre en el servidor. +If an image is being served from a private network or from a server that requires authentication, it can't be viewed by {% data variables.product.prodname_dotcom %}. In fact, it can't be viewed by any user without asking them to log into the server. -Para solucionar esto, mueva la imagen a un servicio que esté disponible públicamente. +To fix this, please move the image to a service that is publicly available. -## Leer más +## Further reading -- "[Imágenes de usuarios de conexiones proxy](https://github.com/blog/1766-proxying-user-images)" en {% data variables.product.prodname_blog %} +- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 3cf47edeed..000a98288d 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -1,6 +1,6 @@ --- -title: Acerca de la autenticación en GitHub -intro: 'Puedes acceder de manera segura a los recursos de tu cuenta si te atutenticas en {% data variables.product.product_name %}, utilizando diferentes credenciales dependiendo de en donde te autenticas.' +title: About authentication to GitHub +intro: 'You can securely access your account''s resources by authenticating to {% data variables.product.product_name %}, using different credentials depending on where you authenticate.' versions: fpt: '*' ghes: '*' @@ -12,85 +12,84 @@ topics: redirect_from: - /github/authenticating-to-github/about-authentication-to-github - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github -shortTitle: Autenticación en GitHub +shortTitle: Authentication to GitHub --- +## About authentication to {% data variables.product.prodname_dotcom %} -## Acerca de la autenticación en {% data variables.product.prodname_dotcom %} +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. -Para mantener tu cuenta segura, debes atutenticarte antes de poder acceder a{% ifversion not ghae %} algunos{% endif %} recursos en {% data variables.product.product_name %}. Cuando te autenticas en {% data variables.product.product_name %}, proporcionas o confirmas las credenciales que son específicas para ti y así compruebas de que eres exactamente quien estás declarando ser. +You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. -Puedes acceder a tus recursos en {% data variables.product.product_name %} de muchas maneras: en el buscador, a través de {% data variables.product.prodname_desktop %} o de alguna otra aplicación de escritorio, con la API o a través de la línea de comandos. Cada forma de acceder a {% data variables.product.product_name %} es compatible con diferentes modalidades de autenticación. +- {% ifversion ghae %}Your identity provider (IdP){% else %}Username and password with two-factor authentication{% endif %} +- Personal access token +- SSH key -- {% ifversion ghae %}Tu proveedor de identidad (IdP){% else %}Nombre de usuario y contraseña con autenticación bifactorial{% endif %} -- Token de acceso personal -- Llave SSH +## Authenticating in your browser -## Autenticarte en tu buscador - -Puedes autenticarte en {% data variables.product.product_name %} en tu buscador {% ifversion ghae %} utilizando tu IdP. Para obtener más información, consulta la sección "[Acera de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)".{% else %} de varias formas. +You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. {% ifversion fpt or ghec %} -- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. {% endif %} -- **Nombre de usuario y contraseña únicamente** - - Crearás una contraseña cuando crees tu cuenta de usuario en {% data variables.product.product_name %}. Te recomendamos que utilices un administrador de contraseñas para generar una contraseña aleatoria y única. Para obtener más información, consulta la sección "[Crear una contraseña fuerte](/github/authenticating-to-github/creating-a-strong-password)". -- **Autenticación de dos factores (2FA)** (recomendada) - - Si habilitas la 2FA, también te pediremos que proporciones un código que genera una aplicación en tu dispositivo móvil o que mandes un mensaje de texto (SMS) después de que ingreses tu usuario y contraseña con éxito. Para obtener más información, consulta "[Acceder a {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". - - Adicionalmente a la autenticación con una aplicación móvil o con un mensaje de texto, puedes agregar opcionalmente un método secundario de autenticación con una llave de seguridad utilizando WebAuthn. Para obtener más información, consulta la sección "[Configurar la autenticación de dos factores utilizando una llave de seguridad](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". +- **Username and password only** + - You'll create a password when you create your user account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)." +- **Two-factor authentication (2FA)** (recommended) + - If you enable 2FA, we'll also prompt you to provide a code that's generated by an application on your mobile device or sent as a text message (SMS) after you successfully enter your username and password. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." + - In addition to authentication with a mobile application or a text message, you can optionally add a secondary method of authentication with a security key using WebAuthn. For more information, see "[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)." {% endif %} -## Autenticarte con {% data variables.product.prodname_desktop %} +## Authenticating with {% data variables.product.prodname_desktop %} -Puedes autenticarte con {% data variables.product.prodname_desktop %} utilizando tu buscador. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." +You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." -## Autenticarte con la API +## Authenticating with the API -Puedes autenticarte con la API de varias formas. +You can authenticate with the API in different ways. -- **Tokens de acceso personal** - - En situaciones limitadas, tales como cuando se hacen pruebas, puedes utilizar un token de acceso personal para acceder a la API. El utilizar un token de acceso personal te habilita para revocarle el acceso en cualquier momento. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". -- **Flujo de aplicaciones Web** - - Para las Apps de OAuth productivas, debes autenticarte utilizando el flujo de las aplicaciones web. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)". +- **Personal access tokens** + - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +- **Web application flow** + - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." - **GitHub Apps** - - Para las Github Apps productivas, debes autenticarte en nombre de la instalación de la app. Para obtener más información, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)". + - For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)." -## Autenticarte con la línea de comandos +## Authenticating with the command line -Puedes acceder a los repositorios en {% data variables.product.product_name %} desde la línea de comandos en dos formas, HTTPS y SSH, y ambas tienen una forma diferente para autenticarte. El método para autenticarte se determina con base en si escoges una URL remota de HTTPS o SSH cuando clonas el repositorio. Para obtener más información acerca de la forma en la que accedes, consulta la sección "[Acerca de los repositorios remotos](/github/getting-started-with-github/about-remote-repositories)". +You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." ### HTTPS -Puedes trabajar con todos los repositorios en {% data variables.product.product_name %} a través de HTTPS, aún si estás detrás de un cortafuegos o de un proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. -Si te autenticas con el {% data variables.product.prodname_cli %}, puedes ya sea autenticarte con un token de acceso personal o a través del buscador web. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -Si te autenticas sin el {% data variables.product.prodname_cli %}, debes autenticarte con un token de acceso personal. {% data reusables.user_settings.password-authentication-deprecation %} Cada que utilices Git para autenticarte con {% data variables.product.product_name %}, se te pedirá que ingreses tus credenciales para autenticarte con {% data variables.product.product_name %} a menos de que las guardes en caché en un [ayudante para credenciales](/github/getting-started-with-github/caching-your-github-credentials-in-git). +If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user_settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH -Puedes trabajar con todos los repositorios en {% data variables.product.product_name %} a través de SSH, aunque los cortafuegos y los proxys podrían rehusarse a permitir las conexiones de SSH. +You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxys might refuse to allow SSH connections. -Si te autenticas con el{% data variables.product.prodname_cli %}, este encontrará llaves SSH públicas en tu máquina y te pedirá seleccionar una para cargar. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Entonces podrás ya sea autenticarte con un token de acceso personal o a través del buscador web. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Then, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta "[Generar una nueva llave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Cada que utilizas Git para autenticarte con {% data variables.product.product_name %}, se te solicitará que ingreses tu frase de ingreso de la llave SSH, a menos de que hayas [almacenado la llave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). +If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). -### Autorizar para el inicio de sesión única de SAML +### Authorizing for SAML single sign-on -{% ifversion fpt or ghec %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o la sección "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} +{% ifversion fpt or ghec %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Formatos de los tokens de {% data variables.product.company_short %} +## {% data variables.product.company_short %}'s token formats -{% data variables.product.company_short %} emite tokens que inician con un prefijo para indicar el tipo de los mismos. +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. -| Tipo de token | Prefijo | Más información | -|:---------------------------------------------------------------------------------------- |:------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Token de acceso personal | `ghp_` | "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" | -| Token de acceso OAuth | `gho_` | "[Autorizar las {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | -| Token de usuario a servidor para una {% data variables.product.prodname_github_app %} | `ghu_` | "[Identificar y autorizar a los usuarios para las {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | -| Token de servidor a servidor para una {% data variables.product.prodname_github_app %} | `ghs_` | "[Autenticarse con las {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | -| Actualizar un token para una {% data variables.product.prodname_github_app %} | `ghr_` | "[Actualizar los tokens de acceso de usuario a servidor](/developers/apps/refreshing-user-to-server-access-tokens)" | +| Token type | Prefix | More information | +| :- | :- | :- | +| Personal access token | `ghp_` | "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | {% endif %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md index d7bfd68e7e..c23c0e6cc6 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md @@ -1,6 +1,6 @@ --- -title: Acerca de las direcciones de IP de GitHub -intro: '{% data variables.product.product_name %} proporciona aplicaciones desde varios rangos de dirección IP, que están disponibles usando la API.' +title: About GitHub's IP addresses +intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.' redirect_from: - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist/ - /categories/73/articles/ @@ -16,23 +16,25 @@ versions: topics: - Identity - Access management -shortTitle: Direcciones IP de GitHub +shortTitle: GitHub's IP addresses --- -Puedes recuperar una lista de direcciones IP de {% data variables.product.prodname_dotcom %} desde el punto de conexión de API [meta](https://api.github.com/meta). Para obtener más información, consulta la sección "[Meta](/rest/reference/meta)". +You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)." {% note %} -**Nota:** La lista de direcciones IP de {% data variables.product.prodname_dotcom %} que devuelve la API de Meta no pretende ser una lista exhaustiva. Por ejemplo, puede que no se listen las direcciones IP para algunos servicios de {% data variables.product.prodname_dotcom %}, tales como LFS o {% data variables.product.prodname_registry %}. +**Note:** The list of {% data variables.product.prodname_dotcom %} IP addresses returned by the Meta API is not intended to be an exhaustive list. For example, IP addresses for some {% data variables.product.prodname_dotcom %} services might not be listed, such as LFS or {% data variables.product.prodname_registry %}. {% endnote %} -Estos rangos están en [notación CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). Puedes usar una herramienta de conversión en línea como esta [Calculadora Supernet CIDR / VLSM](http://www.subnet-calculator.com/cidr.php) para convertir de una notación CIDR a rangos de dirección IP. +These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds. -Hacemos cambios a nuestras direcciones IP de vez en cuando. No te recomendamos hacer una lista blanca por dirección de IP, sin embargo, si utilizas estos rangos de IP te exhortamos enfáticamente a monitorear nuestra API con frecuencia. +These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges. -Para que las aplicaciones funcionen, debes habilitar los puertos TCP 22, 80, 443 y 9418 mediante nuestros rangos de IP para `github.com`. +We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API. -## Leer más +For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via our IP ranges for `github.com`. -- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" +## Further reading + +- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)" diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md index ccbbfeff98..e19bb80294 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md @@ -1,5 +1,5 @@ --- -title: Revisar tus claves SSH +title: Reviewing your SSH keys intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' redirect_from: - /articles/keeping-your-application-access-tokens-safe/ @@ -16,32 +16,32 @@ topics: - Identity - Access management --- - -Puedes eliminar las claves SSH no autorizadas (o posiblemente comprometidas) para garantizar que un atacante no tenga más acceso a tus repositorios. También puedes aprobar llaves SSH existentes que sean válidas. +You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid. {% mac %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. En la página de Parámetros SSH, anota las claves SSH asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay claves SSH válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de claves SSH](/assets/images/help/settings/settings-ssh-key-review.png) +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - **Nota:** Si estás auditando tus claves SSH por una operación de Git fallida, la clave no verificada que provocó el [error de auditoría de clave SSH](/articles/error-we-re-doing-an-ssh-key-audit) se resaltará en la lista de claves SSH. + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. Abre Terminal. +4. Open Terminal. {% data reusables.command_line.start_ssh_agent %} -6. Busca tu huella digital de llave pública y anótala. +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. Las claves SSH en {% data variables.product.product_name %} *deben* coincidir con las mismas calves en tu computadora. +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endmac %} @@ -49,27 +49,28 @@ Puedes eliminar las claves SSH no autorizadas (o posiblemente comprometidas) par {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. En la página de Parámetros SSH, anota las claves SSH asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay claves SSH válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de claves SSH](/assets/images/help/settings/settings-ssh-key-review.png) +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - **Nota:** Si estás auditando tus claves SSH por una operación de Git fallida, la clave no verificada que provocó el [error de auditoría de clave SSH](/articles/error-we-re-doing-an-ssh-key-audit) se resaltará en la lista de claves SSH. + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. Abre Git Bash. Si estás usando Git Shell, que se incluye en {% data variables.product.prodname_desktop %}, abre Git Shell y avanza hasta el paso 6. +4. Open Git Bash. 5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -6. Busca tu huella digital de llave pública y anótala. +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. Las claves SSH en {% data variables.product.product_name %} *deben* coincidir con las mismas calves en tu computadora. +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endwindows %} @@ -77,30 +78,31 @@ Puedes eliminar las claves SSH no autorizadas (o posiblemente comprometidas) par {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. En la página de Parámetros SSH, anota las claves SSH asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay claves SSH válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de claves SSH](/assets/images/help/settings/settings-ssh-key-review.png) +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - **Nota:** Si estás auditando tus claves SSH por una operación de Git fallida, la clave no verificada que provocó el [error de auditoría de clave SSH](/articles/error-we-re-doing-an-ssh-key-audit) se resaltará en la lista de claves SSH. + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. Abre Terminal. +4. Open Terminal. {% data reusables.command_line.start_ssh_agent %} -6. Busca tu huella digital de llave pública y anótala. +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. Las claves SSH en {% data variables.product.product_name %} *deben* coincidir con las mismas calves en tu computadora. +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endlinux %} {% warning %} -**Advertencia**: Si ves una clave SSH que no te resulta familiar en {% data variables.product.product_name %}, elimínala de inmediato y contáctate con {% data variables.contact.contact_support %} para recibir más ayuda. Una llave pública no identificada puede indicar un posible problema de seguridad. +**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern. {% endwarning %} diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index f57f655a43..0a0564460c 100644 --- a/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -1,6 +1,6 @@ --- -title: Acerca de la verificación de firma de confirmación -intro: 'Puedes firmar etiquetas y confirmaciones localmente utilizando GPG o S/MIME. Estas etiquetas o confirmaciones se marcan como verificadas en {% data variables.product.product_name %} para que otras personas tengan la confianza de que los cambios vienen de una fuente confiable.' +title: About commit signature verification +intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.' redirect_from: - /articles/about-gpg-commit-and-tag-signatures/ - /articles/about-gpg/ @@ -15,85 +15,84 @@ versions: topics: - Identity - Access management -shortTitle: Verificción de la firma de confirmación +shortTitle: Commit signature verification --- +## About commit signature verification -## Acerca de la verificación de firma de confirmación +You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% ifversion fpt or ghec %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %} -Puedes firmar confirmaciones y etiquetas localmente para darles a otras personas la confianza necesaria sobre el origen de un cambio que hayas realizado. Si una confirmación o etiqueta tiene una firma GPG o S/MIME que se pueda verificar criptográficamente, GitHub la marcará como {% ifversion fpt or ghec %}"Verificada" o "Verificada parcialmente".{% else %}"Verificada".{% endif %} - -![Confirmación verificada](/assets/images/help/commits/verified-commit.png) +![Verified commit](/assets/images/help/commits/verified-commit.png) {% ifversion fpt or ghec %} -Las confirmaciones y etiquetas tienen los siguientes estados de verificación dependiendo de si las habilitaste en modo vigilante. Predeterminadamente, el modo vigilante no está habilitado. Para obtener más información sobre cómo habilitar el modo vigilante, consulta la sección "[Mostrar los estados de verificación para todas tus confirmaciones](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)". +Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)." {% data reusables.identity-and-permissions.vigilant-mode-beta-note %} -### Estados predeterminados +### Default statuses -| Estado | Descripción | -| -------------------------- | ----------------------------------------------------------- | -| **Verificado** | La confirmación se firmó y la firma se verificó con éxito. | -| **Sin verificar** | La confirmación se firmó pero la firma no pudo verificarse. | -| Sin estado de verificación | La confirmación no se firmó. | +| Status | Description | +| -------------- | ----------- | +| **Verified** | The commit is signed and the signature was successfully verified. +| **Unverified** | The commit is signed but the signature could not be verified. +| No verification status | The commit is not signed. -### Estados con modo vigilante habilitado +### Statuses with vigilant mode enabled {% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %} {% else %} -Si una confirmaciòn o etiqueta tiene una firma que no puede verificarse, {% data variables.product.product_name %} marcarà la confirmaciòn o etiqueta como "No verificada". +If a commit or tag has a signature that can't be verified, {% data variables.product.product_name %} marks the commit or tag "Unverified." {% endif %} -Los administradores de repositorios pueden implementar la firma de confirmación requerida en una rama para bloquear todas las confirmaciones que no estén firmadas y verificadas. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-signed-commits)". +Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)." {% data reusables.identity-and-permissions.verification-status-check %} {% ifversion fpt or ghec %} -{% data variables.product.product_name %} utilizará GPG automáticamente para firmar las confirmaciones que hagas utilizando la interface web de {% data variables.product.product_name %}, con excepción de cuando combinas y fusionas una solicitud de cambios de la cual no seas autor. Las confirmaciones que firme {% data variables.product.product_name %} tendrán un estado verificado en {% data variables.product.product_name %}. Puedes verificar la firma localmente usando la clave pública disponible en https://github.com/web-flow.gpg. La huella dactilar completa de la llave es `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. Opcionalmente, puedes elegir que {% data variables.product.product_name %} firme las confirmaciones que hagas en {% data variables.product.prodname_codespaces %}. Para obtener más información sobre cómo habilitar la verificación de GPG para tus codespaces, consulta la sección "[Administrar la verificación de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." {% endif %} -## Verificación de firma de confirmación GPG +## GPG commit signature verification -Puedes usar GPG para firmar confirmaciones con una clave GPG que generas tu mismo. +You can use GPG to sign commits with a GPG key that you generate yourself. {% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. -Para firmar confirmaciones usando GPG y que esas confirmaciones sean verificadas en {% data variables.product.product_name %}, sigue estos pasos: +To sign commits using GPG and have those commits verified on {% data variables.product.product_name %}, follow these steps: -1. [Comprobar las claves GPG existentes](/articles/checking-for-existing-gpg-keys) -2. [Generar una clave GPG nueva](/articles/generating-a-new-gpg-key) -3. [Agregar una clave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account) -4. [Informarle a Git acerca de tu clave de firma](/articles/telling-git-about-your-signing-key) -5. [Firmar confirmaciones](/articles/signing-commits) -6. [Firmar etiquetas](/articles/signing-tags) +1. [Check for existing GPG keys](/articles/checking-for-existing-gpg-keys) +2. [Generate a new GPG key](/articles/generating-a-new-gpg-key) +3. [Add a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account) +4. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key) +5. [Sign commits](/articles/signing-commits) +6. [Sign tags](/articles/signing-tags) -## Verificación de firma de confirmación S/MIME +## S/MIME commit signature verification -Puedes usar S/MIME para firmar confirmaciones con una clave X.509 emitida por tu organización. +You can use S/MIME to sign commits with an X.509 key issued by your organization. -{% data variables.product.product_name %} usa [el paquete de certificados CA Debian](https://packages.debian.org/hu/jessie/ca-certificates), el mismo almacenamiento de confianza usado por los navegadores Mozilla, para confirmar que tus confirmaciones y etiquetas firmadas localmente son criptográficamente comprobables con una clave pública en un certificado raíz de confianza. +{% data variables.product.product_name %} uses [the Debian ca-certificates package](https://packages.debian.org/hu/jessie/ca-certificates), the same trust store used by Mozilla browsers, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key in a trusted root certificate. {% data reusables.gpg.smime-git-version %} -Para firmar confirmaciones usando S/MIME y que esas confirmaciones sean verificadas en {% data variables.product.product_name %}, sigue estos pasos: +To sign commits using S/MIME and have those commits verified on {% data variables.product.product_name %}, follow these steps: -1. [Informarle a Git acerca de tu clave de firma](/articles/telling-git-about-your-signing-key) -2. [Firmar confirmaciones](/articles/signing-commits) -3. [Firmar etiquetas](/articles/signing-tags) +1. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key) +2. [Sign commits](/articles/signing-commits) +3. [Sign tags](/articles/signing-tags) -No es necesario cargar tu clave pública a {% data variables.product.product_name %}. +You don't need to upload your public key to {% data variables.product.product_name %}. {% ifversion fpt or ghec %} -## Verificación de firma para bots +## Signature verification for bots -Las organizaciones y {% data variables.product.prodname_github_apps %} que requieren de la firma de confirmación pueden usar bots para firmar las confirmaciones. Si una confirmación o etiqueta tienen una firma de bot que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada. +Organizations and {% data variables.product.prodname_github_apps %} that require commit signing can use bots to sign commits. If a commit or tag has a bot signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag as verified. -La verificación de firma para bots solo funcionará si la solicitud se verifica y se autentica como la {% data variables.product.prodname_github_app %} o el bot y no contiene información de autor personalizada, información de persona que confirma el cambio personalizada ni información de firma personalizada, como API de confirmaciones. +Signature verification for bots will only work if the request is verified and authenticated as the {% data variables.product.prodname_github_app %} or bot and contains no custom author information, custom committer information, and no custom signature information, such as Commits API. {% endif %} -## Leer más +## Further reading -- "[Firmar confirmaciones](/articles/signing-commits)" -- "[Firmar etiquetas](/articles/signing-tags)" -- "[Solucionar problemas de la verificación de firma de confirmación](/articles/troubleshooting-commit-signature-verification)" +- "[Signing commits](/articles/signing-commits)" +- "[Signing tags](/articles/signing-tags)" +- "[Troubleshooting commit signature verification](/articles/troubleshooting-commit-signature-verification)" diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md index 2d7402c17a..e62f06f827 100644 --- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md +++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md @@ -1,6 +1,6 @@ --- -title: 'Error: ssh-add: opción ilegal -- K' -intro: 'Este error significa que tu versión de `ssh-add` no es compatible con la integración keychain macOS, que te permite almacenar tu contraseña en la keychain.' +title: 'Error: ssh-add: illegal option -- K' +intro: 'This error means your version of `ssh-add` does not support macOS keychain integration, which allows you to store your passphrase in the keychain.' redirect_from: - /articles/error-ssh-add-illegal-option-k - /articles/error-ssh-add-illegal-option----k @@ -15,25 +15,24 @@ topics: - SSH shortTitle: 'ssh-add: illegal option -- K' --- +The `-K` option is in Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an ssh key to the ssh-agent. If you have installed a different version of `ssh-add`, it may lack support for `-K`. -La opción `-K` es una versión estándar de Apple de `ssh-add`, que almacena la contraseña en tu keychain cuando agregas una clave SSH al ssh-agent. Si has instalado una versión diferente de `ssh-add`, es posible que no sea compatible para `-K`. +## Solving the issue -## Resolver el problema - -Para agregar tu llave privada SSH al ssh-agent, puedes especificar la ruta a la versión de Apple de `ssh-add`: +To add your SSH private key to the ssh-agent, you can specify the path to the Apple version of `ssh-add`: ```shell - $ /usr/bin/ssh-add -K ~/.ssh/id_rsa + $ /usr/bin/ssh-add -K ~/.ssh/id_ed25519 ``` {% note %} -**Nota:** {% data reusables.ssh.add-ssh-key-to-ssh-agent %} +**Note:** {% data reusables.ssh.add-ssh-key-to-ssh-agent %} {% endnote %} -## Leer más +## Further reading -- "[Generar una clave SSH nueva y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" -- [Página de manual de Linux para SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html) -- Para ver la página del manual de Apple para SSH-ADD, ejecuta `man ssh-add` en Terminal. +- "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" +- [Linux man page for SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html) +- To view Apple's man page for SSH-ADD, run `man ssh-add` in Terminal diff --git a/translations/es-ES/content/billing/index.md b/translations/es-ES/content/billing/index.md index 72b15f43a7..067b356ef5 100644 --- a/translations/es-ES/content/billing/index.md +++ b/translations/es-ES/content/billing/index.md @@ -1,15 +1,46 @@ --- -title: Facturación y pagos para GitHub -shortTitle: Facturación y pagos -intro: '{% ifversion fpt %}{% data variables.product.product_name %} ofrece productos gratuitos y de pago para todas las cuentas. Puedes mejorar, bajar de nivel y ver los cambios pendientes de la suscripción de tu cuenta en cualquier momento.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} cobra por el uso {% ifversion ghec or ghae %} de {% data variables.product.product_name %} para los miembros de tu empresa{% elsif ghes %} plazas de licencia de {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} y cualquier servicio adicional que compres{% endif %}{% endif %}.{% endif %}' +title: Billing and payments on GitHub +shortTitle: Billing and payments +intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github +introLinks: + overview: '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/about-billing-on-github{% elsif ghes%}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' +featuredLinks: + guides: + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method{% endif %}' + - '{% ifversion fpt %}/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription{% endif %}' + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/setting-your-billing-email{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/about-per-user-pricing{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + popular: + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + guideCards: + - /billing/managing-your-github-billing-settings/removing-a-payment-method + - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process + - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud{% endif %}' +layout: product-landing versions: fpt: '*' - ghec: '*' ghes: '*' ghae: '*' + ghec: '*' +topics: + - Billing children: - /managing-your-github-billing-settings - /managing-billing-for-your-github-account @@ -17,10 +48,10 @@ children: - /managing-billing-for-github-codespaces - /managing-billing-for-github-packages - /managing-your-license-for-github-enterprise + - /managing-licenses-for-visual-studio-subscriptions-with-github-enterprise - /managing-billing-for-github-advanced-security - /managing-billing-for-github-sponsors - /managing-billing-for-github-marketplace-apps - /managing-billing-for-git-large-file-storage - /setting-up-paid-organizations-for-procurement-companies ---- - +--- \ No newline at end of file diff --git a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md index f2683340d4..58d20b070d 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md @@ -1,6 +1,6 @@ --- -title: Acerca de la facturación para Github Advanced Security -intro: 'Si quieres utilizar las características de la {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} en un repositorio interno o privado{% endif %}, necesitas una licencia.{% ifversion fpt or ghec %} Estas características están disponibles gratuitamente para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' +title: About billing for GitHub Advanced Security +intro: 'If you want to use {% data variables.product.prodname_GH_advanced_security %} features{% ifversion fpt or ghec %} in a private or internal repository{% endif %}, you need a license{% ifversion fpt %} for your enterprise{% endif %}.{% ifversion fpt or ghec %} These features are available free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' product: '{% data reusables.gated-features.ghas %}' redirect_from: - /admin/advanced-security/about-licensing-for-github-advanced-security @@ -16,18 +16,22 @@ topics: - Advanced Security - Enterprise - Licensing -shortTitle: Facturación de Advanced Security +shortTitle: Advanced Security billing --- -## Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %} +## About billing for {% data variables.product.prodname_GH_advanced_security %} -{% ifversion fpt or ghec %} +{% ifversion fpt %} -Si quieres utilizar las características de {% data variables.product.prodname_GH_advanced_security %} en cualquier repositorio aparte de uno público en {% data variables.product.prodname_dotcom_the_website %}, necesitarás una licencia. Para obtener más información acerca de {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)". +If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." + +{% elsif ghec %} + +If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." {% elsif ghes %} -Puedes poner a disposición de los usuarios algunas características adicionales para la seguridad de código si compras y cargas una licencia de la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información acerca de {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)". +You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." {% endif %} @@ -37,9 +41,9 @@ Puedes poner a disposición de los usuarios algunas características adicionales {% endif %} -Para debatir sobre el licenciamiento de {% data variables.product.prodname_GH_advanced_security %} para tu empresa, contacta a {% data variables.contact.contact_enterprise_sales %}. +To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}. -## Acerca de los números de confirmante para {% data variables.product.prodname_GH_advanced_security %} +## About committer numbers for {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.about-committer-numbers-ghec-ghes %} @@ -49,200 +53,26 @@ Para debatir sobre el licenciamiento de {% data variables.product.prodname_GH_ad {% endif %} -Puedes requerir políticas para permitir o dejar de permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen la {% data variables.product.prodname_advanced_security %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% ifversion fpt or ghes or ghec %} -Para obtener más información sobre cómo ver el uso de licencias, consulta la sección "[Ver tu uso de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". +For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." {% endif %} -## Calcular los gastos de los confirmantes +## Understanding active committer usage -La siguiente línea de tiempo de ejemplo demuestra los eventos mensuales que afectan la facturación de {% data variables.product.prodname_GH_advanced_security %} en una empresa. Para cada mes, encontrarás eventos, la cuenta total de confirmantes y la cantidad total de confirmantes por la que cobrará {% data variables.product.company_short %}. +The following example timeline demonstrates how active committer count for {% data variables.product.prodname_GH_advanced_security %} could change over time in an enterprise. For each month, you will find events, along with the resulting committer count. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - Fecha - - Eventos del mes - - Cuenta total de confirmantes - - Confirmantes por los que se cobrará en el mes -
    - 1 de agosto - - Un miembro de tu empresa habilita {% data variables.product.prodname_GH_advanced_security %} para el repositorio X. El repositorio X tiene 50 confirmantes en los últimos 90 días. - - 50 - - 50 -
    - 5 de septiembre - - El desarrollador A sale del equipo que está trabajando en el repositorio X. Las contribuciones del desarrollador A siguen contando durante 90 días. - - 50 - - 50 -
    - 8 de septiembre - - El desarrolador B sube una confirmación al repositorio X por primera vez. El uso del desarrollador B se prorratea, ya que el desarrollador comenzó a contribuir al repositorio X ya empezado el mes. - - _50 + 1_
    51 -     		- _50 + 0.8_
    50.8 -
    - Octubre y noviembre - - Las contribuciones del desarrollador X al repositorio X siguen contando, ya que estas se hicieron dentro de los últimos 90 días. {% data variables.product.company_short %} ahora cobra por el mes completo del desarrollador B, ya que el desarrollador B ahora tiene contribuciones dentro de los 90 días pasados. - - 51 - - 51 -
    - 4 de diciembre - - Han pasado 90 días desde que el desarrollador A hizo su última contribución al repositorio _X. Pasaron 90 días después de que comenzó diciembre, así que {% data variables.product.company_short %} cobra por todo el mes del desarrollador A. - - _51 - 1_
    50 -     		-
    51 -
    - 11 de diciembre - - El desarrollador C se une a la compañía y sube una confirmación al repositorio X por primera vez. El uso del desarrollador C se prorratea en 70% durante 21 de los 30 días. - - _50 + 1_
    51 -     		- _51 + .07_
    51.7 -
    - Enero - - {% data variables.product.company_short %} ya no cobra por el desarrollador A. {% data variables.product.company_short %} cobra por todo el mes del desarrollador C. - - 51 - - 51 -
    - 15 de febrero - - Un miembro de tu empresa inhabilita la {% data variables.product.prodname_GH_advanced_security %} para el repositorio X. Los 51 contribuyentes del repositorio X no trabajan en ningún otro repositorio que cuente con la {% data variables.product.prodname_GH_advanced_security %}. {% data variables.product.company_short %} cobra por el uso de los desarrolladores en el repositorio X en febrero. - - _51 - 51_
    0 -     		-
    51 -
    - Marzo - - Ningún repositorio que pertenezca a tu empresa tiene habilitada la {% data variables.product.prodname_GH_advanced_security %}. - - 0 - - 0 -
    +| Date | Events during the month | Total committers | +| :- | :- | -: | +| April 15 | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Repository **X** has 50 committers over the past 90 days. | **50** | +| May 1 | Developer **A** leaves the team working on repository **X**. Developer **A**'s contributions continue to count for 90 days. | **50** | **50** | +| August 1 | Developer **A**'s contributions no longer count towards the licences required, because 90 days have passed. | _50 - 1_
    **49** | +| August 15 | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | _49 + 10_
    **59** | +| August 16 | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | _49 - 29_
    **20** | -## Sacar el mayor provecho de la {% data variables.product.prodname_GH_advanced_security %} +## Getting the most out of {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.getting-the-most-from-your-license %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md index 43734d2656..6e4ccf2989 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md @@ -1,6 +1,6 @@ --- -title: Visualizar tu uso de GitHub Advanced Security -intro: 'Puedes ver el uso de {% data variables.product.prodname_GH_advanced_security %} de tu empresa.' +title: Viewing your GitHub Advanced Security usage +intro: 'You can view usage of {% data variables.product.prodname_GH_advanced_security %} for your enterprise.' permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.' product: '{% data reusables.gated-features.ghas %}' redirect_from: @@ -13,38 +13,100 @@ versions: ghes: '>=3.1' fpt: '*' ghec: '*' + ghae: 'issue-5378' +miniTocMaxHeadingLevel: 3 type: how_to topics: - Advanced Security - Enterprise -shortTitle: Visualizar el uso de la Seguridad Avanzada +shortTitle: View Advanced Security usage --- -## Acerca de las licencias para {% data variables.product.prodname_GH_advanced_security %} +## About licenses for {% data variables.product.prodname_GH_advanced_security %} -{% data reusables.advanced-security.about-ghas-license-seats %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". +{% data reusables.advanced-security.about-ghas-license-seats %} 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)." -## Visualizar el uso del licenciamiento de {% data variables.product.prodname_GH_advanced_security %} para tu cuenta empresarial +## Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account -Puedes verificar cuántas plazas incluye tu licencia y cuántas de ellas se están utilizando. +You can check how many seats your license includes and how many of them are currently used. {% ifversion fpt or ghec %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} - La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Si te quedas sin plazas, la sección estará en rojo y mostrará "Límite excedido". Debes ya sea reducir tu uso de {% data variables.product.prodname_GH_advanced_security %} o comprar más plazas. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)". ![{% data variables.product.prodname_GH_advanced_security %} en los ajustes de licenciamiento de empresa mostrando "Límite excedido"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) -4. Opcionalmente, para ver un resumen detallado del uso por organización, en la barra lateral izquierda, haz clic en **Facturación**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) En la sección de "{% data variables.product.prodname_GH_advanced_security %}" puedes ver la cantidad de confirmantes y confirmantes únicos de cada organización. ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png) -5. Opcionalmente, haz clic en el nombre de una organización que te pertenezca para mostrar la configuración de seguridad y análisis para la organización. ![Organización que te pertenece en la sección de {% data variables.product.prodname_GH_advanced_security %} de la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". + The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. + ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) + If you run out of seats, the section will be red and show "Limit exceeded." You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. 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#getting-the-most-out-of-github-advanced-security)." + ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings showing "Limit exceeded"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) +4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. + ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) + In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. + ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png) +5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. + ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) +6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. + ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) + For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% elsif ghes %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} - La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. Puedes ver la cantidad total de plazas utilizadas, así como una tabla con la cantidad de confirmantes y confirmantes únicos para cada organización. ![Sección de {% data variables.product.prodname_GH_advanced_security %} de la licencia empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) -5. Opcionalmente, haz clic en el nombre de una organización que te pertenezca para mostrar la configuración de seguridad y análisis para la organización. ![Organización que te pertenece en la sección de {% data variables.product.prodname_GH_advanced_security %} de la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". + The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization. + ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) +5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. + ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) +6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. + ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) + For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." + +{% endif %} + +{% ifversion ghec or ghes > 3.3 or ghae-issue-5378 %} + +## Downloading {% data variables.product.prodname_GH_advanced_security %} license usage information + +You can download a CSV file with {% data variables.product.prodname_GH_advanced_security %} license usage information at both the enterprise and organization levels. The CSV file contains information about each {% data variables.product.prodname_advanced_security %} seat that is in use, including: + +- The username of the person using the seat +- The {% data variables.product.prodname_advanced_security %}-enabled repositories where commits were made +- The organizations that people using seats belong to +- The most recent commit dates + +You can use this information for insights into how your {% data variables.product.prodname_advanced_security %} licenses are being used, such as which members of your enterprise are using an {% data variables.product.prodname_advanced_security %} seat or how {% data variables.product.prodname_advanced_security %} licenses are being consumed across your organizations. + +You can download the {% data variables.product.prodname_advanced_security %} license usage CSV through the {% data variables.product.product_name %} user interface or the REST API. + +### Downloading {% data variables.product.prodname_advanced_security %} license usage information through the UI + +#### At the organization-level + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.billing_plans %} +1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," click {% octicon "download" aria-label="The download icon" %} next to "Committers." + ![Download button for organization-level data](/assets/images/help/billing/download-organization-GHAS-usage-data.png) + +#### At the enterprise-level + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Under "{% data variables.product.prodname_GH_advanced_security %}," click {% octicon "download" aria-label="The download icon" %} next to "Commiters." + ![Download button for enterprise-level data](/assets/images/help/billing/download-enterprise-GHAS-usage-data.png) + +### Downloading {% data variables.product.prodname_advanced_security %} license usage information through the REST API + +You can retrieve {% data variables.product.prodname_advanced_security %} usage information via the billing API. + +{% ifversion ghec %} + +For organization-level data, use the `/orgs/{org}/settings/billing/advanced-security` endpoint. For more information, see "[Billing](/rest/reference/billing#get-github-advanced-security-active-committers-for-an-organization)" in the {% data variables.product.prodname_dotcom %} REST API documentation. + +{% endif %} + +For enterprise-level data, use the `/enterprises/{enterprise}/settings/billing/advanced-security` endpoint. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-github-advanced-security-active-committers-for-an-enterprise)" in the {% data variables.product.prodname_dotcom %} REST API documentation. {% endif %} diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md index 3e00a8f4fa..86724905ed 100644 --- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md @@ -39,7 +39,7 @@ You can view the number of {% data variables.product.prodname_enterprise %} lice {% tip %} -**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](https://docs-internal-19656--vss-ghe-s.herokuapp.com/en/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. +**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. {% endtip %} diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md index 46d5ad602a..617e5c273f 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Administrar tu licencia de GitHub Enterprise -shortTitle: Licenci de GitHub Enterprise +title: Managing your license for GitHub Enterprise +shortTitle: GitHub Enterprise license intro: '{% data variables.product.prodname_enterprise %} includes both cloud and self-hosted deployment options. If you host a {% data variables.product.prodname_ghe_server %} instance, you must unlock the instance with a license file. You can view, manage, and update the license file.' redirect_from: - /free-pro-team@latest/billing/managing-your-license-for-github-enterprise @@ -23,6 +23,5 @@ children: - /uploading-a-new-license-to-github-enterprise-server - /viewing-license-usage-for-github-enterprise - /syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud - - /managing-licenses-for-visual-studio-subscription-with-github-enterprise --- diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index b6f3d72c2b..c51ed6834e 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -1,6 +1,6 @@ --- -title: Configurar el escaneo de código -intro: 'Puedes configurar la forma en que {% data variables.product.prodname_dotcom %} escanea el código en tu proyecto para encontrar vulnerabilidades y errores.' +title: Configuring code scanning +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' miniTocMaxHeadingLevel: 3 @@ -22,88 +22,89 @@ topics: - Pull requests - JavaScript - Python -shortTitle: Configura el escaneo de código +shortTitle: Configure code scanning --- - {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -## Acerca de la configuración de {% data variables.product.prodname_code_scanning %} +## About {% data variables.product.prodname_code_scanning %} configuration -Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %} si utilizas las {% data variables.product.prodname_actions %} o desde tu sistema de integración continua (IC). Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" o +You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or {%- ifversion fpt or ghes > 3.0 or ghae-next %} -"[Acerca del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". +"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." {%- else %} -"[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." +"[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." {% endif %} -Este artículo se trata de ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %} utilizando acciones. +This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions. -Antes de que puedas configurar el {% data variables.product.prodname_code_scanning %} para un repositorio, debes configurar el {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a este. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". +Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} -El análisis de {% data variables.product.prodname_codeql %} es tan solo un tipo de {% data variables.product.prodname_code_scanning %} que puedes hacer en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} en {% data variables.product.prodname_dotcom_the_website %}{% endif %} contiene otros flujos de trabajo de {% data variables.product.prodname_code_scanning %} que puedes utilizar. {% ifversion fpt or ghec %}Puedes encontrar una selección de estos en la página "Iniciar con {% data variables.product.prodname_code_scanning %}", a la cual puedes acceder desde la pestaña de **{% octicon "shield" aria-label="The shield symbol" %} Seguridad**.{% endif %} Los ejemplos específicos que se dan a este artículo se relacionan con el archivo {% data variables.product.prodname_codeql_workflow %}. +{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. -## Editing a code scanning workflow +## Editing a {% data variables.product.prodname_code_scanning %} workflow -{% data variables.product.prodname_dotcom %} guarda los archivos de flujo de trabajo en el directorio de _.github/workflows_ de tu repositorio. Puedes encontrar un flujo de trabajo que hayas agregado si buscas su nombre de archivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. +{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. -1. En tu repositorio, navega hasta el archivo de flujo de trabajo que deseas editar. -1. En el ángulo superior derecho de la vista del archivo, para abrir el editor de flujo de trabajo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}.![Botón para editar un archivo de flujo de trabajo](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. Después de que hayas editado el archivo, da clic en **Iniciar confirmación** y completa el formato de "Cambios de la confirmación". Puedes elegir confirmar directamente en la rama actual, o crear una rama nueva e iniciar una solicitud de extracción. ![Confirmar la actualización del flujo de trabajo de codeql.yml](/assets/images/help/repository/code-scanning-workflow-update.png) +1. In your repository, browse to the workflow file you want to edit. +1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. +![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. +![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) -Para obtener más información acerca de cómo editar los archivos de flujo de trabajo, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -## Configurar la frecuencia +## Configuring frequency -Puedes escanear código con cierta programación o cuando ocurren eventos específicos en un repositorio. +You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. -Escanear el código en cada carga al repositorio, y cada vez que se crea una solicitud de extracción, previene que los desarrolladores introduzcan vulnerabilidades y errores nuevos en dicho código. Escanear el código con una programación definida te informará de las últimas vulnerabilidades y errores que {% data variables.product.company_short %}, los investigadores de seguridad, y la comunidad descubren, aún cuando los desarrolladores no estén manteniendo el repositorio activamente. +Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. -### Escanear cuando se carga información +### Scanning on push -Si utilizas el flujo de trabajo predeterminado, el {% data variables.product.prodname_code_scanning %} escaneará el código en tu repositorio una vez por semana, adicionalmente a los escaneos activados por los eventos. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)". +By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." -Si escaneas al subir, entonces los resultados aparecen en la pestaña de **Seguridad** de tu repositorio. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." {% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} -Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." +Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} -### Escanear las solicitudes de extracción +### Scanning pull requests -El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza el evento `pull_request` para activar un escaneo de código sobre las solilcitudes de cambios que se dirigen a la rama predeterminada. {% ifversion ghes %}El evento de `pull_request` no se activará si la solicitud de cambios se abrió desde una bifurcación privada.{% else %}Si una solicitud de cambios es de una bifurcación privada, el evento de `pull_request` solo se activará si seleccionaste la opción de "Ejecutar flujos de trabajo desde solicitudes de cambios de la bifurcación" en la configuración del repositorio. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %} +The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% ifversion ghes %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} -Para obtener más información acerca del evento `pull_request`, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". +For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." -Si escaneas las solicitudes de cambios, entonces los resultados aparecerán como alertas en una verificación de solicitud de cambios. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del escaneo de código en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". +If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -### Definir las gravedades que causan el fallo en la verificación de las solicitudes de cambio +### Defining the severities causing pull request check failure -Predeterminadamente, solo las alertas con un nivel de gravedad de `Error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %} o nivel de gravedad de seguridad de `Crítica` o `Alta`{% endif %} ocasionarán que falle la verificación de una solicitud de cambios y la verificación aún tendrá éxito con aquellas alertas de gravedades menores. Puedes cambiar los niveles de gravedad de las alertas{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %} y de las gravedades de seguridad{% endif %} que ocasionarán el fallo de una verificación de solicitud de cambios en los ajustes de tu repositorio. Para obtener más información sobre los niveles de gravedad, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)". +By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -1. Debajo de "Escaneo de código", a la derecha de "Fallo de verificación", utiliza el menú desplegable para seleccionar el nivel de gravedad que quisieras que ocasionara un fallo de verificación en la solicitud de cambios. -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %} -![Configuración de fallo de verificación](/assets/images/help/repository/code-scanning-check-failure-setting.png) +1. Under "Code scanning", to the right of "Check Failure", use the drop-down menu to select the level of severity you would like to cause a pull request check failure. +{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +![Check failure setting](/assets/images/help/repository/code-scanning-check-failure-setting.png) {% else %} -![Configuración de fallo de verificación](/assets/images/help/repository/code-scanning-check-failure-setting-ghae.png) +![Check failure setting](/assets/images/help/repository/code-scanning-check-failure-setting-ghae.png) {% endif %} {% endif %} -### Evitar escaneos innecesarios en las solicitudes de cambios +### Avoiding unnecessary scans of pull requests -Puede que quieras evitar que se active un escaneo de código en solicitudes de cambio específicas que se dirijan a la rama predeterminada, independientemente de los archivos que se hayan cambiado. Puedes configurar esto si especificas `on:pull_request:paths-ignore` o `on:pull_request:paths` en el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. Por ejemplo, si los únicos cambios en una solicitud de cambios se hacen en archivos con las extensiones `.md` o `.txt`, puedes utilizar el siguiente arreglo de `paths-ignore`. +You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. ``` yaml on: @@ -118,28 +119,28 @@ on: {% note %} -**Notas** +**Notes** -* `on:pull_request:paths-ignore` y `on:pull_request:paths` configuran condiciones que determinan si una acción en el flujo de trabajo se ejecutará en una solicitud de cambios. No determinan qué archivos se analizarán cuando las acciones _se_ ejecuten. Cuando una solicitud de cambios contiene cualquier archivo que no coincida con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, el flujo de trabajo ejecuta las acciones y escanea todos los archivos que cambiaron en la solicitud de cambios, incluyendo aquellos que coincidieron con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, a menos de que éstos se hayan excluido. Para obtener más información sobre cómo excluir archivos del análisis, consulta la sección "[Especificar directorios para escanear](#specifying-directories-to-scan)". -* Para los archivos de flujo de trabajo del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, no utilices las palabras clave `paths-ignore` o `paths` con el evento `on:push`, ya que es probable que cause que falten análisis. Para obtener resultados precisos, el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} necesita poder comparar los cambios nuevos con el análisis de la confirmación previa. +* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." +* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. {% endnote %} -Para obtener más información acerca de utilizar `on:pull_request:paths-ignore` y `on:pull_request:paths` para determinar cuando se ejecutará un flujo de trabajo para una solicitud de cambios, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". +For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -### Escanear de forma pre-programada +### Scanning on a schedule -El flujo de trabajo del {% data variables.product.prodname_code_scanning %} utiliza el evento `pull_request` para activar un escaneo de código en la confirmación `HEAD` de una solicitud de extracción. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)". +If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." {% note %} -**Nota**: {% data variables.product.prodname_dotcom %} solo ejecuta jobs pre-programados que se encuentren en flujos de trabajo de la rama predeterminada. Cambiar la programación en un flujo de trabajo en cualquier otra rama no tendrá efecto hasta que fusiones esta rama con la predeterminada. +**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. {% endnote %} -### Ejemplo +### Example -El siguiente ejemplo muestra un {% data variables.product.prodname_codeql_workflow %} para un repositorio particular que tiene una rama predeterminada que se llama `main` y una protegida que se llama `protected`. +The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. ``` yaml on: @@ -151,16 +152,16 @@ on: - cron: '20 14 * * 1' ``` -Este flujo de trabajo escanea: -* Cada subida a la rama predeterminada y a la rama protegida -* Cada solicitud de cambios a la rama predeterminada -* La rama predeterminada cada lunes a las 14:20 UTC +This workflow scans: +* Every push to the default branch and the protected branch +* Every pull request to the default branch +* The default branch every Monday at 14:20 UTC -## Especificar un sistema operativo +## Specifying an operating system -Si tu código requiere un sistema operativo específico para compilar, puedes configurarlo en tu flujo de trabajo. Edita el valor de `jobs.analyze.runs-on` para especificar el sistema operativo para la máquina que ejecuta tus acciones de {% data variables.product.prodname_code_scanning %}. {% ifversion ghes %}Especificas el sistema operativo utilizando una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% else %} +If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} -Si eliges utilizar une ejecutor auto-hospedado para el escaneo de código, puedes especificar un sistema operativo si utilizas una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% endif %} +If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} ``` yaml jobs: @@ -169,16 +170,16 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} +{% ifversion fpt or ghec %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_code_scanning_capc %} es compatible con las últimas versiones de macOs, Ubuntu, y Windows. Los valores habituales para esta configuración son por lo tanto: `ubuntu-latest`, `windows-latest`, y `macos-latest`. Para obtener más información, consulta las secciones {% ifversion ghes %}"[Sintaxis de flujos de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" y "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}". +{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% ifversion ghes %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." -{% ifversion ghes %}Debes asegurarte de qeu Git esté en la variable "PATH" en tus ejecutores auto-hospedados.{% else %}Si utilizas el ejecutor auto-hospedado, debes asegurarte de que git esté en la variable "PATH".{% endif %} +{% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Especificar la ubicación de las bases de datos de {% data variables.product.prodname_codeql %} +## Specifying the location for {% data variables.product.prodname_codeql %} databases -En general, no necesitas preocuparte por dónde {% data variables.product.prodname_codeql_workflow %} coloca las bases de dato de {% data variables.product.prodname_codeql %}, ya que los pasos subsecuentes encontrarán automáticamente las bases de datos que crearon los pasos previos. Sin embargo, si estás escribiendo un paso de un flujo de trabajo personalizado que requiera que la base de datos de {% data variables.product.prodname_codeql %} esté en una ubicación de disco específica, por ejemplo, para cargar la base de datos como un artefacto de flujo de trabajo, puedes especificar esa ubicación utilizando el parámetro `db-location` bajo la acción `init`. +In general, you do not need to worry about where the {% data variables.product.prodname_codeql_workflow %} places {% data variables.product.prodname_codeql %} databases since later steps will automatically find databases created by previous steps. However, if you are writing a custom workflow step that requires the {% data variables.product.prodname_codeql %} database to be in a specific disk location, for example to upload the database as a workflow artifact, you can specify that location using the `db-location` parameter under the `init` action. {% raw %} ``` yaml @@ -188,22 +189,22 @@ En general, no necesitas preocuparte por dónde {% data variables.product.prodna ``` {% endraw %} -El {% data variables.product.prodname_codeql_workflow %} esperará que se pueda escribir la ruta que se proporcionó en `db-location` y que ya sea no exista o sea un directorio vacío. Cuando utilizamos este parámetro en un job que se ejecuta en un ejecutor auto-hospedado o utilizando un contenedor de Docker, es responsabilidad del usuario garantizar que el directorio elegido se limpie entre ejecuciones o que las bases de datos se eliminen una vez que ya no se necesiten. No es necesario para los jobs que se ejecutan en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, los cuales obtienen una instancia nueva y un sistema de archivos limpio cada vez que se ejecutan. Para obtener más información, consulta la sección "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)". +The {% data variables.product.prodname_codeql_workflow %} will expect the path provided in `db-location` to be writable, and either not exist, or be an empty directory. When using this parameter in a job running on a self-hosted runner or using a Docker container, it's the responsibility of the user to ensure that the chosen directory is cleared between runs, or that the databases are removed once they are no longer needed. {% ifversion fpt or ghec or ghes %} This is not necessary for jobs running on {% data variables.product.prodname_dotcom %}-hosted runners, which obtain a fresh instance and a clean filesystem each time they run. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."{% endif %} -Si no se utiliza este parámetro, el {% data variables.product.prodname_codeql_workflow %} creará bases de datos en una ubicación temporal de su propia elección. +If this parameter is not used, the {% data variables.product.prodname_codeql_workflow %} will create databases in a temporary location of its own choice. {% endif %} -## Cambiar los lenguajes que se analizan +## Changing the languages that are analyzed -El {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} detecta automáticamente el código que se escribe en los lenguajes compatibles. +{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. {% data reusables.code-scanning.codeql-languages-bullets %} -El archivo predeterminado del {% data variables.product.prodname_codeql_workflow %} contiene una matriz de compilación que se llama `language`, la cual lista los lenguajes en tu repositorio que se han analizado. El {% data variables.product.prodname_codeql %} llena automáticamente esta matriz cuando agregas el {% data variables.product.prodname_code_scanning %} a un repositorio. Cuando se utiliza la matriz de `language` se optimiza a {% data variables.product.prodname_codeql %} para ejecutar cada análisis en paralelo. Te recomendamos que todos los flujos de trabajo adopten esta configuración debido a los beneficios de rendimiento que implica el paralelizar las compilaciones. Para obtener más información acerca de las matrices de compilación, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)". +The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." {% data reusables.code-scanning.specify-language-to-analyze %} -Si tu flujo de trabajo utiliza la matriz `language`, entonces {% data variables.product.prodname_codeql %} se codifica fijamente para analizar únicamente los lenguajes en dicha matriz. Para cambiar los lenguajes que quieres analizar, edita el valor de la variable de la matriz. Puedes eliminar un lenguaje para que no se analice, o puedes agregar alguno que no estuviera presente en el repositorio cuando se configuró el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se configuró el {% data variables.product.prodname_code_scanning %}, y luego quieres agregar código de Python, entonces necesitarás agregar `python` a la matriz. +If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. ```yaml jobs: @@ -216,7 +217,7 @@ jobs: language: ['javascript', 'python'] ``` -Si tu flujo de trabajo no contiene una matriz que se llame `language`, entonces {% data variables.product.prodname_codeql %} se configurará para ejecutar un análisis secuencialmente. Si no especificas los lenguajes en los flujos de trabajo, {% data variables.product.prodname_codeql %} detectará e intentará analizar cualquier lenguaje compatible que haya en el repositorio. Si quieres elegir qué lenguajes analizar sin utilizar una matriz, puedes utilizar el parámetro `languages` en la acción de `init`. +If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. ```yaml - uses: github/codeql-action/init@v1 @@ -224,15 +225,15 @@ Si tu flujo de trabajo no contiene una matriz que se llame `language`, entonces languages: cpp, csharp, python ``` {% ifversion fpt or ghec %} -## Analizar las dependencias de Python +## Analyzing Python dependencies -Para los ejecutores hospedados en GitHub que utilicen solo Linux, el {% data variables.product.prodname_codeql_workflow %} intentarà instalar automàticamente las dependencias de Python para dar màs resultados para el anàlisis de CodeQL. Puedes controlar este comportamiento si especificas el paràmetro `setup-python-dependencies` para la acciòn que el paso "Initialize CodeQL" llama. Predeterminadamente, este paràmetro se configura como `true`: +For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: -- Si el repositorio contiene còdigo escrito en Python, el paso "Initialize CodeQL" instala las dependencias necesarias en el ejecutor hospedado en GitHub. Si la instalaciòn automàtica es exitosa, la acciòn tambièn configura la variable de ambiente `CODEQL_PYTHON` en el archivo ejecutable de Python que incluye las dependencias. +- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. -- Si el repositorio no tiene ninguna dependencia de Python o si las dependencias se especifican en una forma inesperada, obtendràs una advertencia y la acciòn seguirà con los jobs restantes. La acciòn puede ejecutarse exitosamente aùn cuando existan problemas para interpretar las dependencias, pero los resultados podrìan estar incompletos. +- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. -Como alternativa, puedes instalar las dependencias de Python manualmente en cualquier sistema operativo. Necesitaràs agregar a `setup-python-dependencies` y configurarlo como `false`, asì como configurar `CODEQL_PYTHON` para el ejecutable de Python que incluye las dependencias, tal como se muestra en este extracto de flujo de trabajo: +Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: ```yaml jobs: @@ -269,11 +270,11 @@ jobs: {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Configurar una cateogría para el análisis +## Configuring a category for the analysis -Utiliza `category` para distinguir entre análisis múltiples de la misma herramienta y confirmación, pero que se lleven a cabo en lenguajes o partes diferentes del código. La categoría que especificas en tu flujo de trabajo se incluirá en el archivo de resultados de SARIF. +Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file. -Este parámetro es particularmente útil si trabajas en monorepositorios y tienes vrios archivos SARIF para diferentes componentes de este. +This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo. {% raw %} ``` yaml @@ -287,34 +288,34 @@ Este parámetro es particularmente útil si trabajas en monorepositorios y tiene ``` {% endraw %} -Si no especificas un parámetro de `category` en tu flujo de trabajo, {% data variables.product.product_name %} generará un nombre de categoría para ti con base en el nombre del archivo de flujo de trabajo que activó la acción, el nombre de la acción y cualquier variable de la matriz. Por ejemplo: -- El flujo de trabajo `.github/workflows/codeql-analysis.yml` y la acción `analyze` producirán la categoría `.github/workflows/codeql.yml:analyze`. -- Las variables Del flujo de trabajo de `.github/workflows/codeql-analysis.yml`, la acción `analyze`, y la matriz de `{language: javascript, os: linux}` producirán la categoría `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`. +If you don't specify a `category` parameter in your workflow, {% data variables.product.product_name %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. For example: +- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`. +- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`. -El valor `category` se mostrará como la propiedad `.automationDetails.id` en SARIF v2.1.0. Para obtener más información, consulta la sección "[Soporte de SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)". +The `category` value will appear as the `.automationDetails.id` property in SARIF v2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)." -La categoría que especificaste no sobrescribirá los detalles del objeto `runAutomationDetails` en el archivo SARIF, si es que se incluye. +Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included. {% endif %} -## Ejecutar consultas adicionales +## Running additional queries {% data reusables.code-scanning.run-additional-queries %} {% if codeql-packs %} -### Utilizar los paquetes de consultas de {% data variables.product.prodname_codeql %} +### Using {% data variables.product.prodname_codeql %} query packs {% data reusables.code-scanning.beta-codeql-packs-cli %} -Para agregar uno o más paquetes de consulta de {% data variables.product.prodname_codeql %} (beta), agrega una entrada de `with: packs:` dentro de la sección de `uses: github/codeql-action/init@v1` del flujo de trabajo. Dentro de `packs` especificas uno o más paquetes a utilizar y, opcionalmente, la versión a descargar. Donde no especifiques una versión, se descargará la más reciente. Si quieres utilizar paquetes que no están disponibles al público, necesitarás configurar la variable de ambiente `GITHUB_TOKEN` como un secreto que tenga acceso a los paquetes. Para obtener más información, consulta las secciones "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)". +To add one or more {% data variables.product.prodname_codeql %} query packs (beta), add a `with: packs:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. Within `packs` you specify one or more packages to use and, optionally, which version to download. Where you don't specify a version, the latest version is downloaded. If you want to use packages that are not publicly available, you need to set the `GITHUB_TOKEN` environment variable to a secret that has access to the packages. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." {% note %} -**Nota:** Para el caso de los flujos de trabajo que generan bases de dato de {% data variables.product.prodname_codeql %} para lenguajes múltiples, en su lugar, debes especificar los paquetes de consultas de {% data variables.product.prodname_codeql %} en un archivo de configuración. Para obtener más información, consulta la sección "[Especificar los paquetes de consultas de {% data variables.product.prodname_codeql %}](#specifying-codeql-query-packs)" a continuación. +**Note:** For workflows that generate {% data variables.product.prodname_codeql %} databases for multiple languages, you must instead specify the {% data variables.product.prodname_codeql %} query packs in a configuration file. For more information, see "[Specifying {% data variables.product.prodname_codeql %} query packs](#specifying-codeql-query-packs)" below. {% endnote %} -En el siguiente ejemplo, `scope` es la organización o cuenta personal que publicó el paquete. Cuando se ejecuta el flujo de trabajo, los tres paquetes de consulta de {% data variables.product.prodname_codeql %} se descargan de {% data variables.product.product_name %} y se ejecutan las consultas predeterminadas o suite de consultas para cada paquete. La última versión de `pack1` se descarga, ya que no se especificó ninguna versión. Se descarga la versión 1.2.3 del `pack2`, así como la última versión del `pack3` que es compatible con la versión 1.2.3. +In the example below, `scope` is the organization or personal account that published the package. When the workflow runs, the three {% data variables.product.prodname_codeql %} query packs are downloaded from {% data variables.product.product_name %} and the default queries or query suite for each pack run. The latest version of `pack1` is downloaded as no version is specified. Version 1.2.3 of `pack2` is downloaded, as well as the latest version of `pack3` that is compatible with version 1.2.3. {% raw %} ``` yaml @@ -325,9 +326,9 @@ En el siguiente ejemplo, `scope` es la organización o cuenta personal que publi ``` {% endraw %} -### Utilizar las consultas en los paquetes de QL +### Using queries in QL packs {% endif %} -Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. Si las consultas están en un repositorio privado, utiliza el parámetro `external-repository-token` para especificar un token que tiene acceso para verificar el repositorio privado. +To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to checkout the private repository. {% raw %} ``` yaml @@ -339,17 +340,17 @@ Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` ``` {% endraw %} -También puedes ejecutar conjuntos de consultas adicionales si los especificas en un archivo de configuración. Los conjuntos de consultas son colecciones de consultas que a menudo se agrupan por propósito o lenguaje. +You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. {% data reusables.code-scanning.codeql-query-suites %} {% if codeql-packs %} -### Trabajar con archivos de configuración personalizados +### Working with custom configuration files {% endif %} -Si también utilizas un archivo de configuración para los ajustes personalizados, cualquier {% if codeql-packs %}paquete o{% endif %} consulta adicional especificados en tu flujo de trabajo se utilizarán en vez de aquellos especificados en el archivo de configuración. Si quieres ejecutar el juego combinado de {% if codeql-packs %}paquetes o {% endif %} consultas adicionales, coloca un prefijo en el valor de {% if codeql-packs %}`packs` o {% endif %}`queries` en el flujo de trabajo con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)". +If you also use a configuration file for custom settings, any additional {% if codeql-packs %}packs or {% endif %}queries specified in your workflow are used instead of those specified in the configuration file. If you want to run the combined set of additional {% if codeql-packs %}packs or {% endif %}queries, prefix the value of {% if codeql-packs %}`packs` or {% endif %}`queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." -En el siguiente ejemplo, el símbolo `+` garantiza que los {% if codeql-packs %}paquetes y {% endif %}consultas adicionales especificados se utilicen juntos con cualquiera que se haya especificado en el archivo de configuración referenciado. +In the following example, the `+` symbol ensures that the specified additional {% if codeql-packs %}packs and {% endif %}queries are used together with any specified in the referenced configuration file. ``` yaml - uses: github/codeql-action/init@v1 @@ -361,11 +362,11 @@ En el siguiente ejemplo, el símbolo `+` garantiza que los {% if codeql-packs %} {% endif %} ``` -## Utilizar una herramienta de escaneo de código de terceros +## Using a custom configuration file -Un archivo de configuración personalizado es una forma alterna de especificar {% if codeql-packs %}paquetes y{% endif %} consultas adicionales a ejecutar. También puedes utilizar el archivo para inhabilitar las consultas predeterminadas y para especificar qué directorios escanear durante el análisis. +A custom configuration file is an alternative way to specify additional {% if codeql-packs %}packs and {% endif %}queries to run. You can also use the file to disable the default queries and to specify which directories to scan during analysis. -En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acción `init` para especificar la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _./.github/codeql/codeql-config.yml_. +In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. ``` yaml - uses: github/codeql-action/init@v1 @@ -375,7 +376,7 @@ En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acc {% data reusables.code-scanning.custom-configuration-file %} -El archivo de configuración se ubica en un repositorio privado externo, utiliza el parámetro `external-repository-token` de la acción `init` para especificar un token que tenga acceso al repositorio privado. +If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository. {% raw %} ```yaml @@ -385,14 +386,14 @@ El archivo de configuración se ubica en un repositorio privado externo, utiliza ``` {% endraw %} -Los ajustes en el archivo de configuración se escriben en formato YAML. +The settings in the configuration file are written in YAML format. {% if codeql-packs %} -### Especificar paquetes de consultas de {% data variables.product.prodname_codeql %} +### Specifying {% data variables.product.prodname_codeql %} query packs {% data reusables.code-scanning.beta-codeql-packs-cli %} -Especificas paquetes de consultas de {% data variables.product.prodname_codeql %} en un arreglo. Nota que el formato es deferente a aquél que utiliza el archivo de flujo de trabajo. +You specify {% data variables.product.prodname_codeql %} query packs in an array. Note that the format is different from the format used by the workflow file. {% raw %} ``` yaml @@ -406,7 +407,7 @@ packs: ``` {% endraw %} -Si tienes un flujo de trabajo que genere más de una base de datos de {% data variables.product.prodname_codeql %}, puedes especificar cualquier paquete de consultas de {% data variables.product.prodname_codeql %} para que se ejecute en un archivo de configuración personalizado utilizando un mapa de paquetes anidado. +If you have a workflow that generates more than one {% data variables.product.prodname_codeql %} database, you can specify any {% data variables.product.prodname_codeql %} query packs to run in a custom configuration file using a nested map of packs. {% raw %} ``` yaml @@ -423,9 +424,9 @@ packs: {% endraw %} {% endif %} -### Especificar consultas adicionales +### Specifying additional queries -Puedes especificar consultas adicionales en una matriz de `queries`. Cada elemento de la matriz contiene un parámetro de `uses` con un valor que identifica un archivo de consulta simple, un directorio que contiene los archivos de consulta, o un archivo de suite de definiciones de una consulta. +You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. ``` yaml queries: @@ -434,15 +435,15 @@ queries: - uses: ./query-suites/my-security-queries.qls ``` -Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración. Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)". +Optionally, you can give each array element a name, as shown in the example configuration files below. For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. -### Inhabilitar las consultas predeterminadas +### Disabling the default queries -Si solo quieres ejecutar consultas personalizadas, puedes inhabilitar las consultas de seguridad predeterminadas si agregas `disable-default-queries: true` a tu archivo de configuración. +If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. -### Especificar directorios para escanear +### Specifying directories to scan -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %}, Ruby{% endif %} and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. Puedes excluir del análisis los archivos en los directorios específicos si agregas un arreglo de `paths-ignore`. +For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %}, Ruby{% endif %} and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. ``` yaml paths: @@ -454,28 +455,28 @@ paths-ignore: {% note %} -**Nota**: +**Note**: -* Las palabras clave `paths` y `paths-ignore` que se utilizan en el contexto del archivo de configuración del {% data variables.product.prodname_code_scanning %} no deben confundirse con las mismas palabras clave cuando se utilizan para `on..paths` en un flujo de trabajo. Cuando se tulizan para modificar `on.` en un flujo de trabajo, éstas determinan si las acciones se ejecutarán cuando alguien modifique el código en los directorios especificados. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". -* Los caracteres de patrón de filtro como `?`, `+`, `[`, `]`, y `!` no son compatibles y se empatarán literalmente. -* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por ejemplo, `foo/**`, `**/foo`, y `foo/**/bar` son todas sintaxis permitidas, pero `**foo` no lo es. Sin embargo, puedes utilizar asteriscos sencillos con otros caracteres, tal como se muestra en el ejemplo. Tendrás que poner entre comillas todo lo que contenga un caracter de `*`. +* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally. +* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. {% endnote %} -Para los lenguajes compilados, si quieres limitar el {% data variables.product.prodname_code_scanning %} para directorios específicos en tu proyecto, debes especificar los pasos de compilación adecuados en el flujo de trabajo. Los comandos que necesites utilizar para excluir un directorio de la compilación dependerán en tu sistema de compilación. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -Puedes analizar rápidamente partes pequeñas de un monorepo cuando modificas el código en directorios específicos. Necesitarás tanto excluir los directorios en tus pasos de compilación como utilizar las palabras clave `paths-ignore` y `paths` para [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) en tu archivo de flujo de trabajo. +You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. -### Ejemplos de archivos de configuración +### Example configuration files {% data reusables.code-scanning.example-configuration-files %} -## Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados +## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} -{% data reusables.code-scanning.autobuild-add-build-steps %} Para obtener más información sobre cómo configurar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} para los lenguajes compilados, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)". +{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)." -## Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}. +## Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} -{% data variables.product.prodname_dotcom %} puede mostrar los datos de análisis de código que se generan externamente con una herramienta de terceros. Puedes mostrar el análisis de código de una herramienta de terceros en {{ site.data.variables.product.prodname_dotcom }} su agregas la acción `upload-sarif` en tu flujo de trabajo. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)". +{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)." diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md index c05798ca08..4f9478f221 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md @@ -1,7 +1,7 @@ --- -title: Escanear tu código automáticamente para encontrar vulnerabilidades y errores -shortTitle: Escanear el código automáticamente -intro: 'Puedes encontrar vulnerabilidades y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.' +title: Automatically scanning your code for vulnerabilities and errors +shortTitle: Scan code automatically +intro: 'You can find vulnerabilities and errors in your project''s code on {% data variables.product.prodname_dotcom %}, as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors @@ -19,6 +19,7 @@ children: - /triaging-code-scanning-alerts-in-pull-requests - /setting-up-code-scanning-for-a-repository - /managing-code-scanning-alerts-for-your-repository + - /tracking-code-scanning-alerts-in-issues-using-task-lists - /configuring-code-scanning - /about-code-scanning-with-codeql - /configuring-the-codeql-workflow-for-compiled-languages @@ -26,5 +27,4 @@ children: - /running-codeql-code-scanning-in-a-container - /viewing-code-scanning-logs --- - diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index ca27cad123..2b8052ebfc 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- -title: Administrar las alertas del escaneo de código para tu repositorio -shortTitle: Administra las alertas -intro: 'Desde la vista de seguridad, puedes ver, corregir, descartar o borrar las alertas de las vulnerabilidades o errores potenciales en el código de tu proyecto.' +title: Managing code scanning alerts for your repository +shortTitle: Manage alerts +intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -23,222 +23,237 @@ topics: - Alerts - Repositories --- - {% data reusables.code-scanning.beta %} -## Acerca de las alertas de {% data variables.product.prodname_code_scanning %} +## About alerts from {% data variables.product.prodname_code_scanning %} -Puedes configurar el {% data variables.product.prodname_code_scanning %} para que verifique el código en un repositorio utilizando el análisis predeterminado de {% data variables.product.prodname_codeql %}, un análisis de terceros, o varios tipos de análisis. Cuando se complete el análisis, las alertas resultantes se mostrarán unas junto a otras en la vista de seguridad del repositorio. Los resultados de las herramientas de terceros o de las consultas personalizadas podrían no incluir todas las propiedades que ves para las alertas que se detectan con el análisis predeterminado del {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". +You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." -Predeterminadamente, el {% data variables.product.prodname_code_scanning %} analiza tu código periódicamente en la rama predeterminada y durante las solicitudes de cambios. Para obtener información acerca de la administración de alertas en una solicitud de cambios, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". +By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% data reusables.code-scanning.upload-sarif-alert-limit %} -## Acerca de los detalles de las alertas +## About alerts details -Cada alerta resalta un problema en el código y el nombre de la herramienta que lo identificó. Puedes ver la línea de código que activó la alerta, así como las propiedades de dicha alerta, tales como la gravedad{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %}, gravedad de seguridad{% endif %} y la naturaleza del problema. Las alertas también te dicen si el problema se introdujo por primera vez. Para las alertas que identificó el análisis de {% data variables.product.prodname_codeql %}, también verás información de cómo arreglar elproblema. +Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem. -![Ejemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) +![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) -Si configuras el {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_codeql %}, esto también puede detectar problemas de flujo de datos en tu código. El análisis de flujo de datos encuentra problemas de seguridad potenciales en el código, tales como: utilizar los datos de formas no seguras, pasar argumentos peligrosos a las funciones y tener fugas de información sensible. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. -Cuando {% data variables.product.prodname_code_scanning %} reporta alertas de flujo de datos, {% data variables.product.prodname_dotcom %} te muestra como se mueven los datos a través del código. El {% data variables.product.prodname_code_scanning_capc %} te permite identificar las áreas de tu código que filtran información sensible y que podrían ser el punto de entrada para los ataques que hagan los usuarios malintencionados. +When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. -### Acerca de los niveles de gravedad +### About severity levels -Los niveles de gravedad de las alertas pueden ser `Error`, `Warning`, o `Note`. +Alert severity levels may be `Error`, `Warning`, or `Note`. -Predeterminadamente, cualquier resultado del escaneo de código con una severidad de `error` causará una falla de verificación. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %}Puedes especificar el nivel de gravedad en el cual deberían fallar las solicitudes de cambios que activan las alertas del escaneo de código. Para obtener más información, consulta la sección "[Definir las gravedades que ocasionan un fallo en la verificación de las solicitudes de cambios](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %} -### Acerca de los niveles de gravedad +{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +### About security severity levels -El {% data variables.product.prodname_code_scanning_capc %} muestra los niveles de gravedad de seguridad para las alertas que generan las consultas de seguridad. Los niveles de seguridad pueden ser `Critical`, `High`, `Medium` o `Low`. +{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. -Para calcular la gravedad de seguridad de una alerta, utilizamos los datos del Sistema de Puntuación para Vulnerabilidades Comunes (CVSS). El CVSS es un marco de trabajo de código abierto para comunicar las características y gravedad de las vulnerabilidades de software y otros productos de seguridad lo utilizan habitualmente para puntuar las alertas. Para obtener más información sobre cómo se calculan los niveles de gravedad, consulta [la publicación del blog](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). +To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). -Predeterminadamente, cualquier resultado del escaneo de código con una gravedad de seguridad `Critical` o `High` ocasionarán un fallo de verificación. Puedes especificar qué nivel de gravedad de seguridad para de los resultados del escaneo de código deberían ocasionar una falla de verificación. Para obtener más información, consulta la sección "[Definir las gravedades que ocasionan un fallo en la verificación de las solicitudes de cambios](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".{% endif %} +By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -### Acerca de las etiquetas para las alertas que no se encuentran en el código de la aplicación +### About labels for alerts that are not found in application code -{% data variables.product.product_name %} asigna una etiqueta de categoría a las alertas que no se encuentran en el código de aplicación. La etiqueta se relaciona con la ubicación de la alerta. +{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert. -- **Generado**: Código que genera el proceso de compilación -- **Prueba**: Código de prueba -- **Librería**: Librería o código de terceros -- **Documentación**: Documentación +- **Generated**: Code generated by the build process +- **Test**: Test code +- **Library**: Library or third-party code +- **Documentation**: Documentation -El {% data variables.product.prodname_code_scanning_capc %} categoriza los archivos por sus rutas. No puedes categorizar los archivos de origen manualmente. +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files. -Aquí tienes un ejemplo de la lista de alertas del {% data variables.product.prodname_code_scanning %} para una alerta que se marcó como ocurrente en código de librería. +Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code. -![Alerta de librería del escaneo de código en la lista](/assets/images/help/repository/code-scanning-library-alert-index.png) +![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png) -En la página de alertas, puedes ver si la ruta de archivo se marca como código de librería (etiqueta `Library`). +On the alert page, you can see that the filepath is marked as library code (`Library` label). -![Detalles de la alerta de librería del escaneo de código](/assets/images/help/repository/code-scanning-library-alert-show.png) +![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png) -## Visualizar las alertas de un repositorio +## Viewing the alerts for a repository -Cualquiera con permisos de escritura en un repositorio puede ver las anotaciones del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de extracción](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -Necesitas permisos de escritura para ver un resumen de todas las alertas de un repositorio en la pestaña de **Seguridad**. +You need write permission to view a summary of all the alerts for a repository on the **Security** tab. -Predeterminadamente, la página de alertas del escaneo de código se filtra para mostrar las alertas únicamente para la rama predeterminada del repositorio. +By default, the code scanning alerts page is filtered to show alerts for the default branch of the repository only. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -1. Opcionalmente, utiliza la caja de búsqueda de texto libre o los menús desplegables para filtrar las alertas. Por ejemplo, puedes filtrar por la herramienta que se utilizó para identificar las alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} -1. Debajo de "{% data variables.product.prodname_code_scanning_capc %}", da clic en la alerta que quisieras explorar. +1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. + ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% data reusables.code-scanning.explore-alert %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Resumen de alertas](/assets/images/help/repository/code-scanning-click-alert.png) + ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} - ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} -1. Opcionalmente, si la alerta resalta un problema con el flujo de datos, da clic en **Mostrar rutas** para mostrar la ruta desde la fuente de datos hacia el consumidor de datos en donde se utiliza. ![El enlace de "Mostrar rutas" en una alerta](/assets/images/help/repository/code-scanning-show-paths.png) -1. Las alertas del análisis de {% data variables.product.prodname_codeql %} incluyen una descripción del problema. Da clic en **Mostrar más** para obtener orientación sobre cómo arreglar tu código. ![Detalles de una alerta](/assets/images/help/repository/code-scanning-alert-details.png) +1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. + ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png) +1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. + ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png) {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} {% note %} -**Nota:** Para realizar el análisis del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}, puedes ver la información sobre la última ejecución en un encabezado en la parte superior de la lisa de alertas del {% data variables.product.prodname_code_scanning %} para el repositorio. +**Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. -Por ejemplo, puedes ver cuándo se ejecutó el último escaneo, la cantidad de líneas de código que se analizó en comparación con la cantidad de líneas de código totales en tu repositorio y la cantidad total de alertas qeu se generaron. ![Letrero de IU](/assets/images/help/repository/code-scanning-ui-banner.png) +For example, you can see when the last scan ran, the number of lines of code analyzed compared to the total number of lines of code in your repository, and the total number of alerts that were generated. + ![UI banner](/assets/images/help/repository/code-scanning-ui-banner.png) {% endnote %} {% endif %} -## Filtrar las alertas del {% data variables.product.prodname_code_scanning %} +## Filtering {% data variables.product.prodname_code_scanning %} alerts -Puedes filtrar las alertas que se muestran en la vista de alertas del {% data variables.product.prodname_code_scanning %}. Esto es útil si hay muchas alertas, ya que puedes enfocarte en un tipo particular de estas. Hay algunos filtros predefinidos y rangos de palabras clave que puedes utilizar para refinar la lista de alertas que se muestran. +You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. -- Para utilizar un filtro predefinido, haz clic en **Filtros** o en un filtro que se muestre en el encabezado de la lista de alertas y elige un filtro de la lista desplegable. - {% ifversion fpt or ghes > 3.0 or ghec %}![Filtros predefinidos](/assets/images/help/repository/code-scanning-predefined-filters.png) +- To use a predefined filter, click **Filters**, or a filter shown in the header of the list of alerts, and choose a filter from the drop-down list. + {% ifversion fpt or ghes > 3.0 or ghec %}![Predefined filters](/assets/images/help/repository/code-scanning-predefined-filters.png) {% else %}![Predefined filters](/assets/images/enterprise/3.0/code-scanning-predefined-filters.png){% endif %} -- Para utilizar una palabra clave, teclea directamente en los filtros de la caja de texto o: - 1. Haz clic en la caja de texto de filtros para que se muestre una lista de palabras clave de filtro disponibles. - 2. Haz clic en la palabra clave que quieras utilizar y luego elige un valor de la lista desplegable. ![Lista de filtros de palabra clave](/assets/images/help/repository/code-scanning-filter-keywords.png) +- To use a keyword, either type directly in the filters text box, or: + 1. Click in the filters text box to show a list of all available filter keywords. + 2. Click the keyword you want to use and then choose a value from the drop-down list. + ![Keyword filters list](/assets/images/help/repository/code-scanning-filter-keywords.png) -El beneficio de utilizar filtros de palabra clave es que solo los valores con resultados se muestran en las listas desplegables. Esto hace más fácil el evitar configurar filtros que no encuentran resultados. +The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. -Si ingresas filtros múltiples, la vista te mostrará las alertas que empatan con _todos_ ellos. Por ejemplo, `is:closed severity:high branch:main` solo mostrará las aletas de gravedad alta cerradas que estén presentes en la rama `main`. La excepción son filtros que se relacionan a los refs (`ref`, `branch` y `pr`): `is:open branch:main branch:next` que te mostrarán alertas abiertas tanto de la rama `main` como de la `next`. +If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. -### Restringir los resultados únicamente al código de la aplicación +### Restricting results to application code only -Puedes utilizar el filtro de "Solo alertas en el código de la aplicación" o la palabra clave y el valor `autofilter:true` para restringir a las alertas en el código de aplicación. Consulta la sección "[Acerca de las etiquetas para las alertas que no estén en el código de la aplicación](#about-labels-for-alerts-that-are-not-found-in-application-code)" para obtener más información sobre los tipos de código que no estén en el código de la aplicación. +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. See "[About labels for alerts not in application code](#about-labels-for-alerts-that-are-not-found-in-application-code)" above for more information about the types of code that are not application code. {% ifversion fpt or ghes > 3.1 or ghec %} -## Buscar las alertas del {% data variables.product.prodname_code_scanning %} +## Searching {% data variables.product.prodname_code_scanning %} alerts -Puedes buscar la lista de alertas. Esto es útil si hay una gran cantidad de alertas en tu repositorio o si no sabes el nombre exacto de una alerta, por ejemplo. {% data variables.product.product_name %} realiza la búsqueda de texto gratuita a través de: -- El nombre de la alerta -- La descripción de la alerta -- Los detalles de la alerta (esto también incluye la información qeu se esconde de la vista predeterminada en la sección retraible de **Mostrar más**) +You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across: +- The name of the alert +- The alert description +- The alert details (this also includes the information hidden from view by default in the **Show more** collapsible section) - ![La información de la alerta que se utiliza en las búsquedas](/assets/images/help/repository/code-scanning-free-text-search-areas.png) + ![The alert information used in searches](/assets/images/help/repository/code-scanning-free-text-search-areas.png) -| Búsqueda compatible | Ejemplo de sintaxis | Resultados | -| -------------------------------------------------------------- | ------------------- | ---------------------------------------------------------------------------- | -| Búsqueda de palabra sencilla | `injection` | Devuelve todas las alertas que contienen la palabra `injection` | -| Búsqueda de palabras múltiples | `sql injection` | Devuelve todas las alertas que contienen la palabra `sql` o `injection` | -| Búsqueda de coincidencia exacta
    (utilizar comillas dobles) | `"sql injection"` | Devuelve todas las alertas que contienen la frase exacta `sql injection` | -| Búsqueda con OR | `sql OR injection` | Devuelve todas las alertas que contienen la palabra `sql` o `injection` | -| Búsqueda con AND | `sql AND injection` | Devuelve todas las alertas que contienen ambas palabras: `sql` e `injection` | +| Supported search | Syntax example | Results | +| ---- | ---- | ---- | +| Single word search | `injection` | Returns all the alerts containing the word `injection` | +| Multiple word search | `sql injection` | Returns all the alerts containing `sql` or `injection` | +| Exact match search
    (use double quotes) | `"sql injection"` | Returns all the alerts containing the exact phrase `sql injection` | +| OR search | `sql OR injection` | Returns all the alerts containing `sql` or `injection` | +| AND search | `sql AND injection` | Returns all the alerts containing both words `sql` and `injection` | {% tip %} -**Tips:** -- La búsuqeda de palabras múltiples es equivalente auna búsqueda con OR. -- La búsqueda con AND devolverá resultados en donde los términos de búsqueda se encuentren _en cualquier lugar_ y en cualquier órden en el nombre, descripción o detalles de la alerta. +**Tips:** +- The multiple word search is equivalent to an OR search. +- The AND search will return results where the search terms are found _anywhere_, in any order in the alert name, description, or details. {% endtip %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. A la derecha de los menús desplegables de **Filtros**, teclea las palabras clave a buscar en la caja de búsqueda de texto gratuita. ![La caja de búsqueda de texto gratuita](/assets/images/help/repository/code-scanning-search-alerts.png) -2. Presiona return. El listado de alerta contendrá las alertas abiertas del {% data variables.product.prodname_code_scanning %} que empaten con tus criterios de búsqueda. +1. To the right of the **Filters** drop-down menus, type the keywords to search for in the free text search box. + ![The free text search box](/assets/images/help/repository/code-scanning-search-alerts.png) +2. Press return. The alert listing will contain the open {% data variables.product.prodname_code_scanning %} alerts matching your search criteria. {% endif %} -## Arreglar una alerta +{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %} +## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues -Cualquiera con permisos de escritura en un repositorio puede arreglar una alerta si confirma una corrección en el código. Si el repositorio tiene programado un {% data variables.product.prodname_code_scanning %} para ejecutarse en las solicitudes de cambios, es mejor levantar una solicitud de cambios con tu corrección. Esto activará el análisis del {% data variables.product.prodname_code_scanning %} en los cambios y probará que tu arreglo no introduciría ningún problema nuevo. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" y "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". +{% data reusables.code-scanning.beta-alert-tracking-in-issues %} +{% data reusables.code-scanning.github-issues-integration %} +{% data reusables.code-scanning.alert-tracking-link %} -Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista de "Cerrado" muestra las alertas arregladas y las que los usuarios han descartado. +{% endif %} -Puedes utilizar{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} la búsqueda gratuita por texto o {% endif %} los filtros para mostrar un subconjunto de alertas y luego, a su vez, marcar todas las alertas coincidentes como cerradas. +## Fixing an alert -Las alertas pueden arreglarse en una rama pero no en alguna otra. Puedes utilizar el menú desplegable de "Rama", en el resumen de las alertas, para verificar si una alerta se arregló en una rama en particular. +Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." + +If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed. + +You can use{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. + +Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -![Filtrar alertas por rama](/assets/images/help/repository/code-scanning-branch-filter.png) +![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} -![Filtrar alertas por rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% endif %} -## Descartar o borrar las alertas +## Dismissing or deleting alerts -Hay dos formas de cerrar una alerta. Puedes arreglar el problema en el código, o puedes descartar la alerta. Como alternativa, si tienes permisos adminsitrativos en el repositorio, puedes borrar las alertas. Borrar las alertas es útil en situaciones en donde configuraste una herramienta del {% data variables.product.prodname_code_scanning %} y luego decidiste eliminarla, o donde configuraste el análisis de {% data variables.product.prodname_codeql %} con un conjunto más grande de consultas que quieres seguir utilizando y después eliminaste algunas de ellas de la herramienta. En ambos casos, el borrar las alertas te permite limpiar tus resultados del {% data variables.product.prodname_code_scanning %}. Puedes borrar las alertas de la lista de resumen dentro de la pestaña de **Seguridad**. +There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. -El descartar una alerta es una forma de cerrar aquellas que no crees que necesiten arreglo. {% data reusables.code-scanning.close-alert-examples %} Puedes eliminar alertas desde las anotaciones del {% data variables.product.prodname_code_scanning %} en el código, o desde la lista de resumen dentro de la pestaña de **Seguridad**. +Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab. -Cuando descartas una alerta: +When you dismiss an alert: -- Se descarta en todas las ramas. -- La alerta se elimina de la cantidad de alertas actuales para tu proyecto. -- La alerta se mueve a la lista de "Cerrado" en el resumen de alertas, desde donde puedes volver a abrirla en caso de que lo necesites. -- La razón por la cual cerraste la alerta se registra. -- La siguiente vez que se ejecute el {% data variables.product.prodname_code_scanning %}, este código no volverá a generar una alerta. +- It's dismissed in all branches. +- The alert is removed from the number of current alerts for your project. +- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required. +- The reason why you closed the alert is recorded. +- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert. -Cuando borras una alerta: +When you delete an alert: -- Se borra en todas las ramas. -- La alerta se elimina de la cantidad de alertas actuales para tu proyecto. -- _No_ seagrega a la lista de "Cerrado" en el resumen de las alertas. -- Si el código que generó la alerta se mantiene tal cual, y se ejecuta nuevamente la misma herramienta del {% data variables.product.prodname_code_scanning %} sin ningún cambio de configuración, la alerta se mostrará nuevamente en los resultados de tu análisis. +- It's deleted in all branches. +- The alert is removed from the number of current alerts for your project. +- It is _not_ added to the "Closed" list in the summary of alerts. +- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results. -Para descartar o borrar una alerta: +To dismiss or delete alerts: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. Si tienes permisos administrativos en el repositorio y quieres borrar las alertas para esta herramienta del {% data variables.product.prodname_code_scanning %}, selecciona algunas o todas las casillas de verificación y da clic en **Borrar**. +1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**. - ![Borrar alertas](/assets/images/help/repository/code-scanning-delete-alerts.png) + ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png) - Opcionalmente, puedes utilizar {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} la búsqueda gratuita por texto o{% endif %} los filtros para mostrar un subconjunto de alertas y luego borrar todas las alertas coincidentes a la vez. Por ejemplo, si eliminaste una consulta desde el análisis de {% data variables.product.prodname_codeql %}, puedes utilizar el filtro de "Regla" para listar solo las alertas para esa consulta y luego seleccionar y borrar todas esas alertas. + Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Filtrar alertas por regla](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} - ![Filtrar alertas por regla](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) + ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) {% endif %} -1. Si quieres descartar una alerta, es importante explorarla primero para que puedas elegir la razón correcta para descartarla. Da clic en la alerta que quisieras explorar. +1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Abrir una alerta desde la lista de sumario](/assets/images/help/repository/code-scanning-click-alert.png) + ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} - ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} -1. Revisa la alerta y da clic en **Descartar** y elije una razón para cerrarla. ![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) +1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. + ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} {% data reusables.code-scanning.false-positive-fix-codeql %} -### Descartar varias alertas al mismo tiempo +### Dismissing multiple alerts at once -Si un proyecto tiene varias alertas que quieras descartar por la misma razón, puedes descartarlas por lote desde el resúmen de las alertas. Habitualmente quieres filtrar la lista y luego descartar todas las alertas coincidentes. Por ejemplo, puede que quieras descartar todas las alertas actuales del proyecto que se hayan etiquetado para una vulnerabilidad de Enumeración de Debilidades (CWE, por sus siglas en inglés) Común en particular. +If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability. -## Leer más +## Further reading -- "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" -- "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" -- "[Acerca de la integración con {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)" +- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" +- "[About integration with {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)" diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index a586d2c66e..261690a29f 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -1,7 +1,7 @@ --- -title: Configurar el escaneo de código en un repositorio -shortTitle: Configurar el escaneo de código -intro: 'Puedes configurar el {% data variables.product.prodname_code_scanning %} si agregas un flujo de trabajo a tu repositorio.' +title: Setting up code scanning for a repository +shortTitle: Set up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' redirect_from: @@ -23,131 +23,134 @@ topics: - Actions - Repositories --- - {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -## Opciones para configurar el {% data variables.product.prodname_code_scanning %} +## Options for setting up {% data variables.product.prodname_code_scanning %} -Tú decides cómo generar las alertas del {% data variables.product.prodname_code_scanning %} y qué herramientas utilizar a nivel de repositorio. {% data variables.product.product_name %} te proporciona compatibilidad total e integrada para el análisis de {% data variables.product.prodname_codeql %} y también es compatible con el análisis de herramientas de terceros. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning#about-tools-for-code-scanning)". +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning#about-tools-for-code-scanning)." {% data reusables.code-scanning.enabling-options %} -## Configurar el {% data variables.product.prodname_code_scanning %} utilizando acciones +## Setting up {% data variables.product.prodname_code_scanning %} using actions -{% ifversion fpt or ghec %}El utilizar acciones para ejecutar el {% data variables.product.prodname_code_scanning %} utilizará minutos. Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".{% endif %} +{% ifversion fpt or ghec %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. A la derecha de "alertas del {% data variables.product.prodname_code_scanning_capc %}", haz clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}Si falta el {% data variables.product.prodname_code_scanning %}, necesitas pedir al propietario de la organización o adminsitrador del repositorio que habilite la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis en tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" o "[Administrar la configuración de seguridad y análisis en tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} ![Botón de "Configurar el {% data variables.product.prodname_code_scanning %}" a la derecha de "{% data variables.product.prodname_code_scanning_capc %}" en el resumen de seguridad](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Debajod e "Iniciar con el {% data variables.product.prodname_code_scanning %}", da clic en **Configurar este flujo de trabajo** en el {% data variables.product.prodname_codeql_workflow %} o en el flujo de trabajo de terceros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)Los flujos de trabajo solo se muestran si son relevantes para los lenguajes de programación que se detectan en el repositorio. El {% data variables.product.prodname_codeql_workflow %} siempre se muestra, pero el botón de "Configurar este flujo de trabajo" solo se habilita si el análisis de {% data variables.product.prodname_codeql %} es compatible con los lenguajes presentes en el repositorio. -5. Para personalizar la forma en que el {% data variables.product.prodname_code_scanning %} escanea tu còdigo, edita el flujo de trabajo. +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} + !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. + !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository. +5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. - Generalmente, puedes confirmar el {% data variables.product.prodname_codeql_workflow %} sin hacerle ningùn cambio. Sin embargo, muchos de los flujos de trabajo de terceros requieren de configuraciones adicionales, asì que lee los comentarios en el flujo de trabajo antes de confirmar. + Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. - Para obtener más información, consulta "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)". -6. Utiliza el menú desplegable de**Comenzar confirmación**, y teclea un mensaje de confirmación. ![Iniciar confirmación](/assets/images/help/repository/start-commit-commit-new-file.png) -7. Escoge si te gustaría confirmar directamente en la rama predeterminada, o crear una nueva rama y comenzar una solicitud de extracción. ![Escoger dónde confirmar](/assets/images/help/repository/start-commit-choose-where-to-commit.png) -8. Da clic en **Confirmar archivo nuevo** o en **Proponer archivo nuevo**. + For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)." +6. Use the **Start commit** drop-down, and type a commit message. + ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png) +7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. + ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. Click **Commit new file** or **Propose new file**. -En el {% data variables.product.prodname_codeql_workflow %} predeterminado, el {% data variables.product.prodname_code_scanning %} se configura para analizar tu código cada vez que ya sea subas un cambio a la rama predeterminada o a cualquier rama protegida, o que levantes una solicitud de cambios contra la rama predeterminada. Como resultado, el {% data variables.product.prodname_code_scanning %} comenzarà ahora. +In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. -Los activadores del escaneo de código `on:pull_request` y `on:push` son útiles para propósitos distintos. Para obtener más información, consulta las secciones "[Escanear solicitudes de cambios](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" y "[Escanear al subir](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)". -## Configuración del {% data variables.product.prodname_code_scanning %} por lotes +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." +## Bulk set up of {% data variables.product.prodname_code_scanning %} -Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. Si te gustaría utilizar un script para levantar solicitudes de cambios que agreguen un flujo de trabajo de {% data variables.product.prodname_actions %} a varios repositorios, consulta el repositorio de [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para encontrar un ejemplo utilizando Powershell o el de [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para los equipos que no tengan Powershell y quieran utilizar NodeJS en su lugar. +You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. -## Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} +## Viewing the logging output from {% data variables.product.prodname_code_scanning %} -Después de configurar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones mientras se ejecutan. +After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. {% data reusables.repositories.actions-tab %} - Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. El texto de la entrada es el título que le diste a tu mensaje de confirmación. + You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. - ![Lista de acciones que muestran el flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) -1. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. +1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. -1. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**. +1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. - ![Registro de salida del flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) -1. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan. +1. Review the logging output from the actions in this workflow as they run. -1. Una vez que todos los jobs se completen, puedes ver los detalles de cualquier alerta del {% data variables.product.prodname_code_scanning %} que se hayan identificado. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." {% note %} -**Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}. +**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} - ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endif %} {% endnote %} -## Entender las verificaciones de la solicitud de cambios +## Understanding the pull request checks -Cada flujo de trabajo del {% data variables.product.prodname_code_scanning %} que configuras para que se utilice en las solicitudes de cambios siempre tiene por lo menos dos entradas listadas en la sección de verificaciones de una solicitud de cambios. Solo hay una entrada para cada uno de los jobs de anàlisis en el flujo de trabajo y uno final para los resultados del anàlisis. +Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. -Los nombres de las verificaciones del anàlisis del {% data variables.product.prodname_code_scanning %} se expresan en la forma: "NOMBRE DE LA HERRAMIENTA / NOMBRE DEL JOB (ACTIVADOR)." Por ejemplo, para {% data variables.product.prodname_codeql %}, el anàlisis de còdigo en C++ tiene la entrada "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)". Puedes dar clic en **Detalles** en una entrada de anàlisis de {% data variables.product.prodname_code_scanning %} para ver los datos de registro. Esto te permite depurar un problema si falla el job de anàlisis. Por ejemplo, para el anàlisis del {% data variables.product.prodname_code_scanning %} de los lenguajes compilados, esto puede suceder si la acciòn no puede compilar el còdigo. +The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code. - ![Verificaciones de solicitudes de cambios del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) + ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) -Cuando se completan los jobs del {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dotcom %} averigua si la solicitud de cambios agregò alguna alerta y agrega la entrada "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA" a la lista de verificaciones. Despuès de que se lleve a cabo el {% data variables.product.prodname_code_scanning %} por lo menos una vez, puedes dar clic en **Detalles** para ver los resultados del anàlisis. Si utilizaste una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} al repositorio, inicialmente verás un mensaje de {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} "Analysis not found"{% else %} "Missing analysis"{% endif %} cuando haces clic en **Detalles** en la verificación de "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME". +When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} - ![Mensaje de confirmación de "Analysis not found"](/assets/images/help/repository/code-scanning-analysis-not-found.png) + ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -La tabla lista una o más categorías. Cada categoría se relaciona con análisis específicos, para la misma herramienta y confirmación, que se realizan en un lenguaje o parte del código diferentes. En cada categoría, la tabla muestra los dos análisis que {% data variables.product.prodname_code_scanning %} intentó comparar para determinar qué alertas se introdujeron o corrigieron en la solicitud de cambios. +The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. -Por ejemplo, en la captura de pantalla anterior, el {% data variables.product.prodname_code_scanning %} encontró un análisis para la confirmación de fusión de la solicitud de cambios, pero no encontró ningún análisis para el encabezado de la rama principal. +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. {% else %} - ![Falta el análisis para el mensaje de confirmación](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) + ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} -### Razones para obtener el mensaje "Analysis not found" +### Reasons for the "Analysis not found" message {% else %} -### Razones para obtener el mensaje "Missing analysis" +### Reasons for the "Missing analysis" message {% endif %} -Despuès de que el {% data variables.product.prodname_code_scanning %} analiza el còdigo en una solicitud de cambios, necesita comparar el anàlisis de la rama de tema (la rama que utilizaste para crear la silicolicitud de cambios) con el anàlisis de la rama base (la rama en la cual quieres fusionar la solicitud de cambios). Esto permite al {% data variables.product.prodname_code_scanning %} calcular què alertas introdujo la solicitud de cambios recientemente, cuàles ya estaban presentes en la rama base y si es que cualquiera de las alertas existentes se arreglan con los cambios que lleva la solicitud. Inicialmente, si utilizas una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} a un repositorio, la rama base no se ha analizado, asì que no es posible calcular estos detalles. En este caso, cuando haces clic desde la verificación de resultados en la solicitud de cambios, verás el mensaje {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %}. +After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. -Existen otras situaciones en donde puede que no haya un anàlisis para la ùltima confirmaciòn hacia la rama base para una solicitud de cambios. Entre estas se incluyen cuando: +There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: -* La solicitud de cambios se levantó contra una rama diferente a la predeterminada y ésta no se ha analizado. +* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed. - Para verificar si se ha escaneado una rama, ve a la pàgina de {% data variables.product.prodname_code_scanning_capc %}, da clic en el menù desplegable de **Rama** y selecciona la rama relevante. + To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Elige una rama del menú desplegable de Rama](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} - ![Elige una rama del menú desplegable de Rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) {% endif %} - La soluciòn a esta situaciòn es agregar el nombre de esta rama base a las especificaciones de `on:push` y `on:pull_request` en el flujo de trabajo del {% data variables.product.prodname_code_scanning %} en esta rama y luego hacer un cambio que actualice la solicitud de cambios abierta que quieres escanear. + The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. -* La ùltima confirmaciòn en la rama base para la solicitud de cambios se està analizando actualmente y dicho anàlisis no està disponible aùn. +* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. - Espera algunos minutos y luego sube un cambio a la solicitud de extracciòn para reactivar el {% data variables.product.prodname_code_scanning %}. + Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. -* Ocurriò un error mientras se analizaba la ùltima confirmaciòn en la rama base y el anàlisis para esa confirmaciòn no està disponible. +* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available. - Fusiona un cambio trivial en la rama base para activar el {% data variables.product.prodname_code_scanning %} en esta ùltima confirmaciòn, luego sube un cambio a la solicitud de extracciòn para volver a activar el {% data variables.product.prodname_code_scanning %}. + Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. -## Pasos siguientes +## Next steps -Después de configurar el {% data variables.product.prodname_code_scanning %} y permitir que se completen sus acciones, puedes: +After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: -- Ver todas las alertas del {% data variables.product.prodname_code_scanning %} que se han generado para este repositorio. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". -- Ver cualquier alerta que se genere para una solicitud de cambios que se emitió después de que configuraste el {% data variables.product.prodname_code_scanning %}. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de extracción](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". -- Configurar las notificaciones para las ejecuciones que se hayan completado. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)". -- Visualizar las bitácoras que generó el análisis del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)". -- Investigar cualquier problema que ocurre con la configuración inicial del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Solucionar problemas del flujo de trabajo de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)". -- Personaliza cómo el {% data variables.product.prodname_code_scanning %} escanea el código en tu repositorio. Para obtener más información, consulta "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)". +- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." +- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." +- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." +- View the logs generated by the {% data variables.product.prodname_code_scanning %} analysis. For more information, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)." +- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)." +- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)." diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index e42694e7a6..c185d25ea2 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -1,7 +1,7 @@ --- -title: Clasificar las alertas del escaneo de código en las solicitudes de cambios -shortTitle: Clasificar las alertas en las solicitudes de cambio -intro: 'Cuando el {% data variables.product.prodname_code_scanning %} identifica un problema en una solicitud de extracción, puedes revisar el código que se ha resaltado y resolver la alerta.' +title: Triaging code scanning alerts in pull requests +shortTitle: Triage alerts in pull requests +intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.' redirect_from: @@ -21,76 +21,75 @@ topics: - Alerts - Repositories --- - {% data reusables.code-scanning.beta %} -## Acerca de los resultados del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios +## About {% data variables.product.prodname_code_scanning %} results on pull requests -En los repositorios donde se configura el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambios, éste verificará el código en dicha solicitud. Predeterminadamente, esto se limita a solicitudes de cambios que apuntan a la rama predeterminada, pero puedes cambiar esta configuración dentro de {% data variables.product.prodname_actions %} o en un sistema de IC/EC de terceros. Si el fusionar los cambios puede introducir alertas nuevas de {% data variables.product.prodname_code_scanning %} a la rama destino, éstas se reportarán como resultados de verificación en la solicitud de cambios. Las alertas también se muestran como anotaciones en la pestaña de **Archivos que cambiaron** de la solicitud de cambios. Si tienes permisos de escritura para el repositorio, puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} existente en la pestaña de **Seguridad**. Para obtener más información sobre las alertas de los repositorios, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". +In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." {% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} -Si tu solicitud de cambios apunta a una rama protegida que utiliza el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces la verificación de los "resultados del {% data variables.product.prodname_code_scanning_capc %}" debe pasar antes de que puedas fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". +If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." -## Acerca del {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambio +## About {% data variables.product.prodname_code_scanning %} as a pull request check -Hay muchas opciones para configurar el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambio, así que la configuración de cada repositorio variará y algunas tendrán más de una verificación. +There are many options for configuring {% data variables.product.prodname_code_scanning %} as a pull request check, so the exact setup of each repository will vary and some will have more than one check. -### Verificación de resultados de {% data variables.product.prodname_code_scanning_capc %} +### {% data variables.product.prodname_code_scanning_capc %} results check -Para todas las configuraciones del {% data variables.product.prodname_code_scanning %}, la verificación que contiene los resultados del {% data variables.product.prodname_code_scanning %} es: **resultados de {% data variables.product.prodname_code_scanning_capc %}**. Los resultados para cada herramienta de análisis se muestran por separado. Cualquier alerta nueva que ocasionen los cambios en la solicitud de cambios se muestran como anotaciones. +For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} Para ver el conjunto de alertas completo de la rama analizada, haz clic en **Ver todas las alertas de rama**. Esto abre la vista completa de alertas en donde puedes filtrar todas las de la rama por tipo, gravedad, etiqueta, etc. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)". +{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." -![verificación de resultados de {% data variables.product.prodname_code_scanning_capc %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-results-check.png) +![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} -### Fallos de verificación de resultados de {% data variables.product.prodname_code_scanning_capc %} +### {% data variables.product.prodname_code_scanning_capc %} results check failures -Si la verificación de los resultados del {% data variables.product.prodname_code_scanning %} encuentra cualquier problema con una gravedad de `error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %}, `critical`, o `high`,{% endif %} la verificación fallará y el error se reportará en los resultados de verificación. Si todos los resultados que encontró el {% data variables.product.prodname_code_scanning %} tienen gravedades menores, las alertas se tratarán como advertencias o notas y la verificación tendrá éxito. +If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, `critical`, or `high`,{% endif %} the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds. -![Verificación fallida del {% data variables.product.prodname_code_scanning %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-check-failure.png) +![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}Puedes anular el comportamiento predeterminado de los ajustes de tu repositorio si especificas el nivel de gravedad {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 or ghec %} y las gravedades de seguridad {% endif %} que ocasionarán el fallo de una verificación de solicitud de cambios. Para obtener más información, consulta la sección "[Definir las gravedades que ocasionan un fallo en la verificación de las solicitudes de cambios](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". +{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". {% endif %} -### Otras verificaciones del {% data variables.product.prodname_code_scanning %} +### Other {% data variables.product.prodname_code_scanning %} checks -Dependiendo de tu configuración, podrías ver verificaciones adicionales ejecutándose en las solicitudes de cambios con el {% data variables.product.prodname_code_scanning %} configurado. A menudo, estos son flujos de trabajo que analizan el código o que cargan resultados del {% data variables.product.prodname_code_scanning %}. Estas verificaciones son útiles para solucionar problemas cuando el análisis los presenta. +Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis. -Por ejemplo, si el repositorio utiliza el {% data variables.product.prodname_codeql_workflow %}, se ejecutará una verificación de **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** para cada lenguaje antes de que se ejecute la verificación de resultados. La verificación del análisis podría fallar si existieran problemas de configuración o si la solicitud de cambios impide la compilación para un lenguaje que el análisis necesita compilar (por ejemplo, C/C++, C# o Java). +For example, if the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java). -Así como con otras verificaciones de solicitudes de cambios, puedes ver todos los detalles de la falla de la verificación en la pestaña de **Verificaciones**. Para obtener más información acerca de la configuración y la soución de problemas, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" o "[Solucionar problemas del flujo de trabajo de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)". +As with other pull request checks, you can see full details of the check failure on the **Checks** tab. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)." -## Visualizar una alerta en tu solicitud de cambios +## Viewing an alert on your pull request -Puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} que se haya introducido en una solicitud de cambios si muestras la pestaña de **Archivos que cambiaron**. Cada alerta se muestra como una anotación en las líneas de código que la activaron. La gravedad de la alerta se muestra en la anotación. +You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation. -![Anotación de alerta dentro de un diff de una solicitud de cambios](/assets/images/help/repository/code-scanning-pr-annotation.png) +![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) -Si tienes permisos de escritura para el repositorio, algunas anotaciones contendrán enlaces con un contexto adicional de la alerta. En el ejemplo anterior del análisis de {% data variables.product.prodname_codeql %}, puedes dar clic en **valor proporcionado por el usuario** para ver en dónde ingresarían los datos no confiables dentro del flujo de datos (a esto se le conoce como la fuente). En este caso, también puedes ver la ruta completa desde la fuente hasta el código que utiliza los datos (el consumidor de datos) dando clic en **Mostrar rutas**. Esto facilita la revisión, ya sea que los datos no sean confiables o que el análisis falle en reconocer un paso de sanitización de datos entre la fuente y el consumidor de datos. Para obtener información sobre cómo analizar el flujo de datos utilizando {% data variables.product.prodname_codeql %}, consulta la sección "[Acerca del análisis de flujo de datos](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)". +If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)." -Para ver más información sobre una alerta, los usuarios con permisos de escritura pueden dar clic en el enlace de **Mostrar más detalles** que se muestra en la anotación. Esto te permite ver todo el contexto y los metadatos que proporciona la herramienta en una vista de alertas. En el siguiente ejemplo, puedes ver que las etiquetas muestran la severidad, tipo y las enumeraciones de los puntos débiles comunes (los CWE) del problema. La vista también muestra qué confirmación introdujo el problema. +To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem. -En la vista detallada de una alerta, algunas herramientas del {% data variables.product.prodname_code_scanning %}, como el análisis de {% data variables.product.prodname_codeql %}, también incluyen una descripción del problema y un enlace de **Mostrar más** para orientarte sobre cómo arreglar tu código. +In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code. -![Descripción de alerta y enlace para mostrar más información](/assets/images/help/repository/code-scanning-pr-alert.png) +![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png) -## Arreglar una alerta en tu solicitud de cambios +## Fixing an alert on your pull request -Cualquiera con acceso de subida a una solicitud de cambios puede arreglar una alerta del {% data variables.product.prodname_code_scanning %}, la cual se identifique en dicha solicitud. Si confirmas cambios en la solicitud de extracción, esto activará una ejecución nueva de las verificaciones de dicha solicitud. Si tus cambios arreglan el problema, la alerta se cierra y la anotación se elimina. +Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed. -## Descartar una alerta en tu solicitud de cambios +## Dismissing an alert on your pull request -Una forma alterna de cerrar una alerta es descartarla. Puedes descartar una alerta si no crees que necesite arreglarse. {% data reusables.code-scanning.close-alert-examples %} Si tienes permisos de escritura en el repositorio, el botón de **Descartar** está disponible en las anotaciones de código y en el resumen de alertas. Cuando das clic en **Descartar** se te pedirá elegir una razón para cerrar la alerta. +An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert. -![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) +![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} {% data reusables.code-scanning.false-positive-fix-codeql %} -Para obtener más información acerca de descartar alertas, consulta la sección "[Administrar alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)". +For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)." diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md index d1a3d99299..f6811cfb39 100644 --- a/translations/es-ES/content/code-security/getting-started/github-security-features.md +++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md @@ -1,6 +1,6 @@ --- -title: Características de seguridad de GitHub -intro: 'Un resumen de las características de seguridad de {% data variables.product.prodname_dotcom %}.' +title: GitHub security features +intro: 'An overview of {% data variables.product.prodname_dotcom %} security features.' versions: fpt: '*' ghes: '*' @@ -14,72 +14,76 @@ topics: - Advanced Security --- -## Acerca de las característicfas de seguridad de {% data variables.product.prodname_dotcom %} +## About {% data variables.product.prodname_dotcom %}'s security features -{% data variables.product.prodname_dotcom %} tiene características de seguridad que ayudan a mantener seguros el código y los secretos en los repositorios y a través de las organizaciones. Algunas características están disponibles para todos los repositorios y otras solo están disponibles {% ifversion fpt or ghec %}para repositorios públicos y para aquellos{% endif %}con una licencia de {% data variables.product.prodname_GH_advanced_security %}. +{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. Some features are available for all repositories and others are only available {% ifversion fpt or ghec %}for public repositories and for repositories {% endif %}with a {% data variables.product.prodname_GH_advanced_security %} license. -La {% data variables.product.prodname_advisory_database %} contiene una lista organizada de vulnerabilidades de seguridad que puedes ver, buscar y filtrar. {% data reusables.security-advisory.link-browsing-advisory-db %} +The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -## Disponible para todos los repositorios +## Available for all repositories {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -### Política de seguridad - -Facilítale a tus usuarios el poder reportar de forma confidencial las vulnerabilidades de seguridad que hayan encontrado en tu repositorio. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)". +### Security policy + +Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." {% endif %} {% ifversion fpt or ghec %} -### Asesorías de seguridad +### Security advisories -Debate en privado y arregla las vulnerabilidades de seguridad en el código de tu repositorio. Entonces podrás publicar una asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad y exhortar a sus miembros a hacer la actualización correspondiente. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". +Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." -### {% data variables.product.prodname_dependabot_alerts %} y actualizaciones de seguridad +{% endif %} +{% ifversion fpt or ghec or ghes > 3.2 %} -Ver alertas acerca de las dependencias de las cuales se sabe contienen vulnerabilidades de seguridad y elige si se generarán automáticamente las solicitudes de extracción para actualizar dichas dependencias. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +### {% data variables.product.prodname_dependabot_alerts %} and security updates + +View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" +and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae-issue-4864 %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} -Visualiza las alertas sobre las dependencias de las cuales se conoce que contienen vulnerabilidades de seguridad y adminístralas. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". +View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} -{% ifversion fpt or ghec %} -### Las actualizaciones de versión del {% data variables.product.prodname_dependabot %} +{% ifversion fpt or ghec or ghes > 3.2 %} +### {% data variables.product.prodname_dependabot %} version updates -Utilizan al {% data variables.product.prodname_dependabot %} para levantar las solicitudes de cambios automáticamente para mantener tus dependencias actualizadas. Esto te ayuda a reducir tu exposición a las versiones anteriores de las dependencias. El utilizar versiones más nuevas facilita aún más la aplicación de parches si se descubren las vulnerabilidades de seguridad, y también facilita que las {% data variables.product.prodname_dependabot_security_updates %} levante las solicitudes de cambios exitosamente para mejorar las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". +Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -### Gráfica de dependencias -La gráfica de dependencias te permite explorar los ecosistemas y paquetes de los cuales depende tu repositorio y los repositorios y paquetes que dependen de tu repositorio. +### Dependency graph +The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. -Puedes encontrar la gráfica de dependencias en lapestaña de **Perspectivas** para tu repositorio. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -## Disponible {% ifversion fpt or ghec %}para los repositorios públicos y para aquellos {% endif %}con {% data variables.product.prodname_advanced_security %} +## Available {% ifversion fpt or ghec %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} {% ifversion fpt or ghes or ghec %} -Estas características están disponibles {% ifversion fpt or ghec %}para todos los repositorios públicos y para los repositorios privados que pertenezcan a las organizaciones con {% else %}si tienes {% endif %}una licencia de {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} +These features are available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} {% endif %} -### Alertas de {% data variables.product.prodname_code_scanning_capc %} +### {% data variables.product.prodname_code_scanning_capc %} alerts -Detecta automáticamente las vulnerabilidades de seguridad y los errores de código en el código nuevo o modificado. Se resaltan los problemas potenciales, con información detallada, lo cual te permite arreglar el código antes de que se fusione en tu rama predeterminada. Para obtener más información, consulta la sección "[Acerca del escaneo de código"](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning). +Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." -### alertas del {% data variables.product.prodname_secret_scanning_caps %} +### {% data variables.product.prodname_secret_scanning_caps %} alerts -{% ifversion fpt or ghec %}Para los repositorios privados, ve {% else %}Ve {% endif %}cualquier secreto que {% data variables.product.prodname_dotcom %} haya encontrado en tu código. Deberías tratar a los tokens o las credenciales que se hayan registrado en tu repositorio como puestos en riesgo. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). +{% ifversion fpt or ghec %}For private repositories, view {% else %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -### Revisión de dependencias +### Dependency review -Muestra el impacto total de los cambios a las dependencias y ve los detalles de cualquier versión vulnerable antes de que fusiones una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)". +Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -## Leer más -- "[Productos de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)" -- "[soporte de idiomas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-language-support)" +## Further reading +- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)" +- "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)" diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md index b27b5d80d9..f88ddfd505 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md @@ -1,6 +1,6 @@ --- -title: Asegurar tu organización -intro: 'Puedes utilizar varias características de {% data variables.product.prodname_dotcom %} para ayudar a mantener tu organización segura.' +title: Securing your organization +intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.' permissions: Organization owners can configure organization security settings. versions: fpt: '*' @@ -13,112 +13,112 @@ topics: - Dependencies - Vulnerabilities - Advanced Security -shortTitle: Asegurar tu organización +shortTitle: Secure your organization --- -## Introducción -Esta guía te muestra cómo configurar las características de seguridad para una organización. Las necesidades de seguridad de tu organización son únicas y puede que no necesites habilitar cada una de las características de seguridad. Para obtener más información, consulta la sección "[Características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". +## Introduction +This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." Some security features are only available {% ifversion fpt or ghec %}for public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} -## Administrar el acceso a tu organización +## Managing access to your organization You can use roles to control what actions people can take in your organization. {% if security-managers %}For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghec %} -## Crear una política de seguridad predeterminada +## Creating a default security policy -Puedes crear una política de seguridad predeterminada que se mostrará en cualquier repositorio público de tu organización que no tenga su propia política de seguridad. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." +You can create a default security policy that will display in any of your organization's public repositories that do not have their own security policy. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %} -## Administrar las {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias +## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias para todos los repositorios privados que pertenezcan a tu organización. +{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. -1. Haz clic en tu foto de perfil y luego en **Organizaciones**. -2. Haz clic en **Configuración** junto a tu organización. -3. Haz clic en **Análisis & seguridad**. -4. Haz clic en **Habilitar todo** o en **Inhabilitar todo** junto a la característica que quieras administrar. -5. Opcionalmente, selecciona **Habilitar automáticamente para los repositorios nuevos**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to the feature that you want to manage. +5. Optionally, select **Automatically enable for new repositories**. {% endif %} {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -Para obtener más información, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Explorar las dependencias de un repositorio](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," y "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -## Administrar la revisión de dependencias +## Managing dependency review -La revisión de dependencias te permite visualizar los cambios a las dependencias en las solicitudes de cambios antes de que se fusionen con tus repositorios. -{% ifversion fpt or ghec %}Dependency review is available in all public repositories. Para los repositorios internos y privados, requieres una licencia para {% data variables.product.prodname_advanced_security %}. Para habilitar la revisión de dependencias de una organización, habilita la gráfica de dependencias y la {% data variables.product.prodname_advanced_security %}. -{% elsif ghes or ghae %}La revisión de dependencias se encuentra disponible cuando se habilite la gráfica de dependencias para {% data variables.product.product_location %} y también la {% data variables.product.prodname_advanced_security %} para la organización (consulta a continuación).{% endif %} -Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". +Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. +{% ifversion fpt or ghec %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for an organization, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. +{% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %} +For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." {% endif %} -{% ifversion fpt or ghec %} -## Administrar las {% data variables.product.prodname_dependabot_security_updates %} +{% ifversion fpt or ghec or ghes > 3.2 %} +## Managing {% data variables.product.prodname_dependabot_security_updates %} -En el caso de cualquier repositorio que utilice las {% data variables.product.prodname_dependabot_alerts %}, puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para levantar solicitudes de cambio con actualizaciones de seguridad cuando se detectan las vulnerabilidades. También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios a lo largo de tu organización. +For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization. -1. Haz clic en tu foto de perfil y luego en **Organizaciones**. -2. Haz clic en **Configuración** junto a tu organización. -3. Haz clic en **Análisis & seguridad**. -4. Haz clic en **Habilitar todas** or en **Inhabilitar todas** junto a {% data variables.product.prodname_dependabot_security_updates %}. -5. Opcionalmente, selecciona **Habilitar automáticamente para los repositorios nuevos**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_dependabot_security_updates %}. +5. Optionally, select **Automatically enable for new repositories**. -Para obtener más información, consulta las secciones "[Acerca de {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" y "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -## Administrar las {% data variables.product.prodname_dependabot_version_updates %} +## Managing {% data variables.product.prodname_dependabot_version_updates %} -Puedes habilitar el {% data variables.product.prodname_dependabot %} para levantar automáticamente las solicitudes de cambios para mantener tus dependencias actualizadas. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)". +You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)." -Para habilitar las {% data variables.product.prodname_dependabot_version_updates %}, debes crear un archivo de configuración *dependabot.yml*. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/code-security/supply-chain-security/enabling-and-disabling-version-updates)". +To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." {% endif %} {% ifversion fpt or ghes > 2.22 or ghae or ghec %} -## Admnistrar la {% data variables.product.prodname_GH_advanced_security %} +## Managing {% data variables.product.prodname_GH_advanced_security %} {% ifversion fpt or ghes > 2.22 or ghec %} -Si tu organización cuenta con una licencia de {% data variables.product.prodname_advanced_security %}, puedes habilitar o inhabilitar las características de la {% data variables.product.prodname_advanced_security %}. +If your organization has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features. {% elsif ghae %} -Puedes habilitar o inhabilitar las características de la {% data variables.product.prodname_advanced_security %}. +You can enable or disable {% data variables.product.prodname_advanced_security %} features. {% endif %} -1. Haz clic en tu foto de perfil y luego en **Organizaciones**. -2. Haz clic en **Configuración** junto a tu organización. -3. Haz clic en **Análisis & seguridad**. -4. Haz clic en **Habilitar todas** or en **Inhabilitar todas** junto a {% data variables.product.prodname_GH_advanced_security %}. -5. Opcionalmente, selecciona **Habilitar automáticamente para los repositorios privados nuevos**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_GH_advanced_security %}. +5. Optionally, select **Automatically enable for new private repositories**. -Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" y "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -## Configurar el {% data variables.product.prodname_secret_scanning %} +## Configuring {% data variables.product.prodname_secret_scanning %} {% data variables.product.prodname_secret_scanning_caps %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. -Puedes habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} para todos los repositorios a lo largo de tu organización que tengan habilitada la {% data variables.product.prodname_advanced_security %}. +You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled. -1. Haz clic en tu foto de perfil y luego en **Organizaciones**. -2. Haz clic en **Configuración** junto a tu organización. -3. Haz clic en **Análisis & seguridad**. -4. Haz clic en **Habilitar todo** o en **Inhabilitar todo** junto a {% data variables.product.prodname_secret_scanning_caps %} (solo para repositorios de la {% data variables.product.prodname_GH_advanced_security %}). -5. Opcionalmente, selecciona **Habilitar automáticamente para los repositorios privados que se agregan a la {% data variables.product.prodname_advanced_security %}**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_secret_scanning_caps %} ({% data variables.product.prodname_GH_advanced_security %} repositories only). +5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. -Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -## Pasos siguientes -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. Para obtener más información, consulta la sección "[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)".{% endif %} +## Next steps +{% ifversion fpt or ghes > 3.1 or ghec %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% endif %} -Puedes ver y administrar las alertas de las características de seguridad para abordar dependencias y vulnerabilidades en tu código. For more information, see {% ifversion fpt or ghes > 2.22 or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes > 2.22 or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. Para obtener más información, consulta las secciones "[Acerca de {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" y "[Crear una asesoría de seguridad](/code-security/security-advisories/creating-a-security-advisory)". +{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md index b16b07bc89..8b7f466b77 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md @@ -1,6 +1,6 @@ --- -title: Asegurar tu repositorio -intro: 'Puedes utilizar varias características de {% data variables.product.prodname_dotcom %} para ayudar a mantener tu repositorio seguro.' +title: Securing your repository +intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your repository secure.' permissions: Repository administrators and organization owners can configure repository security settings. redirect_from: - /github/administering-a-repository/about-securing-your-repository @@ -16,119 +16,119 @@ topics: - Dependencies - Vulnerabilities - Advanced Security -shortTitle: Asegurar tu repositorio +shortTitle: Secure your repository --- -## Introducción -Esta guía te muestra cómo configurar las características de seguridad para un repositorio. Debes ser un administrador de repositorio o propietario de organización para configurar las caracteristicas de seguridad de un repositorio. +## Introduction +This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository. -Tus necesidades de seguridad son únicas de tu repositorio, así que puede que no necesites habilitar todas las características de seguridad para este. Para obtener más información, consulta la sección "[Características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". +Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." Some security features are only available {% ifversion fpt or ghec %}for public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} -## Administrar el acceso a tu repositorio +## Managing access to your repository -El primer paso para asegurar un repositorio es configurar quién puede ver y modificar tu código. Para obtener más información, consulta la sección "[Administrar la configuración de los repositorios](/github/administering-a-repository/managing-repository-settings)". +The first step to securing a repository is to set up who can see and modify your code. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)." -Desde la página principal de tu repositorio, haz clic en **{% octicon "gear" aria-label="The Settings gear" %} Configuración** y luego desplázate hacia abajo, hacia la "Zona de Peligro". +From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**, then scroll down to the "Danger Zone." -- Para cambiar quién puede ver tu repositorio, haz clic en **Cambiar la visibilidad**. Para obtener más información, consulta la sección "[Configurar la visibilidad de los repositorios](/github/administering-a-repository/setting-repository-visibility)".{% ifversion fpt or ghec %} -- Puedes cambiar quién puede acceder a tu repositorio y ajustar los permisos, haz clic en **Administrar acceso**. Para obtener más información, consulta la sección "[Administrar los equipos y personas con acceso a tu repositorio](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)".{% endif %} +- To change who can view your repository, click **Change visibility**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %} +- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)."{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -## Configurar una política de seguridad +## Setting a security policy -1. Desde la página principal de tu repositorio, haz clic en **{% octicon "shield" aria-label="The shield symbol" %} Seguridad**. -2. Haz clic en **Política de seguridad**. -3. Haz clic en **Start setup** (Iniciar configuración). -4. Agrega información sobre las versiones compatibles con tu proyecto y de cómo reportar las vulnerabilidades. +1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**. +2. Click **Security policy**. +3. Click **Start setup**. +4. Add information about supported versions of your project and how to report vulnerabilities. -Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)". +For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." {% endif %} {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -## Administrar la gráfica de dependencias +## Managing the dependency graph {% ifversion fpt or ghec %} -Una vez que hayas [habilitado la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), esta se generará automáticamente para todos los repositorios públicos y podrás elegir habilitarla para los repositorios privados. +Once you have [enabled the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), it is automatically generated for all public repositories, and you can choose to enable it for private repositories. -1. Desde la página principal de tu repositorio, haz clic en **{% octicon "gear" aria-label="The Settings gear" %} Configuración**. -2. Haz clic en **Análisis & seguridad**. -3. Junto a la gráfica de dependencias, haz clic en **Habilitar** o **Inhabilitar**. +1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**. +2. Click **Security & analysis**. +3. Next to Dependency graph, click **Enable** or **Disable**. {% endif %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". +For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." {% endif %} {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -## Administrar las {% data variables.product.prodname_dependabot_alerts %} +## Managing {% data variables.product.prodname_dependabot_alerts %} -{% ifversion fpt or ghec %}Predeterminadamente, {% data variables.product.prodname_dotcom %} detecta vulnerabilidades en repositorios públicos y genera {% data variables.product.prodname_dependabot_alerts %}. Las {% data variables.product.prodname_dependabot_alerts %} también pueden habilitarse para los repositorios privados. +{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} can also be enabled for private repositories. -1. Haz clic en tu foto de perfil y luego en **Configuración**. -2. Haz clic en **Análisis & seguridad**. -3. Haz clic en **Habilitar todas** junto a {% data variables.product.prodname_dependabot_alerts %}. +1. Click your profile photo, then click **Settings**. +2. Click **Security & analysis**. +3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}. {% endif %} {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -Para obtener más información, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" y "[Administrar la configuración de seguridad y análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}". +For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -## Administrar la revisión de dependencias +## Managing dependency review -La revisión de dependencias te permite visualizar los cambios a las dependencias en las solicitudes de cambios antes de que se fusionen con tus repositorios. -{%- ifversion fpt %}La revisión de dependencias está disponible en todos los repositorios públicos. Para los repositorios internos y privados, requieres una licencia para {% data variables.product.prodname_advanced_security %}. Para habilitar la revisión de dependencias de un repositorio, habilita la gráfica de dependencias y la {% data variables.product.prodname_advanced_security %}. -{%- elsif ghes or ghae %}La revisión de dependencias se encuentra disponible cuando se habilite la gráfica de dependencias para {% data variables.product.product_location %} y también la {% data variables.product.prodname_advanced_security %} para la el repositorio (consulta a continuación).{% endif %} -Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". +Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. +{%- ifversion fpt %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for a repository, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. +{%- elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the repository (see below).{% endif %} +For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.2 %} -## Administrar las {% data variables.product.prodname_dependabot_security_updates %} +## Managing {% data variables.product.prodname_dependabot_security_updates %} -En el caso de cualquier repositorio que utilice las {% data variables.product.prodname_dependabot_alerts %}, puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para levantar solicitudes de cambio con actualizaciones de seguridad cuando se detectan las vulnerabilidades. +For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. -1. Desde la página principal de tu repositorio, haz clic en **{% octicon "gear" aria-label="The Settings gear" %} Configuración**. -2. Haz clic en **Análisis & seguridad**. -3. Junto a {% data variables.product.prodname_dependabot_security_updates %}, haz clic en **Habilitar**. +1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**. +2. Click **Security & analysis**. +3. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**. -Para obtener más información, consulta las secciones "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)". +For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)." -## Administrar las {% data variables.product.prodname_dependabot_version_updates %} +## Managing {% data variables.product.prodname_dependabot_version_updates %} -Puedes habilitar el {% data variables.product.prodname_dependabot %} para levantar automáticamente las solicitudes de cambios para mantener tus dependencias actualizadas. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)". +You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)." -Para habilitar las {% data variables.product.prodname_dependabot_version_updates %}, debes crear un archivo de configuración *dependabot.yml*. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/code-security/supply-chain-security/enabling-and-disabling-version-updates)". +To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." {% endif %} -## Configurar {% data variables.product.prodname_code_scanning %} +## Configuring {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} se encuentra disponible {% ifversion fpt or ghec %}para todos los repositorios públicos y para los repositorios privados que pertenezcan a organizaciones con{% else %} para repositorios que pertenezcan a organizaciones si tienen{% endif %}una licencia de {% data variables.product.prodname_advanced_security %}. +{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. -Puedes configurar el {% data variables.product.prodname_code_scanning %} para que identifique automáticamente las vulnerabilidades y los errores en el código que se almacena en tu repositorio si utilizas un {% data variables.product.prodname_codeql_workflow %} o una herramienta de terceros. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". +You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.product.prodname_codeql_workflow %} or third-party tool. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." -## Configurar el {% data variables.product.prodname_secret_scanning %} -{% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible {% ifversion fpt or ghec %}para todos los repositorios públicos y para los repositorios privados que pertenezcan a organizaciones con{% else %} para repositorios que pertenezcan a organizaciones si tienen{% endif %}una licencia de {% data variables.product.prodname_advanced_security %}. +## Configuring {% data variables.product.prodname_secret_scanning %} +{% data variables.product.prodname_secret_scanning_caps %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. -El {% data variables.product.prodname_secret_scanning_caps %} podría estar habilitado para tu repositorio predeterminadamente dependiendo de la configuración de tu organización. +{% data variables.product.prodname_secret_scanning_caps %} may be enabled for your repository by default depending upon your organization's settings. -1. Desde la página principal de tu repositorio, haz clic en **{% octicon "gear" aria-label="The Settings gear" %} Configuración**. -2. Haz clic en **Análisis & seguridad**. -3. Si {% data variables.product.prodname_GH_advanced_security %} no está habilitada previamente, haz clic en **Habilitar**. -4. Junto a {% data variables.product.prodname_secret_scanning_caps %}, haz clic en **Habilitar**. +1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**. +2. Click **Security & analysis**. +3. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**. +4. Next to {% data variables.product.prodname_secret_scanning_caps %}, click **Enable**. -## Pasos siguientes -Puedes ver y administrar las alertas de las características de seguridad para abordar dependencias y vulnerabilidades en tu código. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +## Next steps +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. Para obtener más información, consulta las secciones "[Acerca de {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" y "[Crear una asesoría de seguridad](/code-security/security-advisories/creating-a-security-advisory)". +{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/es-ES/content/code-security/guides.md b/translations/es-ES/content/code-security/guides.md index 4b6db5829d..ad1f3074c0 100644 --- a/translations/es-ES/content/code-security/guides.md +++ b/translations/es-ES/content/code-security/guides.md @@ -1,6 +1,6 @@ --- -title: Guías para la seguridad del código -intro: 'Aprende sobre las formas diferentes en las que {% data variables.product.product_name %} puede ayudarte a mejorar la seguridad de tu código.' +title: Guides for code security +intro: 'Learn about the different ways that {% data variables.product.product_name %} can help you improve your code''s security.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -26,6 +26,7 @@ includeGuides: - /code-security/secret-security/about-secret-scanning - /code-security/secret-security/configuring-secret-scanning-for-your-repositories - /code-security/secret-security/managing-alerts-from-secret-scanning + - /code-security/code-scanning//automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages @@ -58,7 +59,7 @@ includeGuides: - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates - - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates + - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot diff --git a/translations/es-ES/content/code-security/index.md b/translations/es-ES/content/code-security/index.md index 5fff44167e..49eee619c6 100644 --- a/translations/es-ES/content/code-security/index.md +++ b/translations/es-ES/content/code-security/index.md @@ -1,7 +1,7 @@ --- -title: Seguridad de código -shortTitle: Seguridad de código -intro: 'Crea la seguridad de tu flujo de trabajo de {% data variables.product.prodname_dotcom %} con características para mantener tus secretos y vulnerabilidades duera de tu base de código{% ifversion not ghae %} y para mantener la cadena de suministro de tu software{% endif %}.' +title: Code security +shortTitle: Code security +intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.' introLinks: overview: /code-security/getting-started/github-security-features featuredLinks: @@ -12,7 +12,7 @@ featuredLinks: - '{% ifversion ghes or ghae %}/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository{% endif%}' guideCards: - '{% ifversion fpt %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates{% endif %}' - - '{% ifversion fpt %}/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates{% endif %}' + - '{% ifversion fpt %}/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates{% endif %}' - '{% ifversion fpt %}/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository{% endif %}' - '{% ifversion ghes %}/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository{% endif %}' - '{% ifversion ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}' diff --git a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md index f6176a0efa..7d62a67574 100644 --- a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md @@ -1,7 +1,8 @@ --- -title: Acerca del escaneo de secretos -intro: '{% data variables.product.product_name %} escanea repositorios para encontrar tipos conocidos de secretos para prevenir el uso fraudulento de aquellos que se confirmaron por accidente.' +title: About secret scanning +intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.' product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 3 redirect_from: - /github/administering-a-repository/about-token-scanning - /articles/about-token-scanning @@ -22,54 +23,61 @@ topics: {% data reusables.secret-scanning.beta %} {% data reusables.secret-scanning.enterprise-enable-secret-scanning %} -Si tu proyecto se comunica con un servicio externo, puedes utilizar un token o llave privada para autenticación. Los tokens y llaves privadas son ejemplos de secretos que puede emitir un proveedor de servicios. Si registras un secreto en un repositorio, cualquiera que tenga acceso de lectura al mismo puede utilizarlo para acceder al servicio externo con tus privilegios. Te recomendamos que almacenes los secretos en una ubicación dedicada y segura fuera del repositorio de tu proyecto. +If your project communicates with an external service, you might use a token or private key for authentication. Tokens and private keys are examples of secrets that a service provider can issue. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. We recommend that you store secrets in a dedicated, secure location outside of the repository for your project. -{% data variables.product.prodname_secret_scanning_caps %} escaneará todo tu historial de Git en todas las ramas presentes en tu repositorio de {% data variables.product.prodname_dotcom %} en búsqueda de cualquier secreto. Los proveedores de servicio pueden asociarse con {% data variables.product.company_short %} para proporcionar sus formatos de secreto para el escaneo.{% ifversion fpt or ghec %} Para obtener más información, consulta la sección "[Programa asociado para el escaneo de secretos](/developers/overview/secret-scanning-partner-program)". +{% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for any secrets. Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning.{% ifversion fpt or ghec %} For more information, see "[Secret scanning partner program](/developers/overview/secret-scanning-partner-program)." {% endif %} {% data reusables.secret-scanning.about-secret-scanning %} {% ifversion fpt or ghec %} -## Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios públicos +## About {% data variables.product.prodname_secret_scanning %} for public repositories -Las {% data variables.product.prodname_secret_scanning_caps %} se habilitan automáticamente en los repositorios públicos. Cuando subes información a un repositorio público, {% data variables.product.product_name %} escanea el contenido de las confirmaciones para los secretos. Si cambias un repositorio de privado a público, {% data variables.product.product_name %} escanea todo el repositorio en busca de secretos. +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets. -Cuando {% data variables.product.prodname_secret_scanning %} detecta un conjunto de credenciales, notificamos al proveedor del servicio que emitió el secreto. El proveedor del servicio valida la credencial y luego decide si debería retirar el secreto, emitir uno nuevo, o contactarte directamente, lo cual dependerá de los riesgos asociados a ti o a dicho proveedor. Para encontrar un resumen de cómo trabajamos con nuestros socios que emiten tokens, consulta la sección "[Porgrama de socios del escaneo de secretos](/developers/overview/secret-scanning-partner-program)". +When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider. For an overview of how we work with token-issuing partners, see "[Secret scanning partner program](/developers/overview/secret-scanning-partner-program)." -Actualmente, {% data variables.product.product_name %} escanea los repositorios públicos en busca de secretos emitidos por los siguientes proveedores de servicios. +### List of supported secrets for public repositories + +{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. {% data reusables.secret-scanning.partner-secret-list-public-repo %} -## Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios privados +## About {% data variables.product.prodname_secret_scanning %} for private repositories {% endif %} {% ifversion ghes or ghae %} -## Acerca del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.product_name %} +## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} -El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible en todos los repositorios que pertenezcan a la organización como parte de la {% data variables.product.prodname_GH_advanced_security %}. No se encuentra disponible en repositorios que pertenezcan a usuarios individuales. +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. {% endif %} -Si eres un administrador de repositorio o un propietario de organización, puedes habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% ifversion fpt or ghec %} privados{% endif %} que pertenezcan a las organizaciones. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% ifversion fpt or ghec %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)".{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."{% endif %} When you push commits to a{% ifversion fpt or ghec %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% ifversion fpt or ghec %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} generates an alert. -- {% data variables.product.prodname_dotcom %} envía una alerta por correo electrónico a los administradores del repositorio y a los propietarios de la organización. +- {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners. {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -- {% data variables.product.prodname_dotcom %} envía una alerta por correo electrónico al contribuyente que confirmó el secreto en el repositorio con un enlace a la alerta del {% data variables.product.prodname_secret_scanning %} relacionada. El autor de la confirmación puede entonces ver la alerta en el repositorio y resolverla. +- {% data variables.product.prodname_dotcom %} sends an email alert to the contributor who committed the secret to the repository, with a link to the related {% data variables.product.prodname_secret_scanning %} alert. The commit author can then view the alert in the repository, and resolve the alert. {% endif %} -- {% data variables.product.prodname_dotcom %} muestra una alerta en el repositorio.{% ifversion ghes = 3.0 %} Para obtener más información, consulta la sección "[Administrar alertas desde {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)".{% endif %} +- {% data variables.product.prodname_dotcom %} displays an alert in the repository.{% ifversion ghes = 3.0 %} For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -Para obtener más información sobre visualizar y resolver las alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)".{% endif %} +For more information about viewing and resolving {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %} -Los administradores de repositorio y propietarios de las organizaciones pueden otorgar a los usuarios y equipos acceso a las alertas del {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% ifversion fpt or ghes > 3.0 or ghec %} -Para monitorear los resultados del {% data variables.product.prodname_secret_scanning %} a lo largo de tus repositorios privados o de tu organización, puedes utilizar la API de {% data variables.product.prodname_secret_scanning %}. Para obtener más información acerca de las terminales de las API, consulta la sección "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)".{% endif %} +To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} + +{% ifversion ghes or ghae %} +## List of supported secrets{% else %} +### List of supported secrets for private repositories +{% endif %} {% data variables.product.prodname_dotcom %} currently scans{% ifversion fpt or ghec %} private{% endif %} repositories for secrets issued by the following service providers. @@ -78,12 +86,12 @@ Para monitorear los resultados del {% data variables.product.prodname_secret_sca {% ifversion ghes < 3.2 or ghae %} {% note %} -**Nota:**{% data variables.product.prodname_secret_scanning_caps %} no permite actualmente que definas tus propios parámetros para detectar secretos. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} does not currently allow you to define your own patterns for detecting secrets. {% endnote %} {% endif %} -## Leer más +## Further reading -- "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)" -- "[Mantener la seguridad en tu cuenta y tus datos](/github/authenticating-to-github/keeping-your-account-and-data-secure)" +- "[Securing your repository](/code-security/getting-started/securing-your-repository)" +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 3085c2ae7f..e4cde2b237 100644 --- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -1,7 +1,7 @@ --- -title: Definir patrones personalizados para el escaneo de secretos -shortTitle: Definir patrones personalizados -intro: 'Puedes definir los patrones personalizados para el {% data variables.product.prodname_secret_scanning %} en las organizaciones y repositorios privados.' +title: Defining custom patterns for secret scanning +shortTitle: Define custom patterns +intro: 'You can define custom patterns for {% data variables.product.prodname_secret_scanning %} in organizations and private repositories.' product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /code-security/secret-security/defining-custom-patterns-for-secret-scanning @@ -17,36 +17,40 @@ topics: {% ifversion ghes < 3.3 or ghae %} {% note %} -**Nota:** Los patrones personalizados del {% data variables.product.prodname_secret_scanning %} se encuentran actualmente en beta y están sujetos a cambios. +**Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change. {% endnote %} {% endif %} -## Acerca de los patrones personalizados para el {% data variables.product.prodname_secret_scanning %} +## About custom patterns for {% data variables.product.prodname_secret_scanning %} -{% data variables.product.company_short %} lleva a cabo el {% data variables.product.prodname_secret_scanning %} en los repositorios{% ifversion fpt or ghec %}públicos y privados{% endif %} para los patrones de secretos que proporcionan los socios de {% data variables.product.company_short %} y {% data variables.product.company_short %}. Para obtener más información sobre el programa asociado del {% data variables.product.prodname_secret_scanning %}, consulta la sección "Programa asociado de escaneo de secretos". +{% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt or ghec %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "Secret scanning partner program." -Sin embargo, puede que existan situaciones en las que quieras escanear en búsqueda de otros patrones de secreto en tus repositorios {% ifversion fpt or ghec %}privados{% endif %}. Por ejemplo, puede que tengas un patrón secreto que sea interno a tu organización. Para estos casos, puedes definir patrones personalizados del {% data variables.product.prodname_secret_scanning %} en tu empresa, organización, o epositorio {% ifversion fpt or ghec %}privado{% endif %} en{% data variables.product.product_name %}. Puedes definir hasta 100 patrones personalizados para cada cuenta de organización o empresa y hasta 20 de ellos por repositorio {% ifversion fpt or ghec %}repositorio privado{% endif %}. +However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt or ghec %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt or ghec %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to +{%- ifversion fpt or ghec or ghes > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per {% ifversion fpt or ghec %}private{% endif %} repository. +{%- elsif ghes = 3.3 %} 100 custom patterns for each organization or enterprise account, and per repository. +{%- else %} 20 custom patterns for each organization or enterprise account, and per repository. +{%- endif %} {% ifversion ghes < 3.3 or ghae %} {% note %} -**Nota:** Durante el beta, hay algunas limitaciones al utilizar patrones personalizados para el {% data variables.product.prodname_secret_scanning %}: +**Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}: -* No hay una funcionalidad de simulacro. -* No puedes editar patrones personalizados después de que se hayan creado. Para cambiar un patrón, debes borrarlo y volverlo a crear. -* No hay una API para crear, editar o borrar patrones personalizados. Sin embargo, los resultados para los patrones personalizados se devuelven en la [API de alertas para el escaneo de secretos](/rest/reference/secret-scanning). +* There is no dry-run functionality. +* You cannot edit custom patterns after they're created. To change a pattern, you must delete it and recreate it. +* There is no API for creating, editing, or deleting custom patterns. However, results for custom patterns are returned in the [secret scanning alerts API](/rest/reference/secret-scanning). {% endnote %} {% endif %} -## Sintaxis de expresión regular para los patrones personalizados +## Regular expression syntax for custom patterns -Los patrones personalizados del {% data variables.product.prodname_secret_scanning %} se especifican como expresiones regulares. El {% data variables.product.prodname_secret_scanning_caps %} utiliza la [biblioteca Hyperscan](https://github.com/intel/hyperscan) y solo es compatible con las construcciones de regex de Hyperscan, las cuales son un subconjunto de la sintaxis PCRE. Los modificadores de opción de Hyperscan no son compatibles. Para obtener más información sobre las consturcciones de patrones de Hyperscan, consulta el "[Soporte para patrones](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" en la documentación de Hyperscan. +Custom patterns for {% data variables.product.prodname_secret_scanning %} are specified as regular expressions. {% data variables.product.prodname_secret_scanning_caps %} uses the [Hyperscan library](https://github.com/intel/hyperscan) and only supports Hyperscan regex constructs, which are a subset of PCRE syntax. Hyperscan option modifiers are not supported. For more information on Hyperscan pattern constructs, see "[Pattern support](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" in the Hyperscan documentation. -## Definir un patrón común para un repositorio +## Defining a custom pattern for a repository -Antes de definir un patrón personalizado, debes asegurarte de que el {% data variables.product.prodname_secret_scanning %} esté habilitado en tu repositorio. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_secret_scanning %} para tus repositorios](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)". +Before defining a custom pattern, you must ensure that {% data variables.product.prodname_secret_scanning %} is enabled on your repository. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your repositories](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -55,15 +59,15 @@ Antes de definir un patrón personalizado, debes asegurarte de que el {% data va {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -Después de que se crea tu patrón, {% data reusables.secret-scanning.secret-scanning-process %} Para obtener más información sobre cómo visualizar alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -## Definir un patrón común para una organización +## Defining a custom pattern for an organization -Antes de definir un patrón personalizado, debes asegurarte de que hayas habilitado el {% data variables.product.prodname_secret_scanning %} para los repositorios {% ifversion fpt or ghec %}privados{% endif %} que quieras escanear en tu organización. Para habilitar el {% data variables.product.prodname_secret_scanning %} en todos los repositorios {% ifversion fpt or ghec %}privados{% endif %} de tu organizción, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +Before defining a custom pattern, you must ensure that you enable {% data variables.product.prodname_secret_scanning %} for the {% ifversion fpt or ghec %}private{% endif %} repositories that you want to scan in your organization. To enable {% data variables.product.prodname_secret_scanning %} on all {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% note %} -**Nota:** Como no hay funcionalidad de pruebas en seco, te recomendamos probar tus patrones personalizados en un repositorio antes de definirlos para toda tu organización. De esta forma, puedes evitar crear un exceso de alertas de {% data variables.product.prodname_secret_scanning %} falsas positivas. +**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire organization. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. {% endnote %} @@ -74,15 +78,15 @@ Antes de definir un patrón personalizado, debes asegurarte de que hayas habilit {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -Después de que se cree un patrón, el {% data variables.product.prodname_secret_scanning %} escaneará cualquier secreto en los repositorios {% ifversion fpt or ghec %}privados{% endif %} de tu organización, incluyendo el historial completo de Git en todas las ramas. Se alertará a los propietarios de organizaciones y administradores de repositorios de cualquier secreto que se encuentre y estos podrán revisar la alerta en el repositorio en donde se encontró el secreto. Para obtener más información sobre cómo ver las alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -## Definir un patrón común para una cuenta empresarial +## Defining a custom pattern for an enterprise account -Antes de definir un patrón personalizado, debes garantizar que habilitaste el escaneo de secretos para tu cuenta empresarial. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_GH_advanced_security %} en tu empresa]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)". +Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." {% note %} -**Nota:** Como no hay funcionalidad de pruebas en seco, te recomendamos probar tus patrones personalizados en un repositorio antes de definirlos para toda tu empresa. De esta forma, puedes evitar crear alertas del {% data variables.product.prodname_secret_scanning %} falsas positivas en exceso. +**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. {% endnote %} @@ -90,35 +94,35 @@ Antes de definir un patrón personalizado, debes garantizar que habilitaste el e {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.advanced-security-policies %} {% data reusables.enterprise-accounts.advanced-security-security-features %} -1. Debajo de "Patrones personalizados del escaneo de secretos", haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}. +1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -Después de que se cree tu patrón, el {% data variables.product.prodname_secret_scanning %} escaneará en búsqueda de cualquier secreto en los repositorios {% ifversion fpt or ghec %}privados{% endif %} dentro de las organizaciones de tu empresa que cuenten con la {% data variables.product.prodname_GH_advanced_security %} habilitada, incluyendo todo su historial de Git en todas las ramas. Se alertará a los propietarios de organizaciones y administradores de repositorios de cualquier secreto que se encuentre y estos podrán revisar la alerta en el repositorio en donde se encontró el secreto. Para obtener más información sobre cómo ver las alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghes > 3.2 or ghec %} -## Editar un patrón personalizado +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} +## Editing a custom pattern -Cuando guardas un cambio en un patrón personalizado, este cierra todas las alertas del {% data variables.product.prodname_secret_scanning %} que se crearon utilizando la versión anterior del patrón. -1. Navegar a donde se creó el patrón personalizado. Un patrón personalizado puede crearse en un repositorio, organización o cuenta empresarial. - * Para un repositorio u organización, muestra los ajustes de "Seguridad & análisis" para el repositorio u organización en donde se creó el patrón personalizado. Para obtener más información, consulta las secciones anteriores "[Definir un patrón personalizado para un repositorio](#defining-a-custom-pattern-for-a-repository)" o "[Definir un patrón personalizado apra una organización](#defining-a-custom-pattern-for-an-organization)". - * Para una empresa, debajo de "Políticas", muestra el área de "Seguridad Avanzada" y luego haz clic en **Características de seguridad**. Para obtener más información, consulta la sección anterior "[Definir un patrón personalizado para una cuenta empresarial](#defining-a-custom-pattern-for-an-enterprise-account)". -2. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", a la derecha del patrón personalizado que quieras editar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. -3. Cuando hayas revisado y probado tus cambios, haz clic en **Guardar cambios**. +When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern. +1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. + * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above. + * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. +2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. +3. When you have reviewed and tested your changes, click **Save changes**. {% endif %} -## Eliminar un patrón personalizado +## Removing a custom pattern -1. Navegar a donde se creó el patrón personalizado. Un patrón personalizado se puede crear en un repositorio, organización o cuenta empresarial. +1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. - * Para un repositorio u organización, muestra los ajustes de "Seguridad & análisis" para el repositorio u organización en donde se creó el patrón personalizado. Para obtener más información, consulta las secciones anteriores "[Definir un patrón personalizado para un repositorio](#defining-a-custom-pattern-for-a-repository)" o "[Definir un patrón personalizado apra una organización](#defining-a-custom-pattern-for-an-organization)". - * Para una empresa, debajo de "Políticas", muestra el área de "Seguridad Avanzada" y luego haz clic en **Características de seguridad**. Para obtener más información, consulta la sección anterior "[Definir un patrón personalizado para una cuenta empresarial](#defining-a-custom-pattern-for-an-enterprise-account)". -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -1. A la derecha del patrón personalizado que quieras eliminar, haz clic en {% octicon "trash" aria-label="The trash icon" %}. -1. Revisa la confirmación y seleccionar el método para tratar con cualquier alerta abierta que tenga relación con el patrón personalizado. -1. Haz clic en **Sí, borrar este patrón**. + * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above. + * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. +{%- ifversion fpt or ghes > 3.2 or ghae %} +1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. +1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern. +1. Click **Yes, delete this pattern**. - ![Confirmación del borrado de un patrón personalizado del {% data variables.product.prodname_secret_scanning %} ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) + ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) {%- elsif ghes = 3.2 %} -1. A la derecha del patrón personalizado que quieras eliminar, haz clic en **Eliminar**. -1. Revisa la confirmación y haz clic en **Eliminar patrón personalizado**. +1. To the right of the custom pattern you want to remove, click **Remove**. +1. Review the confirmation, and click **Remove custom pattern**. {%- endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md index 0af7322bea..74a407f85c 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md @@ -1,6 +1,6 @@ --- -title: Acerca de las actualizaciones a la versión del Dependabot -intro: 'Puede utilizar el {% data variables.product.prodname_dependabot %} para mantener los paquetes que utilizas actualizados a su versión más reciente.' +title: About Dependabot version updates +intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.' redirect_from: - /github/administering-a-repository/about-dependabot - /github/administering-a-repository/about-github-dependabot @@ -10,6 +10,7 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '> 3.2' type: overview topics: - Dependabot @@ -17,48 +18,50 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Actualizaciones de versión del dependabot +shortTitle: Dependabot version updates --- -## Acerca de {% data variables.product.prodname_dependabot_version_updates %} +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -El {% data variables.product.prodname_dependabot %} hace el esfuerzo de mantener tus dependencias. Puedes utilizarlo para garantizar que tu repositorio se mantenga automáticamente con los últimos lanzamientos de los paquetes y aplicaciones de los que depende. +## About {% data variables.product.prodname_dependabot_version_updates %} -Se habilitan las {% data variables.product.prodname_dependabot_version_updates %} al registrar un archivo de configuración en tu repositorio. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario. +{% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. -Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Lara las dependencias delegadas a proveedores, el {% data variables.product.prodname_dependabot %} levanta una solicitud de cambios para reemplazar la dependencia desactualizada directamente con la versión nueva. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. -Si habilitas las actualizaciones de seguridad, el {% data variables.product.prodname_dependabot %} también levantará las solicitudes de extracción para actualizar las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." + +If you enable _security updates_, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% data reusables.dependabot.pull-request-security-vs-version-updates %} {% data reusables.dependabot.dependabot-tos %} -## Frecuencia de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} +## Frequency of {% data variables.product.prodname_dependabot %} pull requests -Tú eres quien especifica qué tan a menudo se revisa cada ecosistema para encontrar nuevas versiones en el archivo de configuración: diario, semanalmente, o mensualmente. +You specify how often to check each ecosystem for new versions in the configuration file: daily, weekly, or monthly. {% data reusables.dependabot.initial-updates %} -Si habilitaste las actualizaciones de seguridad, algunas veces verás solicitudes de extracción adicionales para actualizaciones de seguridad. Esto se activa con una alerta del {% data variables.product.prodname_dependabot %} para una dependencia en tu rama predeterminada. El {% data variables.product.prodname_dependabot %} levanta automáticamente una solicitud de extracción para actualizar la dependencia vulnerable. +If you've enabled security updates, you'll sometimes see extra pull requests for security updates. These are triggered by a {% data variables.product.prodname_dependabot %} alert for a dependency on your default branch. {% data variables.product.prodname_dependabot %} automatically raises a pull request to update the vulnerable dependency. -## Repositorios y ecosistemas compatibles +## Supported repositories and ecosystems -Puedes configurar las actualizaciones de versión para los repositorios que contengan un manifiesto de dependencias o un archivo fijado para alguno de los administradores de paquetes compatibles. Para algunos administradores de paquetes, también puedes configurar la delegación a proveedores para las dependencias. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)". - +You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#vendor)." {% note %} -{% data reusables.dependabot.private-dependencies-note %} +{% data reusables.dependabot.private-dependencies-note %} -El {% data variables.product.prodname_dependabot %} no es compatible con dependencias privadas de {% data variables.product.prodname_dotcom %} para todos los administradores de paquetes. Consulta los detalles en la tabla a continuación. +{% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. See the details in the table below. {% endnote %} {% data reusables.dependabot.supported-package-managers %} -Si tu repositorio ya utiliza una integración para la administración de dependencias, necesitarás inhabilitarlo antes de habilitar el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Acerca de las integraciones](/github/customizing-your-github-workflow/about-integrations)". +If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. {% ifversion fpt or ghec %}For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)."{% endif %} -## Acerca de las notificaciones para las actualizaciones de versión del {% data variables.product.prodname_dependabot %} +## About notifications for {% data variables.product.prodname_dependabot %} version updates -Puedes filtrar tus notificaciones en {% data variables.product.company_short %} para mostrar las actualizaciones de versión del {% data variables.product.prodname_dependabot %}. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". +You can filter your notifications on {% data variables.product.company_short %} to show notifications for pull requests created by {% data variables.product.prodname_dependabot %}. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index 342be34cf7..b62275e4e3 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -1,11 +1,12 @@ --- -title: Automatizar al Dependabot con las GitHub Actions -intro: 'Ejemplos de cómo puedes utilizar las {% data variables.product.prodname_actions %} para automatizar las tareas comunes relacionadas con el {% data variables.product.prodname_dependabot %}.' +title: Automating Dependabot with GitHub Actions +intro: 'Examples of how you can use {% data variables.product.prodname_actions %} to automate common {% data variables.product.prodname_dependabot %} related tasks.' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_actions %} to respond to {% data variables.product.prodname_dependabot %}-created pull requests.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Actions @@ -15,29 +16,42 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Utiliza el Dependabot con las acciones +shortTitle: Use Dependabot with actions --- -## Acerca del {% data variables.product.prodname_dependabot %} y de las {% data variables.product.prodname_actions %} +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -El {% data variables.product.prodname_dependabot %} crea las solicitudes de cambios para mantener actualizadas tus dependencias y puedes utilizar las {% data variables.product.prodname_actions %} para llevar a cabo tareas automatizadas cuando se creen estas solicitudes de cambios. Por ejemplo, recupera artefactos adicionales, agrega etiquetas, ejecuta pruebas o modifica la solicitud de cambios de cualquier otra forma. +## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %} -## Responder a los eventos +{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date, and you can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modifying the pull request. -El {% data variables.product.prodname_dependabot %} puede activar los flujos de trabajo de las {% data variables.product.prodname_actions %} en sus solicitudes de cambios y comentarios; sin embargo, debido a que los["Flujos de trabajo de las GitHub Actions que activen las solicitudes de cambios del Dependabot se ejecutarán con permisos de solo lectura"](https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/), se tratará a algunos eventos de forma distinta. +## Responding to events -En el caso de los flujos de trabajos que inició el {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) y que utilizan los eventos `pull_request`, `pull_request_review`, `pull_request_review_comment`, y `push`, aplicarán las siguientes restricciones: +{% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, due to ["GitHub Actions: Workflows triggered by Dependabot PRs will run with read-only permissions"](https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/), certain events are treated differently. -- `GITHUB_TOKEN` tiene permisos de solo lectura. -- No se puede acceder a los secretos. +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply: -Para obtener màs informaciòn, consulta la secciòn "[Mantener seguras tus GitHub Actions y flujos de trabajo: Prevenir solicitudes de tipo pwn](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)". +- `GITHUB_TOKEN` has read-only permissions. +- Secrets are inaccessible. -### Manejar los eventos de `pull_request` +For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). -Si tu flujo de trabajo necesita acceso a los secretos o a un `GITHUB_TOKEN` con permisos de escritura, tienes dos opciones: utilizar `pull_request_target`, o utilizar dos flujos de trabajo separados. En esta sección, describiremos a detalle cómo utilizar `pull_request_target` y utilizaremos los dos siguientes flujos de trabajo en cómo "[Manejar eventos `push`](#handling-push-events)". +{% ifversion ghes > 3.2 %} +{% note %} -Debajo hay un ejemplo simple de un flujo de trabajo de una `pull_request` que podría estar fallando ahora: +**Note:** Your site administrator can override these restrictions for {% data variables.product.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." + +If the restrictions are removed, when a workflow is triggered by {% data variables.product.prodname_dependabot %} it will have access to any secrets that are normally available. In addition, workflows triggered by {% data variables.product.prodname_dependabot %} can use the `permissions` term to increase the default scope of the `GITHUB_TOKEN` from read-only access. + +{% endnote %} +{% endif %} + +### Handling `pull_request` events + +If your workflow needs access to secrets or a `GITHUB_TOKEN` with write permissions, you have two options: using `pull_request_target`, or using two separate workflows. We will detail using `pull_request_target` in this section, and using two workflows below in "[Handling `push` events](#handling-push-events)." + +Below is a simple example of a `pull_request` workflow that might now be failing: {% raw %} ```yaml @@ -56,11 +70,11 @@ jobs: ``` {% endraw %} -Puedes reemplazar a `pull_request` con `pull_request_target`, el cual se utiliza para las solicitudes de cambio de las bifurcaciones y revisar explícitamente el `HEAD` de la solicitud de cambios. +You can replace `pull_request` with `pull_request_target`, which is used for pull requests from forks, and explicitly check out the pull request `HEAD`. {% warning %} -**Advertencia:** El utilizar `pull_request_target` como sustituto de `pull_request` de expone a un comportamiento inseguro. Te recomendamos utilizar el método de dos flujos de trabajo de acuerdo con lo que se describe a continuación en "[Administrar eventos `push`](#handling-push-events)". +**Warning:** Using `pull_request_target` as a substitute for `pull_request` exposes you to insecure behavior. We recommend you use the two workflow method, as described below in "[Handling `push` events](#handling-push-events)." {% endwarning %} @@ -87,13 +101,13 @@ jobs: ``` {% endraw %} -También se recomienda fuertemente que bajes el alcance de los permisos que otorgas al `GITHUB_TOKEN` para poder evitar que se fugue un token con más privilegios de lo necesario. Para obtener más información, consulta ña sección "[Permisos del `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +It is also strongly recommended that you downscope the permissions granted to the `GITHUB_TOKEN` in order to avoid leaking a token with more privilege than necessary. For more information, see "[Permissions for the `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." -### Manejar eventos `push` +### Handling `push` events -Ya que no hay un equivalente de `pull_request_target` para los eventos `push`, tendrás que utilizar dos flujos de trabajo: uno no confiable que termine cargando artefactos, el cual activará un segundo flujo de trabajo que descargará los artefactos y seguirá procesándose. +As there is no `pull_request_target` equivalent for `push` events, you will have to use two workflows: one untrusted workflow that ends by uploading artifacts, which triggers a second trusted workflow that downloads artifacts and continues processing. -El primer flujo de trabajo lleva a cabo cualquier trabajo no confiable: +The first workflow performs any untrusted work: {% raw %} ```yaml @@ -111,7 +125,7 @@ jobs: ``` {% endraw %} -El segundo flujo de trabajo llevará a cabo el trabajo confiable después de que el primero se complete exitosamente: +The second workflow performs trusted work after the first workflow completes successfully: {% raw %} ```yaml @@ -120,7 +134,7 @@ name: Dependabot Trusted Workflow on: workflow_run: workflows: ["Dependabot Untrusted Workflow"] - types: + types: - completed permissions: @@ -135,19 +149,19 @@ jobs: ``` {% endraw %} -### Volver a ejecutar un flujo de trabajo manualmente +### Manually re-running a workflow -También puedes volver a ejecutar un flujo de trabajo fallido del Dependabot manualmente y este seguirá ejecutándose con un token de lectura-escritura y con acceso a los secretos. Antes de volver a ejecutar los flujos de trabajo fallidos manualmente, siempre debes verificar la dependencia que se está actualizando para asegurarte de que el cambio no introduzca ningún comportamiento imprevisto o malicioso. +You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior. -## Automatizaciones comunes del Dependabot +## Common Dependabot automations -Aquí mostramos varios escenarios comunes que pueden automatizarse utilizando las {% data variables.product.prodname_actions %}. +Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}. -### Recuperar metadatos de una solicitud de cambios +### Fetch metadata about a pull request -Automatizar mucho requiere saber información del contenido de la solicitud de cambios: cuál era el nombre de la dependencia, si es una dependencia productva y si es una actualización de parche menor o mayor. +A large amount of automation requires knowing information about the contents of the pull request: what the dependency name was, if it's a production dependency, and if it's a major, minor, or patch update. -La acción `dependabot/fetch-metadata` te proporciona toda esta información: +The `dependabot/fetch-metadata` action provides all that information for you: {% raw %} ```yaml @@ -165,24 +179,24 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" # The following properties are now available: - # - steps.metadata.outputs.dependency-names - # - steps.metadata.outputs.dependency-type - # - steps.metadata.outputs.update-type + # - steps.dependabot-metadata.outputs.dependency-names + # - steps.dependabot-metadata.outputs.dependency-type + # - steps.dependabot-metadata.outputs.update-type ``` {% endraw %} -Para obtener más información, consulta el repositorio [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata). +For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository. -### Etiquetar una solicitud de cambios +### Label a pull request -Si tienes otros flujos de trabajo de automatización o clasificación que se basen en etiquetas de {% data variables.product.prodname_dotcom %}, puedes configurar una acción para asignar etiquetas con base en los metadatos proporcionados. +If you have other automation or triage workflows based on {% data variables.product.prodname_dotcom %} labels, you can configure an action to assign labels based on the metadata provided. -Por ejemplo, si quieres etiquetar todas las actualizaciones de las dependencias de producción con una etiqueta: +For example, if you want to flag all production dependency updates with a label: {% raw %} ```yaml @@ -200,21 +214,21 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Add a label for all production dependencies - if: ${{ steps.metadata.outputs.dependency-type == 'direct:production' }} + if: ${{ steps.dependabot-metadata.outputs.dependency-type == 'direct:production' }} run: gh pr edit "$PR_URL" --add-label "production" env: PR_URL: ${{github.event.pull_request.html_url}} ``` {% endraw %} -### Aprobar una solicitud de cambios +### Approve a pull request -Si quieres aprobar las solicitudes de cambios del Dependabot automáticamente, puedes utilizar el {% data variables.product.prodname_cli %} en un flujo de trabajo: +If you want to automatically approve Dependabot pull requests, you can use the {% data variables.product.prodname_cli %} in a workflow: {% raw %} ```yaml @@ -230,7 +244,7 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" @@ -242,11 +256,11 @@ jobs: ``` {% endraw %} -### Habilita la fusión automática en una solicitud de cambios +### Enable auto-merge on a pull request -Si quieres fusionar tus solicitudes de cambios automáticamente, puedes utilizar la funcionalidad de fusión automática de {% data variables.product.prodname_dotcom %}. Esto habilita a la solicitud de cambios para que se fusione cuando se cumpla con todas las pruebas y aprobaciones requeridas. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)". +If you want to auto-merge your pull requests, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." -Aquí tienes un ejemplo de cómo habilitar la fusión automática para todas las actualizaciones de parche en `my-dependency`: +Here is an example of enabling auto-merge for all patch updates to `my-dependency`: {% raw %} ```yaml @@ -263,12 +277,12 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Enable auto-merge for Dependabot PRs - if: ${{contains(steps.metadata.outputs.dependency-names, 'my-dependency') && steps.metadata.outputs.update-type == 'version-update:semver-patch'}} + if: ${{contains(steps.dependabot-metadata.outputs.dependency-names, 'my-dependency') && steps.dependabot-metadata.outputs.update-type == 'version-update:semver-patch'}} run: gh pr merge --auto --merge "$PR_URL" env: PR_URL: ${{github.event.pull_request.html_url}} @@ -276,13 +290,13 @@ jobs: ``` {% endraw %} -## Solucionar los problemas de las ejecuciones de flujo de trabajo fallidas +## Troubleshooting failed workflow runs -Si tu ejecución de flujo de trabajo falla, verifica lo siguiente: +If your workflow run fails, check the following: -- Estás ejecutando el flujo de trabajo únicamente cuando el actor adecuado lo activa. -- Estás verificando la `ref` de tu `pull_request`. -- No estás intentando acceder a los secretos desde un evento de `pull_request`, `pull_request_review`, `pull_request_review_comment`, o `push` activado por el Dependabot. -- No estás intentando llevar a cabo ninguna acción de `write` desde dentro de un evento de tipo `pull_request`, `pull_request_review`, `pull_request_review_comment`, o `push` que haya activado el Dependabot. +- You are running the workflow only when the correct actor triggers it. +- You are checking out the correct `ref` for your `pull_request`. +- You aren't trying to access secrets from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event. +- You aren't trying to perform any `write` actions from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event. -Para obtener más información sobre cómo escribir y depurar las {% data variables.product.prodname_actions %}, consulta la sección "[Aprender sobre las Acciones de GitHub](/actions/learn-github-actions)". +For information on writing and debugging {% data variables.product.prodname_actions %}, see "[Learning GitHub Actions](/actions/learn-github-actions)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md index de635b9b67..6914c997cb 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md @@ -1,6 +1,6 @@ --- -title: Opciones de configuración para actualizaciones de dependencias -intro: 'La información detallada para todas las opciones que puedes utilizar para personalizar como el {% data variables.product.prodname_dependabot %} mantiene tus repositorios.' +title: Configuration options for dependency updates +intro: 'Detailed information for all the options you can use to customize how {% data variables.product.prodname_dependabot %} maintains your repositories.' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.' redirect_from: - /github/administering-a-repository/configuration-options-for-dependency-updates @@ -9,6 +9,7 @@ miniTocMaxHeadingLevel: 3 versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: reference topics: - Dependabot @@ -16,68 +17,71 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Opciones de configuración +shortTitle: Configuration options --- -## Acerca del archivo *dependabot.yml* +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -El archivo de configuración del {% data variables.product.prodname_dependabot %}, *dependabot.yml*, utiliza la sintaxis YAML. Si eres nuevo en YAML y deseas conocer más, consulta "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". +## About the *dependabot.yml* file -Debes almacenar este archivo en el directorio `.github` de tu repositorio. Cuando agregas o actualizas el archivo *dependabot.yml*, esto activa una revisión inmediata de las actualizaciones de la versión. Cualquier opción que también afecte las actualizaciones de seguridad se utiliza en la siguiente ocasión en que una alerta de seguridad active una solicitud de cambios para una actualización de seguridad. Para obtener más información, consulta las secciónes "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". +The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." -El archivo *dependabot.yml* tiene dos claves mandatorias de nivel superior: `version`, y `updates`. Opcionalmente, puedes incluir una clave de `registries` de nivel superior. El archivo debe comenzar con `version: 2`. +You must store this file in the `.github` directory of your repository. When you add or update the *dependabot.yml* file, this triggers an immediate check for version updates. Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)." -## Opciones de configuración para las actualizaciones +The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key. The file must start with `version: 2`. -La clave `updates` de nivel superior es obligatoria. La utilizas para configurar la forma en que el {% data variables.product.prodname_dependabot %} actualiza las versiones o las dependencias de tu proyecto. Cada entrada configura los ajustes de actualización para un administrador de paquetes en particular. Puedes utilizar las siguientes opciones. +## Configuration options for updates -| Opción | Requerido | Descripción | -|:-------------------------------------------------------------------------- |:---------:|:-------------------------------------------------------------------------------------------------- | -| [`package-ecosystem`](#package-ecosystem) | **X** | Administrador de paquetes a utilizar | -| [`directorio`](#directory) | **X** | Ubicación de los manifiestos del paquete | -| [`schedule.interval`](#scheduleinterval) | **X** | Qué tan a menudo se revisará si hay actualizaciones | -| [`allow`](#allow) | | Personalizar qué actualizaciones se permitirán | -| [`asignatarios`](#assignees) | | Los asignados a configurar en las solicitudes de extracción | -| [`commit-message`](#commit-message) | | Preferencias de mensaje de confirmación | -| [`ignore`](#ignore) | | Ignorar ciertas dependencias o versiones | -| [`insecure-external-code-execution`](#insecure-external-code-execution) | | Permite o rechaza la ejecución de código en los archivos de manifiesto | -| [`etiquetas`](#labels) | | Las etiquetas a configurar en las solicitudes de extracción | -| [`hito`](#milestone) | | Hito a configurar en las solicitudes de extracción | -| [`open-pull-requests-limit`](#open-pull-requests-limit) | | Limitar la cantidad de solicitudes de extracción abiertas para las actualizaciones de versión | -| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | Cambiar el separador para los nombres de rama de la solicitud de extracción | -| [`rebase-strategy`](#rebase-strategy) | | Inhabilitar el rebase automático | -| [`registries`](#registries) | | Los registros privados a los que puede acceder el {% data variables.product.prodname_dependabot %} -| [`reviewers`](#reviewers) | | Los revisores a configurar en las solicitudes de extracción | -| [`schedule.day`](#scheduleday) | | Día de la semana para revisar si hay actualizaciones | -| [`schedule.time`](#scheduletime) | | Hora del día para revisar si hay actualizaciones (hh:mm) | -| [`schedule.timezone`](#scheduletimezone) | | Huso horario para la hora del día (identificador de zona) | -| [`target-branch`](#target-branch) | | Rama contra la cual se creará la solicitud de extracción | -| [`vendor`](#vendor) | | Actualiza las dependencias delegadas a proveedores o almacenadas en caché | -| [`versioning-strategy`](#versioning-strategy) | | Cómo actualizar los requisitos de la versión del manifiesto | +The top-level `updates` key is mandatory. You use it to configure how {% data variables.product.prodname_dependabot %} updates the versions or your project's dependencies. Each entry configures the update settings for a particular package manager. You can use the following options. -Estas opciones caen a groso modo en las siguientes categorías. +| Option | Required | Description | +|:---|:---:|:---| +| [`package-ecosystem`](#package-ecosystem) | **X** | Package manager to use | +| [`directory`](#directory) | **X** | Location of package manifests | +| [`schedule.interval`](#scheduleinterval) | **X** | How often to check for updates | +| [`allow`](#allow) | | Customize which updates are allowed | +| [`assignees`](#assignees) | | Assignees to set on pull requests | +| [`commit-message`](#commit-message) | | Commit message preferences | +| [`ignore`](#ignore) | | Ignore certain dependencies or versions | +| [`insecure-external-code-execution`](#insecure-external-code-execution) | | Allow or deny code execution in manifest files | +| [`labels`](#labels) | | Labels to set on pull requests | +| [`milestone`](#milestone) | | Milestone to set on pull requests | +| [`open-pull-requests-limit`](#open-pull-requests-limit) | | Limit number of open pull requests for version updates| +| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | Change separator for pull request branch names | +| [`rebase-strategy`](#rebase-strategy) | | Disable automatic rebasing | +| [`registries`](#registries) | | Private registries that {% data variables.product.prodname_dependabot %} can access| +| [`reviewers`](#reviewers) | | Reviewers to set on pull requests | +| [`schedule.day`](#scheduleday) | | Day of week to check for updates | +| [`schedule.time`](#scheduletime) | | Time of day to check for updates (hh:mm) | +| [`schedule.timezone`](#scheduletimezone) | | Timezone for time of day (zone identifier) | +| [`target-branch`](#target-branch) | | Branch to create pull requests against | +| [`vendor`](#vendor) | | Update vendored or cached dependencies | +| [`versioning-strategy`](#versioning-strategy) | | How to update manifest version requirements | -- Opciones de configuración esenciales que debes incluir en todas las configuraciones: [`package-ecosystem`](#package-ecosystem), [`directory`](#directory),[`schedule.interval`](#scheduleinterval). -- Opciones para personalizar el calendario de actualización: [`schedule.time`](#scheduletime), [`schedule.timezone`](#scheduletimezone), [`schedule.day`](#scheduleday). -- Las opciones para controlar qué dependencias se actualizarán: [`allow`](#allow), [`ignore`](#ignore), [`vendor`](#vendor). -- Opciones para agregar metadatos a las solicitudes de extracción: [`reviewers`](#reviewers), [`assignees`](#assignees), [`labels`](#labels), [`milestone`](#milestone). -- Opciones para cambiar el comportamiento de las solicitudes de extracción: [`target-branch`](#target-branch), [`versioning-strategy`](#versioning-strategy), [`commit-message`](#commit-message), [`rebase-strategy`](#rebase-strategy), [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator). +These options fit broadly into the following categories. -Adicionalmente, la opción [`open-pull-requests-limit`](#open-pull-requests-limit) cambia la cantidad máxima de solicitudes de extracción para las actualizaciones de versión que puede abrir el {% data variables.product.prodname_dependabot %}. +- Essential set up options that you must include in all configurations: [`package-ecosystem`](#package-ecosystem), [`directory`](#directory),[`schedule.interval`](#scheduleinterval). +- Options to customize the update schedule: [`schedule.time`](#scheduletime), [`schedule.timezone`](#scheduletimezone), [`schedule.day`](#scheduleday). +- Options to control which dependencies are updated: [`allow`](#allow), [`ignore`](#ignore), [`vendor`](#vendor). +- Options to add metadata to pull requests: [`reviewers`](#reviewers), [`assignees`](#assignees), [`labels`](#labels), [`milestone`](#milestone). +- Options to change the behavior of the pull requests: [`target-branch`](#target-branch), [`versioning-strategy`](#versioning-strategy), [`commit-message`](#commit-message), [`rebase-strategy`](#rebase-strategy), [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator). + +In addition, the [`open-pull-requests-limit`](#open-pull-requests-limit) option changes the maximum number of pull requests for version updates that {% data variables.product.prodname_dependabot %} can open. {% note %} -**Nota:** Algunas de estas opciones de configuración también pueden afectar a las solicitudes de extracción que se levantan para las actualizaciones de seguridad de los manifiestos delos paquetes vulnerables. +**Note:** Some of these configuration options may also affect pull requests raised for security updates of vulnerable package manifests. -Las actualizaciones de seguridad se levantan para los manifiestos de paquetes vulnerables únicamente en la rama predeterminada. Cuando se establecen las opciones de configuración para la misma rama (como "true" a menos de que utilices `target-branch`), y se especifica un `package-ecosystem` y `directory` para el manifiesto vulnerable, entonces las solicitudes de extracción para las actualizaciones de seguridad utilizan las opciones relevantes. +Security updates are raised for vulnerable package manifests only on the default branch. When configuration options are set for the same branch (true unless you use `target-branch`), and specify a `package-ecosystem` and `directory` for the vulnerable manifest, then pull requests for security updates use relevant options. -En general, las actualizaciones de seguridad utilizan cualquier opción de configuración que afecte las solicitudes de extracción, por ejemplo, agregar metadatos o cambiar su comportamiento. Para obtener más información acerca de las actualizaciones de seguridad, consulta la sección "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". +In general, security updates use any configuration options that affect pull requests, for example, adding metadata or changing their behavior. For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)." {% endnote %} ### `package-ecosystem` -**Requerido**. Agregarás un elemento de `package-ecosystem` para cada administrador de paquetes que quieras que monitoree el {% data variables.product.prodname_dependabot %} para encontrar versiones nuevas. El repositorio también debe contener un archivo bloqueado o de manifiesto de dependencias para cada uno de estos administradores de paquetes. Si quieres habilitar la delegación a proveedores para un administrador de paquetes que sea compatible con ella, las dependencias delegadas a proveedores deben ubicarse en el directorio requerido. Para obtener más información, consulta la sección [`vendor`](#vendor) a continuación. +**Required**. You add one `package-ecosystem` element for each package manager that you want {% data variables.product.prodname_dependabot %} to monitor for new versions. The repository must also contain a dependency manifest or lock file for each of these package managers. If you want to enable vendoring for a package manager that supports it, the vendored dependencies must be located in the required directory. For more information, see [`vendor`](#vendor) below. {% data reusables.dependabot.supported-package-managers %} @@ -106,9 +110,9 @@ updates: interval: "daily" ``` -### `directorio` +### `directory` -**Requerido**. Debes definir la ubicación de los manifiestos de los paquetes para cada administrador de paquetes (por ejemplo, el *package.json* o *Gemfile*). Tú definierás el directorio relativo a la raíz del repositorio para todos los ecosistemas, menos para GitHub Actions. Para GitHub Actions, configura el directorio para que sea `/` y así revisar los archivos de flujo de trabajo en `.github/workflows`. +**Required**. You must define the location of the package manifests for each package manager (for example, the *package.json* or *Gemfile*). You define the directory relative to the root of the repository for all ecosystems except GitHub Actions. For GitHub Actions, set the directory to `/` to check for workflow files in `.github/workflows`. ```yaml # Specify location of manifest files for each package manager @@ -137,11 +141,11 @@ updates: ### `schedule.interval` -**Requerido**. Debes definir la frecuencia en la que se verificará si hay versiones nuevas para cada administrador de paquetes. Predeterminadamente, el {% data variables.product.prodname_dependabot %} asigna una hora aleatoria para aplicar todas las actualizaciones en el archivo de configuración. Para configurar una hora específica, puedes utilizar [`schedule.time`](#scheduletime) y [`schedule.timezone`](#scheduletimezone). +**Required**. You must define how often to check for new versions for each package manager. By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. To set a specific time, you can use [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone). -- `daily`—se ejecuta en cada día de la semana, de Lunes a Viernes. -- `weekly`—se ejecuta una vez cada semana. Predeterminadamente, esto ocurre los lunes. Para modificar esto, utiliza [`schedule.day`](#scheduleday). -- `monthly`—se ejecuta una vez al mes. Esto ocurre en el primer día de cada mes. +- `daily`—runs on every weekday, Monday to Friday. +- `weekly`—runs once each week. By default, this is on Monday. To modify this, use [`schedule.day`](#scheduleday). +- `monthly`—runs once each month. This is on the first day of the month. ```yaml # Set update schedule for each package manager @@ -164,7 +168,7 @@ updates: {% note %} -**Note**: `schedule` define cuando el {% data variables.product.prodname_dependabot %} intenta hacer una actualización nueva. Sin embargo, no es la única ocasión en la que podrías recibir solilcitudes de cambio. Las actualizaciones pueden activarse con base en los cambios a tu archivo de `dependabot.yml`, los cambios a tus archivo(s) de manifiesto después de una actualización fallida, o las {% data variables.product.prodname_dependabot_security_updates %}. Para obtener más información, consulta las secciones "[Frecuencia de las solicitudes de cambio del {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" y "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +**Note**: `schedule` defines when {% data variables.product.prodname_dependabot %} attempts a new update. However, it's not the only time you may receive pull requests. Updates can be triggered based on changes to your `dependabot.yml` file, changes to your manifest file(s) after a failed update, or {% data variables.product.prodname_dependabot_security_updates %}. For more information, see "[Frequency of {% data variables.product.prodname_dependabot %} pull requests](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." {% endnote %} @@ -172,18 +176,18 @@ updates: {% data reusables.dependabot.default-dependencies-allow-ignore %} -Utiliza la opción `allow` para personalizar qué dependencias se actualizan. Esto aplica tanto a la versión como a las actualizaciones de seguridad. Puedes utilizar las siguientes opciones: +Use the `allow` option to customize which dependencies are updated. This applies to both version and security updates. You can use the following options: -- `dependency-name`—se utiliza para permitir actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId`, por ejemplo: `org.kohsuke:github-api`. -- `dependency-type`—utilízalo para permitir actualizaciones para dependencias de tipos específicos. +- `dependency-name`—use to allow updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId`, for example: `org.kohsuke:github-api`. +- `dependency-type`—use to allow updates for dependencies of specific types. - | Tipos de dependencia | Administradores de paquete compatibles | Permitir actualizaciones | - | -------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | - | `direct` | Todas | Todas las dependencias definidas explícitamente. | - | `indirect` | `bundler`, `pip`, `composer`, `cargo` | Las dependencias de las dependencias directas (también conocidas como sub-dependencias, o dependencias transitorias). | - | `all` | Todas | Todas las dependencias definidas explícitamente. Para `bundler`, `pip`, `composer`, `cargo`, también las dependencias de las dependencias directas. | - | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Solo las dependencias en el "Grupo de dependencias de producción". | - | `development` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Únicamente las dependencias en el "Grupo de dependencias de desarrollo". | + | Dependency types | Supported by package managers | Allow updates | + |------------------|-------------------------------|--------| + | `direct` | All | All explicitly defined dependencies. | + | `indirect` | `bundler`, `pip`, `composer`, `cargo` | Dependencies of direct dependencies (also known as sub-dependencies, or transient dependencies).| + | `all` | All | All explicitly defined dependencies. For `bundler`, `pip`, `composer`, `cargo`, also the dependencies of direct dependencies.| + | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Production dependency group". | + | `development`| `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Development dependency group". | ```yaml # Use `allow` to specify which dependencies to maintain @@ -222,9 +226,9 @@ updates: dependency-type: "production" ``` -### `asignatarios` +### `assignees` -Utiliza `assignees` para especificar a los asignados individuales para todas las solicitudes de extracción levantadas para un administrador de paquete. +Use `assignees` to specify individual assignees for all pull requests raised for a package manager. {% data reusables.dependabot.option-affects-security-updates %} @@ -244,13 +248,13 @@ updates: ### `commit-message` -Predeterminadamente, el {% data variables.product.prodname_dependabot %} intenta detectar tus preferencias de mensajes de confirmación y utiliza patrones similares. Utiliza la opción`commit-message` para especificar tus preferencias explícitamente. +By default, {% data variables.product.prodname_dependabot %} attempts to detect your commit message preferences and use similar patterns. Use the `commit-message` option to specify your preferences explicitly. -Opciones compatibles +Supported options -- `prefix` especifica un prefijo para todos los mensajes de confirmación. -- `prefix-development` especifica un prefijo separado para todos los mensajes de confirmación que actualizan dependencias en el grupo de dependencias de desarrollo. Cuando especificas un valor para esta opción, `prefix` se utiliza únicamente para las actualizaciones a las dependencias en el grupo de dependencias de producción. Esto es compatible con: `bundler`, `composer`, `mix`, `maven`, `npm`, y `pip`. -- `include: "scope"` especifica que cualquier prefijo es sucedido por una lista de dependencias actualizadas en la confirmación. +- `prefix` specifies a prefix for all commit messages. +- `prefix-development` specifies a separate prefix for all commit messages that update dependencies in the Development dependency group. When you specify a value for this option, the `prefix` is used only for updates to dependencies in the Production dependency group. This is supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`. +- `include: "scope"` specifies that any prefix is followed by a list of the dependencies updated in the commit. {% data reusables.dependabot.option-affects-security-updates %} @@ -293,25 +297,25 @@ updates: {% data reusables.dependabot.default-dependencies-allow-ignore %} -Las dependencias pueden ignorarse ya sea agregándolas a `ignore` o utilizando el comando `@dependabot ignore` en una solicitud de cambios que haya abierto el {% data variables.product.prodname_dependabot %}. +Dependencies can be ignored either by adding them to `ignore` or by using the `@dependabot ignore` command on a pull request opened by {% data variables.product.prodname_dependabot %}. -#### Crear condiciones de `ignore` desde `@dependabot ignore` +#### Creating `ignore` conditions from `@dependabot ignore` -Las dependencias que se ignoran utilizando el comando `@dependabot ignore` se almacenan centralmente para cada administrador de paquete. Si comienzas a ignorar las dependencias en el archivo `dependabot.yml`, estas preferencias existentes se consideran junto con las dependencias de `ignore` en la configuración. +Dependencies ignored by using the `@dependabot ignore` command are stored centrally for each package manager. If you start ignoring dependencies in the `dependabot.yml` file, these existing preferences are considered alongside the `ignore` dependencies in the configuration. -Puedes verificar si un repositorio tiene preferencias de `ignore` almacenadas si buscas `"@dependabot ignore" in:comments` en este. Si quieres dejar de ignorar una dependencia que se haya ignorado de esta forma, vuelve a abrir la solicitud de cambios. +You can check whether a repository has stored `ignore` preferences by searching the repository for `"@dependabot ignore" in:comments`. If you wish to un-ignore a dependency ignored this way, re-open the pull request. -Para obtener más información acerca de los comandos de `@dependabot ignore`, consulta la sección "[Administrar las solicitudes de extracción para las actualizaciones de dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)". +For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)." -#### Especificar dependencias y versiones para ignorar +#### Specifying dependencies and versions to ignore -Puedes utilizar la opción `ignore` para personalizar qué dependencias se actualizarán. La opción `ignore` es compatible con las siguientes opciones. +You can use the `ignore` option to customize which dependencies are updated. The `ignore` option supports the following options. -- `dependency-name`—se utiliza para ignorar actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId` (por ejemplo: `org.kohsuke:github-api`). -- `versions`—se utiliza para ignorar versiones o rangos específicos de las versiones. Si quieres definir un rango, utiliza el patrón estándar del administrador de paquetes (por ejemplo: `^1.0.0` para npm, o `~> 2.0` para Bundler). -- `update-types`—Se utiliza para ignorar tipos de actualizaciones tales como las de tipo `major`, `minor`, o `patch` en actualizaciones de versión (por ejemplo: `version-update:semver-patch` ignorará las actualizaciones de parche). Puedes combinar esto con `dependency-name: "*"` para ignorar algún `update-types` en particular en todas las dependencias. Actualmente, `version-update:semver-major`, `version-update:semver-minor`, y `version-update:semver-patch` son las únicas opciones compatibles. Este ajuste no afectará a las actualizaciones de seguridad. +- `dependency-name`—use to ignore updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId` (for example: `org.kohsuke:github-api`). +- `versions`—use to ignore specific versions or ranges of versions. If you want to define a range, use the standard pattern for the package manager (for example: `^1.0.0` for npm, or `~> 2.0` for Bundler). +- `update-types`—use to ignore types of updates, such as semver `major`, `minor`, or `patch` updates on version updates (for example: `version-update:semver-patch` will ignore patch updates). You can combine this with `dependency-name: "*"` to ignore particular `update-types` for all dependencies. Currently, `version-update:semver-major`, `version-update:semver-minor`, and `version-update:semver-patch` are the only supported options. Security updates are unaffected by this setting. -Si las `versions` y los `update-types` se utilizan juntos, el {% data variables.product.prodname_dependabot %} ignorará todas las actualizaciones en cualquiera que se configure. +If `versions` and `update-types` are used together, {% data variables.product.prodname_dependabot %} will ignore any update in either set. {% data reusables.dependabot.option-affects-security-updates %} @@ -337,16 +341,16 @@ updates: {% note %} -**Nota**: El {% data variables.product.prodname_dependabot %} solo puede ejecutar actualizaciones de versión en los archivos de bloqueo o de manifiesto si puede acceder a todas las dependencias en estos archivos, aún si agregas dependencias inaccesibles a la opción `ignore` de tu archivo de configuración. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" y "[Solución de problemas para errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)". +**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." {% endnote %} ### `insecure-external-code-execution` -Los administradores de paquetes con los valores `bundler`, `mix`, y `pip` de `package-ecosystem` pueden ejecutar el código externo en el manifiesto como parte del proceso de actualización de la versión. Esto podría permitir que un paquete que se haya puesto en riesgo borre las credenciales u obtenga acceso a los registros configurados. Cuando agregas un ajuste de [`registries`](#registries) dentro de una configuración de `updates`, el {% data variables.product.prodname_dependabot %} prevendrá automáticamente la ejecución de código externo, en cuyo caso, la actualización de versión podría fallar. Puedes elegir ignorar este comportamiento y permitir la ejecución de código externo para los administradores de paquetes `bundler`, `mix`, y `pip` si configuras a `insecure-external-code-execution` en `allow`. +Package managers with the `package-ecosystem` values `bundler`, `mix`, and `pip` may execute external code in the manifest as part of the version update process. This might allow a compromised package to steal credentials or gain access to configured registries. When you add a [`registries`](#registries) setting within an `updates` configuration, {% data variables.product.prodname_dependabot %} automatically prevents external code execution, in which case the version update may fail. You can choose to override this behavior and allow external code execution for `bundler`, `mix`, and `pip` package managers by setting `insecure-external-code-execution` to `allow`. -Puedes negar explícitamente la ejecución de código externo, sin importar si es que hay un ajuste de `registries` para esta configuración de actualización, configurando a `insecure-external-code-execution` en `deny`. +You can explicitly deny external code execution, irrespective of whether there is a `registries` setting for this update configuration, by setting `insecure-external-code-execution` to `deny`. {% raw %} ```yaml @@ -368,11 +372,12 @@ updates: ``` {% endraw %} -### `etiquetas` +### `labels` {% data reusables.dependabot.default-labels %} -Utiliza `labels` para anular las etiquetas predeterminadas y especificar las etiquetas alternas para todas las solicitudes de extracción que se levante para un administrador de paquete. Si ninguna de estas etiquetas se define en el repositorio, entonces se ha ignorado. Para inhabilitar todas las etiquetas, incluyendo aquellas predeterminadas, utiliza `labels: [ ]`. +Use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. If any of these labels is not defined in the repository, it is ignored. +To disable all labels, including the default labels, use `labels: [ ]`. {% data reusables.dependabot.option-affects-security-updates %} @@ -391,9 +396,9 @@ updates: - "dependencies" ``` -### `hito` +### `milestone` -Utiliza `milestone` para asociar todas las solicitudes de extracción que se han levantado para un administrador de paquete con un hito. Necesitas especificar el identificador numérico del hito y, no así, su etiqueta. Si ves un hito, la parte final de la URL de la página, después de `milestone`, es el identificador. Por ejemplo: `https://github.com///milestone/3`. +Use `milestone` to associate all pull requests raised for a package manager with a milestone. You need to specify the numeric identifier of the milestone and not its label. If you view a milestone, the final part of the page URL, after `milestone`, is the identifier. For example: `https://github.com///milestone/3`. {% data reusables.dependabot.option-affects-security-updates %} @@ -412,9 +417,9 @@ updates: ### `open-pull-requests-limit` -Predeterminadamente, {% data variables.product.prodname_dependabot %} abre un máximo de cinco solicitudes de extracción para las actualizaciones de versión. Una vez que hayan cinco solicitudes de cambio abiertas, las solicitudes nuevas se bloquearán hasta que fusiones o cierres algunas de las sollicitudes abiertas, después de lo cual, las solicitudes de cambiso nuevas pueden abrirse en actualizaciones subsecuentes. Utiliza `open-pull-requests-limit` para cambiar este límite. Esto también proporciona una forma simple de inhabilitar temporalmente las actualizaciones de versión para un administrador de paquete. +By default, {% data variables.product.prodname_dependabot %} opens a maximum of five pull requests for version updates. Once there are five open pull requests, new requests are blocked until you merge or close some of the open requests, after which new pull requests can be opened on subsequent updates. Use `open-pull-requests-limit` to change this limit. This also provides a simple way to temporarily disable version updates for a package manager. -Esta opción no tiene impacto en las actualizaciones de seguridad que tienen un límite separado e interno de diez solicitudes de extracción abiertas. +This option has no impact on security updates, which have a separate, internal limit of ten open pull requests. ```yaml # Specify the number of open pull requests allowed @@ -438,9 +443,9 @@ updates: ### `pull-request-branch-name.separator` -El {% data variables.product.prodname_dependabot %} genera una rama para cada solicitud de extracción. Cada nombre de rama incluye `dependabot`, y el administrador de paquete y la dependencia que se actualizaron. Predeterminadamente, estas partes están separadas por un símbolo de `/`, por ejemplo: `dependabot/npm_and_yarn/next_js/acorn-6.4.1`. +{% data variables.product.prodname_dependabot %} generates a branch for each pull request. Each branch name includes `dependabot`, and the package manager and dependency that are updated. By default, these parts are separated by a `/` symbol, for example: `dependabot/npm_and_yarn/next_js/acorn-6.4.1`. -Utiliza `pull-request-branch-name.separator` para especificar un separador diferente. Este puede ser alguno de entre: `"-"`, `_` o `/`. El símbolo de guión debe estar entre comillas porque, de lo contrario, se interpretará como que está declarando una lista YAML vacía. +Use `pull-request-branch-name.separator` to specify a different separator. This can be one of: `"-"`, `_` or `/`. The hyphen symbol must be quoted because otherwise it's interpreted as starting an empty YAML list. {% data reusables.dependabot.option-affects-security-updates %} @@ -461,12 +466,12 @@ updates: ### `rebase-strategy` -Predeterminadamente, el{% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de cambios abiertas y detecta cualquier cambio en ellas. Utiliza `rebase-strategy` para inhabilitar este comportamiento. +By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. Use `rebase-strategy` to disable this behavior. -Estrategias de rebase disponibles +Available rebase strategies -- `disabled` para inhabilitar el rebase automático. -- `auto` para utilizar el comportamiento predeterminado y rebasar las solicitudes de cambios abiertas cuando se detecten cambios. +- `disabled` to disable automatic rebasing. +- `auto` to use the default behavior and rebase open pull requests when changes are detected. {% data reusables.dependabot.option-affects-security-updates %} @@ -485,9 +490,9 @@ updates: ### `registries` -Para permitir que el {% data variables.product.prodname_dependabot %} acceda a un registro de paquete privado cuando esté realizando una actualización de versión, debes incluir un ajuste de `registries` dentro de la configuración relevante de `updates`. Puedes permitir que se utilicen todos los registros definidos si configuras a `registries` en `"*"`. Como alternativa, puedes listar los registros que puede utilizar la actualización. Para hacerlo, utiliza el nombre del registro como se define en la sección `registries` de nivel superior en el archivo _dependabot.yml_. +To allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you must include a `registries` setting within the relevant `updates` configuration. You can allow all of the defined registries to be used by setting `registries` to `"*"`. Alternatively, you can list the registries that the update can use. To do this, use the name of the registry as defined in the top-level `registries` section of the _dependabot.yml_ file. -Para permitir que el {% data variables.product.prodname_dependabot %} utilice los administradores de paquetes `bundler`, `mix`, y `pip` para actualizar dependencias en los registros privados, puedes elegir el permitir la ejecución de código externo. Para obtener más información, consulta [`insecure-external-code-execution`](#insecure-external-code-execution). +To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution). ```yaml # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries @@ -518,7 +523,7 @@ updates: ### `reviewers` -Utiliza `reviewers` para especificar los revisores o equipos individuales de revisores para las solicitudes de extracción que se levantaron para un administrador de paquete. Debes utilizar el nombre completo del equipo, incluyendo la organización, como si lo estuvieras @mencionando. +Use `reviewers` to specify individual reviewers or teams of reviewers for all pull requests raised for a package manager. You must use the full team name, including the organization, as if you were @mentioning the team. {% data reusables.dependabot.option-affects-security-updates %} @@ -540,9 +545,9 @@ updates: ### `schedule.day` -Cuando configuras una programación de actualizaciones en `weekly`, predeterminadamente, {% data variables.product.prodname_dependabot %} revisa si hay versiones nuevas los lunes en alguna hora aleatoria para el repositorio. Utiliza `schedule.day` para especificar un día alterno para revisar si hay actualizaciones. +When you set a `weekly` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions on Monday at a random set time for the repository. Use `schedule.day` to specify an alternative day to check for updates. -Valores compatibles +Supported values - `monday` - `tuesday` @@ -567,7 +572,7 @@ updates: ### `schedule.time` -Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones en una hora aleatoria para el repositorio. Utiliza `schedule.time` para especificar una hora alterna para revisar si hay actualizaciones (formato: `hh:mm`). +By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`). ```yaml # Set a time for checks @@ -583,7 +588,7 @@ updates: ### `schedule.timezone` -Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones en una hora aleatoria para el repositorio. Utiliza `schedule.timezone` para especificar un huso horario alternativo. El identificador de zona debe ser tomado de la base de datos de Husos Horarios que mantiene [iana](https://www.iana.org/time-zones). Para obtener más información, consulta la [Lista de bases de datos tz para husos horarios](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.timezone` to specify an alternative time zone. The time zone identifier must be from the Time Zone database maintained by [iana](https://www.iana.org/time-zones). For more information, see [List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```yaml # Specify the timezone for checks @@ -601,7 +606,7 @@ updates: ### `target-branch` -Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay archivos de manifiesto en las ramas predeterminadas y levanta solicitudes de extracción para las actualizaciones de versión contra dicha rama. Utiliza `target-branch` para especificar una rama diferente para los archivos de manifiesto y para las solicitudes de extracción. Cuando utilizas esta opción, la configuración para este administrador de paquete ya no afectará ninguna solicitud de extracción que se haya levantado para las actualizaciones de seguridad. +By default, {% data variables.product.prodname_dependabot %} checks for manifest files on the default branch and raises pull requests for version updates against this branch. Use `target-branch` to specify a different branch for manifest files and for pull requests. When you use this option, the settings for this package manager will no longer affect any pull requests raised for security updates. ```yaml # Specify a non-default branch for pull requests for pip @@ -632,7 +637,7 @@ updates: ### `vendor` -Utiliza la opción `vendor` para indicar al {% data variables.product.prodname_dependabot %} delegar las dependencias a los proveedores cuando se actualicen. No utilices esta opción si estás usando `gomod`, ya que el {% data variables.product.prodname_dependabot %} detecta la delegación a vendedores automáticamente para esta herramienta. +Use the `vendor` option to tell {% data variables.product.prodname_dependabot %} to vendor dependencies when updating them. Don't use this option if you're using `gomod` as {% data variables.product.prodname_dependabot %} automatically detects vendoring for this tool. ```yaml # Configure version updates for both dependencies defined in manifests and vendored dependencies @@ -647,34 +652,34 @@ updates: interval: "weekly" ``` -El {% data variables.product.prodname_dependabot %} solo actualiza las dependencias delegadas a proveedores que se ubiquen en directorios específicos en un repositorio. +{% data variables.product.prodname_dependabot %} only updates the vendored dependencies located in specific directories in a repository. -| Administración de paquetes | Ruta de archivo requerida para las dependencias delegadas | Más información | -| -------------------------- | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- | -| `bundler` | Las dependencias deben estar en el directorio _vendor/cache_.
    Otras rutas de archivo no son compatibles. | [documentación de `bundle cache`](https://bundler.io/man/bundle-cache.1.html) | -| `gomod` | No hay requisitos de ruta (las dependencias se ubican habitualmente en el directorio _vendor_) | [documentación de `go mod vendor`](https://golang.org/ref/mod#go-mod-vendor) | +| Package manager | Required file path for vendored dependencies | More information | + |------------------|-------------------------------|--------| + | `bundler` | The dependencies must be in the _vendor/cache_ directory.
    Other file paths are not supported. | [`bundle cache` documentation](https://bundler.io/man/bundle-cache.1.html) | + | `gomod` | No path requirement (dependencies are usually located in the _vendor_ directory) | [`go mod vendor` documentation](https://golang.org/ref/mod#go-mod-vendor) | ### `versioning-strategy` -Cuando el {% data variables.product.prodname_dependabot %} edita un archivo de manifiesto para actualizar una versión, utiliza las siguientes estrategias generales: +When {% data variables.product.prodname_dependabot %} edits a manifest file to update a version, it uses the following overall strategies: -- Para las apps, los requisitos de versión se incrementan, por ejemplo: npm, pip y Composer. -- Para las bibliotecas, el rango de versiones se amplía, por ejemplo: Bundler y Cargo. +- For apps, the version requirements are increased, for example: npm, pip and Composer. +- For libraries, the range of versions is widened, for example: Bundler and Cargo. -Utiliza la opción `versioning-strategy` para cambiar este comportamiento para los administradores de paquete compatibles. +Use the `versioning-strategy` option to change this behavior for supported package managers. {% data reusables.dependabot.option-affects-security-updates %} -Estrategias de actualización disponibles +Available update strategies -| Opción | Compatible con | Acción | -| ----------------------- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `lockfile-only` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Crear únicamente solicitudes de cambios para actualizar archivos de bloqueo. Ignorar cualquier versión nueva que pudiera requerir cambios en el paquete del manifiesto. | -| `auto` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Seguir la estrategia predeterminada descrita anteriormente. | -| `widen` | `composer`, `npm` | Relajar el requisito de versión para que incluya tanto la versión nueva como la anterior, cuando sea posible. | -| `increase` | `bundler`, `composer`, `npm` | Siempre incrementar el requisito de versión para que empate con la versión nueva. | -| `increase-if-necessary` | `bundler`, `composer`, `npm` | Incrementar el requisito de versión únicamente cuando lo requiera la versión nueva. | +| Option | Supported by | Action | +|--------|--------------|--------| +| `lockfile-only` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Only create pull requests to update lockfiles. Ignore any new versions that would require package manifest changes. | +| `auto` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Follow the default strategy described above.| +| `widen`| `composer`, `npm` | Relax the version requirement to include both the new and old version, when possible. | +| `increase`| `bundler`, `composer`, `npm` | Always increase the version requirement to match the new version. | +| `increase-if-necessary` | `bundler`, `composer`, `npm` | Increase the version requirement only when required by the new version. | ```yaml # Customize the manifest version strategy @@ -706,17 +711,17 @@ updates: versioning-strategy: lockfile-only ``` -## Opciones de configuración para los registros privados +## Configuration options for private registries -La clave de nivel superior `registries` es opcional. Esta te permite especificar los detalles de autenticación que el {% data variables.product.prodname_dependabot %} puede utilizar para acceder a los registros de paquetes privados. +The top-level `registries` key is optional. It allows you to specify authentication details that {% data variables.product.prodname_dependabot %} can use to access private package registries. {% note %} -**Nota:** Los registros privados detras de los cortafuegos en las redes privadas no son compatibles. +**Note:** Private registries behind firewalls on private networks are not supported. {% endnote %} -El valor de la clave `registries` es un arreglo asociativo, del cual cada elemento consiste de una clave que identifica un registro en particular y un valor que es un arreglo asociativo que especifica la configuración que se requiere para acceder a dicho registro. El siguiente archivo de *dependabot.yml* configura un registro que se identifica como `dockerhub` en la sección de `registries` del archivo y luego lo referencia en la sección de `updates` del mismo. +The value of the `registries` key is an associative array, each element of which consists of a key that identifies a particular registry and a value which is an associative array that specifies the settings required to access that registry. The following *dependabot.yml* file, configures a registry identified as `dockerhub` in the `registries` section of the file and then references this in the `updates` section of the file. {% raw %} ```yaml @@ -739,24 +744,24 @@ updates: ``` {% endraw %} -Utilizarás las siguientes opciones para especificar la configuración de acceso. La configuración del registro debe contener un `type` y una `url` y, habitualmente, ya sea una combinación de `username` y `password` o un `token`. +You use the following options to specify access settings. Registry settings must contain a `type` and a `url`, and typically either a `username` and `password` combination or a `token`. -| Opción                 | Descripción | -|:------------------------------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `type` | Identifica el tipo de registro. Consulta la lista completa de tipos más adelante. | -| `url` | La URL a utilizar para acceder a las dependencias en el registro. El protocolo es opcional. Si no se especifica, se asumirá que es `https://`. El {% data variables.product.prodname_dependabot %} agrega o ignora las diagonales iniciales conforme sea necesario. | -| `nombre de usuario` | El nombre de usuario que utilizará el {% data variables.product.prodname_dependabot %} para acceder al registro. | -| `contraseña` | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga la contraseña del usuario específico. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". | -| `clave` | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga una clave de acceso para este registro. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". | -| `token` | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga un token de acceso para este registro. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". | -| `replaces-base` | Para los registros con `type: python-index`, si el valor booleano es `true`, pip resuleve las dependencias utilizando la URL especificada en vez de la URL base del Índice de Paquetes de Python (que predeterminadamente es `https://pypi.org/simple`). | +| Option                 | Description | +|:---|:---| +| `type` | Identifies the type of registry. See the full list of types below. | +| `url` | The URL to use to access the dependencies in this registry. The protocol is optional. If not specified, `https://` is assumed. {% data variables.product.prodname_dependabot %} adds or ignores trailing slashes as required. | +| `username` | The username that {% data variables.product.prodname_dependabot %} uses to access the registry. | +| `password` | A reference to a {% data variables.product.prodname_dependabot %} secret containing the password for the specified user. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." | +| `key` | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access key for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." | +| `token` | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access token for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." | +| `replaces-base` | For registries with `type: python-index`, if the boolean value is `true`, pip resolves dependencies by using the specified URL rather than the base URL of the Python Package Index (by default `https://pypi.org/simple`). | -Cada `type` de configuración requiere que proporciones ajustes en particular. Algunos tipos permiten más de una forma de conectarse. Las siguientes secciones proporcionan detalles de las configuraciones que deberías utilizar para cada `type`. +Each configuration `type` requires you to provide particular settings. Some types allow more than one way to connect. The following sections provide details of the settings you should use for each `type`. -### `composer-repository` +### `composer-repository` -El tipo `composer-repository` es compatible con nombre de usuario y contraseña. +The `composer-repository` type supports username and password. {% raw %} ```yaml @@ -769,9 +774,9 @@ registries: ``` {% endraw %} -### `docker-registry` +### `docker-registry` -El tipo `docker-registry` es compatible con nombre de usuario y contraseña. +The `docker-registry` type supports username and password. {% raw %} ```yaml @@ -784,7 +789,7 @@ registries: ``` {% endraw %} -El tipo `docker-registry` también se puede utilizar para extraer información de Amazon ECR utilizando las credenciales estáticas de AWS. +The `docker-registry` type can also be used to pull from Amazon ECR using static AWS credentials. {% raw %} ```yaml @@ -797,9 +802,9 @@ registries: ``` {% endraw %} -### `git` +### `git` -El tipo `git` es compatible con nombre de usuario y contraseña. +The `git` type supports username and password. {% raw %} ```yaml @@ -812,9 +817,9 @@ registries: ``` {% endraw %} -### `hex-organization` +### `hex-organization` -El tipo `hex-organization` es compatible con organizaciones y claves. +The `hex-organization` type supports organization and key. {% raw %} ```yaml @@ -828,7 +833,7 @@ registries: ### `maven-repository` -El tipo `maven-repository` es compatible con usuario y contraseña. +The `maven-repository` type supports username and password. {% raw %} ```yaml @@ -843,9 +848,9 @@ registries: ### `npm-registry` -El tipo `npm-registry` es compatible con nombre de usuario y contraseña, o token. +The `npm-registry` type supports username and password, or token. -Cuando utilizas un nombre de usuario y contraseña, tu token de autorización de `.npmrc` podría contener un `_password` cifrado en `base64`; sin embargo, la contraseña referenciada en tu archivo de configuración del {% data variables.product.prodname_dependabot %} podría ser la contraseña original (descifrada). +When using username and password, your `.npmrc`'s auth token may contain a `base64` encoded `_password`; however, the password referenced in your {% data variables.product.prodname_dependabot %} configuration file must be the original (unencoded) password. {% raw %} ```yaml @@ -868,9 +873,9 @@ registries: ``` {% endraw %} -### `nuget-feed` +### `nuget-feed` -El tipo `nuget-feed` es compatible con nombre de usuario y contraseña, o token. +The `nuget-feed` type supports username and password, or token. {% raw %} ```yaml @@ -893,9 +898,9 @@ registries: ``` {% endraw %} -### `python-index` +### `python-index` -El tipo `python-index` es compatible con nombre de usuario y contraseña, o token. +The `python-index` type supports username and password, or token. {% raw %} ```yaml @@ -922,7 +927,7 @@ registries: ### `rubygems-server` -El tipo `rubygems-server` es compatible con nombre de usuario y contraseña, o token. +The `rubygems-server` type supports username and password, or token. {% raw %} ```yaml @@ -947,7 +952,7 @@ registries: ### `terraform-registry` -El tipo `terraform-registry` es comatible con un token. +The `terraform-registry` type supports a token. {% raw %} ```yaml diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md index 81e96ee2e5..217257ceb2 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md @@ -1,6 +1,6 @@ --- -title: Personalizar las actualizaciones de las dependencias -intro: 'Puedes personalizar cómo el {% data variables.product.prodname_dependabot %} mantiene tus dependencias.' +title: Customizing dependency updates +intro: 'You can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies.' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.' redirect_from: - /github/administering-a-repository/customizing-dependency-updates @@ -8,6 +8,7 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Dependabot @@ -17,34 +18,37 @@ topics: - Dependencies - Pull requests - Vulnerabilities -shortTitle: Pesonalizar las actualizaciones +shortTitle: Customize updates --- -## Acerca de personalizar las actualizaciones de las dependencias +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -Después de que hayas habilitado la actualización de versiones, puedes personalizar como el {% data variables.product.prodname_dependabot %} mantiene tus dependencias si agregas más opciones al archivo *dependabot.yml*. Por ejemplo, podrías: +## About customizing dependency updates -- Especifica en qué día de la semana se abrirán las solicitudes de extracción para la actualización de versiones: `schedule.day` -- Establece revisores, asignados y etiquetas para cada administrador de paquete: `reviewers`, `assignees`, y `labels` -- Define una estrategia de versionamiento para los cambios que se realicen en cada archivo de manifiesto: `versioning-strategy` -- Cambia la cantidad máxima de solicitudes de extracción abiertas para actualizaciones de versión del valor predeterminado que es 5: `open-pull-requests-limit` -- Abre solicitudes de extracción para actualizaciones de versión para seleccionar una rama específica en vez de la rama predeterminada: `target-branch` +After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could: -Para obtener más información acerca de las opciones de configuración, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". +- Specify which day of the week to open pull requests for version updates: `schedule.day` +- Set reviewers, assignees, and labels for each package manager: `reviewers`, `assignees`, and `labels` +- Define a versioning strategy for changes to each manifest file: `versioning-strategy` +- Change the maximum number of open pull requests for version updates from the default of 5: `open-pull-requests-limit` +- Open pull requests for version updates to target a specific branch, instead of the default branch: `target-branch` -Cuando actualizas el archivo *dependabot.yml* en tu repositorio, el {% data variables.product.prodname_dependabot %} ejecuta una revisión inmediata con la nueva configuración. Verás una lista de dependencias actualizada en cuestión de minutos en la pestaña de **{% data variables.product.prodname_dependabot %}**, esto podría tomar más tiempo si el reposiorio tiene muchas dependencias. También puedes ver las solicitudes de extracción nuevas para las actualizaciones de versión. Para obtener más información, consulta la sección "[Listar dependencias configuradas para actualizaciones de versión](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". +For more information about the configuration options, see "[Configuration options for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)." -## Impacto de los cambios de configuración en las actualizaciones de seguridad +When you update the *dependabot.yml* file in your repository, {% data variables.product.prodname_dependabot %} runs an immediate check with the new configuration. Within minutes you will see an updated list of dependencies on the **{% data variables.product.prodname_dependabot %}** tab, this may take longer if the repository has many dependencies. You may also see new pull requests for version updates. For more information, see "[Listing dependencies configured for version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)." -Si personalizas el archivo *dependabot.yml*, podrías notar algunos cambios en las solicitudes de extracción que se levantan para las actualizaciones de seguridad. Estas solicitudes de extracción siempre se activan mediante una asesoría de seguridad para una dependencia en vez de mediante un calendario de programación del {% data variables.product.prodname_dependabot %}. Sin embargo, estas heredan la configuración de ajustes relevante del archivo *dependabot.yml* a menos de que especifiques una rama destino diferente para las actualizaciones de versión. +## Impact of configuration changes on security updates -Por ejemplo, consulta la sección "[Configurar etiquetas personalizadas](#setting-custom-labels)" a más adelante. +If you customize the *dependabot.yml* file, you may notice some changes to the pull requests raised for security updates. These pull requests are always triggered by a security advisory for a dependency, rather than by the {% data variables.product.prodname_dependabot %} schedule. However, they inherit relevant configuration settings from the *dependabot.yml* file unless you specify a different target branch for version updates. -## Modificar la programación +For an example, see "[Setting custom labels](#setting-custom-labels)" below. -Cuando configuras una actualización de tipo `daily`, predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. Puedes utilizar `schedule.time` para especificar una hora alterna para que revise actualizaciones (en formato: `hh:mm`). +## Modifying scheduling -El archivo *dependabot.yml* de ejemplo a continuación expande la configuración de npm para especificar cuándo el {% data variables.product.prodname_dependabot %} debería revisar si hay actualizaciones de versión para las dependencias. +When you set a `daily` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions at 05:00 UTC. You can use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`). + +The example *dependabot.yml* file below expands the npm configuration to specify when {% data variables.product.prodname_dependabot %} should check for version updates to dependencies. ```yaml # dependabot.yml file with @@ -61,13 +65,13 @@ updates: time: "02:00" ``` -## Configurar los revisores y asignados +## Setting reviewers and assignees -Predeterminadamente, el {% data variables.product.prodname_dependabot %} levanta solicitudes de extracción sin ningún revisor o asignado. +By default, {% data variables.product.prodname_dependabot %} raises pull requests without any reviewers or assignees. -Puedes utilizar `reviewers` y `assignees` para especificar los revisores y asignados para todas las solicitudes de extracción que se levanten para un administrador de paquete. Cuando especificas un equipo, debes utilizar el nombre completo de éste, como si estuvieras @mencionándolo (incluyendo la organización). +You can use `reviewers` and `assignees` to specify reviewers and assignees for all pull requests raised for a package manager. When you specify a team, you must use the full team name, as if you were @mentioning the team (including the organization). -El ejemplo de archivo *dependabot.yml* mostrado a continuación cambia las configuraciones npm para que todas las solicitudes de extracción que se hayan abierto con actualizaciones de versión y de seguridad para npm tengan dos revisores y un asignado. +The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have two reviewers and one assignee. ```yaml # dependabot.yml file with @@ -89,17 +93,17 @@ updates: - "user-name" ``` -## Configurar las etiquetas personalizadas +## Setting custom labels {% data reusables.dependabot.default-labels %} -Puedes utilizar `labels` para anular las etiquetas predeterminadas y especificar etiquetas alternas para todas las solicitudes de extracción que se han levantado para un administrador de paquete. No puedes crear etiquetas nuevas en el archivo *dependabot.yml*, así que las etiquetas alternas ya deben existir en el repositorio. +You can use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. You can't create new labels in the *dependabot.yml* file, so the alternative labels must already exist in the repository. -El siguiente ejemplo de archivo *dependabot.yml* cambia la configuración de npm para que las solicitudes de extracción abiertas con actualizaciones de versión y de seguridad para npm tengan etiquetas personalizadas. También cambia la configuración de Docker para revisar las actualizaciones de versión contra una rama personalizada y para levantar solicitudes de extracción con etiquetas personalizadas contra dicha rama personalizada. Los cambios en Docker no afectarán las solicitudes de extracción para actualizaciones de seguridad, ya que dichas actualizaciones de seguridad siempre se hacen contra la rama predeterminada. +The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have custom labels. It also changes the Docker configuration to check for version updates against a custom branch and to raise pull requests with custom labels against that custom branch. The changes to Docker will not affect security update pull requests because security updates are always made against the default branch. {% note %} -**Nota:** La nueva `target-branch` deberá contener un Dockerfile para actualizar, de lo contrario, este cambio tendrá el efecto de inhabilitar las actualizaciones de versión para Docker. +**Note:** The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker. {% endnote %} @@ -134,6 +138,6 @@ updates: - "triage-board" ``` -## Más ejemplos +## More examples -Para obtener más ejemplos, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". +For more examples, see "[Configuration options for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md index 5d25880620..1c04b588f6 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md @@ -1,11 +1,12 @@ --- -title: Mantener tus dependencias actualizadas automáticamente -intro: 'El {% data variables.product.prodname_dependabot %} puede mantener tus dependencias de repositorio automáticamente.' +title: Keeping your dependencies updated automatically +intro: '{% data variables.product.prodname_dependabot %} can maintain your repository''s dependencies automatically.' redirect_from: - /github/administering-a-repository/keeping-your-dependencies-updated-automatically versions: fpt: '*' ghec: '*' + ghes: '>3.2' topics: - Repositories - Dependabot @@ -15,7 +16,7 @@ topics: children: - /about-dependabot-version-updates - /upgrading-from-dependabotcom-to-github-native-dependabot - - /enabling-and-disabling-version-updates + - /enabling-and-disabling-dependabot-version-updates - /listing-dependencies-configured-for-version-updates - /managing-pull-requests-for-dependency-updates - /automating-dependabot-with-github-actions @@ -23,6 +24,7 @@ children: - /customizing-dependency-updates - /configuration-options-for-dependency-updates - /keeping-your-actions-up-to-date-with-dependabot -shortTitle: Auto-actualizar las dependencias +shortTitle: Auto-update dependencies --- +{% data reusables.dependabot.beta-security-and-version-updates %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md index bf9274a332..7261cc6b3b 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md @@ -1,6 +1,6 @@ --- -title: Mantener tus acciones actualizadas con el Dependabot -intro: 'Puedes utilizar el {% data variables.product.prodname_dependabot %} para mantener las acciones que utilizas actualizadas en sus versiones más recientes.' +title: Keeping your actions up to date with Dependabot +intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the actions you use updated to the latest versions.' redirect_from: - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot - /github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot @@ -8,34 +8,39 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Repositories - Dependabot - Version updates - Actions -shortTitle: Acciones de actualización automática +shortTitle: Auto-update actions --- -## Acerca de {% data variables.product.prodname_dependabot_version_updates %} para las acciones +{% data reusables.dependabot.beta-security-and-version-updates %} -Las acciones a menudo se actualizan con correcciones de errores y con nuevas características para que los procesos automatizados sean más confiables, rápidos y seguros. Cundo habilitas las {% data variables.product.prodname_dependabot_version_updates %} para {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} te ayudará a asegurarte de que las referencias para las acciones en el archivo *workflow.yml* de un repositorio se mantengan actualizadas. El {% data variables.product.prodname_dependabot %} verifica la referencia de la acción para cada una de ellas en el archivo (habitualmente un número de versión o identificador de confirmación que se asocie con la acción) contra la última versión. Si alguna versión más reciente de la acción está disponible, el {% data variables.product.prodname_dependabot %} te enviará una solicitud de extracción que actualice la referencia en el archivo de flujo de trabajo a su última versión. Para obtener más información acerca de las {% data variables.product.prodname_dependabot_version_updates %}, consulta la sección "[Acerca del {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". Para obtener más información acerca de configurar flujos de trabajo para las {% data variables.product.prodname_actions %}, consulta la sección "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +{% data reusables.dependabot.enterprise-enable-dependabot %} +## About {% data variables.product.prodname_dependabot_version_updates %} for actions + +Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." + {% data reusables.actions.workflow-runs-dependabot-note %} -## Habilitar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones +## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions -{% data reusables.dependabot.create-dependabot-yml %}Si ya habilitaste las {% data variables.product.prodname_dependabot_version_updates %} para otros ecosistemas o administradores de paquetes, simplemente abre el archivo *dependabot.yml* existente. -1. Especifica `"github-actions"` como el `package-ecosystem` a monitorear. -1. Configura el `directory` como `"/"` para verificar los archivos de flujo de trabajo en `.github/workflows`. -1. Configura un `schedule.interval` para especificar la frecuencia en la que se revisará si hay versiones nuevas. -{% data reusables.dependabot.check-in-dependabot-yml %}Si editaste un archivo existente, guarda tus cambios. +{% data reusables.dependabot.create-dependabot-yml %} If you have already enabled {% data variables.product.prodname_dependabot_version_updates %} for other ecosystems or package managers, simply open the existing *dependabot.yml* file. +1. Specify `"github-actions"` as a `package-ecosystem` to monitor. +1. Set the `directory` to `"/"` to check for workflow files in `.github/workflows`. +1. Set a `schedule.interval` to specify how often to check for new versions. +{% data reusables.dependabot.check-in-dependabot-yml %} If you have edited an existing file, save your changes. -También puedes habilitar las {% data variables.product.prodname_dependabot_version_updates %} en las bifurcaciones. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates#enabling-version-updates-on-forks)". +You can also enable {% data variables.product.prodname_dependabot_version_updates %} on forks. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)." -### Archivo de ejemplo de *dependabot.yml* para {% data variables.product.prodname_actions %} +### Example *dependabot.yml* file for {% data variables.product.prodname_actions %} -El siguiente ejemplo de archivo de *dependabot.yml* configura las actualizaciones de versión para {% data variables.product.prodname_actions %}. El `directory` debe configurarse como `"/"` para verificar los archivos de flujo de trabajo en `.github/workflows`. El `schedule.interval` se configura en `"daily"`. Después de que se verifique o actualice este archivo, el {% data variables.product.prodname_dependabot %} revisará si hay versiones nuevas de tus acciones. El {% data variables.product.prodname_dependabot %} levantará solicitudes de extracción para las actualizaciones de versión de cualquier acción desactualizada que encuentre. Después de las actualizaciones de versión iniciales, el {% data variables.product.prodname_dependabot %} seguirá buscando versiones desactualizadas para las acciones una vez por día. +The example *dependabot.yml* file below configures version updates for {% data variables.product.prodname_actions %}. The `directory` must be set to `"/"` to check for workflow files in `.github/workflows`. The `schedule.interval` is set to `"daily"`. After this file has been checked in or updated, {% data variables.product.prodname_dependabot %} checks for new versions of your actions. {% data variables.product.prodname_dependabot %} will raise pull requests for version updates for any outdated actions that it finds. After the initial version updates, {% data variables.product.prodname_dependabot %} will continue to check for outdated versions of actions once a day. ```yaml # Set update schedule for GitHub Actions @@ -50,10 +55,10 @@ updates: interval: "daily" ``` -## Configurar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones +## Configuring {% data variables.product.prodname_dependabot_version_updates %} for actions -Cuando habilitas las {% data variables.product.prodname_dependabot_version_updates %} para las acciones, debes especificar los valores de `package-ecosystem`, `directory`, y `schedule.interval`. Hay muchas más propiedades opcionales que puedes configurar para personalizar tus actualizaciones de versión aún más. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". +When enabling {% data variables.product.prodname_dependabot_version_updates %} for actions, you must specify values for `package-ecosystem`, `directory`, and `schedule.interval`. There are many more optional properties that you can set to further customize your version updates. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates)." -## Leer más +## Further reading -- "[Acerca de GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)" +- "[About GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)" diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md index 2d7e71d46f..4a0585c911 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md @@ -1,34 +1,41 @@ --- -title: Listar dependencias configuradas para las actualizaciones de versión -intro: 'Puedes ver las dependencias que monitorea el {% data variables.product.prodname_dependabot %} pára encontrar actualizaciones.' +title: Listing dependencies configured for version updates +intro: 'You can view the dependencies that {% data variables.product.prodname_dependabot %} monitors for updates.' redirect_from: - /github/administering-a-repository/listing-dependencies-configured-for-version-updates - /code-security/supply-chain-security/listing-dependencies-configured-for-version-updates versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Repositories - Dependabot - Version updates - Dependencies -shortTitle: Dependencias configuradas en la lista +shortTitle: List configured dependencies --- -## Visualizar dependencias que monitorea el {% data variables.product.prodname_dependabot %} +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -Después de que habilites las actualizaciones de versión, puedes confirmar que tu configuración es la correcta si utilizas la pestaña de **{% data variables.product.prodname_dependabot %}** en la gráfica de dependencias para el repositorio. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". +## Viewing dependencies monitored by {% data variables.product.prodname_dependabot %} + +After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %} {% data reusables.dependabot.click-dependabot-tab %} -5. Opcionalmente, para ver los archivos que se monitorean para un administrador de paquete, da clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} asociado. ![Archivos de dependencia monitoreados](/assets/images/help/dependabot/monitored-dependency-files.png) +1. Optionally, to view the files monitored for a package manager, click the associated {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + ![Monitored dependency files](/assets/images/help/dependabot/monitored-dependency-files.png) -Si no encuentras alguna dependencia, revisa los archivos de bitácora para ver los errores. En caso de que no encuentres algún administrador de paquete, revisa el archivo de configuración. +If any dependencies are missing, check the log files for errors. If any package managers are missing, review the configuration file. -## Visualizar los archivos de bitácora del {% data variables.product.prodname_dependabot %} +## Viewing {% data variables.product.prodname_dependabot %} log files -1. En la **pestaña de {% data variables.product.prodname_dependabot %}**, da clic en **Revisado por última vez hace *TIME*** para ver el archivo de bitácora que generó el {% data variables.product.prodname_dependabot %} durante su última verificación de actualizaciones de versión. ![Ver el archivo de bitácora](/assets/images/help/dependabot/last-checked-link.png) -2. Opcionalmente, para volver a ejecutar la revisión de versión, da clic en **Revisar si hay actualizaciones**. ![Revisar si hay actualizaciones](/assets/images/help/dependabot/check-for-updates.png) +1. On the **{% data variables.product.prodname_dependabot %}** tab, click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. + ![View log file](/assets/images/help/dependabot/last-checked-link.png) +2. Optionally, to rerun the version check, click **Check for updates**. + ![Check for updates](/assets/images/help/dependabot/check-for-updates.png) diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md index 3bd3c54c63..e177ef64a7 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md @@ -1,12 +1,13 @@ --- -title: Administrar los secretos cifrados para el Dependabot -intro: 'Puedes almacenar la información sensible, como las contraseñas y tokens de acceso, como secretos cifrados y luego referenciarlos en el archivo de configuración del {% data variables.product.prodname_dependabot %}.' +title: Managing encrypted secrets for Dependabot +intro: 'You can store sensitive information, like passwords and access tokens, as encrypted secrets and then reference these in the {% data variables.product.prodname_dependabot %} configuration file.' redirect_from: - /github/administering-a-repository/managing-encrypted-secrets-for-dependabot - /code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Dependabot @@ -14,15 +15,17 @@ topics: - Secret store - Repositories - Dependencies -shortTitle: Administrar los secretos cifrados +shortTitle: Manage encrypted secrets --- -## Acerca de los secretos cifrados para los {% data variables.product.prodname_dependabot %} +{% data reusables.dependabot.beta-security-and-version-updates %} -Los secretos del {% data variables.product.prodname_dependabot %} son credenciales cifradas que creas ya sea a nivel de la organización o del repositorio. -Cuando agregas un secreto a nivel de la organización, puedes especificar qué repositorios pueden acceder a éste. Puedes utilizar secretos para permitir que el {% data variables.product.prodname_dependabot %} actualice las dependencias que se ubiquen en los registros del paquete. Cuando agregas un secreto que está cifrado antes de llegar a {% data variables.product.prodname_dotcom %} y permanece cifrado hasta que lo utiliza el {% data variables.product.prodname_dependabot %} para acceder a un registro de paquetes privado. +## About encrypted secrets for {% data variables.product.prodname_dependabot %} -Después de que agregas un secreto del {% data variables.product.prodname_dependabot %}, puedes referenciarlo en el archivo de configuración _dependabot.yml_ de esta forma: {% raw %}`${{secrets.NAME}}`{% endraw %}, en donde "NAME" es el nombre que eliges para el secreto. Por ejemplo: +{% data variables.product.prodname_dependabot %} secrets are encrypted credentials that you create at either the organization level or the repository level. +When you add a secret at the organization level, you can specify which repositories can access the secret. You can use secrets to allow {% data variables.product.prodname_dependabot %} to update dependencies located in private package registries. When you add a secret it's encrypted before it reaches {% data variables.product.prodname_dotcom %} and it remains encrypted until it's used by {% data variables.product.prodname_dependabot %} to access a private package registry. + +After you add a {% data variables.product.prodname_dependabot %} secret, you can reference it in the _dependabot.yml_ configuration file like this: {% raw %}`${{secrets.NAME}}`{% endraw %}, where "NAME" is the name you chose for the secret. For example: {% raw %} ```yaml @@ -30,16 +33,16 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}} ``` {% endraw %} -Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". +For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." -### Nombrar tus secretos +### Naming your secrets -El nombre de un secreto del {% data variables.product.prodname_dependabot %}: -* Solo puede contener caracteres alfanuméricos (`[A-Z]`, `[0-9]`) o guiones bajos (`_`). No se permiten espacios. Si escribes en minúscula, se cambiará todo a mayúsculas. -* No puede iniciar con el prefijo `GITHUB_`. -* No puede iniciar con un número. +The name of a {% data variables.product.prodname_dependabot %} secret: +* Can only contain alphanumeric characters (`[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed. If you enter lowercase letters these are changed to uppercase. +* Must not start with the `GITHUB_` prefix. +* Must not start with a number. -## Agregar un secreto de repositorio para el {% data variables.product.prodname_dependabot %} +## Adding a repository secret for {% data variables.product.prodname_dependabot %} {% data reusables.github-actions.permissions-statement-secrets-repository %} @@ -47,18 +50,18 @@ El nombre de un secreto del {% data variables.product.prodname_dependabot %}: {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.sidebar-secret %} {% data reusables.dependabot.dependabot-secrets-button %} -1. Da clic en **Secreto de repositorio nuevo**. -1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. -1. Ingresa el valor de tu secreto. -1. Haz clic en **Agregar secreto** (Agregar secreto). +1. Click **New repository secret**. +1. Type a name for your secret in the **Name** input box. +1. Enter the value for your secret. +1. Click **Add secret**. - El nombre del secreto se lista en la página de secretos del Dependabot. Puedes hacer clic en **Actualizar** para cambiar el valor del secreto. Puedes hacer clic en **Eliminar** para borrar el secreto. + The name of the secret is listed on the Dependabot secrets page. You can click **Update** to change the secret value. You can click **Remove** to delete the secret. - ![Actualizar o eliminar un secreto del repositorio](/assets/images/help/dependabot/update-remove-repo-secret.png) + ![Update or remove a repository secret](/assets/images/help/dependabot/update-remove-repo-secret.png) -## Agregar un secreto de organización para el {% data variables.product.prodname_dependabot %} +## Adding an organization secret for {% data variables.product.prodname_dependabot %} -Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos. +When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories. {% data reusables.github-actions.permissions-statement-secrets-organization %} @@ -66,22 +69,23 @@ Cuando creas un secreto en una organización, puedes utilizar una política para {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} {% data reusables.dependabot.dependabot-secrets-button %} -1. Da clic en **Secreto de organización nuevo**. -1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. -1. Ingresa el **Valor** para tu secreto. -1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. -1. Si eliges **Repositorios seleccionados**: +1. Click **New organization secret**. +1. Type a name for your secret in the **Name** input box. +1. Enter the **Value** for your secret. +1. From the **Repository access** dropdown list, choose an access policy. +1. If you chose **Selected repositories**: - * Da clic en {% octicon "gear" aria-label="The Gear icon" %}. - * Elige los repositorios que pueden acceder a este secreto. ![Selecciona los repositorios para este secreto](/assets/images/help/dependabot/secret-repository-access.png) - * Haz clic en **Actualizar selección**. + * Click {% octicon "gear" aria-label="The Gear icon" %}. + * Choose the repositories that can access this secret. + ![Select repositories for this secret](/assets/images/help/dependabot/secret-repository-access.png) + * Click **Update selection**. -1. Haz clic en **Agregar secreto** (Agregar secreto). +1. Click **Add secret**. - El nombre del secreto se lista en la página de secretos del Dependabot. Puedes hacer clic en **Actualizar** para cambiar el valor del secreto o su política de acceso. Puedes hacer clic en **Eliminar** para borrar el secreto. + The name of the secret is listed on the Dependabot secrets page. You can click **Update** to change the secret value or its access policy. You can click **Remove** to delete the secret. - ![Actualiza o elimina un secreto de organización](/assets/images/help/dependabot/update-remove-repo-secret.png) + ![Update or remove an organization secret](/assets/images/help/dependabot/update-remove-org-secret.png) + +## Adding {% data variables.product.prodname_dependabot %} to your registries IP allow list -## Agregar al {% data variables.product.prodname_dependabot %} a tu lista de direcciones IP permitidas de tus registros - -Si tu registro privado se configura con una lista de direcciones IP permitidas, puedes encontrar las direcciones IP que utiliza el {% data variables.product.prodname_dependabot %} para acceder al registro en la terminal API del meta, bajo la clave `dependabot`. Para obtener más información, consulta la sección "[Meta](/rest/reference/meta)". +If your private registry is configured with an IP allow list, you can find the IP addresses {% data variables.product.prodname_dependabot %} uses to access the registry in the meta API endpoint, under the `dependabot` key. For more information, see "[Meta](/rest/reference/meta)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md index 04c031796c..99176596b7 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md @@ -1,12 +1,13 @@ --- -title: Administrar las solicitudes de extracción para las actualizaciones de dependencia -intro: 'Administrarás las solicitudes de extracción que levante el {% data variables.product.prodname_dependabot %} de casi la misma forma que cualquier otra solicitud de extracción, pero hay algunas opciones adicionales.' +title: Managing pull requests for dependency updates +intro: 'You manage pull requests raised by {% data variables.product.prodname_dependabot %} in much the same way as other pull requests, but there are some extra options.' redirect_from: - /github/administering-a-repository/managing-pull-requests-for-dependency-updates - /code-security/supply-chain-security/managing-pull-requests-for-dependency-updates versions: fpt: '*' ghec: '*' + ghes: '> 3.2' type: how_to topics: - Repositories @@ -15,46 +16,50 @@ topics: - Pull requests - Dependencies - Vulnerabilities -shortTitle: Administrar las solicitudes de cambios del Dependabot +shortTitle: Manage Dependabot PRs --- -## Acerca de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} + +## About {% data variables.product.prodname_dependabot %} pull requests {% data reusables.dependabot.pull-request-introduction %} -Cuando el {% data variables.product.prodname_dependabot %} levanta una solicitud de extracción, se te notificará con el método que hayas escogido para el repositorio. Cada solicitud de cambios contiene información detallada sobre el cambio propusto, que se toma del administrador de paquetes. Estas solicitudes de extracción siguen las revisiones y pruebas normales que se definieron en tu repositorio. Adicionalmente, si hay información suficiente disponible, verás una puntuación de compatibilidad. Esto también podría ayudarte a decidir si quieres fusionar el cambio o no. Para obtener información sobre esta puntuación, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +When {% data variables.product.prodname_dependabot %} raises a pull request, you're notified by your chosen method for the repository. Each pull request contains detailed information about the proposed change, taken from the package manager. These pull requests follow the normal checks and tests defined in your repository. +{% ifversion fpt or ghec %}In addition, where enough information is available, you'll see a compatibility score. This may also help you decide whether or not to merge the change. For information about this score, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."{% endif %} -Si tienes muchas dependencias para administrar, tal vez quieras personalizar la configuración para cada administrador de paquete y que así, las solicitudes de extracción tengan revisores, asignados, y etiquetas específicos. Para obtener más información, consulta la sección "[Personalizar actualizaciones de dependencias](/github/administering-a-repository/customizing-dependency-updates)". +If you have many dependencies to manage, you may want to customize the configuration for each package manager so that pull requests have specific reviewers, assignees, and labels. For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)." -## Visualizar las solicitudes de extracción del {% data variables.product.prodname_dependabot %} +## Viewing {% data variables.product.prodname_dependabot %} pull requests {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -1. Cualquier solicitud de extracción para actualizaciones de versión o de seguridad se puede identificar fácilmente. - - El autor es [dependabot](https://github.com/dependabot), la cuenta bot que utiliza la app del {% data variables.product.prodname_dependabot %}. - - Predeterminadamente, tienen la etiqueta `dependencies`. +1. Any pull requests for security or version updates are easy to identify. + - The author is {% ifversion fpt or ghec %}[dependabot](https://github.com/dependabot){% else %}dependabot{% endif %}, the bot account used by {% data variables.product.prodname_dependabot %}. + - By default, they have the `dependencies` label. -## Cambiar la estrategia de rebase para las solicitudes de extracción del {% data variables.product.prodname_dependabot %} +## Changing the rebase strategy for {% data variables.product.prodname_dependabot %} pull requests -Predeterminadamente, el {% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de extracción para resolver cualquier conflicto. Si prefieres manejar los conflictos de fusión manualmente, puedes inhabilitar esta opción utilizando la opción de `rebase-strategy`. Para obtener más detalles, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)". +By default, {% data variables.product.prodname_dependabot %} automatically rebases pull requests to resolve any conflicts. If you'd prefer to handle merge conflicts manually, you can disable this using the `rebase-strategy` option. For details, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)." -## Administrar las solicitudes de extracción del {% data variables.product.prodname_dependabot %} con comandos de comentario +## Managing {% data variables.product.prodname_dependabot %} pull requests with comment commands -El {% data variables.product.prodname_dependabot %} responde a comandos simples en los comentarios. Cada solicitud de cambios contiene detalles de los comandos que puedes utilizar para procesarla (por ejemplo: para fusionarla, combinarla, reabrirla, cerrarla o rebasarla) bajo la sección de "comandos y opciones del {% data variables.product.prodname_dependabot %}". El objetivo es facilitar tanto como sea posible el que se pueda clasificar automáticamente las solicitudes de extracción generadas. +{% data variables.product.prodname_dependabot %} responds to simple commands in comments. Each pull request contains details of the commands you can use to process the pull request (for example: to merge, squash, reopen, close, or rebase the pull request) under the "{% data variables.product.prodname_dependabot %} commands and options" section. The aim is to make it as easy as possible for you to triage these automatically generated pull requests. -Puedes utilizar cualquiera de los siguientes comandos en una solicitud de cambios del {% data variables.product.prodname_dependabot %}. +You can use any of the following commands on a {% data variables.product.prodname_dependabot %} pull request. -- `@dependabot cancel merge` cancela una fusión previamente solicitada. -- `@dependabot close` cierra la solicitud de cambios y previene que el {% data variables.product.prodname_dependabot %} vuelva a crearla. Puedes lograr el mismo resultado si cierras la solicitud de cambios manualmente. -- `@dependabot ignore this dependency` cierra la solicitud de cambios y previene que {% data variables.product.prodname_dependabot %} cree más solicitudes de cambios para esta dependencia (a menos de que vuelvas a abrir la solicitud de cambios para mejorarla a la versión sugerida de la dependencia tú mismo). -- `@dependabot ignore this major version` cierra la solicitud de cambios y previene que el {% data variables.product.prodname_dependabot %} cree más solicitudes de cambio para esta versión mayor (a menos de que vuelvas a abrir la solicitud de cambios o de que tú mismo mejores a esta versión mayor). -- `@dependabot ignore this minor version` cierra la solicitud de cambios y previene que el {% data variables.product.prodname_dependabot %} cree más solicitudes de cambio para esta versión menor (a menos de que vuelvas a abrir la solicitud de cambios o que tú mismo mejores a esta versión menor). -- `@dependabot merge` fusiona la solicitud de cambios una vez que tus pruebas de IC hayan pasado. -- `@dependabot rebase` rebasa la solicitud de cambios. -- `@dependabot recreate` vuelve a crear la solicitud de cambios, sobreescribiendo cualquier edición que se le haya hecho. -- `@dependabot reopen` vuelve a abrir la solicitud de cambios si es que se había cerrado. -- `@dependabot squash and merge` combina y fusiona la solicitud de cambios una vez que hayan pasado tus pruebas de IC. +- `@dependabot cancel merge` cancels a previously requested merge. +- `@dependabot close` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from recreating that pull request. You can achieve the same result by closing the pull request manually. +- `@dependabot ignore this dependency` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from creating any more pull requests for this dependency (unless you reopen the pull request or upgrade to the suggested version of the dependency yourself). +- `@dependabot ignore this major version` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from creating any more pull requests for this major version (unless you reopen the pull request or upgrade to this major version yourself). +- `@dependabot ignore this minor version` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from creating any more pull requests for this minor version (unless you reopen the pull request or upgrade to this minor version yourself). +- `@dependabot merge` merges the pull request once your CI tests have passed. +- `@dependabot rebase` rebases the pull request. +- `@dependabot recreate` recreates the pull request, overwriting any edits that have been made to the pull request. +- `@dependabot reopen` reopens the pull request if the pull request is closed. +- `@dependabot squash and merge` squashes and merges the pull request once your CI tests have passed. -El {% data variables.product.prodname_dependabot %} reaccionará con un emoji de "pulgares arriba" para reconocer el comando y podrá responder con un comentario de la solicitud de cambios. Si bien el {% data variables.product.prodname_dependabot %} a menudo responde rápidamente, algunos comandos podrían tardar varios minutos para completarse si el {% data variables.product.prodname_dependabot %} está ocupado procesando otras actualizaciones o comandos. +{% data variables.product.prodname_dependabot %} will react with a "thumbs up" emoji to acknowledge the command, and may respond with a comment on the pull request. While {% data variables.product.prodname_dependabot %} usually responds quickly, some commands may take several minutes to complete if {% data variables.product.prodname_dependabot %} is busy processing other updates or commands. -Si ejecutas cualquiera de los comandos para ignorar las dependencias o las versiones, el {% data variables.product.prodname_dependabot %} almacena las preferencias para el repositorio centralmente. Si bien esta es una solución rápida, para aquellos repositorios con más de un colaborador, es mejor definir explícitamente las dependencias y versiones a ignorar en el archivo de configuración. Esto hace que todos los colaboradores puedan ver más fácilmente por qué una dependencia en particular no se está actualizando automáticamente. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". +If you run any of the commands for ignoring dependencies or versions, {% data variables.product.prodname_dependabot %} stores the preferences for the repository centrally. While this is a quick solution, for repositories with more than one contributor it is better to explicitly define the dependencies and versions to ignore in the configuration file. This makes it easy for all contributors to see why a particular dependency isn't being updated automatically. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index c4d1b57022..1359ccf52a 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -1,6 +1,6 @@ --- -title: Acerca de las alertas para las dependencias vulnerables -intro: '{% data variables.product.product_name %} envía {% data variables.product.prodname_dependabot_alerts %} cuando detectamos vulnerabilidades que afectan tu repositorio.' +title: About alerts for vulnerable dependencies +intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository.' redirect_from: - /articles/about-security-alerts-for-vulnerable-dependencies - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies @@ -18,79 +18,78 @@ topics: - Vulnerabilities - Repositories - Dependencies -shortTitle: Las alertas del dependabot +shortTitle: Dependabot alerts --- - -## Acerca de las dependencias vulnerables +## About vulnerable dependencies {% data reusables.repositories.a-vulnerability-is %} -Cuando tu código depende de un paquete que tiene una vulnerabilidad de seguridad, esta dependencia puede causar una serie de problemas para tu proyecto o para las personas que lo utilizan. +When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. -## Detección de dependencias vulnerables +## Detection of vulnerable dependencies {% data reusables.dependabot.dependabot-alerts-beta %} -{% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables y envía {% data variables.product.prodname_dependabot_alerts %} cuando: +{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt or ghec %} -- Se agrega una vulnerabilidad nueva a la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta las secciones "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" y [Acerca de las {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)".{% else %} -- Se sincronizan los datos de las asesorías nuevas en {% data variables.product.product_location %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} -- La gráfica de dependencias para los cambios a un repositorio. Por ejemplo, cuando un colaborador sube una confirmación para cambiar los paquetes o versiones de los cuales depende{% ifversion fpt or ghec %}, o cuando cambia el código de alguna de las dependencias{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/about-the-dependency-graph)". +- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %} +- New advisory data is synchronized to {% data variables.product.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} +- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)." {% data reusables.repositories.dependency-review %} -Para encontrar una lista de ecosistemas para las cuales {% data variables.product.product_name %} puede detectar vulnerabilidades y dependencias, consulta la sección [ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." {% note %} -**Nota:** Es importante mantener actualizados tu manifiesto y tus archivos bloqueados. Si la gráfica de dependencias no refleja con exactitud tus versiones y dependencias actuales, entonces podrías dejar pasar las alertas de las dependencias vulnerables que utilizas. También podrías obtener alertas de las dependencias que ya no utilizas. +**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. {% endnote %} -## Alertas del {% data variables.product.prodname_dependabot %} para dependencias vulnerables +## {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta dependencias vulnerables en repositorios _públicos_ y genera {% data variables.product.prodname_dependabot_alerts %} predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." For information about access requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)." -{% data variables.product.product_name %} comienza a generar la gráfica de dependencias inmediatamente y genera alertas de cualquier dependencia vulnerable tan pronto como las identifique. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". +{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes > 3.0 %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes > 3.0 %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} también podría notificar a los mantenedores de los repositorios afectados sobre la nueva alerta de acuerdo con sus preferencias de notificaciones. Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)". +When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes > 3.0 %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes > 3.0 %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)." -{% ifversion fpt or ghec %} -Para los repositorios en donde están habilitadas las {% data variables.product.prodname_dependabot_security_updates %}, la alerta también podría contener un enlace a una solicitud de cambios o a una actualización en el archivo de bloqueo o de manifiesto para la versión mínima que resuelva la vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +{% ifversion fpt or ghec or ghes > 3.2 %} +For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} {% warning %} -**Nota**: Las características de seguridad de {% data variables.product.product_name %} no aseguran que se detectarán todas las vulnerabilidades. Aunque siempre estamos tratando de actualizar nuestra base de datos de vulnerabilidades y de generar alertas con nuestra información más actualizada, no podremos atrapar todo o garantizar decirte acerca de las vulnerabilidades conocidas dentro de un periodo de tiempo determinado. Estas características no son sustitutos de la revisión humana de cada dependencia por posibles vulnerabilidades o cualquier otra cuestión. Te recomendamos consultar con un servicio de seguridad o realizar una revisión de vulnerabilidad exhaustiva cuando sea necesario. +**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. {% endwarning %} -## Acceso a las alertas del {% data variables.product.prodname_dependabot %} +## Access to {% data variables.product.prodname_dependabot %} alerts -Puedes ver todas las alertas que afectan un proyecto en particular{% ifversion fpt or ghec %} en la pestaña de Seguridad del repositorio o{% endif %} en la gráfica de dependencias del repositorio. Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositiorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)". +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." -Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades identificadas de ningún repositorio. También puedes hacer que las {% data variables.product.prodname_dependabot_alerts %} sean visibles para más personas o equipos que trabajen en los repositorios que te pertenecen o para los cuales tienes permisos administrativos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} {% data reusables.notifications.vulnerable-dependency-notification-enable %} -{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)". +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)." -También puedes ver todas las {% data variables.product.prodname_dependabot_alerts %} que corresponden a una vulnerabilidad en particular en la {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %} +You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghec %} -## Leer más +{% ifversion fpt or ghec or ghes > 3.2 %} +## Further reading -- "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.prodname_dotcom %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} +- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% endif %} +{% ifversion fpt or ghec %}- "[Understanding how {% data variables.product.prodname_dotcom %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md index 522fc27451..71502324aa 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md @@ -1,7 +1,7 @@ --- title: About Dependabot security updates -intro: '{% data variables.product.prodname_dependabot %} puede arreglar tus dependencias vulnerables levantando solicitudes de extracción con actualizaciones de seguridad.' -shortTitle: Actualizaciones de seguridad del dependabot +intro: '{% data variables.product.prodname_dependabot %} can fix vulnerable dependencies for you by raising pull requests with security updates.' +shortTitle: Dependabot security updates redirect_from: - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates - /github/managing-security-vulnerabilities/about-dependabot-security-updates @@ -9,6 +9,7 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '> 3.2' type: overview topics: - Dependabot @@ -21,39 +22,45 @@ topics: -## Acerca de las {% data variables.product.prodname_dependabot_security_updates %} +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -Las {% data variables.product.prodname_dependabot_security_updates %} te facilitan el arreglar las dependencias vulnerables en tu repositorio. Si habilitas esta característica, cuando se levante una alerta del {% data variables.product.prodname_dependabot %} para una dependencia vulnerable en la gráfica de dependencias de tu repositorio, {% data variables.product.prodname_dependabot %} intentará arreglarla automáticamente. Para obtener más información, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". +## About {% data variables.product.prodname_dependabot_security_updates %} -{% data variables.product.prodname_dotcom %} podría enviar alertas del {% data variables.product.prodname_dependabot %} a los repositorios que se vieron afectados por la vulnerabilidad que se divulgó en una asesoría de seguridad de {% data variables.product.prodname_dotcom %} publicada recientemente. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#dependabot-alerts-for-published-security-advisories)". +{% data variables.product.prodname_dependabot_security_updates %} make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a {% data variables.product.prodname_dependabot %} alert is raised for a vulnerable dependency in the dependency graph of your repository, {% data variables.product.prodname_dependabot %} automatically tries to fix it. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +{% data variables.product.prodname_dotcom %} may send {% data variables.product.prodname_dependabot %} alerts to repositories affected by a vulnerability disclosed by a recently published {% data variables.product.prodname_dotcom %} security advisory. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% data variables.product.prodname_dependabot %} verifica si es posible actualizar la dependencia vulnerable a una versión arreglada sin irrumpir en la gráfica de dependencias para el repositorio. Posteriormente, el {% data variables.product.prodname_dependabot %} levanta una solicitud de cambios para actualizar la dependencia a la versión mínima que incluye el parche y los enlaces a la solicitud de cambios para la alerta del {% data variables.product.prodname_dependabot %}, o reporta un error en la alerta. Para obtener más información, consulta la sección "[Solucionar problemas para los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". +{% data variables.product.prodname_dependabot %} checks whether it's possible to upgrade the vulnerable dependency to a fixed version without disrupting the dependency graph for the repository. Then {% data variables.product.prodname_dependabot %} raises a pull request to update the dependency to the minimum version that includes the patch and links the pull request to the {% data variables.product.prodname_dependabot %} alert, or reports an error on the alert. For more information, see "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." {% note %} -**Nota** +**Note** -La característica de {% data variables.product.prodname_dependabot_security_updates %} se encuentra disponible para los repositorios en donde hayas habilitado la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %}. Verás una alerta del {% data variables.product.prodname_dependabot %} por cada dependencia vulnerable que se haya identificado en toda tu gráfica de dependencias. Sin embargo, las actualizaciones de seguridad se activan únicamente para las dependencias que se especifican en un archivo de manifiesto o de bloqueo. El {% data variables.product.prodname_dependabot %} no puede actualizar una dependencia indirecta o transitoria si no se define explícitamente. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)". +The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency that is not explicitly defined. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)." {% endnote %} -Puedes habilitar una característica relacionada, {% data variables.product.prodname_dependabot_version_updates %}, para que el {% data variables.product.prodname_dependabot %} levante solicitudes de cambio para actualizar el manifiesto a la última versión de la dependencia cuando detecte una que esté desactualizada. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)". +You can enable a related feature, {% data variables.product.prodname_dependabot_version_updates %}, so that {% data variables.product.prodname_dependabot %} raises pull requests to update the manifest to the latest version of the dependency, whenever it detects an outdated dependency. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)." {% data reusables.dependabot.pull-request-security-vs-version-updates %} -## Acerca de las solicitudes de cambios para las actualizaciones de seguridad +## About pull requests for security updates -Cada solicitud de cambios contiene todo lo que necesitas para revisar y fusionar de forma rápida y segura un arreglo propuesto en tu proyecto. Esto incluye la información acerca de la vulnerabilidad, como las notas de lanzamiento, las entradas de bitácora de cambios, y los detalles de confirmación. Los detalles de qué vulnerabilidad resuelve una solicitud de cambios se encuentran ocultos para cualquiera que no tenga acceso a las {% data variables.product.prodname_dependabot_alerts %} del repositorio en cuestión. +Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. This includes information about the vulnerability like release notes, changelog entries, and commit details. Details of which vulnerability a pull request resolves are hidden from anyone who does not have access to {% data variables.product.prodname_dependabot_alerts %} for the repository. -Cuando fusionas una solicitud de cambios que contiene una actualización de seguridad, la alerta correspondiente del {% data variables.product.prodname_dependabot %} se marca como resuelta en el repositorio. Para obtener más información acerca de las solicitudes de cambios del {% data variables.product.prodname_dependabot %}, consulta la sección "[Administrar las solicitudes de cambios para las actualizaciones de las dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)". +When you merge a pull request that contains a security update, the corresponding {% data variables.product.prodname_dependabot %} alert is marked as resolved for your repository. For more information about {% data variables.product.prodname_dependabot %} pull requests, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)." {% data reusables.dependabot.automated-tests-note %} -## Acerca de las puntuaciones de compatibilidad +{% ifversion fpt or ghec %} -Las {% data variables.product.prodname_dependabot_security_updates %} podrían incluir puntuaciones de compatibilidad para hacerte saber si el actualizar una dependencia podría causar cambios sustanciales en tu proyecto. Estos se calculan de las pruebas de IC en otros repositorios públicos en donde se ha generado la misma actualización de seguridad. La puntuación de compatibilidad de una actualización es el porcentaje de ejecuciones de IC que pasaron cuando se hicieron actualizaciones en versiones específicas de la dependencia. +## About compatibility scores -## Acerca de las notificaciones para las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} +{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. These are calculated from CI tests in other public repositories where the same security update has been generated. An update's compatibility score is the percentage of CI runs that passed when updating between specific versions of the dependency. -Puedes filtrar tus notificaciones en {% data variables.product.company_short %} para mostrar las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %}. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". +{% endif %} + +## About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md index bb0ef1b55d..ee0c826d03 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md @@ -1,6 +1,6 @@ --- -title: Acerca de la administración de dependencias vulnerables -intro: '{% data variables.product.product_name %} te ayuda a evitar el utilizar software de terceros que contenga vulnerabilidades conocidas.' +title: About managing vulnerable dependencies +intro: '{% data variables.product.product_name %} helps you to avoid using third-party software that contains known vulnerabilities.' redirect_from: - /github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies - /code-security/supply-chain-security/about-managing-vulnerable-dependencies @@ -18,29 +18,29 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Dependencias vulnerabiles +shortTitle: Vulnerable dependencies --- - -{% data variables.product.product_name %} te proporciona las siguientes herramientas para eliminar y evitar las dependencias vulnerables. +{% data variables.product.product_name %} provides the following tools for removing and avoiding vulnerable dependencies. -## Gráfica de dependencias -La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Te muestra los ecosistemas y paquetes de los cuales depende tu base de código (sus dependencias) y los repositorios y paquetes que dependen de tu proyecto (sus dependencias). Tanto la revisión de dependencias como el {% data variables.product.prodname_dependabot %} utilizan la información en la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +## Dependency graph +The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. +For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -## Revisión de dependencias +## Dependency review {% data reusables.dependency-review.beta %} -Si verificas las revisiones de dependencias en las solicitudes de cambios puedes evitar introducir las vulnerabilidades de las dependencias en tu base de código. Si las solicitudes de cambios agregan una dependencia vulnerable o cambian una dependencia a una versión vulnerable, esto se resaltará en la revisión de dependencias. Puedes cambiar la dependencia a una versión parchada antes de fusionar la solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)". +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." ## {% data variables.product.prodname_dependabot_alerts %} -{% data variables.product.product_name %} puede crear {% data variables.product.prodname_dependabot_alerts %} cuando detecta dependencias vulnerables en tu repositorio. La alerta se muestra en la pestaña de seguridad del repositorio. La alerta incluye un enlace al archivo afectado en el proyecto e información acerca de la versión arreglada. {% data variables.product.product_name %} también notifica a los mantenedores del repositorio, de acuerdo con sus preferencias de notificación. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". +{% data variables.product.product_name %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.2 %} ## {% data variables.product.prodname_dependabot_security_updates %} -Cuando {% data variables.product.product_name %} genera una alerta del {% data variables.product.prodname_dependabot %} para una dependencia vulnerable en tu repositorio, el {% data variables.product.prodname_dependabot %} puede intentar arreglarla automáticamente. las {% data variables.product.prodname_dependabot_security_updates %} son solicitudes de cambios que se generan automáticamente y que actualizan una dependencia vulnerable a una versión arreglada. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +When {% data variables.product.product_name %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." ## {% data variables.product.prodname_dependabot_version_updates %} -El habilitar las {% data variables.product.prodname_dependabot_version_updates %} hace que el mantener tus dependencias tome menos esfuerzo. Con las {% data variables.product.prodname_dependabot_version_updates %}, cada que {% data variables.product.prodname_dotcom %} identifique una dependencia desactualizada, levantará una solicitud de cambios para actualizar el manifiesto a la versión más reciente de la dependencia. Como contraste, las {% data variables.product.prodname_dependabot_security_updates %} solo levantan solicitudes de cambios para arreglar dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md index 7beab35fec..ab19259e3d 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md @@ -1,7 +1,7 @@ --- title: Configuring Dependabot security updates -intro: 'Puedes utilizar las {% data variables.product.prodname_dependabot_security_updates %} o las solicitudes de extracción manuales para actualizar fácilmente las dependencias vulnerables.' -shortTitle: Configurar las actualizaciones de seguridad +intro: 'You can use {% data variables.product.prodname_dependabot_security_updates %} or manual pull requests to easily update vulnerable dependencies.' +shortTitle: Configure security updates redirect_from: - /articles/configuring-automated-security-fixes - /github/managing-security-vulnerabilities/configuring-automated-security-fixes @@ -12,6 +12,7 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Dependabot @@ -21,55 +22,58 @@ topics: - Pull requests - Repositories --- - -## Acerca de la configuración de las {% data variables.product.prodname_dependabot_security_updates %} +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +## About configuring {% data variables.product.prodname_dependabot_security_updates %} -Puedes inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual o para todos los repositorios que pertenezcan a tu organización o cuenta de usuario. Para obtener más información, consulta la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-dependabot-security-updates-for-your-repositories)" acontinuación. +You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." -{% data reusables.dependabot.dependabot-tos %} +You can disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository or for all repositories owned by your user account or organization. For more information, see "[Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories](#managing-dependabot-security-updates-for-your-repositories)" below. -## Repositorios compatibles +{% ifversion fpt or ghec %}{% data reusables.dependabot.dependabot-tos %}{% endif %} -{% data variables.product.prodname_dotcom %} habilita las {% data variables.product.prodname_dependabot_security_updates %} automáticamente para cada repositorio que cumpla con estos pre-requisitos. +## Supported repositories + +{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites. {% note %} -**Nota**: Puedes habilitar manualmente las {% data variables.product.prodname_dependabot_security_updates %}, aún si el repositorio no cumple con alguno de los siguientes prerrequisitos. Por ejemplo, puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} en una bifurcación, o para un administrador de paquetes que no sea directamente compatible si sigues las instrucciones en la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-dependabot-security-updates-for-your-repositories)". +**Note**: You can manually enable {% data variables.product.prodname_dependabot_security_updates %}, even if the repository doesn't meet some of the prerequisites below. For example, you can enable {% data variables.product.prodname_dependabot_security_updates %} on a fork, or for a package manager that isn't directly supported by following the instructions in "[Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories](#managing-dependabot-security-updates-for-your-repositories)." {% endnote %} -| Pre-requisito de habilitación automática | Más información | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Que el repositorio no sea una bifrucación | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" | -| Que el repositorio no esté archivado | "[Archivar repositorios](/github/creating-cloning-and-archiving-repositories/archiving-repositories)" | -| Que el repositorio sea público, o que sea privado y hayas habilitado un análisis de solo lectura por {% data variables.product.prodname_dotcom %}, gráfica de dependencias y alertas de vulnerabilidades en la configuración del mismo | "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". | -| Que el repositorio contenga un archivo de manifiesto de dependencias de un ecosistema de paquete que sea compatible con {% data variables.product.prodname_dotcom %} | "[Ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" | -| Las {% data variables.product.prodname_dependabot_security_updates %} no se han inhabilitado para el repositorio | "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tu repositorio](#managing-dependabot-security-updates-for-your-repositories)" | -| Que el repositorio no esté utilizando ya una integración para administración de dependencias | "[Acerca de las integraciones](/github/customizing-your-github-workflow/about-integrations)" | +| Automatic enablement prerequisite | More information | +| ----------------- | ----------------------- | +| Repository is not a fork | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Repository is not archived | "[Archiving repositories](/github/creating-cloning-and-archiving-repositories/archiving-repositories)" |{% ifversion fpt or ghec %} +| Repository is public, or repository is private and you have enabled read-only analysis by {% data variables.product.prodname_dotcom %}, dependency graph, and vulnerability alerts in the repository's settings | "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." |{% endif %} +| Repository contains dependency manifest file from a package ecosystem that {% data variables.product.prodname_dotcom %} supports | "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" | +| {% data variables.product.prodname_dependabot_security_updates %} are not disabled for the repository | "[Managing {% data variables.product.prodname_dependabot_security_updates %} for your repository](#managing-dependabot-security-updates-for-your-repositories)" | -Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sabes por qué, intenta primero habilitarles de acuerdo con las instrucciones que se encuentran en los procedimientos siguientes. Si las actualizaciones aún no funcionan, puedes [contactar a soporte](https://support.github.com/contact?tags=docs-security). +If security updates are not enabled for your repository and you don't know why, first try enabling them using the instructions given in the procedural sections below. If security updates are still not working, you can contact {% data variables.contact.contact_support %}. -## Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios +## Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories -Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual (ver a continuación). +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). -También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -Las {% data variables.product.prodname_dependabot_security_updates %} requieren de configuraciones de repositorio específicas. Para obtener más información, consulta "[Repositorios soportados](#supported-repositories)". +{% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." -### Habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual. +### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -1. Debajo de "Configurar las características de seguridad y análisis", a la derecha de "actualizaciones de seguridad del {% data variables.product.prodname_dependabot %}", da clic en **Habilitar** o **Inhabilitar**. ![Sección "Configurar las características de seguridad y análisis" con botón para habilitar las {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. + {% ifversion fpt or ghec %}!["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png){% else %}!["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} -## Leer más -- "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". -- "[Ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" +## Further reading + +- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec %} +- "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"{% endif %} +- "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md index 04818cc432..6d2de3a534 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md @@ -1,7 +1,7 @@ --- -title: Solucionar problemas de los errores del Dependabot -intro: 'Algunas veces, el {% data variables.product.prodname_dependabot %} no puede levantar solicitudes de cambios para actualizar tus dependencias. Puedes revisar el error y desbloquear al {% data variables.product.prodname_dependabot %}.' -shortTitle: Solución de errores +title: Troubleshooting Dependabot errors +intro: 'Sometimes {% data variables.product.prodname_dependabot %} is unable to raise a pull request to update your dependencies. You can review the error and unblock {% data variables.product.prodname_dependabot %}.' +shortTitle: Troubleshoot errors redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors - /github/managing-security-vulnerabilities/troubleshooting-dependabot-errors @@ -9,6 +9,7 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '>3.2' type: how_to topics: - Dependabot @@ -21,90 +22,108 @@ topics: - Dependencies --- -## Acerca de los errores del {% data variables.product.prodname_dependabot %} +{% data reusables.dependabot.beta-security-and-version-updates %} + +{% data reusables.dependabot.enterprise-enable-dependabot %} + +## About {% data variables.product.prodname_dependabot %} errors {% data reusables.dependabot.pull-request-introduction %} -Si existe algo que impida que el {% data variables.product.prodname_dependabot %} levante una solicitud de cambios, esto se reporta como un error. +If anything prevents {% data variables.product.prodname_dependabot %} from raising a pull request, this is reported as an error. -## Investigar los errores de las {% data variables.product.prodname_dependabot_security_updates %} +## Investigating errors with {% data variables.product.prodname_dependabot_security_updates %} -Cuando se bloquea al {% data variables.product.prodname_dependabot %} y no puede crear una solicitud de cambios para arreglar una alerta del {% data variables.product.prodname_dependabot %}, éste publica el mensaje de error en la alerta. La vista de {% data variables.product.prodname_dependabot_alerts %} muestra una lista de cualquier alerta que aún no se haya resuelto. Para acceder a la vista de alertas, da clic en **{% data variables.product.prodname_dependabot_alerts %}** en la pestaña de **Seguridad** del repositorio. Donde sea que se genere una solicitud de cambios que arregle una dependencia vulnerable, la alerta incluirá un enlace a dicha solicitud. +When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to fix a {% data variables.product.prodname_dependabot %} alert, it posts the error message on the alert. The {% data variables.product.prodname_dependabot_alerts %} view shows a list of any alerts that have not been resolved yet. To access the alerts view, click **{% data variables.product.prodname_dependabot_alerts %}** on the **Security** tab for the repository. Where a pull request that will fix the vulnerable dependency has been generated, the alert includes a link to that pull request. -![Vista de las {% data variables.product.prodname_dependabot_alerts %} que muestra un enlace a una solicitud de cambios](/assets/images/help/dependabot/dependabot-alert-pr-link.png) +![{% data variables.product.prodname_dependabot_alerts %} view showing a pull request link](/assets/images/help/dependabot/dependabot-alert-pr-link.png) -Hay tres razones por las cuales una alerta pudiera no tener un enlace a una solicitud de cambios: +There are three reasons why an alert may have no pull request link: -1. No se han habilitado las {% data variables.product.prodname_dependabot_security_updates %} en el repositorio. -1. La alerta es para una dependencia transitoria o indirecta que no se definió explícitamente en un archivo de bloqueo. -1. Un error bloqueó al {% data variables.product.prodname_dependabot %} y éste no puede crear una solicitud de cambios. +1. {% data variables.product.prodname_dependabot_security_updates %} are not enabled for the repository. +1. The alert is for an indirect or transitive dependency that is not explicitly defined in a lock file. +1. An error blocked {% data variables.product.prodname_dependabot %} from creating a pull request. -Si existe un error que bloqueó al {% data variables.product.prodname_dependabot %} y éste no puede crear una solicitud de cambios, puedes mostrar los detalles del error si das clic en la alerta. +If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert. -![Alerta del {% data variables.product.prodname_dependabot %} que mustra el error que bloqueó la creación de una solicitud de cambios](/assets/images/help/dependabot/dependabot-security-update-error.png) +![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) -## Investigar los errores de las {% data variables.product.prodname_dependabot_version_updates %} +## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %} -Cuando el {% data variables.product.prodname_dependabot %} se bloquea y no puede crear una solicitud de cambios para actualizar una dependencia en un ecosistema, éste publica el icono de error en el archivo de manifiesto. Los archivos de manifiesto que administra el {% data variables.product.prodname_dependabot %} se listan en la pestaña de {% data variables.product.prodname_dependabot %}. Para acceder a esta pestaña, en la pestaña de **perspectivas** del repositorio, da clic en **Gráfica de dependencias**, y luego en la pestaña **{% data variables.product.prodname_dependabot %}**. +When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab. -![vista del {% data variables.product.prodname_dependabot %} que muestra un error](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png) +![{% data variables.product.prodname_dependabot %} view showing an error](/assets/images/help/dependabot/dependabot-tab-view-error.png) -Para ver el archivo de bitácora de cualquier archivo de manifiesto, da clic en el enlace de **Última revisión hace TIEMPO**. Cuando muestras el archivo de bitácora de un manifiesto que se muestra con un símbolo de error (por ejemplo, Maven en la impresión de pantalla anterior), cualquier error se mostrará también. +{% ifversion fpt or ghec %} -![Error y bitácora de una actualizacón de versión del {% data variables.product.prodname_dependabot %} ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png) +To see the log file for any manifest file, click the **Last checked TIME ago** link. When you display the log file for a manifest that's shown with an error symbol (for example, Maven in the screenshot above), any errors are also displayed. -## Entender los errores del {% data variables.product.prodname_dependabot %} +![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/help/dependabot/dependabot-version-update-error.png) -Las solicitudes de cambios para las actualizaciones de seguridad actúan para mejorar una dependencia vulnerable a la versión mínima que incluya un arreglo de la vulnerabilidad. Por el contrario, las solicitudes de cambios para las actualizaciones de versión actúan para mejorar una dependencia a la última versión que permite el paquete de archivos de manifiesto y de configuración del {% data variables.product.prodname_dependabot %}. Como consecuencia, algunos errores son específicos de un tipo de actualización. +{% else %} -### El {% data variables.product.prodname_dependabot %} no puede actualizar la DEPENDENCIA a una versión no-vulnerable +To see the logs for any manifest file, click the **Last checked TIME ago** link, and then click **View logs**. -**Únicamente actualizaciones de seguridad.** El {% data variables.product.prodname_dependabot %} no puede crear una solicitud de cambios para actualizar la dependencia vulnerable a una versión segura sin afectar otras dependencias en la gráfica de dependencias de este repositorio. +![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/enterprise/3.3/dependabot/dependabot-version-update-error.png) -Cada aplicación que tenga dependencias tiene una gráfica de dependencias, esto es, una gráfica acíclica dirigida de cada versión de paquete de la cual depende la aplicación directa o indirectamente. Cada vez que se actualiza una dependencia, esta gráfica debe resolverse o la aplicación no se compilará. Cuando un ecosistema tiene una gráfica de dependencias profunda y compleja, por ejemplo, npm y RubyGems, es a menudo imposible mejorar una sola dependencia sin mejorar todo el ecosistema. +{% endif %} -La mejor forma de evitar este problema es mantenerse actualizado con los lanzamientos de versiones más recientes, por ejemplo, habilitando las actualizaciones de versión. Esto aumenta la probabilidad de que una vulnerabilidad en alguna dependencia pueda resolverse con una mejora simple que no afecte la gráfica de dependencias. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". +## Understanding {% data variables.product.prodname_dependabot %} errors -### El {% data variables.product.prodname_dependabot %} no puede actualizar a la versión requerida porque ya existe una solicitud de cambios abierta para la última versión +Pull requests for security updates act to upgrade a vulnerable dependency to the minimum version that includes a fix for the vulnerability. In contrast, pull requests for version updates act to upgrade a dependency to the latest version allowed by the package manifest and {% data variables.product.prodname_dependabot %} configuration files. Consequently, some errors are specific to one type of update. -**Únicamente actualizaciones de seguridad.** El {% data variables.product.prodname_dependabot %}no creará una solicitud de cambios para actualizar la dependencia vulnerable a una versión segura porque ya existe una solicitud de cambios abierta para actualizar dicha dependencia. Verás éste error cuando se detecte una vulnerabilidad en una dependencia específica y ya exista una solicitud de cambios abierta para actualizar dicha dependencia a la última versión disponible. +### {% data variables.product.prodname_dependabot %} cannot update DEPENDENCY to a non-vulnerable version -Existen dos opciones: puedes revisar la solicitud de cambios abierta y fusionarla tan pronto como puedas garantizar que el cambio es seguro, o cerrar la solicitud de cambios y activar una solicitud nueva de actualización de seguridad. Para obtener más información, consulta la sección "[Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". +**Security updates only.** {% data variables.product.prodname_dependabot %} cannot create a pull request to update the vulnerable dependency to a secure version without breaking other dependencies in the dependency graph for this repository. -### El {% data variables.product.prodname_dependabot %} agotó el tiempo de espera durante su actualización +Every application that has dependencies has a dependency graph, that is, a directed acyclic graph of every package version that the application directly or indirectly depends on. Every time a dependency is updated, this graph must resolve otherwise the application won't build. When an ecosystem has a deep and complex dependency graph, for example, npm and RubyGems, it is often impossible to upgrade a single dependency without upgrading the whole ecosystem. -El {% data variables.product.prodname_dependabot %} tardó más del límite de tiempo máximo permitido para valorar la actualización requerida y preparar una solicitud de cambios. Este error a menudo se ve únicamente en los repositorios grandes con muchos archivos de manifiesto, por ejemplo, en los proyectos de npm o yarn monorepo, que tienen cientos de archivos *package.json*. Las actualizaciones en el ecosistema de Composer también llevan más tiempo para su valoración y podrían exceder el tiempo de espera. +The best way to avoid this problem is to stay up to date with the most recently released versions, for example, by enabling version updates. This increases the likelihood that a vulnerability in one dependency can be resolved by a simple upgrade that doesn't break the dependency graph. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." -Es difícil tratar a este error. Si una actualización de versión excede el tiempo de espera, podrías especificar las dependencias más importantes a actualizar utilizando el parámetro `allow` o, como alternativa, utilizar el parámetro `ignore` para excluir algunas de las dependencias de estas actualizaciones. El actualizar tu configuración podría permitir que el {% data variables.product.prodname_dependabot %} revise la actualización de versión y genere la solicitud de cambios en el tiempo disponible. +### {% data variables.product.prodname_dependabot %} cannot update to the required version as there is already an open pull request for the latest version -Si una actualización de seguridad excede el tiempo de espera, puedes reducir la probabilidad de que esto suceda si mantienes las dependencias actualizadas, por ejemplo, habilitando las actualizaciones de versión. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". +**Security updates only.** {% data variables.product.prodname_dependabot %} will not create a pull request to update the vulnerable dependency to a secure version because there is already an open pull request to update this dependency. You will see this error when a vulnerability is detected in a single dependency and there's already an open pull request to update the dependency to the latest version. -### El {% data variables.product.prodname_dependabot %} no puede abrir más solicitudes de cambios +There are two options: you can review the open pull request and merge it as soon as you are confident that the change is safe, or close that pull request and trigger a new security update pull request. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)." -Hay un límite en la cantidad de solicitudes de cambios abiertas que el {% data variables.product.prodname_dependabot %} puede generar. Cuando se llega a éste límite, no se podrán abrir más solicitudes de cambios y se reportará este error. La mejor forma de resolver este error es revisar y fusionar algunas de las solicitudes de cambios abiertas. +### {% data variables.product.prodname_dependabot %} timed out during its update -Hay límites separados para las solicitudes de cambios de actualización de seguridad y de versión, y esto es para que aquellas de actualización de versión no bloqueen la creación de las de actualización de seguridad. El límite para las solicitudes de cambios de actualizaciones de seguridad es de 10. Predeterminadamente, el límite para las actualizaciones de versión es de 5, pero puedes cambiar ésto utilizando el parámetro `open-pull-requests-limit` en el archivo de configuración. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)". +{% data variables.product.prodname_dependabot %} took longer than the maximum time allowed to assess the update required and prepare a pull request. This error is usually seen only for large repositories with many manifest files, for example, npm or yarn monorepo projects with hundreds of *package.json* files. Updates to the Composer ecosystem also take longer to assess and may time out. -La mejor forma de resolver este error es fusionar o cerrar algunas de las solicitudes de cambios existentes y activar una solicitud de cambios nueva manualmente. Para obtener más información, consulta la sección "[Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". +This error is difficult to address. If a version update times out, you could specify the most important dependencies to update using the `allow` parameter or, alternatively, use the `ignore` parameter to exclude some dependencies from updates. Updating your configuration might allow {% data variables.product.prodname_dependabot %} to review the version update and generate the pull request in the time available. -### El {% data variables.product.prodname_dependabot %} no puede resolver o acceder a tus dependencias +If a security update times out, you can reduce the chances of this happening by keeping the dependencies updated, for example, by enabling version updates. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." -Si el {% data variables.product.prodname_dependabot %} intenta verificar si las referencias de la dependencia necesitan actualizarse en un repositorio, pero no puede acceder a uno o más de los archivos referenciados, la operación fallará con el mensaje de error "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". El tipo de error de la API es `git_dependencies_not_reachable`. +### {% data variables.product.prodname_dependabot %} cannot open any more pull requests -De forma similar, si el {% data variables.product.prodname_dependabot %} no puede acceder a un registro de un paquete privado en el cual se ubica la dependencia, se generará alguno de los siguientes errores: +There's a limit on the number of open pull requests {% data variables.product.prodname_dependabot %} will generate. When this limit is reached, no new pull requests are opened and this error is reported. The best way to resolve this error is to review and merge some of the open pull requests. -* "El dependabot no puede llegar a la dependencia en un registro de paquete privado"
    (Tipo de error de la API: `private_source_not_reachable`) -* "El Dependabot no puede autenticarse en un registro de paquete privado"
    (Tipo de error de la API:`private_source_authentication_failure`) -* "El Dependabot llegó al límite de tiempo de espera para un registro de paquete privado"
    (Tipo de error de la API:`private_source_timed_out`) -* "El Dependabot no pudo validar el certificado para un registro de paquete privado"
    (Tipo de error de la API:`private_source_certificate_failure`) +There are separate limits for security and version update pull requests, so that open version update pull requests cannot block the creation of a security update pull request. The limit for security update pull requests is 10. By default, the limit for version updates is 5 but you can change this using the `open-pull-requests-limit` parameter in the configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)." -Para permitir añ {% data variables.product.prodname_dependabot %} actualizar las referencias de dependencia exitosamente, asegúrate que todas las dependencias referencias se hospeden en ubicaciones accesibles. +The best way to resolve this error is to merge or close some of the existing pull requests and trigger a new pull request manually. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)." -**Únicamente actualizaciones de versión** {% data reusables.dependabot.private-dependencies-note %} Adicionalmente, el {% data variables.product.prodname_dependabot %} no es compatible con dependencias de {% data variables.product.prodname_dotcom %} privadas para todos los administradores de paquetes. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". +### {% data variables.product.prodname_dependabot %} can't resolve or access your dependencies -## Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. -Si desbloqueas al {% data variables.product.prodname_dependabot %}, puedes activar manualmente un nuevo intento de crear una solicitud de cambios. +Similarly, if {% data variables.product.prodname_dependabot %} can't access a private package registry in which a dependency is located, one of the following errors is generated: -- **Actualizaciones de seguridad**—muestra la alerta del {% data variables.product.prodname_dependabot %} que presente el error que arreglaste y da clic en **Crear una actualización de seguridad del {% data variables.product.prodname_dependabot %}**. -- **Actualizaciones de versión**—en la pestaña de **Perspectivas** del repositorio, da clic en **Gráfica de dependencias** y luego en la pestaña de **Dependabot**. Da clic en **Verificado hace *TIME*** para ver el archivo de bitácora que generó el {% data variables.product.prodname_dependabot %} durante la última verificación de actualizaciones de versión. Da clic en **Verificar actualizaciones**. +* "Dependabot can't reach a dependency in a private package registry"
    + (API error type: `private_source_not_reachable`) +* "Dependabot can't authenticate to a private package registry"
    + (API error type:`private_source_authentication_failure`) +* "Dependabot timed out while waiting for a private package registry"
    + (API error type:`private_source_timed_out`) +* "Dependabot couldn't validate the certificate for a private package registry"
    + (API error type:`private_source_certificate_failure`) + +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." + +## Triggering a {% data variables.product.prodname_dependabot %} pull request manually + +If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. + +- **Security updates**—display the {% data variables.product.prodname_dependabot %} alert that shows the error you have fixed and click **Create {% data variables.product.prodname_dependabot %} security update**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 3265a20067..b03339863e 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -1,7 +1,7 @@ --- -title: Solucionar problemas en la detección de dependencias vulnerables -intro: 'Si la información de la dependencia que reportó {% data variables.product.product_name %} no es lo que esperabas, hay varios puntos a considerar y varias cosas que puedes revisar.' -shortTitle: Detección de soluciones de problemas +title: Troubleshooting the detection of vulnerable dependencies +intro: 'If the dependency information reported by {% data variables.product.product_name %} is not what you expected, there are a number of points to consider, and various things you can check.' +shortTitle: Troubleshoot detection redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies - /code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies @@ -25,98 +25,100 @@ topics: - Repositories --- -Los resultados de la detección de dependencias que reporta {% data variables.product.product_name %} pueden ser diferentes a aquellos que devuelven otras herramientas. Esto está justificado y es útil el entender cómo {% data variables.product.prodname_dotcom %} determina las dependencias para tu proyecto. +{% data reusables.dependabot.beta-security-and-version-updates %} -## ¿Por qué parece que faltan algunas dependencias? +The results of dependency detection reported by {% data variables.product.product_name %} may be different from the results returned by other tools. There are good reasons for this and it's helpful to understand how {% data variables.product.prodname_dotcom %} determines dependencies for your project. -{% data variables.product.prodname_dotcom %} genera y muestra los datos de las dependencias de forma diferente a otras herramientas. En consecuencia, si has estado utilizando otra herramienta para identificar dependencias, muy probablemente encuentres resultados diferentes. Considera lo sigueinte: +## Why do some dependencies seem to be missing? -* {% data variables.product.prodname_advisory_database %} es una de las fuentes de datos que utiliza {% data variables.product.prodname_dotcom %} para identificar las dependencias vulnerables. Es una base de datos de información de vulnerabilidades orgtanizada y gratuita para los ecosistemas de paquetes comunes en {% data variables.product.prodname_dotcom %}. Esta incluye tanto los datos reportados directamente a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_security_advisories %}, así como las fuentes oficiales y las comunitarias. {% data variables.product.prodname_dotcom %} revisa y organiza estos datos para garantizar que la información falsa o inprocesable no se comparta con la comunidad de desarrollo. {% data reusables.security-advisory.link-browsing-advisory-db %} -* La gráfica de dependencias analiza todos los archivos de manifiesto de paquetes conocidos en un repositorio de usuario. Por ejemplo, para npm analizará el archivo _package-lock.json_. Construye una gráfica de todas las dependencias del repositorio y de los dependientes públicos. Esto sucede cuando habilitas la gráfica de dependencias y cuando alguien hace cargas a la rama predeterminada, y esto incluye a las confirmaciones que hacen cambios a un formato de manifiesto compatible. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". -* {% data variables.product.prodname_dependabot %} escanea cualquier subida a la rama predeterminada que contenga un archivo de manifiesto. Cuando se agrega un registro de vulnerabilidad nuevo, este escanea todos los repositorios existentes y genera una alerta para cada repositorio vulnerable. Las {% data variables.product.prodname_dependabot_alerts %} se agregan a nivel del repositorio, en vez de crear una alerta por cada vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". -* {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot_security_updates %} se activa cuando recibes una alerta sobre una dependencia vulnerable en tu repositorio. Cuando sea posible, el {% data variables.product.prodname_dependabot %} creará una solicitud de cambios en tu repositorio para actualizar la dependencia vulnerable a la versión segura mínima posible que se requiere para evitar la vulnerabilidad. Para obtener más información, consulta las secciones "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" y "[Solucionar problemas en los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". +{% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following: - {% endif %}El {% data variables.product.prodname_dependabot %} no escanea los repositorios para encontrar dependencias vulnerables en horarios específicos, sino cuando algo cambia. Por ejemplo, se activará un escaneo cuando se agregue una dependencia nueva ({% data variables.product.prodname_dotcom %} verifica esto en cada subida) o cuando se agrega una vulnerabilidad a la base de datos de las asesorías {% ifversion ghes or ghae-issue-4864 %} y se sincroniza con {% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". +* {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %} +* The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +* {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +* {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." + + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." -## ¿Por qué no me llegan alertas de vulnerabilidades de algunos ecosistemas? +## Why don't I get vulnerability alerts for some ecosystems? -{% data variables.product.prodname_dotcom %} limita su soporte para alertas de vulnerabilidades a un conjunto de ecosistemas donde podemos proporcionar datos procesables de alta calidad. Las vulnerabilidades que se seleccionan para la{% data variables.product.prodname_advisory_database %}, la gráfica de dependencias, {% ifversion fpt or ghec %} las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} {% endif %}y las alertas del {% data variables.product.prodname_dependabot %}, se proporcionan para varios ecosistemas, incluyendo Maven de java, npm y Yarn de JavaScript, NuGet de .NET, pip de Python, RubyGems de Ruby y Composer de PHP. Seguiremos agregando soporte para más ecosistemas a la larga. Para obtener una vista general de los ecosistemas de paquete que soportamos, consulta la sección "[Acerca del gráfico de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot %} alerts are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." -No vale de nada que las Asesorías de Seguridad de {% data variables.product.prodname_dotcom %} pudiese existir para otros ecosistemas. La información en una asesoría de seguridad la porporcionan los mantenedores de un repositorio específico. Estos datos no se organizan de la misma forma que la información para los ecosistemas compatibles. {% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %} +It's worth noting that {% data variables.product.prodname_dotcom %} Security Advisories may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems. {% ifversion fpt or ghec %}For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %} -**Verifica**: ¿Acaso la vulnerabilidad que no se detectó aplica a algún ecosistema no compatible? +**Check**: Does the uncaught vulnerability apply to an unsupported ecosystem? -## ¿Acaso la gráfica de dependencias solo encuentra depedencias en los manifiestos y lockfiles? +## Does the dependency graph only find dependencies in manifests and lockfiles? -La gráfica de dependencias incluye información sobre las dependencias, la cual se declara explícitamente en tu ambiente. Esto es, dependencias que se especifican en un manifiesto o en un lockfile. La gráfica de dependencias también incluye dependencias transitivas generalmente, aún cuando no se especifican en un lockfile, mediante la revisión de las dependencias de las dependencias en un archivo de manifiesto. +The dependency graph includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file. -Las {% data variables.product.prodname_dependabot_alerts %} te asesoran sobre las dependencias que debes actualizar, incluyendo aquellas transitivas en donde la versión se puede determinar desde un manifiesto o lockfile. {% ifversion fpt or ghec %}Las {% data variables.product.prodname_dependabot_security_updates %} solo sugieren un cambio donde el {% data variables.product.prodname_dependabot %} pueda "arreglar" la dependencia directamente, es decir, cuando estas son: -* Dependencias directas declaradas explícitamente en un manifiesto o lockfile -* Dependencias transitorias declaradas en un archivo de bloqueo{% endif %} +{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are: +* Direct dependencies explicitly declared in a manifest or lockfile +* Transitive dependencies declared in a lockfile{% endif %} -The dependency graph doesn't include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile. +The dependency graph doesn't include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile. -**Verifica**; ¿Acaso no se especifica la vulnerabilidad no detectada para un componente en el manifiesto o lockfile del repositorio? +**Check**: Is the uncaught vulnerability for a component that's not specified in the repository's manifest or lockfile? -## ¿Acaso la gráfica de dependencias detecta dependencias que se especifican utilizando variables? +## Does the dependency graph detect dependencies specified using variables? -La gráfica de dependencias analiza los manifiestos mientras se suben a {% data variables.product.prodname_dotcom %}. Por lo tanto, la gráfica de dependencias no tiene acceso al ambiente de compilación del proyecto, así que no puede resolver variables que se utilizan dentro de los manifiestos. Si utilizas variables dentro de un manifiesto para especificar el nombre, o más comunmente la versión de una dependencia, entonces dicha dependencia no se incluirá en la gráfica de dependencias. +The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not be included in the dependency graph. -**Verifica**: ¿Acaso la dependencia faltante se declara en el manifiesto utilizando una variable para su nombre o versión? +**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version? -## ¿Existen límites que afecten los datos de la gráfica de dependencias? +## Are there limits which affect the dependency graph data? -Sí, la gráfica de dependencias tiene dos categorías de límites: +Yes, the dependency graph has two categories of limits: -1. **Límites de procesamiento** +1. **Processing limits** - Estos afectan la gráfica de dependencias que se muestra dentro de {% data variables.product.prodname_dotcom %} y también previenen la creación de {% data variables.product.prodname_dependabot_alerts %}. + These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created. - Los manifiestos mayores a 0.5 MB solo se procesan para las cuentas empresariales. En el caso de otras cuentas, los manifiestos mayores a 0.5 MB se ingoran y no crearán {% data variables.product.prodname_dependabot_alerts %}. + Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}. - Predeterminadamente, {% data variables.product.prodname_dotcom %} no procesará más de 20 manifiestos por repositorio. Las {% data variables.product.prodname_dependabot_alerts %} no se crean para los manifiestos más allá de este límite. Si necesitas incrementar el límite, contacta a {% data variables.contact.contact_support %}. + By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. -2. **Límites de visualización** +2. **Visualization limits** - Estos afectan a lo que se muestra en la gráfica de dependencias dentro de {% data variables.product.prodname_dotcom %}. Sin embargo, estos no afectan las {% data variables.product.prodname_dependabot_alerts %} que se crean. + These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created. - La vista de dependencias de la gráfica de dependencias para un repositorio solo muestra 1000 manifiestos. Habitualmente, esto es tan adecuado como es significativamente más alto que el límite de procesamiento descrito anteriormente. En situaciones en donde le límite de procesamiento es mayor a 100, las {% data variables.product.prodname_dependabot_alerts %} se crearán aún para cualquier manifiesto que no se muestre dentro de {% data variables.product.prodname_dotcom %}. + The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}. -**Verifica**: ¿La dependencia faltante está en un archivo de manifiesto que tiene más de 0.5 MB, o en un repositorio con una gran cantidad de manifiesto? +**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests? -## ¿Acaso el {% data variables.product.prodname_dependabot %} genera alertas para vulnerabilidades que se han conocido por muchos años? +## Does {% data variables.product.prodname_dependabot %} generate alerts for vulnerabilities that have been known for many years? -La {% data variables.product.prodname_advisory_database %} se lanzó en noviembre de 2019 e incialmente rellenó la inclusión de vulnerabilidades informáticas para los ecosistemas compatibles, comenzando en 2017. Cuando agregas CVE a la base de datos, priorizamos la organización de CVE nuevos y los CVE que afecten las versiones nuevas del software. +The {% data variables.product.prodname_advisory_database %} was launched in November 2019, and initially back-filled to include vulnerability information for the supported ecosystems, starting from 2017. When adding CVEs to the database, we prioritize curating newer CVEs, and CVEs affecting newer versions of software. -Alguna información sobre las vulnerabilidades antiguas se encuentra disponible, especialmente en donde estos CVE se diseminan específicamente, sin embargo, algunas vulnerabilidades no se incluyen en la {% data variables.product.prodname_advisory_database %}. Si hay una vulnerabilidad antigua específica la cual necesites incluir en la base de datos, contacta a {% data variables.contact.contact_support %}. +Some information on older vulnerabilities is available, especially where these CVEs are particularly widespread, however some old vulnerabilities are not included in the {% data variables.product.prodname_advisory_database %}. If there's a specific old vulnerability that you need to be included in the database, contact {% data variables.contact.contact_support %}. -**Verifica**: ¿Acaso la vulnerabilidad no detectada tiene una fecha depublicación más antigua de 2017 en la Base de Datos de Vulnerabilidades Nacional? +**Check**: Does the uncaught vulnerability have a publish date earlier than 2017 in the National Vulnerability Database? -## Por qué la {% data variables.product.prodname_advisory_database %} utiliza un subconjunto de datos de vulnerabilidades publicados? +## Why does {% data variables.product.prodname_advisory_database %} use a subset of published vulnerability data? -Algunas herramientas de terceros utilizan datos de CVE sin organizar y no las verificó ni filtró un humano. Esto significa que los CVE con errores de etiquetado o de severidad, o con cualquier problema de calidad, causarán alertas más frecuentes, ruidosas y menos útiles. +Some third-party tools use uncurated CVE data that isn't checked or filtered by a human. This means that CVEs with tagging or severity errors, or other quality issues, will cause more frequent, more noisy, and less useful alerts. -Ya que {% data variables.product.prodname_dependabot %} utiliza datos organizado en la {% data variables.product.prodname_advisory_database %}, la cantidad de alertas podría ser menor, pero las alertas que sí recibas serán exactas y relevantes. +Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant. {% ifversion fpt or ghec %} -## ¿Acaso cada vulnerabilidad de la dependencia genera una alerta separada? +## Does each dependency vulnerability generate a separate alert? -Cuadno una dependencia tiene vulnerabilidades múltiples, solo se genera una alerta agregada para esta dependencia en vez de una por cada vulnerabilidad. +When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability. -Las {% data variables.product.prodname_dependabot_alerts %} cuentan en {% data variables.product.prodname_dotcom %} y muestran un total para la cantidad de alertas, es decir, la cantidad de dependencias con vulnerabilidades y no la cantidad de vulnerabilidades. +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities. -![Vista de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-view.png) +![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png) -Cuando das clic para mostrar los detalles de la alerta puedes ver cuántas vulnerabilidades se incluyen en la misma. +When you click to display the alert details, you can see how many vulnerabilities are included in the alert. -![Vulnerabilidades múltiples para una alerta de {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png) +![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png) -**Verifica**: Si hay una discrepancia en la cantidad total que ves, verifica si no estás comparando la cantidad de alertas con la cantidad de vulnerabilidades. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers. {% endif %} -## Leer más +## Further reading -- "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Administrar la configuración de seguridad y análisis de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% ifversion fpt or ghec %} -- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} +- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index fcb1f3d6c7..2d6aa9f46c 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -1,12 +1,12 @@ --- -title: Ver y actualizar dependencias vulnerables en tu repositorio -intro: 'Si {% data variables.product.product_name %} descubre una dependencia vulnerable en tu proyecto, podrás verla en la pestaña de alertas del Dependabot de tu repositorio. Posteriormente, podrás actualizar tu proyecto para resolver o descartar la vulnerabilidad.' +title: Viewing and updating vulnerable dependencies in your repository +intro: 'If {% data variables.product.product_name %} discovers vulnerable dependencies in your project, you can view them on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the vulnerability.' redirect_from: - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository permissions: Repository administrators and organization owners can view and update dependencies. -shortTitle: Ver las dependencias vulnerables +shortTitle: View vulnerable dependencies versions: fpt: '*' ghes: '*' @@ -22,51 +22,63 @@ topics: - Repositories --- -La pestaña de alertas del {% data variables.product.prodname_dependabot %} de tu repositorio lista todas las {% data variables.product.prodname_dependabot_alerts %} abiertas y cerradas{% ifversion fpt or ghec %} y las {% data variables.product.prodname_dependabot_security_updates %} correspondientes{% endif %}. Puedes clasificar la lista de alertas si seleccionas el menú desplegable y haces clic en alertas específicas para obtener más detalles. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -{% ifversion fpt or ghec %} -Puedes habilitar las alertas de seguridad automáticas para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." + +{% ifversion fpt or ghec or ghes > 3.2 %} +You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." +{% endif %} {% data reusables.repositories.dependency-review %} -## Acerca de las actualizaciones para las dependencias vulnerables en tu repositorio +{% ifversion fpt or ghec or ghes > 3.2 %} +## About updates for vulnerable dependencies in your repository -{% data variables.product.product_name %} genera {% data variables.product.prodname_dependabot_alerts %} cuando detectamos que tu base de código está utilizando dependencias con vulnerabilidades conocidas. Para los repositorios en donde se habilitan las {% data variables.product.prodname_dependabot_security_updates %} cuando {% data variables.product.product_name %} detecta una dependencia vulnerable en la rama predeterminada, {% data variables.product.prodname_dependabot %} crea una solicitud de cambios para arreglarla. La solicitud de extracción mejorará la dependencia a la versión segura mínima que sea posible y necesaria para evitar la vulnerabilidad. +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. {% endif %} -## Ver y actualizar las dependencias vulnerables +## Viewing and updating vulnerable dependencies -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.2 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} -1. Haz clic en la alerta que quieres ver. ![Alerta seleccionada en la lista de alertas](/assets/images/help/graphs/click-alert-in-alerts-list.png) -1. Revisa los detalles de la vulnerabilidad y, en caso de que esté disponible, la solicitud de extracción que contienen la actualización de seguridad automatizada. -1. Opcionalmente, si no existe ya una actualización de {% data variables.product.prodname_dependabot_security_updates %} para la alerta, para crear una solicitud de extracción o para resolver la vulnerabilidad, da clic en **Crear una actualización de eguridad del {% data variables.product.prodname_dependabot %}**. ![Crea un botón de actualización de seguridad del {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/create-dependabot-security-update-button.png) -1. Cuando estés listo para actualizar tu dependencia y resolver la vulnerabilidad, fusiona la solicitud de extracción. Cada solicitud de extracción que levante el {% data variables.product.prodname_dependabot %} incluye información sobre los comandos que puedes utilizar para controlar el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Adminsitrar las solicitudes de extracción para las actualizaciones de las dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)". -1. Opcionalmente, si se está arreglando la alerta, si es incorrecta o si se ubica en una sección de código sin utilizar, selecciona el menú desplegable de "Descartar" y haz clic en una razón para descartar la alerta. ![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) +1. Click the alert you'd like to view. + ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list.png) +1. Review the details of the vulnerability and, if available, the pull request containing the automated security update. +1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**. + ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button.png) +1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)." +1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. + ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) {% elsif ghes > 3.0 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} -1. Haz clic en la alerta que quieres ver. ![Alerta seleccionada en la lista de alertas](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png) -1. Revisa los detalles de la vulnerabilidad y determina si necesitas actualizar la dependencia o no. -1. Cuando fusionas una solicitud de cambios que actualice el archivo de manifiesto o de bloqueo a una versión segura de la dependencia, esto resolverá la alerta. Como alternativa, si decides no actualizar la dependencia, selecciona el menú desplegable **Descartar** y haz clic en una razón para descartar la alerta. ![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png) +1. Click the alert you'd like to view. + ![Alert selected in list of alerts](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png) +1. Review the details of the vulnerability and determine whether or not you need to update the dependency. +1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, select the **Dismiss** drop-down, and click a reason for dismissing the alert. + ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png) {% else %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %} -1. Haz clic en el número de versión de la dependencia vulnerable para mostrar la información detallada. ![Información detallada de la dependencia vulnerable](/assets/images/enterprise/3.0/dependabot-alert-info.png) -1. Revisa los detalles de la vulnerabilidad y determina si necesitas actualizar la dependencia o no. Cuando fusionas una solicitud de cambios que actualice el archivo de manifiesto o de bloqueo a una versión segura de la dependencia, esto resolverá la alerta. -1. El letrero en la parte superior de la pestaña de **Dependencias** se muestra hasta que todas las dependencias vulnerables se resuelven o hasta que lo descartes. Haz clic en **Descartar** en la esquina superior derecha del letrero y selecciona una razón para descartar la alerta. ![Descartar el letrero de seguridad](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png) +1. Click the version number of the vulnerable dependency to display detailed information. + ![Detailed information on the vulnerable dependency](/assets/images/enterprise/3.0/dependabot-alert-info.png) +1. Review the details of the vulnerability and determine whether or not you need to update the dependency. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. +1. The banner at the top of the **Dependencies** tab is displayed until all the vulnerable dependencies are resolved or you dismiss it. Click **Dismiss** in the top right corner of the banner and select a reason for dismissing the alert. + ![Dismiss security banner](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png) {% endif %} -## Leer más +## Further reading -- "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec %} -- "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %} -- "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" -- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec %} -- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} +- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)"{% endif %} +- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" +- "[Troubleshooting the detection of vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 57d4e3d398..9a661152a1 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -1,8 +1,8 @@ --- -title: Acerca de la revisión de dependencias -intro: 'La revisión de dependencias te permite detectar las dependencias vulnerables antes de que las introduzcas a tu ambiente y te proporciona información sobre la licencia, dependientes y edad de las dependencias.' +title: About dependency review +intro: 'Dependency review lets you catch vulnerable dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.' product: '{% data reusables.gated-features.dependency-review %}' -shortTitle: Revisión de dependencias +shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' @@ -21,29 +21,29 @@ redirect_from: {% data reusables.dependency-review.beta %} -## Acerca de la revisión de dependencias +## About dependency review {% data reusables.dependency-review.feature-overview %} -Si una solicitud de cambios apunta a la rama predeterminada de tu repositorio y contiene cambios a los archivos de bloqueo o de manifiesto empaquetados, puedes mostrar una revisión de dependencias para ver qué ha cambiado. La revisión de dependencias incluye detalles de los cambios a las dependencias indirectas en los archivos de bloqueo, y te dice si cualquiera de las dependencias que se agregaron o actualizaron contienen vulnerabilidades conocidas. +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. {% ifversion fpt or ghec %} -La revisión de dependencias se encuentra disponible en: +Dependency review is available in: -* Todos los repositorios públicos. -* Los repositorios privados que pertenecen a las organizaciones con una licencia de {% data variables.product.prodname_advanced_security %} que tengan la gráfica dependencias habilitada. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." {% elsif ghes or ghae %} -La revisión de dependencias se encuentra disponible cuando se habilita la gráfica de dependencias de {% data variables.product.product_location %} y cuando se habilita la {% data variables.product.prodname_advanced_security %} para la organización o el repositorio. +Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. {% endif %} -Algunas veces puede que solo quieras actualizar la versión de una dependencia en un manifiesto y generar una solicitud de cambios. Sin embargo, si la versión actualizada de esta dependencia directa también tiene dependencias actualizadas, tu solicitud de cambios podría tener más cambios de lo que esperas. La revisión de dependencias para cada archivo de bloqueo y de manifiesto proporciona un aforma sencilla para ver lo que ha cambiado y te deja saber si cualquiera de las versiones nuevas de las dependencias contienen vulnerabilidades conocidas. +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. -Cuando verificas las revisiones de dependencias en una solicitud de cambios y cambias cualquier dependencia que se marque como vulnerable, puedes evitar que las vulnerabilidades se agreguen a tu proyecto. Para obtener más información acerca de cómo funciona la revisión de dependencias, consulta la sección "[Revisar los cambios a las dependencias en las solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)." -Las {% data variables.product.prodname_dependabot_alerts %} encontrarán vulnerabilidades que ya se encuentran en tus dependencias, pero es mucho mejor evitar introducir problemas potenciales que arreglarlos posteriormente. Para obtener más informació acera de las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". +{% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix problems at a later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." -La revisión de dependencias es compatible con los mismos lenguajes de programación y ecosistemas de administración de paquetes que la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." -## Habilitar la revisión de dependencias +## Enabling dependency review -La característica de revisión de dependencias se encuentra disponible cuando habilitas la gráfica de dependencias. {% ifversion fpt or ghec %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae %}For more information, see "[Enabling the dependency graph and Dependabot alerts on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} +The dependency review feature becomes available when you enable the dependency graph. {% ifversion fpt or ghec %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae %}For more information, see "[Enabling the dependency graph and Dependabot alerts on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 9884228864..14ea4e4b20 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -1,6 +1,6 @@ --- -title: Acerca del gráfico de dependencias -intro: Puedes utilizar la gráfica de dependencias para identificar todas las dependencias de tus proyectos. La gráfica de dependencias es compatible con una variedad de ecosistemas de paquetes populares. +title: About the dependency graph +intro: You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems. redirect_from: - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph - /code-security/supply-chain-security/about-the-dependency-graph @@ -14,89 +14,92 @@ topics: - Dependency graph - Dependencies - Repositories -shortTitle: Gráfica de dependencias +shortTitle: Dependency graph --- - -## Disponibilidad de la gráfica de dependencias +## Dependency graph availability -La gráfica de dependencias está disponible para cada repositorio público que define las dependencias en un ecosistema de paquetes compatible {% ifversion fpt or ghec %}utilizando un formato de archivos compatible. Los administradores de repositorio también pueden configurar la gráfica de dependencias para los repositorios privados.{% endif %} +{% ifversion fpt or ghec %}The dependency graph is available for every public repository that defines dependencies in a supported package ecosystem using a supported file format. Repository administrators can also set up the dependency graph for private repositories.{% endif %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -## Acerca del gráfico de dependencias +## About the dependency graph -La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Para cada repositorio, muestra{% ifversion fpt or ghec %}: +The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% ifversion fpt or ghec %}: -- Las dependencias, ecosistemas y paquetes de los cuales depende -- Los dependientes, repositorios y paquetes que dependen de ella{% else %} dependencias, es decir, los ecosistemas y los paquetes de los cuales depende. {% data variables.product.product_name %} no calcula información alguna sobre los dependientes, repositorios y paquetes que dependen de un repositorio.{% endif %} +- Dependencies, the ecosystems and packages it depends on +- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.product_name %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} -Cuando cargas una confirmación a {% data variables.product.product_name %} que cambie o agregue un archivo de bloqueo o de manifiesto a la rama predeterminada, la gráfica de dependencias se actualizará automáticamente.{% ifversion fpt or ghec %} Adicionalmente, la gráfica se actualiza cuando alguien cargue un cambio en el repositorio de una de tus dependencias.{% endif %} Para obtener más información sobre los sistemas y archivos de manifiesto compatibles, consulta la sección "[Ecosistemas de paquetes compatibles](#supported-package-ecosystems)" a continuación. +When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% ifversion fpt or ghec %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. {% ifversion fpt or ghes > 3.1 or ghae or ghec %} -Cuando creas una solicitud de cambios que contenga los cambios de las dependencias que apuntan a la rama predeterminada, {% data variables.product.prodname_dotcom %} utiliza la gráfica de dependencias para agregar revisiones de dependencia a la solicitud de cambios. Estas indican si las dependencias contendrán vulnerabilidades y, si es el caso, la versión de la dependencia en la cual se arregló la vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)". +When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -## Dependencias que se incluyen +## Dependencies included -La gráfica de dependencias incluye todas las dependencias de un repositorio que se describan en los archivos de manifiesto y de bloqueo o sus equivalentes para los ecosistemas compatibles. Esto incluye: +The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: -- Las dependencias directas que se definen explícitamente en el archivo de manifiesto o de bloqueo -- Las dependencias indirectas de estas dependencias directas, también conocidas como dependencias transitorias o sub-dependencias +- Direct dependencies, that are explicitly defined in a manifest or lock file +- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies -La gráfica de dependencias identifica dependencias indirectas{% ifversion fpt or ghec %} ya sea explícitamente desde un archivo de bloqueo o mediante la verificación de dependencias de tus dependencias directas. Para la gráfica más confiable, debes utilizar archivos de bloqueo (o su equivalente), ya que estos definen exactamente qué versiones de las dependencias directas e indirectas estás utilizando actualmente. Si utilizas archivos de bloqueo, también te aseguras de que todos los contribuyentes del repositorio están utilizando las mismas versiones, lo cual te facilitará el probar y depurar el código{% else %} de los archivos de bloqueo{% endif %}. +The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. {% ifversion fpt or ghec %} -## Dependientes incluídos +## Dependents included -Para los repositorios públicos, únicamente se reportan los repositorios públicos que dependen de éste o de los paquetes que publicas. Esta información no se reporta para los repositorios privados.{% endif %} +For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} -## Utiizar la gráfica de dependencias +## Using the dependency graph -Puedes utilizar la gráfica de dependencias para: +You can use the dependency graph to: -- Explora los repositorios de los cuales depende tu código{% ifversion fpt or ghec %}, y aquellos que dependen de éste{% endif %}. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% ifversion fpt or ghec %} -- Ver en un solo tablero un resumen de las dependencias que se utilizan en los repositorios de tu organización. Para obtener más información, consulta "[Ver información de tu organización](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %} -- Ver y actualizar las dependencias vulnerables de tu repositorio. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". |{% ifversion fpt or ghes > 3.1 or ghec %} -- Consulta la información sobre las dependencias vulnerables en las solicitudes de cambios. Para obtener más información, consulta la sección "[Revisar los cambios de dependencia en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)".{% endif %} +- Explore the repositories your code depends on{% ifversion fpt or ghec %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% ifversion fpt or ghec %} +- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} +- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes > 3.1 or ghec %} +- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %} -## Habilitar la gráfica de dependencias +## Enabling the dependency graph -{% ifversion fpt or ghec %}Para generar una gráfica de dependencias, {% data variables.product.product_name %} necesita acceso de solo lectura a los archivos de manifiesto y de bloqueo de un repositorio. La gráfica de dependencias se genera automáticamente para todos los repositorios públicos y puedes elegir habilitarla para los privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% ifversion fpt or ghec %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% ifversion ghes or ghae %}Si la gráfica de dependencias no se encuentra disponible en tu sistema, tu propietario de empresa puede habilitarla junto con las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)".{% endif %} +{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} -Cuando la gráfica de dependencias se habilita por primera vez, cualquier manifiesto y archivo de bloqueo para los ecosistemas compatibles se pasarán de inmediato. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Una vez que se habilita, la gráfica se actualiza automáticamente con cada carga al repositorio{% ifversion fpt or ghec %} y con cada carga a cualquier otro repositorio de la gráfica{% endif %}. +When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}. -## Ecosistemas de paquetes compatibles +## Supported package ecosystems -Los formatos recomendados definen explícitamente qué versiones se utilizan para todas las dependencias directas e indirectas. Si utilizas estos formatos, tu gráfica de dependencias será más precisa. También refleja la configuración actual de la compilación y habilita a la gráfica de dependencias para que reporte las vulnerabilidades tanto en las dependencias directas como en las indirectas.{% ifversion fpt or ghec %} Las dependencias indirectas que se infieren desde un archivo de manifiesto (o equivalente) se excluyen de las verificaciones para dependencias vulnerables.{% endif %} +The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% ifversion fpt or ghec %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} -| Administración de paquetes | Idiomas | Formatos recomendados | Todos los formatos compatibles | -| -------------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | +| Package manager | Languages | Recommended formats | All supported formats | +| --- | --- | --- | ---| +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | {%- ifversion fpt or ghes > 3.2 or ghae %} | Go modules | Go | `go.sum` | `go.mod`, `go.sum` | {%- elsif ghes = 3.2 %} | Go modules | Go | `go.mod` | `go.mod` | {%- endif %} -| Maven | Java, Scala | `pom.xml` | `pom.xml` | | npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| | Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | +| Maven | Java, Scala | `pom.xml` | `pom.xml` | +| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | {%- ifversion fpt or ghes > 3.3 %} -| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} | RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} -**Nota:** Si listas tus dependencias de Python dentro de un archivo `setup.py`, es probable que no podamos analizar y listar cada una de las dependencias en tu proyecto. +**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. {% endnote %} -## Leer más +## Further reading -- "[Gráfica de dependencias](https://en.wikipedia.org/wiki/Dependency_graph)" en Wikipedia -- "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} -- "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" +- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia +- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} +- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index 508ff47550..fa87938058 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -1,6 +1,6 @@ --- -title: Explorar las dependencias de un repositorio -intro: 'Puedes utilizar la gráfica de dependencias para ver los paquetes de los que depende tu proyecto en {% ifversion fpt or ghec %} y los repositorios que dependen de él{% endif %}. Adicionalmente, puedes ver cualquier vulnerabilidad que se detecte en sus dependencias.' +title: Exploring the dependencies of a repository +intro: 'You can use the dependency graph to see the packages your project depends on{% ifversion fpt or ghec %} and the repositories that depend on it{% endif %}. In addition, you can see any vulnerabilities detected in its dependencies.' redirect_from: - /articles/listing-the-packages-that-a-repository-depends-on - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on @@ -19,100 +19,102 @@ topics: - Dependency graph - Dependencies - Repositories -shortTitle: Explorar las dependencias +shortTitle: Explore dependencies --- - -## Visualizar la gráfica de dependencias +## Viewing the dependency graph -La gráfica de dependencias muestra las dependencias{% ifversion fpt or ghec %} y los dependientes{% endif %} de tu repositorio. Para obtener más información acerca de la detección de dependencias y de cuáles ecosistemas son compatibles, consulta la sección [Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +The dependency graph shows the dependencies{% ifversion fpt or ghec %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %}{% ifversion fpt or ghec %} -4. Opcionalmente, debajo de "Gráfica de dependencias", da clic en **Dependientes**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} +4. Optionally, under "Dependency graph", click **Dependents**. +![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} {% ifversion ghes or ghae-issue-4864 %} -Los propietarios de las empresas pueden configurar la gráfica de dependencias a nivel empresarial. Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)". +Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." {% endif %} -### Vista de dependencias +### Dependencies view {% ifversion fpt or ghec %} -Las dependencias se agrupan por ecosistema. Puedes expandir una dependencia para ver a su vez sus dependencias. Para las dependencias en repositorios públicos hospedadas en {% data variables.product.product_name %}, también puedes dar clic en una de ellas para ver el repositorio. Las dependencias en los repositorios privados, paquetes privados, o archivos no reconocidos se muestran en texto simple. +Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies on public repositories hosted on {% data variables.product.product_name %}, you can also click a dependency to view the repository. Dependencies on private repositories, private packages, or unrecognized files are shown in plain text. -Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a {% data variables.product.prodname_dependabot_alerts %}. +If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}. -![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph.png) +![Dependencies graph](/assets/images/help/graphs/dependencies_graph.png) {% endif %} {% ifversion ghes or ghae %} -Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a {% data variables.product.prodname_dependabot_alerts %}. +Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}. -![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph_server.png) +![Dependencies graph](/assets/images/help/graphs/dependencies_graph_server.png) {% note %} -**Nota:** {% data variables.product.product_name %} no llena la vista de **Dependientes**. +**Note:** {% data variables.product.product_name %} does not populate the **Dependents** view. {% endnote %} {% endif %} {% ifversion fpt or ghec %} -### Vista de dependientes +### Dependents view -Para los repositorios públicos, la vista de dependientes muestra cómo otros repositorios utilizan este repositorio. Para mostrar únicamente los repositorios que contienen una biblioteca en un administrador de paquetes, da cilc en **CANTIDAD de paquetes** inmediatamente sobre la lista de repositorios dependientes. La cantidad de dependientes es aproximada y podría no siempre empatar con los dependientes listados. +For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed. -![Gráfico de dependencias](/assets/images/help/graphs/dependents_graph.png) +![Dependents graph](/assets/images/help/graphs/dependents_graph.png) -## Habilitar e inhabilitar la gráfica de dependencias para un repositorio privado +## Enabling and disabling the dependency graph for a private repository -Los administradores del repositorio pueden habilitar o inhabilitar la gráfica de dependencias para los repositorios privados. +Repository administrators can enable or disable the dependency graph for private repositories. -También puedes habilitar o inhabilitar la gráfica de dependencias para todos los repositorios que pertenecen a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +You can also enable or disable the dependency graph for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Lee los mensajes sobre el otorgar acceso de solo lectura a {% data variables.product.product_name %} para los datos del repositorio para así habilitar la gráfica de dependencias, posteriormente, da clic en **Habilitar** junto a "Gráfica de Dependencias". ![Botón de "Habilitar" para la gráfica de dependencias](/assets/images/help/repository/dependency-graph-enable-button.png) +4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. + !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png) -Puedes inhabilitar la gráfica de dependencias en cualquier momento si das clic en **Inhabilitar** junto a "Gráfica de Dependencias" en la pestaña de Seguridad & análisis. +You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab. -## Cambiar el paquete "Utilizado por" +## Changing the "Used by" package -Si está habilitada la gráfica de dependencias y tu repositorio contiene un paquete que se publica en un ecosistema de paquetes compatible, {% data variables.product.prodname_dotcom %} muestra una sección de "Utilizado por" en la barra lateral de la pestaña de **Código** de tu repositorio. Para obtener más información sobre los ecosistemas de paquetes compatibles, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." -La sección de "Utilizado por" muestra la cantidad de referencias públicas al paquete que se encontró, y muestra los avatares de algunos de los propietarios de los proyectos dependientes. +The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects. -![Sección de "Utilizado por" en la barra lateral](/assets/images/help/repository/used-by-section.png) +!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png) -Dar clic en cualquier elemento de esta sección te lleva a la pestaña de **Dependientes** de la gráfica de dependencias. +Clicking any item in this section takes you to the **Dependents** tab of the dependency graph. -La sección de "Utilizado por" representa un solo paquete del repositorio. Si tienes permisos de administrador en un repositorio que contenga paquetes múltiples, puedes elegir qué paquete reporesenta la sección de "Utilizado por". +The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Configurar las caracetrísticas de análisis y seguridad"; da clic en el menú desplegable dentro de la sección "Contador de utilizado por" y elige un paquete. ![Elige un paquete de "Utilizado por"](/assets/images/help/repository/choose-used-by-package.png) +4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. + ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png) {% endif %} -## Solución de problemas del gráfico de dependencias +## Troubleshooting the dependency graph -Si tu gráfica de dependencias está vacía, puede que haya un problema con el archivo que contiene tus dependencias. Revisa el archivo para asegurarte de que tiene el formato correcto para el tipo de archivo. +If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type. {% ifversion fpt or ghec %} -Si este archivo tiene el formato correcto, entonces revisa su tamaño. La gráfica de dependencias ignora los archivos individuales de manifiesto y de bloqueo que pesen más de 0.5 Mb, a menos de que seas un usuario de {% data variables.product.prodname_enterprise %}. Este procesa hasta 20 archivos de manifiesto o de bloqueo por repositorio predeterminadamente, así que puedes dividir las dependencias en archivos más pequeños en los subdirectorios del repositorio.{% endif %} +If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 1.5 Mb, unless you are a {% data variables.product.prodname_enterprise %} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %} -Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omiten de la gráfica de dependencias y no podrán verificar si hay dependencias vulnerables. +If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies. -## Leer más +## Further reading -- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% ifversion fpt or ghec %} -- "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" -- "[Entender cómo {% data variables.product.prodname_dotcom %} utiliza y protege tus datos](/github/understanding-how-github-uses-and-protects-your-data)" +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% ifversion fpt or ghec %} +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" +- "[Understanding how {% data variables.product.prodname_dotcom %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 405c4ce1e9..0e1e4f1579 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -1,5 +1,5 @@ --- -title: Entender tu cadena de suministro de software +title: Understanding your software supply chain versions: fpt: '*' ghes: '*' @@ -13,6 +13,6 @@ children: - /about-the-dependency-graph - /exploring-the-dependencies-of-a-repository - /about-dependency-review -shortTitle: Entender la cadena de suministro +shortTitle: Understand your supply chain --- diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md b/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md index 6419e8a24a..fb6299d73c 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md @@ -1,6 +1,6 @@ --- -title: Personalizar Codespaces para tu cuenta -intro: 'Puedes personalizar {% data variables.product.prodname_codespaces %} utilizando un repositorio de `dotfiles` en {% data variables.product.product_name %} o utilizando la sincronización de ajustes.' +title: Personalizing Codespaces for your account +intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' redirect_from: - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account @@ -14,40 +14,40 @@ topics: - Set up - Fundamentals product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Personalizar tu cuenta +shortTitle: Personalize your codespaces --- -## Acerca de personalizar los {% data variables.product.prodname_codespaces %} +## About personalizing {% data variables.product.prodname_codespaces %} -Cuando utilizas cualquier ambiente de desarrollo, personalizar las configuraciones y herramientas de acuerdo con tus preferencias y flujos de trabajo es un paso importante. {% data variables.product.prodname_codespaces %} permite dos formas principales de personalizar tus codespaces. +When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces. -- [Sincronización de ajustes](#settings-sync) - Puedes utilizar y compartir los ajustes de {% data variables.product.prodname_vscode %} entre {% data variables.product.prodname_codespaces %} y otras instancias de {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) – Puedes utilizar un repositorio público de `dotfiles` para especificar scripts, preferencias de shell y otras configuraciones. +- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}. +- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations. -La personalización de {% data variables.product.prodname_codespaces %} aplica a cualquier codespace que crees. +{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create. -Los mantenendores de proyecto también pueden definir una configuración predeterminada que aplique a cada codespace para un repositorio que cree alguien más. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". +Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." -## Sincronización de ajustes +## Settings Sync -La configuración de ajustes te permite compartir configuraciones tales como configuraciones, atajos de teclado, fragmentos de código, extensiones y estados de IU entre máquinas e instancias de {% data variables.product.prodname_vscode %}. +Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}. -Para habilitar la Sincronización de Ajustes, en la esquina inferior izquierda de la Barra de Actividad, selecciona {% octicon "gear" aria-label="The gear icon" %} y haz clic en **Encender la Sincronización de Ajustes…**. Desde el diálogo, selecciona qué ajustes te gustaría sincronizar. +To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. From the dialog, select which settings you'd like to sync. -![La opción de sincronización de ajustes en el menú de administración](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) +![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) -Para obtener más información, consulta la [Guía de sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync) en la documentación de {% data variables.product.prodname_vscode %}. +For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation. ## Dotfiles -Los Dotfiles son archivos y carpetas de sistemas parecidos a Unix que comienzan con `.` y que controlan la configuración de aplicaciones y shells de tu sistema. Puedes alamacenar y administrar tus dotfiles en un repositorio en {% data variables.product.prodname_dotcom %}. Para encontrar consejos y tutoriales sobre qué incluir en tu repositorio de `dotfiles`, consulta la sección [GitHub maneja dotfiles](https://dotfiles.github.io/). +Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your `dotfiles` repository, see [GitHub does dotfiles](https://dotfiles.github.io/). -Si tu cuenta de usuario en {% data variables.product.prodname_dotcom %} es propietaria de un repositorio público que se llama `dotfiles`, {% data variables.product.prodname_dotcom %} puede utilizarlo automáticamente para personalizar tu ambiente de codespaces, una vez que se habilite desde tus [ajustes personales de Codespaces](https://github.com/settings/codespaces). Actualmente, no son compatibles los repositorios `dotfiles` privados. +If your user account on {% data variables.product.prodname_dotcom %} owns a public repository named `dotfiles`, {% data variables.product.prodname_dotcom %} can automatically use this repository to personalize your codespace environment, once enabled from your [personal Codespaces settings](https://github.com/settings/codespaces). Private `dotfiles` repositories are not currently supported. -Tu repositorio `dotfiles` puede incluir los alias de tu shell y tus preferencias, cualquier herramienta que quieras instalar, o cualquier otra personalización del codespace que quieras hacer. +Your `dotfiles` repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make. -Cuando creas un codespace nuevo, {% data variables.product.prodname_dotcom %} clona tu repositorio `dotfiles` hacia el ambiente del codespace, y busca uno de los siguientes archivos para configurar el ambiente. +When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your `dotfiles` repository to the codespace environment, and looks for one of the following files to set up the environment. * _install.sh_ * _install_ @@ -58,42 +58,43 @@ Cuando creas un codespace nuevo, {% data variables.product.prodname_dotcom %} cl * _setup_ * _script/setup_ -Si no encuentra alguno de estos archivos, entonces cualquier archivo o carpeta en `dotfiles` que comience con `.` se enlazará simbólicamente al directorio `~` o `$HOME` del codespace. +If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory. -Cualquier cambio a tu repositorio `dotfiles` se aplicará únicamente a cada codespace nuevo, y no afectará a ningún codespace existente. +Any changes to your `dotfiles` repository will apply only to each new codespace, and do not affect any existing codespace. {% note %} -**Nota:** Actualmente, {% data variables.product.prodname_codespaces %} no es compatible con la personalización de la configuración de _Usuario_ para el editor de {% data variables.product.prodname_vscode %} con tu repositorio de `dotfiles`. Puedes configurar ajustes predeterminados de _Workspace_ y _Remote [Codespaces]_ para un proyecto específico en el repositorio de éste. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)". +**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the _User_ settings for the {% data variables.product.prodname_vscode %} editor with your `dotfiles` repository. You can set default _Workspace_ and _Remote [Codespaces]_ settings for a specific project in the project's repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)." {% endnote %} -### Habilitar tu repositorio de dotfiles para {% data variables.product.prodname_codespaces %} +### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %} -Puedes utilizar tu repositorio público de `dotfiles` para personalizar tu ambiente de {% data variables.product.prodname_codespaces %}. Una vez que configuras el repositorio, puedes agregar tus scripts, preferencias y configuraciones a él. Después, necesitarás habilitar tus dotfiles desde tu página personal de ajustes de {% data variables.product.prodname_codespaces %}. +You can use your public `dotfiles` repository to personalize your {% data variables.product.prodname_codespaces %} environment. Once you set up that repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_codespaces %} settings page. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Debajo de "Dotfiles", selecciona "Instalar dotfiles automáticamente" para que {% data variables.product.prodname_codespaces %} instale tus dotfiles automáticamente en cada codespace nuevo que crees. ![Instalar dotfiles](/assets/images/help/codespaces/install-dotfiles.png) +1. Under "Dotfiles", select "Automatically install dotfiles" so that {% data variables.product.prodname_codespaces %} automatically installs your dotfiles into every new codespace you create. + ![Installing dotfiles](/assets/images/help/codespaces/install-dotfiles.png) {% note %} - **Nota:** Esta opción solo se encuentra disponible si creaste un repositorio público de `dotfiles` para tu cuenta de usuario. + **Note:** This option is only available if you've created a public `dotfiles` repository for your user account. {% endnote %} -Puedes agregar más scripts, preferencias o archivos de configuración a tu repositorio de dotfiles o editar los archivos existentes cuando lo desees. Solo los codespaces nuevos tomarán los cambios a los ajustes. +You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces. -## Otros ajustes disponibles +## Other available settings -También puedes personalizar los {% data variables.product.prodname_codespaces %} utilizando [Ajustes de codespaces](https://github.com/settings/codespaces) adicionales: +You can also personalize {% data variables.product.prodname_codespaces %} using additional [Codespaces settings](https://github.com/settings/codespaces): -- Para configurar tu región predeterminada, consulta la sección "[Configurar tu región predeterminada para los {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)". -- Para configurar tu editor, consulta la sección "[Configurar tu editor predeterminado para los {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)". -- Para agregar secretos cifrados, consulta la sección "[Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)". -- Para habilitar la verificación de GPG, consulta la sección "[Administrar la verificación de GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". -- Para permitir que tus codespaces accedan a otros repositorios, consulta la sección "[Administrar el acceso y la seguridad de los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". +- To set your default region, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." +- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." +- To add encrypted secrets, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)." +- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +- To allow your codespaces to access other repositories, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." -## Leer más +## Further reading -* "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". +* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)" diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 81ebf48639..7d3630f2df 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Crear un codespace -intro: Puedes crear un codespace para una rama en un repositorio para desarrollar en línea. +title: Creating a codespace +intro: You can create a codespace for a branch in a repository to develop online. product: '{% data reusables.gated-features.codespaces %}' permissions: '{% data reusables.codespaces.availability %}' redirect_from: @@ -16,80 +16,85 @@ topics: - Developer --- -## Acerca de la creación de codespaces +## About codespace creation You can create a codespace on {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. {% data reusables.codespaces.codespaces-are-personal %} -Los codespaces se asocian con una rama específica de un repositorio y este repositorio no puede estar vacío. {% data reusables.codespaces.concurrent-codespace-limit %} Para obtener más información, consulta la sección "[Borrar un codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". +Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)." -Cuando creas un codespace, se suscitan varios pasos para crear y conectarte a tu ambiente de desarrollo: +When you create a codespace, a number of steps happen to create and connect you to your development environment: -- Paso 1: se le asignan una MV y almacenamiento a tu codespace. -- Paso 2: Se crea el contenedor y se clona tu repositorio. -- Paso 3: Puedes conectarte al codespace. -- Paso 4: El codespace sigue con la configuración post-creación. +- Step 1: VM and storage are assigned to your codespace. +- Step 2: Container is created and your repository is cloned. +- Step 3: You can connect to the codespace. +- Step 4: Codespace continues with post-creation setup. -Para obtener más información sobre lo que sucede cuando creas un codespace, consulta la sección "[A profundidad](/codespaces/getting-started/deep-dive)". +For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)." + +For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)." + +If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. {% data reusables.codespaces.use-visual-studio-features %} {% data reusables.codespaces.you-can-see-all-your-codespaces %} -## Acceso a los {% data variables.product.prodname_codespaces %} +## Access to {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.availability %} -Cuando tienes acceso a los {% data variables.product.prodname_codespaces %}, verás una pestaña de "Codespaces" dentro del menú desplegable de **{% octicon "code" aria-label="The code icon" %} Código** cuando ves un repositorio. +When you have access to {% data variables.product.prodname_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository. -Tendrás acceso a los codespaces bajo las siguientes condiciones: +You'll have access to codespaces under the following conditions: -* Eres un miembro de la organización que habilitó los {% data variables.product.prodname_codespaces %} y configuró un límite de gastos. -* Un propietario de la organización te proporcionó acceso a los {% data variables.product.prodname_codespaces %}. -* El repositorio le pertenece a la organización que habilitó los {% data variables.product.prodname_codespaces %}. +* You are a member of an organization that has enabled {% data variables.product.prodname_codespaces %} and set a spending limit. +* An organization owner has granted you access to {% data variables.product.prodname_codespaces %}. +* The repository is owned by the organization that has enabled {% data variables.product.prodname_codespaces %}. {% note %} -**Nota:** Los individuos que ya se hayan unido al beta con su cuenta personal de {% data variables.product.prodname_dotcom %} no perderán acceso a los {% data variables.product.prodname_codespaces %}, sin embargo, los {% data variables.product.prodname_codespaces %} para personas individuales seguirán en beta. +**Note:** Individuals who have already joined the beta with their personal {% data variables.product.prodname_dotcom %} account will not lose access to {% data variables.product.prodname_codespaces %}, however {% data variables.product.prodname_codespaces %} for individuals will continue to remain in beta. {% endnote %} -Los propietarios de las organizaciones pueden permitir que los miembros de la organización creen codespaces, limitar la creación de los codespaces para miembros selectos de la organización o inhabilitar la creación de codespaces. Para obtener información sobre cómo administrar el acceso a los codespaces dentro de tu organización, consulta la sección "[Habilitar los Codespaces para los usuarios de tu organización](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)". +Organization owners can allow all members of the organization to create codespaces, limit codespace creation to selected organization members, or disable codespace creation. For more information about managing access to codespaces within your organization, see "[Enable Codespaces for users in your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)." -Antes de que puedas utilizar {% data variables.product.prodname_codespaces %} en una organización, un propietario o gerente de facturación debe haber configurado un límite de gastos. Para obtener más información, consulta la sección "[Acerca de los límites de gastos para los Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)". +Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)." -Si te gustaría crear un codespace para un repositorio que pertenezca a tu cuenta personal o a otro usuario y tienes permiso para crear repositorios en una organización que haya habilitado los {% data variables.product.prodname_codespaces %}, puedes bifurcar repositorios que pertenezcan a los usuarios de esta organización y luego crear un codespace para dicha bifurcación. +If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. -## Crear un codespace +## Creating a codespace {% include tool-switcher %} - + {% webui %} {% data reusables.repositories.navigate-to-repo %} -2. Debajo del nombre de repositorio, utiliza el menú desplegable de "Rama" y selecciona aquella en la que quieras crear un codespace. +2. Under the repository name, use the "Branch" drop-down menu, and select the branch you want to create a codespace for. - ![Menú desplegable de rama](/assets/images/help/codespaces/branch-drop-down.png) + ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png) -3. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. +3. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) + ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - Si eres un miembro de una organización y estás creando un codespace en un repositorio que le pertenece a esta, puedes seleccionar la opción de un tipo de máquina diferente. Desde el diálogo, elige un tipo de máquina y luego haz clic en **Crear codespace**. ![Elección de tipo de máquina](/assets/images/help/codespaces/choose-custom-machine-type.png) + If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**. + ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png) {% endwebui %} - + {% vscode %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} {% endvscode %} - + {% cli %} {% data reusables.cli.cli-learn-more %} -To create a new codespace, use the `gh codespace create` subcommand. +To create a new codespace, use the `gh codespace create` subcommand. ```shell gh codespace create diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index c40c0ff46d..6ee69270ff 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Borrar un codespace -intro: Puedes borrar un codespace que ya no necesites. +title: Deleting a codespace +intro: You can delete a codespace you no longer need. product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-github-codespaces/deleting-a-codespace @@ -21,28 +21,28 @@ topics: {% note %} -**Nota:** Solo la persona que creó un codespace podrá borrarlo. Actualmente no hay forma de que los propietarios de las organizaciones borren los codespaces que se crearon dentro de su organización. +**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization. {% endnote %} {% include tool-switcher %} - + {% webui %} -1. Navegar a la página de "Tus Codespaces" en [github.com/codespaces](https://github.com/codespaces). +1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces). -2. A la derecha del codespace que quieres borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Borrar {% octicon "trash" aria-label="The trash icon" %}** +2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** - ![Botón de borrar](/assets/images/help/codespaces/delete-codespace.png) + ![Delete button](/assets/images/help/codespaces/delete-codespace.png) {% endwebui %} - + {% vscode %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} {% endvscode %} - + {% cli %} @@ -59,3 +59,6 @@ If you have unsaved changes, you'll be prompted to confirm deletion. You can use For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete). {% endcli %} + +## Further reading +- [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle) diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index aad92cf185..29d0a8e09f 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Desarrollar en un codespace -intro: 'Puedes abrir un codespace en {% data variables.product.product_name %} y después desarrollar utilizando las características de {% data variables.product.prodname_vscode %}.' +title: Developing in a codespace +intro: 'You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}''s features.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'You can develop in codespaces you''ve created for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}.' redirect_from: @@ -18,44 +18,47 @@ topics: -## Acerca del desarrollo con {% data variables.product.prodname_codespaces %} +## About development with {% data variables.product.prodname_codespaces %} -{% data variables.product.prodname_codespaces %} te proporciona la experiencia completa de desarrollo de {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} +{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} -![Resumen de codespace con anotaciones](/assets/images/help/codespaces/codespace-overview-annotated.png) +{% data reusables.codespaces.links-to-get-started %} -1. Barra lateral - Predeterminadamente, esta área te muestra los archivos de tu proyexcto en el explorador. -2. Barra de actividad - Esto muestra las vistas y te proporciona una forma de cambiar entre ellas. Puedes volver a ordenar las vistas si las arrastras y las sueltas. -3. Editor - Aquí es donde editas tus archivos. Puedes utilzar la pestaña para que cada editor la posicione exactamente donde la necesitas. -4. Paneles - Aquí es donde puedes ver la información de salida y depuración, así como el lugar predeterminado para la Terminal integrada. -5. Barra de estado - Esta área te proporciona información útil sobre tu codespace y proyecto. Por ejemplo, el nombre de rama, los puertos configurados y más. +![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png) -Para obtener más información sobre cómo utilizar {% data variables.product.prodname_vscode %}, consulta la [Guía de interface de usuario](https://code.visualstudio.com/docs/getstarted/userinterface) en la documentación de {% data variables.product.prodname_vscode %}. +1. Side Bar - By default, this area shows your project files in the Explorer. +2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them. +3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it. +4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. +5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. + +For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. {% data reusables.codespaces.connect-to-codespace-from-vscode %} -{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta la sección "[Solucionar problemas de los clientes de los Codespaces](/codespaces/troubleshooting/troubleshooting-codespaces-clients)". +{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-codespaces-clients)." -### Personalizar tu codespace +### Personalizing your codespace -{% data reusables.codespaces.about-personalization %} Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)". +{% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)." -{% data reusables.codespaces.apply-devcontainer-changes %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". +{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." -### Ejecutar tu app desde un codespace -{% data reusables.codespaces.about-port-forwarding %} Para obtener más información, consulta la sección "[Abrir puertos en tu codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)". +### Running your app from a codespace +{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)." -### Configramr tus cambios +### Committing your changes -{% data reusables.codespaces.committing-link-to-procedure %} +{% data reusables.codespaces.committing-link-to-procedure %} ### Using the {% data variables.product.prodname_vscode_command_palette %} The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." -## Navegar a un codespace existente +## Navigating to an existing codespace 1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. Da clic en el nombre del codespace en el cual quieras desarrollar. ![Nombre del codespace](/assets/images/help/codespaces/click-name-codespace.png) +2. Click the name of the codespace you want to develop in. + ![Name of codespace](/assets/images/help/codespaces/click-name-codespace.png) -Como alternativa, puedes ver cualquier codespace activo en un repositorio si navegas a dicho repositorio y seleccionnas **{% octicon "code" aria-label="The code icon" %} Código**. El menú desplegable mostrará todos los codespaces activos en un repositorio. +Alternatively, you can see any active codespaces for a repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The drop-down menu will display all active codespaces for a repository. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index 3a34b80626..ed01105cf3 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -1,5 +1,5 @@ --- -title: Reenviar puertos en tu codespace +title: Forwarding ports in your codespace intro: '{% data reusables.codespaces.about-port-forwarding %}' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -12,59 +12,60 @@ topics: - Codespaces - Fundamentals - Developer -shortTitle: Reenviar puertos +shortTitle: Forward ports --- -## Acerca de los puertos reenviados +## About forwarded ports -La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging. +Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging. -When an application running inside a codespace prints output to the terminal that contains a localhost URL, such as `http://localhost:PORT` or `http://127.0.0.1:PORT`, the port is automatically forwarded. If you're using {% data variables.product.prodname_github_codespaces %} in the browser or in {% data variable.product.prodname_vscode %}, the URL string in the terminal is converted into a link that you can click to view the web page on your local machine. By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP. +When an application running inside a codespace prints output to the terminal that contains a localhost URL, such as `http://localhost:PORT` or `http://127.0.0.1:PORT`, the port is automatically forwarded. If you're using {% data variables.product.prodname_codespaces %} in the browser or in {% data variables.product.prodname_vscode %}, the URL string in the terminal is converted into a link that you can click to view the web page on your local machine. By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP. -![Reenvío automático de puertos](/assets/images/help/codespaces/automatic-port-forwarding.png) +![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) You can also forward a port manually, label forwarded ports, share forwarded ports with members of your organization, share forwarded ports publicly, and add forwarded ports to the codespace configuration. -## Reenviar un puerto +## Forwarding a port -Puedes reenviar manualmente a un puerto que no se haya reenviado automáticamente. +You can manually forward a port that wasn't forwarded automatically. {% include tool-switcher %} - + {% webui %} {% data reusables.codespaces.navigate-to-ports-tab %} -1. Debajo de la lista de puertos, haz clic en **Agregar puerto**. +1. Under the list of ports, click **Add port**. - ![Botón de agregar puerto](/assets/images/help/codespaces/add-port-button.png) + ![Add port button](/assets/images/help/codespaces/add-port-button.png) -1. Teclea el número de puerto o de dirección y luego presiona enter. +1. Type the port number or address, then press enter. - ![Botón de caja de texto para teclear el puerto](/assets/images/help/codespaces/port-number-text-box.png) + ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) ## Using HTTPS forwarding By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed. {% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to update, then hover over **Change Port Protocol**. ![Option to change port protocol](/assets/images/help/codespaces/update-port-protocol.png) +1. Right click the port you want to update, then hover over **Change Port Protocol**. + ![Option to change port protocol](/assets/images/help/codespaces/update-port-protocol.png) 1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace. {% endwebui %} - + {% vscode %} {% data reusables.codespaces.navigate-to-ports-tab %} -1. Debajo de la lista de puertos, haz clic en **Agregar puerto**. +1. Under the list of ports, click **Add port**. - ![Botón de agregar puerto](/assets/images/help/codespaces/add-port-button.png) + ![Add port button](/assets/images/help/codespaces/add-port-button.png) -1. Teclea el número de puerto o de dirección y luego presiona enter. +1. Type the port number or address, then press enter. - ![Botón de caja de texto para teclear el puerto](/assets/images/help/codespaces/port-number-text-box.png) + ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) {% endvscode %} - + {% cli %} @@ -82,7 +83,7 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c {% endcli %} -## Compartir un puerto +## Sharing a port {% note %} @@ -93,25 +94,29 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate. {% include tool-switcher %} - + {% webui %} {% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**. ![Option to select port visibility in right-click menu](/assets/images/help/codespaces/make-public-option.png) -1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar. ![Copiar el icono para la URL del puerto](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Envía la URL copiada a la persona con la que quieras compartir el puerto. +1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**. + ![Option to select port visibility in right-click menu](/assets/images/help/codespaces/make-public-option.png) +1. To the right of the local address for the port, click the copy icon. + ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) +1. Send the copied URL to the person you want to share the port with. {% endwebui %} - + {% vscode %} {% data reusables.codespaces.navigate-to-ports-tab %} -1. Haz clic derecho en el puerto que quieres compartir y luego en **Hacer público**. ![Opción para hacer el puerto público en el menú de clic derecho](/assets/images/help/codespaces/make-public-option.png) -1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar. ![Copiar el icono para la URL del puerto](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Envía la URL copiada a la persona con la que quieras compartir el puerto. +1. Right click the port you want to share, then click **Make Public**. + ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png) +1. To the right of the local address for the port, click the copy icon. + ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) +1. Send the copied URL to the person you want to share the port with. {% endvscode %} - + {% cli %} To change the visibility of a forwarded port, use the `gh codespace ports visibility` subcommand. {% data reusables.codespaces.port-visibility-settings %} @@ -122,7 +127,7 @@ Replace `codespace-port` with the forwarded port number. Replace `setting` with gh codespace ports visibility codespace-port:setting ``` -You can set the visibility for multiple ports with one command. Por ejemplo: +You can set the visibility for multiple ports with one command. For example: ```shell gh codespace ports visibility 80:private 3000:public 3306:org @@ -132,20 +137,22 @@ For more information about this command, see [the {% data variables.product.prod {% endcli %} -## Etiquetar un puerto +## Labeling a port -Puedes etiquetar un puerto para hacerlo más fácil de identificar en una lista. +You can label a port to make the port more easily identifiable in a list. {% data reusables.codespaces.navigate-to-ports-tab %} -1. Pasa el mouse sobre el puerto que quieras etiquetar y luego haz clic en el icono de etiqueta. ![Icono de etiqueta para el puerto](/assets/images/help/codespaces/label-icon.png) +1. Hover over the port you want to label, then click the label icon. + ![Label icon for port](/assets/images/help/codespaces/label-icon.png) {% data reusables.codespaces.type-port-label %} -## Agregar el peurto a la configuración del codespace +## Adding a port to the codespace configuration -Puedes agregar un puerto reenviado a la configuración de {% data variables.product.prodname_codespaces %} del repositorio para que este pueda reenviarse automáticamente a todos los codespaces que se crearon desde el repositorio. Después de que actualizas la configuración, cualquier codespace creado debe reconstruirse para que el cambio se aplique. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". +You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." -Puedes configurar manualmente los puertos reenviados en un archivo `.devcontainer.json` utilizando la propiedad `forwardPorts` o puedes utilizar el panel "Puertos" en tu codespace. +You can manually configure forwarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace. {% data reusables.codespaces.navigate-to-ports-tab %} -1. Haz clic derecho en el puerto que quieras agregar a la configuración del codespace y luego haz clic en **Configurar etiqueta y actualizar devcontainer.json**. ![Opción para configurar una etiqueta y agregar el puerto a devcntainer.json en el menú de clic derecho](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) +1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. + ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) {% data reusables.codespaces.type-port-label %} diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md index ee690cf263..f5fb2b8625 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md @@ -1,6 +1,6 @@ --- -title: Desarrollar en un codespace -intro: 'Crea un codespace para comenzar a desarrollar tu proyecto dentro de un ambiente dedicado en la nube. Puedes utilizar puertos reenviados para ejecutar tu aplicación e incluso utilizar codespaces dentro de {% data variables.product.prodname_vscode %}' +title: Developing in a codespace +intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -8,6 +8,7 @@ versions: topics: - Codespaces children: + - /codespaces-lifecycle - /creating-a-codespace - /developing-in-a-codespace - /using-source-control-in-your-codespace @@ -18,4 +19,4 @@ children: - /using-codespaces-in-visual-studio-code - /using-codespaces-with-github-cli --- - + diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index db7e5dd3fb..2f9f4c0cdc 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- -title: Utilizar codespaces en Visual Studio Code -intro: 'Puedes desarrollar tu codespace directamente en {% data variables.product.prodname_vscode %} si conectas la extensión de {% data variables.product.prodname_github_codespaces %} con tu cuenta en {% data variables.product.product_name %}.' +title: Using Codespaces in Visual Studio Code +intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code @@ -18,73 +18,90 @@ shortTitle: Visual Studio Code --- +## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} -## Prerrequisitos +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)." -Para hacer desarrollos en un codespace directamente desde {% data variables.product.prodname_vscode %}, debes ingresar en la extensión de {% data variables.product.prodname_github_codespaces %}. La extensión de {% data variables.product.prodname_github_codespaces %} requiere el lanzamiento 1.51 de octubre de 2020 de {% data variables.product.prodname_vscode %} o superior. +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -Utiliza {% data variables.product.prodname_vs %} Marketplace para instalar la extensión de [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obtener más información, consulta la sección[Extensión de Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) en la documentación de {% data variables.product.prodname_vscode %}. +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." + +## Prerequisites + +To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. + +Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. {% mac %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Da clic en **Registrarse para ver {% data variables.product.prodname_dotcom %}...**. +2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. - ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) + ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**. -4. Regístrate en {% data variables.product.product_name %} para aprobar la extensión. +3. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +4. Sign in to {% data variables.product.product_name %} to approve the extension. {% endmac %} {% windows %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Utiliza el menú desplegable de "REMOTE EXPLORER" y luego da clic en **{% data variables.product.prodname_github_codespaces %}**. +2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. - ![El encabezado {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) + ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Da clic en **Registrarse para ver {% data variables.product.prodname_codespaces %}...**. +3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. - ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) + ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**. -5. Regístrate en {% data variables.product.product_name %} para aprobar la extensión. +4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +5. Sign in to {% data variables.product.product_name %} to approve the extension. {% endwindows %} -## Crear un codespace en {% data variables.product.prodname_vscode %} +## Creating a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Abrir un codespace en {% data variables.product.prodname_vscode %} +## Opening a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Debajo de "Codespaces", da clic en el codespace en el que quieras desarrollar. -3. Da clic en en el icono de conexión al codespace. +2. Under "Codespaces", click the codespace you want to develop in. +3. Click the Connect to Codespace icon. - ![Icono de conectarse al codespace en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Cambiar el tipo de máquina en {% data variables.product.prodname_vscode %} +## Changing the machine type in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.codespaces-machine-types %} -Puedes cambiar el tipo de máquina de tu codespace en cualquier momento. +You can change the machine type of your codespace at any time. -1. En {% data variables.product.prodname_vscode %}, abre la paleta de comandos (`shift command P` / `shift control P`). -2. Busca y selecciona "Codespaces: Cambiar mi tipo de máquina". +1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). +2. Search for and select "Codespaces: Change Machine Type." - ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-type-option.png) + ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Haz clic en el codespace que quieras cambiar. +3. Click the codespace that you want to change. - ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) + ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Elige el tipo de máquina que quieres utilizar. +4. Choose the machine type you want to use. -Si el codespace se está ejecutando actualmente, se mostrará un mensaje que pregunta si te gustaría reiniciar y reconectarte con tu codespace ahora. Haz clic en **Sí** en caso de que quieras cambiar el tipo de máquina que se utiliza para este codespace inmediatamente. Si haces clic en **No** o si el codespace no se está ejecutando actualmente, el cambio se reflejará la próxima vez que este se reinicie. +If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. -## Borrar un codespace en {% data variables.product.prodname_vscode %} +## Deleting a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} + +## Switching to the Insiders build of {% data variables.product.prodname_vscode %} + +You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. + +1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**. +2. From the list, select "Switch to Insiders Version". + + ![Clicking on "Insiders Build" in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-insiders-vscode.png) +3. Once selected, {% data variables.product.prodname_codespaces %} will continue to open in Insiders Version. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md index 5dc1237740..399ad2b384 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md @@ -1,6 +1,6 @@ --- title: Using Codespaces with GitHub CLI -shortTitle: CLI de GitHub +shortTitle: GitHub CLI intro: 'You can work with {% data variables.product.prodname_github_codespaces %} directly from your command line by using `gh`, the {% data variables.product.product_name %} command line interface.' product: '{% data reusables.gated-features.codespaces %}' miniTocMaxHeadingLevel: 3 @@ -13,9 +13,9 @@ topics: - Developer --- -## Acerca de {% data variables.product.prodname_cli %} +## About {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +{% data reusables.cli.about-cli %} For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." You can work with {% data variables.product.prodname_codespaces %} in the {% data variables.product.prodname_cli %} to: - [List your codespaces](#list-all-of-your-codespaces) @@ -24,26 +24,30 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da - [Delete a codespace](#delete-a-codespace) - [SSH into a codespace](#ssh-into-a-codespace) - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code) -- [Copying a file to/from a codespace](#copying-a-file-tofrom-a-codespace) +- [Copying a file to/from a codespace](#copy-a-file-tofrom-a-codespace) - [Modify ports in a codespace](#modify-ports-in-a-codespace) - [Access codespace logs](#access-codespace-logs) -## Instalar {% data variables.product.prodname_cli %} +## Installing {% data variables.product.prodname_cli %} {% data reusables.cli.cli-installation %} + +## Using {% data variables.product.prodname_cli %} -## Uso de {% data variables.product.prodname_cli %} - -If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account. +If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account. To use `gh` to work with {% data variables.product.prodname_codespaces %}, type `gh codespace ` or its alias `gh cs `. -As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could: +As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could: -* List your current codespaces, to check whether you have a codespace for a particular repository:
    `gh codespace list` -* Create a new codespace for the required repository branch:
    `gh codespace create -r github/docs -b main` -* SSH into the new codespace:
    `gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w` -* Forward a port to your local machine:
    `gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w` +* List your current codespaces, to check whether you have a codespace for a particular repository:
    + `gh codespace list` +* Create a new codespace for the required repository branch:
    + `gh codespace create -r github/docs -b main` +* SSH into the new codespace:
    + `gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w` +* Forward a port to your local machine:
    + `gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w` ## `gh` commands for {% data variables.product.prodname_github_codespaces %} @@ -71,7 +75,7 @@ The list includes the unique name of each codespace, which you can use in other gh codespace create -r owner/repository [-b branch] ``` -Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". +For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." ### Stop a codespace @@ -87,7 +91,7 @@ For more information, see "[Deep dive into Codespaces](/codespaces/getting-start gh codespace delete -c codespace-name ``` -Para obtener más información, consulta la sección "[Borrar un codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)." +For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)." ### SSH into a codespace @@ -119,7 +123,7 @@ Use the prefix `remote:` on a file or directory name to indicate that it's on th The location of files and directories on the codespace is relative to the home directory of the remote user. -#### Ejemplos +#### Examples * Copy a file from the local machine to the `$HOME` directory of a codespace: @@ -167,13 +171,13 @@ You can set the visibility of a forwarded port. {% data reusables.codespaces.por gh codespace ports visibility codespace-port:private|org|public -c codespace-name ``` -You can set the visibility for multiple ports with one command. Por ejemplo: +You can set the visibility for multiple ports with one command. For example: ```shell gh codespace ports visibility 80:private 3000:public 3306:org -c codespace-name ``` -Para obtener más información, consulta la sección "[Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". +For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." ### Access codespace logs diff --git a/translations/es-ES/content/codespaces/getting-started/deep-dive.md b/translations/es-ES/content/codespaces/getting-started/deep-dive.md index ee2dd24cbf..341f4d1d3d 100644 --- a/translations/es-ES/content/codespaces/getting-started/deep-dive.md +++ b/translations/es-ES/content/codespaces/getting-started/deep-dive.md @@ -1,6 +1,6 @@ --- -title: Conoce los Codespaces a profundidad -intro: 'Comprender cómo funciona {% data variables.product.prodname_codespaces %}.' +title: Deep dive into Codespaces +intro: 'Understand how {% data variables.product.prodname_codespaces %} works.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -11,95 +11,109 @@ topics: - Codespaces --- -{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo basado en la nube e instantáneo que utiliza un contenedor para proporcionarte lenguajes comunes, herramientas y utilidades para el desarrollo. {% data variables.product.prodname_codespaces %} también es configurable, lo cual te permite crear un ambiente de desarrollo personalizado para tu proyecto. Al configurar un ambiente de desarrollo personalizado para tu proyecto, puedes tener una configuración de codespace repetible para todos los usuarios de dicho proyecto. +{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. -## Crea tu codespace +## Creating your codespace -Hay varios puntos de entrada para crear un codespace. +There are a number of entry points to create a codespace. -- Desde tu repositorio para trabajo destacado nuevo. -- Desde una solicitud de cambios abierta para explorar el trabajo en curso. -- Desde una confirmación en el historial del repositorio para investigar un error en un punto específico del tiempo. -- Desde {% data variables.product.prodname_vscode %}. +- From your repository for new feature work. +- From an open pull request to explore work-in-progress. +- From a commit in the repository's history to investigate a bug at a specific point in time. +- From {% data variables.product.prodname_vscode %}. + +Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -Tu codespace puede ser efímero si necesitas probar algo o puedes volver al mismo codespace para trabajar en trabajo destacado a largo plazo. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". +Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you. -Una vez que hayas seleccionado la opción de crear un codespace nuevo, algunos pasos suceden en segundo plano antes de que este esté disponible para ti. +![Open with Codespaces button](/assets/images/help/codespaces/new-codespace-button.png) -![Botón de abrir con codespaces](/assets/images/help/codespaces/new-codespace-button.png) -### Paso 1: Se asigna una MV y un almacenamiento a tu codespace +### Step 1: VM and storage are assigned to your codespace -Cuando creas un codespace, se hace un [clon superficial](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) de tu repositorio en una máquina virtual Linux que es tanto dedicada como privada para ti. El tener una MV dedicada garantiza que tengas un conjunto completo de recursos de cómputo disponibles para ti desde esa máquina. Si es necesario, esto también te permitirá tener acceso de raíz total a tu contenedor. +When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. -### Paso 2: Se crea el contenedor +### Step 2: Container is created -{% data variables.product.prodname_codespaces %} utiliza un contenedor como el ambiente de desarrollo. Este contenedor se crea con base en las configuraciones que puedes definir en un archivo de `devcontainer.json` o Dockerfile en tu repositorio. Si no [configuras un contenedor](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} utilizará una [imagen predeterminada](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), la cual tiene muchos lenguajes y tiempos de ejecución disponibles. Para obtener más información sobre lo que contiene la imagen predeterminada, consulta el repositorio [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux). - -### Paso 3: Conectarse al codespace - -Cuando tu contenedor se crea y se ejecuta cualquier otra inicialización, estarás conectado a tu codespace. Puedes conectarte a este a través de la web o a través de [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code) o a través de ambos, en caso de ser necesario. - -### Paso 4: Ajustes post-creación - -Una vez que estés conectado a tu codespace, la configuración automática que especificaste en tu archivo `devcontainer.json`, tal como ejecutar el `postCreateCommand` y el `postAttachCommand`, podría continuar. Si tienes un {% data variables.product.prodname_codespaces %} de repositorio de dotfiles público, puedes habilitarlo para utilizarlo con el codespace nuevo. Cuando lo habilitas, tus dotfiles se clonarán en el contenedor y buscarán un archivo de instalación. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)". - -Finalmente, todo el historial del repositorio se copiará con un clon integral. - -Durante la configuración post-creación, aún podrás utilizar la terminal integrada y editar tus archivos, pero ten cuidado de evitar cualquier condiciones de carrera entre tu trabajo y los comandos que se están ejecutando. -## Ciclo de vida de los {% data variables.product.prodname_codespaces %} - -### Guardar archivos en tu codespace - -Conforme desarrollas en tu codespace, este guardará cualquier cambio en tus archivos cada algunos cuantos segundos. Tu codespace seguirá ejecutándose durante 30 minutos después de la última actividad. Después de este tiempo, este dejará de ejecutarse, pero puedes reiniciarlo ya sea desde la pestaña existente del buscador o desde la lista de codespaces existentes. Los cambios de archivo del editor y de la salida de la terminal se cuentan como actividad y, por lo tanto, tu codespace no se detendrá si la salida de la terminal sigue. +{% data variables.product.prodname_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't [configure a container](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} uses a [default image](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), which has many languages and runtimes available. For information on what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. {% note %} -**Nota:** Los cambios en un codespace en {% data variables.product.prodname_vscode %} no se guardan automáticamente a menos de que hayas habilitado el [Guardado automático](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**Note:** If you want to use Git hooks in your codespace and apply anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) to your codespace, then you must set up hooks during step 4 after the container is created. + +Since your repository is cloned onto the host VM before the container is created, anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) will not apply in your codespace unless you set up hooks in your `devcontainer.json` configuration file using the `postCreateCommand` in step 4. For more information, see "[Step 4: Post-creation setup](#step-4-post-creation-setup)." + {% endnote %} -### Cerrar o detener tu codespace +### Step 3: Connecting to the codespace -To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). Si sales de tu codespace sin ejecutar el comando para detenerlo (por ejemplo, cerrar la pestaña del buscador) o si dejas el codespace ejecutándose sin interacción, este y sus procesos en ejecución seguirán hasta que ocurra una ventana de inactividad, después de la cual se detendrá el codespace. Predeterminadamente, la ventana de inactividad es de 30 minutos. +When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. -Cuando cierras o detienes tu codespace, todos los cambios sin confirmar se preservan hasta que te conectes al codespace nuevamente. +### Step 4: Post-creation setup +Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. -## Ejecutar tu aplicación +If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. -La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. Por ejemplo, si estás ejecutando una aplicación web por el puerto 4000 dentro de tu codespace, puedes reenviar ese puerto automáticamente para hacer la aplicación accesible desde tu buscador. +If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)." -El reenvío de puertos determina cuáles de ellos se hicieron accesibles para ti desde la máquina remota. Incluso si no reenvías un puerto, este será accesible para otros procesos que se ejecuten dentro del mismo codespace. +Finally, the entire history of the repository is copied down with a full clone. -![Diagrama que muestra cómo funciona el reenvío de puertos en un codespace](/assets/images/help/codespaces/port-forwarding.png) +During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running. +## {% data variables.product.prodname_codespaces %} lifecycle -Cuando una aplicción que se ejecuta dentro del {% data variables.product.prodname_codespaces %} da salida a un puerto hacia la consola, el {% data variables.product.prodname_codespaces %} detecta el patrón de URL del host local y reenvía el puerto automáticamente. Puedes hacer clic en la URL de la terminal o en el mensaje de notificación para abrir el puerto en un buscador. By default, {% data variables.product.prodname_codespaces %} forwards the port using HTTP. Para obtener más información sobre el reenvío de puertos, consulta la sección "[Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". +### Saving files in your codespace -Si bien los puertos pueden reenviarse automáticamente, no son accesibles públicamente en la internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)." - -El ejecutar tu aplicación cuando llegas por primera vez a tu codespace puede convertirse en un bucle de desarrollador interno rápido. Mientras editas, tus cambios se guardan automáticamente y se ponen disponibles en tu puerto reenviado. Para ver los cambios, regresa a la pestaña de la aplicación en ejecución en tu buscador y actualízala. - -## Confirmar y subir tus cambios - -Git se encuentra disponible predeterminadamente en tu codespace, entonces puedes confiar en tu flujo de trabajo existente de Git. Puedes trabajar con Git en tu codespace, ya sea a través de la Terminal o utilizando la IU de control de código fuente de [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol). Para obtener más información, consulta la sección "[Utilizar el control de código fuente en tu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" - -![Ejecutar un estado de git en la Terminal de Codespaces](/assets/images/help/codespaces/git-status.png) - -Puedes crear un codespace desde cualquier rama, confirmación o solicitud de cambios en tu proyecto o puedes cambiar a una rama existente o nueva desde dentro de tu codespace activo. Ya que {% data variables.product.prodname_codespaces %} está diseñado para ser efímero, puedes utilizarlo como un ambiente aislado para experimentar, verificar la solicitud de cambios de un compañero o arreglar conflictos de fusión. Puedes crear más de un codespace por repositorio o incluso por rama. Sin embargo, cada cuenta de usuario tiene un límite de 10 codespaces. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. +As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing. {% note %} -**Nota:** Las confirmaciones desde tu codespace se atribuirán al nombre y correo electrónico público que se configuró en https://github.com/settings/profile. Para autenticarte, se utilizará un token con alcance al repositorio, incluido en el ambiente como `GITHUB_TOKEN`, y tus credenciales de GitHub. +**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +{% endnote %} + +### Closing or stopping your codespace + +To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop. By default, the window of inactivity is 30 minutes. + +When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again. + + +## Running your application + +Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser. + +Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself. + +![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png) + +When an application running inside {% data variables.product.prodname_codespaces %} outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal or in the toast message to open the port in a browser. By default, {% data variables.product.prodname_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." + +While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)." + +Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it. + +## Committing and pushing your changes + +Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" + +![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) + +You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. You can create more than one codespace per repository or even per branch. However, each user account has a limit of 10 codespaces. If you've reached the limit and want to create a new codespace, you must delete a codespace first. + +{% note %} + +**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate. {% endnote %} -## Personalizar tu codespace con extensiones +## Personalizing your codespace with extensions -El utilizar {% data variables.product.prodname_vscode %} en tu codespace te proporciona acceso a el Mercado de {% data variables.product.prodname_vscode %} para que puedas agregar cualquier extensión que necesites. Para obtener más información sobre cómo se ejecutan las extensiones en {% data variables.product.prodname_codespaces %}, consulta la sección [Apoyar el desarrollo remoto y a los Codespaces de GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) en los documentos de {% data variables.product.prodname_vscode %}. +Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. -Si yta utilizas {% data variables.product.prodname_vscode %}, puedes usar la [Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automáticamente extensiones, ajustes, temas y atajos de teclado entre tu instancia local y cualquier {% data variables.product.prodname_codespaces %} que crees. +If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. -## Leer más +## Further reading -- [Habilitar los {% data variables.product.prodname_codespaces %} para tu organización](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Administrar la facturación para los {% data variables.product.prodname_codespaces %} en tu organización](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) -- [Configurar tu proyecto para los Codespaces](/codespaces/setting-up-your-project-for-codespaces) +- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [Setting up your project for Codespaces](/codespaces/setting-up-your-project-for-codespaces) +- [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle) diff --git a/translations/es-ES/content/codespaces/index.md b/translations/es-ES/content/codespaces/index.md index 21bc58c01a..da81bc9add 100644 --- a/translations/es-ES/content/codespaces/index.md +++ b/translations/es-ES/content/codespaces/index.md @@ -1,7 +1,7 @@ --- -title: Documentación de Codespaces de GitHub -shortTitle: Acerca de GitHub Codespaces -intro: 'Crea un codespace o comienza a desarrollar en un ambiente de desarrollo seguro, configurable y dedicado que funciona donde y como tu quieras.' +title: GitHub Codespaces Documentation +shortTitle: GitHub Codespaces +intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.' introLinks: overview: /codespaces/overview quickstart: /codespaces/getting-started/quickstart @@ -11,7 +11,7 @@ featuredLinks: - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - /codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces + - /codespaces/developing-in-codespaces/codespaces-lifecycle popular: - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces diff --git a/translations/es-ES/content/codespaces/overview.md b/translations/es-ES/content/codespaces/overview.md index ba473be48d..3aa1fd900c 100644 --- a/translations/es-ES/content/codespaces/overview.md +++ b/translations/es-ES/content/codespaces/overview.md @@ -1,8 +1,8 @@ --- -title: Resumen de GitHub Codespaces -shortTitle: Resumen +title: GitHub Codespaces overview +shortTitle: Overview product: '{% data reusables.gated-features.codespaces %}' -intro: 'Esta guía te presenta a {% data variables.product.prodname_codespaces %} y te proporciona detalles de cómo funciona y cómo utilizarlo.' +intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.' allowTitleToDifferFromFilename: true redirect_from: - /codespaces/codespaces-reference/about-codespaces @@ -18,26 +18,26 @@ topics: - Codespaces --- -## ¿Qué es un codespace? +## What is a codespace? -Un codespace es un ambiente de desarrollo que se hospeda en la nube. Puedes personalizar tu proyecto para los {% data variables.product.prodname_codespaces %} si confirmas los [archivos de configuración](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) a tu repositorio (lo cual se conoce habitualmente como Configuración-como-código), lo cual crea una configuración de codespace repetible para todos los usuarios de tu proyecto. +A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. -Los {% data variables.product.prodname_codespaces %} se ejecutan en diversas opciones de cómputo basadas en MV hospedadas en {% data variables.product.product_location %}, las cuales puedes configurar desde máquinas de 2 núcleos hasta de 32 núcleos. Puedes conectar tus codespaces desde el buscador o localmente utilizando {% data variables.product.prodname_vscode %}. +{% data variables.product.prodname_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. -![Un diagrama que muestra cómo funciona {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-diagram.png) +![A diagram showing how {% data variables.product.prodname_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) -## Utilizar Codespaces +## Using Codespaces -Puedes crear un codespace desde cualquier rama o confirmación en tu repositorio y comenzar a desarrollar utilizando recursos de cómputo basados en la nube. +You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. {% data reusables.codespaces.links-to-get-started %} -Pra personalizar los tiempos de ejecución y herramientas en tu codespace, puedes crear una configuración personalizada para definir un ambiente (o _contenedor dev_) que sea específico para tu repositorio. El utilizar un contenedor dev te permite especificar un ambiente de desarrollo de Docker con una combinación de herramienta y tiempo de ejecución bien definidos que pueden referenciar una imagen, Dockerfile o docker-compose. Esto significa que, cualquiera que utilice el repositorio, tendrá las mismas herramientas disponibles para ellos cuando creen un codespace. +To customize the runtimes and tools in your codespace, you can create a custom configuration to define an environment (or _dev container_) that is specific for your repository. Using a dev container allows you to specify a Docker environment for development with a well-defined tool and runtime stack that can reference an image, Dockerfile, or docker-compose. This means that anyone using the repository will have the same tools available to them when they create a codespace. -Si no hiciste ninguna configuración personalizada, {% data variables.product.prodname_codespaces %} clonará tu repositorio en un ambiente con la imagen predeterminada del codespace, la cual incluye muchas herramientas, lenguajes y ambientes de tiempo de ejecución. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +If you don't do any custom configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". -También puedes personalizar aspectos de tu ambiente de codespace utilizando un repositorio público de [dotfiles](https://dotfiles.github.io/tutorials/) y la [Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync). Esta personalización puede incluir preferencias de shell, herramientas adicionales, configuración de editores y extensiones de VS Code. Para obtener más información, consulta la sección "[Personalizar tu codespace](/codespaces/customizing-your-codespace)". +You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". -## Acerca de la facturación para {% data variables.product.prodname_codespaces %} +## About billing for {% data variables.product.prodname_codespaces %} -Para obtener más información sobre la facturación de los {% data variables.product.prodname_codespaces %}, consulta la sección "[Administrar la facturación para los {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)". +For information on pricing, storage, and usage for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." -{% data reusables.codespaces.codespaces-spending-limit-requirement %} Para obtener más información sobre cómo los propietarios de las organizaciones y los gerentes de facturación pueden administrar el límite de gastos de {% data variables.product.prodname_codespaces %} para una organización, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". +{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an organization, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md index 1d0ead943d..ffa7251bdf 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md @@ -1,9 +1,9 @@ --- -title: Configurar tu proyecto de C# (.NET) para Codespaces -shortTitle: Configurar tu proyecto de C# (.NET) +title: Setting up your C# (.NET) project for Codespaces +shortTitle: Setting up your C# (.NET) project allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' -intro: 'Inicia con tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' +intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' redirect_from: - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project versions: @@ -15,125 +15,129 @@ topics: -## Introducción +## Introduction -Esta guía te muestra cómo configurar tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. +This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. -### Prerrequisitos +### Prerequisites -- Debes tener un proyecto existente de C# (.NET) en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/2percentsilk/dotnet-quickstart. -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. +- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart. +- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. -## Paso 1: Abre tu proyecto en un codespace +## Step 1: Open your project in a codespace -1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) + ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. + If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor de tu codespace tiene muchos lenguajes de programación y tiempos de ejecución, incluyendo a .NET. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. +When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano. -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. +You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." -## Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla +## Step 2: Add a dev container to your codespace from a template -El contenedor predeterminado para los codespaces tiene la última versión de .NET y las herramientas más recientes preinstaladas. Sin embargo, te exhortamos a que configures un contenedor personalizado para que puedas diseñar las herramientas y scripts que se ejecutan como parte de la creación de un codespace para que satisfagan las necesidades de tu proyecto y garanticen un ambiente totalmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} en tu repositorio. +The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project +](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." {% data reusables.codespaces.command-palette-container %} -2. Para este ejemplo, haz clic en **C# (.NET)**. Si necesitas características adicionales puedes seleccionar cualquier contenedor que sea específico para C# (.NET) o una combinación de herramientas tales como C# (.NET) y MS SQL. ![Selecciona la opción de C# (.NET) de la lista](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Haz clic en la versión recomendada de .NET. ![Selección de la versión de.NET](/assets/images/help/codespaces/add-dotnet-version.png) -4. Acepta la opción predeterminada para agregar a Node.js a tu personalización. ![Agregar la selección Node.js](/assets/images/help/codespaces/dotnet-options.png) +2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. + ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) +3. Click the recommended version of .NET. + ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png) +4. Accept the default option to add Node.js to your customization. + ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png) {% data reusables.codespaces.rebuild-command %} -### Anatomía de tu contenedor dev +### Anatomy of your dev container -El agregar la plantilla de contenedor dev de C# (.NET) agregará una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: +Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - `devcontainer.json` - Dockerfile -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. +The newly added `devcontainer.json` file defines a few properties that are described after the sample. #### devcontainer.json ```json { - "name": "C# (.NET)", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0 - "VARIANT": "5.0", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*", - "INSTALL_AZURE_CLI": "false" - } - }, + "name": "C# (.NET)", + "build": { + "dockerfile": "Dockerfile", + "args": { + // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0 + "VARIANT": "5.0", + // Options + "INSTALL_NODE": "true", + "NODE_VERSION": "lts/*", + "INSTALL_AZURE_CLI": "false" + } + }, - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash" - }, + // Set *default* container specific settings.json values on container create. + "settings": { + "terminal.integrated.shell.linux": "/bin/bash" + }, - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-dotnettools.csharp" - ], + // Add the IDs of extensions you want installed when the container is created. + "extensions": [ + "ms-dotnettools.csharp" + ], - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [5000, 5001], + // Use 'forwardPorts' to make a list of ports inside the container available locally. + // "forwardPorts": [5000, 5001], - // [Optional] To reuse of your local HTTPS dev cert: - // - // 1. Export it locally using this command: - // * Windows PowerShell: - // dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere" - // * macOS/Linux terminal: - // dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere" - // - // 2. Uncomment these 'remoteEnv' lines: - // "remoteEnv": { - // "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere", - // "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx", - // }, - // - // 3. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], + // [Optional] To reuse of your local HTTPS dev cert: + // + // 1. Export it locally using this command: + // * Windows PowerShell: + // dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere" + // * macOS/Linux terminal: + // dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere" + // + // 2. Uncomment these 'remoteEnv' lines: + // "remoteEnv": { + // "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere", + // "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx", + // }, + // + // 3. Do one of the following depending on your scenario: + // * When using GitHub Codespaces and/or Remote - Containers: + // 1. Start the container + // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer + // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" + // + // * If only using Remote - Containers with a local container, uncomment this line instead: + // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "dotnet restore", + // Use 'postCreateCommand' to run commands after the container is created. + // "postCreateCommand": "dotnet restore", - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" + // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. + "remoteUser": "vscode" } ``` -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **Dockerfile** - En el objeto de compilación, `dockerfile` es una referencia al Dockerfile que también se agregó desde la plantilla. +- **Name** - You can name our dev container anything, this is just the default. +- **Build** - The build properties. + - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template. - **Args** - - **Variant**: Este archivo solo contiene el argumento de compilación, el cual es la versión de .NET Core que queremos utilizar. -- **Settings** - Esta es la configuración de {% data variables.product.prodname_vscode %}. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **ms-dotnettools.csharp** - La extensión de C# de Microsoft proporciona soporte enriquecido para desarrollar en C#, incluyendo características tales como IntelliSense, limpieza de código, depuración, navegación de código, formateo de código, refactorización, explorador de variables, explorador de pruebas y más. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar cualquier cosa después de que llegas a tu codespace y esto no se define en el Dockerfile, como `dotnet restore`, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de vscode, pero puedes configurar esto como root opcionalmente. + - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use. +- **Settings** - These are {% data variables.product.prodname_vscode %} settings. + - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this. +- **Extensions** - These are extensions included by default. + - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more. +- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here. +- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. #### Dockerfile @@ -161,26 +165,26 @@ RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-d # RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 ``` -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de nodo o paquetes globales que queremos incluir en nuestro contenedor. +You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container. -## Paso 3: Modifica tu archivo devcontainer.json +## Step 3: Modify your devcontainer.json file -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás porpiedades para instalar extensiones y restablecer las dependencias de tu proyecto cuando se lance tu codespace. +With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependencies when your codespace launches. -1. En el explorador, expande la carpeta `.devcontainer` y selecciona el archivo `devcontainer.json` del árbol para abrirlo. +1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) + ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) -2. Actualiza tu lista de `extensions` en tu archivo `devcontainer.json` para agregar algunas extensiones que son útiles al trabajar con tu proyecto. +2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. ```json{:copy} "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], + "ms-dotnettools.csharp", + "streetsidesoftware.code-spell-checker", + ], ``` -3. Deja de comentar el `postCreateCommand` para restablecer las dependencias como parte del proceso de configuración del codespace. +3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process. ```json{:copy} // Use 'postCreateCommand' to run commands after the container is created. @@ -189,30 +193,30 @@ Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo qu {% data reusables.codespaces.rebuild-command %} - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. + Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. -5. Verifica que tus cambios se hayan aplicado con éxito verificando que se haya instalado la extensión "Code Spell Checker". +5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed. - ![Lista de extensiones](/assets/images/help/codespaces/dotnet-extensions.png) + ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png) -## Paso 4: Ejecuta tu aplicación +## Step 4: Run your application -En la sección anterior, utilizaste el `postCreateCommand` para instalar un conjunto de paquetes a través del comando `dotnet restore`. Ahora que instalamos nuestras dependencias, podemos ejecutar nuestra aplicación. +In the previous section, you used the `postCreateCommand` to install a set of packages via the `dotnet restore` command. With our dependencies now installed, we can run our application. -1. Ejecuta tu aplicación presionando `F5` o ingresando `dotnet watch run` en tu terminal. +1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal. -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. +2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/python-port-forwarding.png) + ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) -## Paso 5: Confirma tus cambios +## Step 5: Commit your changes {% data reusables.codespaces.committing-link-to-procedure %} -## Pasos siguientes +## Next steps -Ahora debes estar listo para comenzar a desarrollar tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. +You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. -- [Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) +- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) +- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) +- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md index 008a226eec..7b2fdad704 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md @@ -1,7 +1,7 @@ --- -title: Configurar tu proyecto de Java para Codespaces -shortTitle: Configurar tu proyecto de Java -intro: 'Inica con tu proyecto de Java en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' +title: Setting up your Java project for Codespaces +shortTitle: Setting up with your Java project +intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces @@ -14,50 +14,52 @@ topics: -## Introducción +## Introduction -Esta guía te muestra cómo configurar tu proyecto de Java en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. +This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. -### Prerrequisitos +### Prerequisites -- Debes tener un proyecto de Java existente en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/microsoft/vscode-remote-try-java -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. +- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java +- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. -## Paso 1: Abre tu proyecto en un codespace +## Step 1: Open your project in a codespace -1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) + ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. + If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo Java, nvm, npm, y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. +When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. +You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." -## Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla +## Step 2: Add a dev container to your codespace from a template -El contenedor predeterminado para los codespaces viene con la última versión de Java, adminsitradores de paquetes (Maven, Gradle) y otras herramientas comunes preinstaladas. Sin embargo, te recomendamos que configures un contenedor personalizado para definir las herramientas y scripts que necesita tu proyecto. Esto garantizará un ambiente totalmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} de tu repositorio. +The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." {% data reusables.codespaces.command-palette-container %} -3. Para este ejemplo, haz clic en **Java**. En la práctica, podrías seleccionar cualquier contenedor que sea específico de Java o una combinación de herramientas tales como Java y Azure Functions. ![Selecciona la opción de Java de la lista](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Haz clic en la versión recomendada de Java. ![Selección de la versión de Java](/assets/images/help/codespaces/add-java-version.png) +3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. + ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png) +4. Click the recommended version of Java. + ![Java version selection](/assets/images/help/codespaces/add-java-version.png) {% data reusables.codespaces.rebuild-command %} -### Anatomía de tu contenedor dev +### Anatomy of your dev container -El agregar la plantilla de contenedor dev de Java agrega una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: +Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - `devcontainer.json` - Dockerfile -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. +The newly added `devcontainer.json` file defines a few properties that are described after the sample. #### devcontainer.json @@ -65,55 +67,55 @@ El archivo `devcontainer.json` recién agregado define unas cuantas propiedades // For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: // https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java { - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, + "name": "Java", + "build": { + "dockerfile": "Dockerfile", + "args": { + // Update the VARIANT arg to pick a Java version: 11, 14 + "VARIANT": "11", + // Options + "INSTALL_MAVEN": "true", + "INSTALL_GRADLE": "false", + "INSTALL_NODE": "false", + "NODE_VERSION": "lts/*" + } + }, - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, + // Set *default* container specific settings.json values on container create. + "settings": { + "terminal.integrated.shell.linux": "/bin/bash", + "java.home": "/docker-java-home", + "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" + }, - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], + // Add the IDs of extensions you want installed when the container is created. + "extensions": [ + "vscjava.vscode-java-pack" + ], - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], + // Use 'forwardPorts' to make a list of ports inside the container available locally. + // "forwardPorts": [], - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", + // Use 'postCreateCommand' to run commands after the container is created. + // "postCreateCommand": "java -version", - // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" + // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. + "remoteUser": "vscode" } ``` -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **Dockerfile** - En el objeto de compilación, dockerfile es una referencia al Dockerfile que también se agregó desde la plantilla. +- **Name** - You can name your dev container anything, this is just the default. +- **Build** - The build properties. + - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - **Args** - - **Variant**: Este archivo solo contiene un argumento de compilación, el cual es la versión de Java que se pasa al Dockerfile. -- **Settings** - Estos son los ajustes de {% data variables.product.prodname_vscode %} que puedes configurar. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **Vscjava.vscode-java-pack** - El paquete de extensión de Java proporciona extensiones populares para que puedas comenzar a desarrollar en Java. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar lo que sea después de que llegas a tu codespace, lo cual no está definido en tu Dockerfile, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de `vscode`, pero puedes configurar esto como `root` opcionalmente. + - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile. +- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. + - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this. +- **Extensions** - These are extensions included by default. + - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started. +- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. +- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. #### Dockerfile @@ -143,48 +145,48 @@ RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/shar # RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 ``` -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de Java o paquetes globales que queremos incluir en nuestro Dockerfile. +You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile. -## Paso 3: Modifica tu archivo devcontainer.json +## Step 3: Modify your devcontainer.json file -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás porpiedades para instalar extensiones y tus dependencias de pryecto cuando se lance tu codespace. +With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches. -1. En el explorador, selecciona el archivo `devcontainer.json` del árbol para abrirlo. Puede que tengas que expandir la carpeta `.devcontainer` para verlo. +1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it. - ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) + ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) -2. Agrega las siguientes líneas a tu archivo `devcontainer.json` después de `extensions`. +2. Add the following lines to your `devcontainer.json` file after `extensions`. ```json{:copy} "postCreateCommand": "npm install", "forwardPorts": [4000], ``` - Para obtener más información sobre las propiedades de `devcontainer.json`, consulta las [referencias de devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) en los documentos de Visual Studio Code. + For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs. {% data reusables.codespaces.rebuild-command %} - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. + Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. -## Paso 4: Ejecuta tu aplicación +## Step 4: Run your application -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de npm. Ahora puedes utilizar esto para ejecutar nuestra aplicación con npm. +In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm. -1. Ejecuta tu aplicación presionando `F5`. +1. Run your application by pressing `F5`. -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. +2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/codespaces-port-toast.png) + ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) -## Paso 5: Confirma tus cambios +## Step 5: Commit your changes {% data reusables.codespaces.committing-link-to-procedure %} -## Pasos siguientes +## Next steps -Ahora debes estar listo para desarrollar tu proyecto de Java en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. +You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. -- [Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) +- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) +- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) +- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md index 9fe18c40ac..e8e9c2062b 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md @@ -1,7 +1,7 @@ --- -title: Configurar tu proyecto de Node.js para Codespaces -shortTitle: Configurar tu proyecto de Node.js -intro: 'Inicia con tu proyecto de JavaScript, Node.js o TypeScript en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' +title: Setting up your Node.js project for Codespaces +shortTitle: Setting up your Node.js project +intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -18,49 +18,51 @@ topics: -## Introducción +## Introduction -Esta guía te muestra cómo configurar tu proyecto de JavaScript, Node.js o TypeScript en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. +This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. -### Prerrequisitos +### Prerequisites -- Debes tener un proyecto existente de JavaScript, Node.js, TypeScript en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/microsoft/vscode-remote-try-node -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. +- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node +- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. -## Paso 1: Abre tu proyecto en un codespace +## Step 1: Open your project in a codespace -1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) + ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. + If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo a Node.js, JavaScript, TypeScript, nvm, npm y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. +When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. +You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." -## Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla +## Step 2: Add a dev container to your codespace from a template -El contenedor predeterminado de codespaces será compatible para ejecutar proyectos de Node.js como [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) fuera de la caja. Al configurar un contenedor personalizado, puedes personalizar las herramientas y scripts que se ejecutan como parte de la creación de codespaces y asegurarte de que haya un ambiente integralmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} en tu repositorio. +The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". {% data reusables.codespaces.command-palette-container %} -3. Para este ejemplo, haz clic en **Node.js**. Si necesitas características adicionales, puedes seleccionar cualquier contenedor que sea específico para Node o una combinación de herramientas tales como Node y MongoDB. ![Selecciona la opción Node de la lista](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Haz clic en la versión recomendada de Node.js. ![Selección de la versión de Node.js](/assets/images/help/codespaces/add-node-version.png) +3. For this example, click **Node.js**. If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. + ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png) +4. Click the recommended version of Node.js. + ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png) {% data reusables.codespaces.rebuild-command %} -### Anatomía de tu contenedor dev +### Anatomy of your dev container -El agregar la plantilla de contenedor dev de Node.js agregará una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: +Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - `devcontainer.json` - Dockerfile -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. +The newly added `devcontainer.json` file defines a few properties that are described after the sample. #### devcontainer.json @@ -68,46 +70,46 @@ El archivo `devcontainer.json` recién agregado define unas cuantas propiedades // For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: // https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node { - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, + "name": "Node.js", + "build": { + "dockerfile": "Dockerfile", + // Update 'VARIANT' to pick a Node version: 10, 12, 14 + "args": { "VARIANT": "14" } + }, - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash" - }, + // Set *default* container specific settings.json values on container create. + "settings": { + "terminal.integrated.shell.linux": "/bin/bash" + }, - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "dbaeumer.vscode-eslint" - ], + // Add the IDs of extensions you want installed when the container is created. + "extensions": [ + "dbaeumer.vscode-eslint" + ], - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], + // Use 'forwardPorts' to make a list of ports inside the container available locally. + // "forwardPorts": [], - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", + // Use 'postCreateCommand' to run commands after the container is created. + // "postCreateCommand": "yarn install", - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" + // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. + "remoteUser": "node" } ``` -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **dockerfile** - En el objeto de compilación, dockerfile es una referencia al Dockerfile que también se agregó desde la plantilla. +- **Name** - You can name your dev container anything, this is just the default. +- **Build** - The build properties. + - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - **Args** - - **Variant**: Este archivo solo contiene un argumento de compilación, el cual es la variante de nodo que queremos utilizar y que se pasa en el Dockerfile. -- **Settings** - Estos son los ajustes de {% data variables.product.prodname_vscode %} que puedes configurar. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **Dbaeumer.vscode-eslint** - ES lint es una extención genial para limpiar código, pero para JavaScript, hay varias extensiones buenas en Marketplace que también podrías incluir. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar lo que sea después de que llegas a tu codespace, lo cual no está definido en tu Dockerfile, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de vscode, pero puedes configurar esto como root opcionalmente. + - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. +- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. + - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this. +- **Extensions** - These are extensions included by default. + - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include. +- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. +- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. #### Dockerfile @@ -128,50 +130,50 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} # RUN su node -c "npm install -g " ``` -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de nodo o paquetes globales que queremos incluir en nuestro Dockerfile. +You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile. -## Paso 3: Modifica tu archivo devcontainer.json +## Step 3: Modify your devcontainer.json file -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás propiedades para instalar npm cuando tu codespace se lance y haga una lista de puertos dentro del contenedor que está disponible localmente. +With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally. -1. En el explorador, selecciona el archivo `devcontainer.json` del árbol para abrirlo. Puede que tengas que expandir la carpeta `.devcontainer` para verlo. +1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it. - ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) + ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) -2. Agrega las siguientes líneas a tu archivo `devcontainer.json` después de `extensions`: +2. Add the following lines to your `devcontainer.json` file after `extensions`: ```json{:copy} "postCreateCommand": "npm install", "forwardPorts": [4000], ``` - Para obtener más información sobre las propiedades de `devcontainer.json`, consulta la [ referencia de devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) en los documentos de {% data variables.product.prodname_vscode %}. + For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs. {% data reusables.codespaces.rebuild-command %} - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. + Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. -## Paso 4: Ejecuta tu aplicación +## Step 4: Run your application -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de npm. Ahora puedes utilizar esto para ejecutar nuestra aplicación con npm. +In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm. -1. Ejecuta tu comando de inicio en la terminal con `npm start`. +1. Run your start command in the terminal with`npm start`. - ![npm start en la terminal](/assets/images/help/codespaces/codespaces-npmstart.png) + ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png) -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. +2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/codespaces-port-toast.png) + ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) -## Paso 5: Confirma tus cambios +## Step 5: Commit your changes {% data reusables.codespaces.committing-link-to-procedure %} -## Pasos siguientes +## Next steps -Ahora debes estar listo para comenzar a desarrollar tu proyecto de JavaScript en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. +You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. -- [Administrar secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) +- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) +- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) +- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md index a814ebd59f..47c32e220d 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md @@ -1,7 +1,7 @@ --- -title: Configurar tu proyecto de Python para Codespaces -shortTitle: Configurar tu proyecto de Python -intro: 'Iniciar con tu proyecto de Python en {% data variables.product.prodname_codespaces %} creando un contenedor de dev personalizado.' +title: Setting up your Python project for Codespaces +shortTitle: Setting up your Python project +intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -17,116 +17,119 @@ topics: -## Introducción +## Introduction -Esta guía te muestra cómo configurar tu proyecto de Python en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. +This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. -### Prerrequisitos +### Prerequisites -- Debes tener un proyecto existente de Python en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/2percentsilk/python-quickstart. -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. +- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart. +- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. -## Paso 1: Abre tu proyecto en un codespace +## Step 1: Open your project in a codespace -1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. +1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) + ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. + If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo a Node.js, JavaScript, TypeScript, nvm, npm y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. +When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. +You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." -## Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla +## Step 2: Add a dev container to your codespace from a template -El contenedor predeterminado de codespaces viene con la última versión de Python, administradores de paquete (pip, Miniconda), y otras herramientas comunes preinstaladas. Sin embargo, te recomendamos que configures un contenedor personalizado para definir las herramientas y scripts que necesita tu proyecto. Esto garantizará un ambiente totalmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} de tu repositorio. +The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." {% data reusables.codespaces.command-palette-container %} -2. Para este ejemplo, haz clic en **Python 3**. Si necesitas características adicionales, puedes seleccionar cualquier contenedor que sea específico para Python o una combinación de herramientas tales como Python 3 y PostgreSQL. ![Selecciona la opción Python de la lista](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Haz clic en la versión recomendada de Python. ![Selección de la versión Python](/assets/images/help/codespaces/add-python-version.png) -4. Acepta la opción predeterminada para agregar a Node.js a tu personalización. ![Agregar la selección Node.js](/assets/images/help/codespaces/add-nodejs-selection.png) +2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgreSQL. + ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png) +3. Click the recommended version of Python. + ![Python version selection](/assets/images/help/codespaces/add-python-version.png) +4. Accept the default option to add Node.js to your customization. + ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png) {% data reusables.codespaces.rebuild-command %} -### Anatomía de tu contenedor dev +### Anatomy of your dev container -El agregar la plantilla de contenedor dev de Python agregará una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: +Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - `devcontainer.json` - Dockerfile -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. +The newly added `devcontainer.json` file defines a few properties that are described after the sample. #### devcontainer.json ```json { - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, + "name": "Python 3", + "build": { + "dockerfile": "Dockerfile", + "context": "..", + "args": { + // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 + "VARIANT": "3", + // Options + "INSTALL_NODE": "true", + "NODE_VERSION": "lts/*" + } + }, - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, + // Set *default* container specific settings.json values on container create. + "settings": { + "terminal.integrated.shell.linux": "/bin/bash", + "python.pythonPath": "/usr/local/bin/python", + "python.linting.enabled": true, + "python.linting.pylintEnabled": true, + "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", + "python.formatting.blackPath": "/usr/local/py-utils/bin/black", + "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", + "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", + "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", + "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", + "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", + "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", + "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" + }, - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], + // Add the IDs of extensions you want installed when the container is created. + "extensions": [ + "ms-python.python", + ], - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], + // Use 'forwardPorts' to make a list of ports inside the container available locally. + // "forwardPorts": [], - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", + // Use 'postCreateCommand' to run commands after the container is created. + // "postCreateCommand": "pip3 install --user -r requirements.txt", - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" + // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. + "remoteUser": "vscode" } ``` -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **Dockerfile** - En el objeto de compilación, `dockerfile` es una referencia al Dockerfile que también se agregó desde la plantilla. +- **Name** - You can name our dev container anything, this is just the default. +- **Build** - The build properties. + - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template. - **Args** - - **Variant**: Este archivo solo contiene un argumento de compilación, el cual es la variante de nodo que queremos utilizar y que se pasa en el Dockerfile. -- **Settings** - Esta es la configuración de {% data variables.product.prodname_vscode %}. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **ms-python.python** - La extensión de Python de Microsoft te proporciona una compatibilidad enriquecida para el lenguaje Python (para todas las versiones compatibles del lenguaje: >=3.6), incluyendo las característcas tales como IntelliSense, limpieza, depuración, navegación de código, formateo de código, refactorización, explorador de variables, explorador de pruebas y más. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar cualquier cosa después de que llegues a tu codespace y que no se defina en el Dockerfile, como `pip3 install -r requirements`, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de `vscode`, pero puedes configurar esto como `root` opcionalmente. + - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. +- **Settings** - These are {% data variables.product.prodname_vscode %} settings. + - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this. +- **Extensions** - These are extensions included by default. + - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more. +- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here. +- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. #### Dockerfile @@ -153,27 +156,27 @@ RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/l # RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 ``` -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de nodo o paquetes globales que queremos incluir en nuestro contenedor. +You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container. -## Paso 3: Modifica tu archivo devcontainer.json +## Step 3: Modify your devcontainer.json file -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás porpiedades para instalar extensiones y tus dependencias de pryecto cuando se lance tu codespace. +With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches. -1. En el explorador, expande la carpeta `.devcontainer` y selecciona el archivo `devcontainer.json` del árbol para abrirlo. +1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) + ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) -2. Actualiza la lista de `extensions` en tu archivo `devcontainer.json` para agregar algunas extensiones que son útiles al trabajar con tu proyecto. +2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. ```json{:copy} "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], + "ms-python.python", + "cstrap.flask-snippets", + "streetsidesoftware.code-spell-checker", + ], ``` -3. Quita el comentario de `postCreateCommand` para instalar automáticamente los requisitos como parte del proceso de configuración de codespaces. +3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process. ```json{:copy} // Use 'postCreateCommand' to run commands after the container is created. @@ -182,30 +185,30 @@ Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo qu {% data reusables.codespaces.rebuild-command %} - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. + Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. -5. Verifica tus cambios en donde se aplicaron con éxito verificando que se hayan instalado las extensiones "Code Spell Checker" y "Flask Snippet". +5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed. - ![Lista de extensiones](/assets/images/help/codespaces/python-extensions.png) + ![Extensions list](/assets/images/help/codespaces/python-extensions.png) -## Paso 4: Ejecuta tu aplicación +## Step 4: Run your application -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de pip3. Ahora que instalaste tus dependencias, puedes ejecutar tu aplicación. +In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application. -1. Ejecuta tu aplicación presionando `F5` o ingresando `python -m flask run` en la terminal del codespace. +1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal. -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. +2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/python-port-forwarding.png) + ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) -## Paso 5: Confirma tus cambios +## Step 5: Commit your changes {% data reusables.codespaces.committing-link-to-procedure %} -## Pasos siguientes +## Next steps -Ahora debes estar listo para comenzar a desarrollar tu proyecto de Python en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. +You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. -- [Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) +- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) +- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) +- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index b2a16c9b7a..5eb72a809c 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -1,6 +1,6 @@ --- -title: Exportar los cambios a una rama -intro: Este artículo proporciona los pasos para exportar los cambios de tu codespace a una rama. +title: Exporting changes to a branch +intro: This article provides steps for exporting your codespace changes to a branch. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -8,21 +8,21 @@ versions: type: reference topics: - Codespaces -shortTitle: Exportar cambios +shortTitle: Exporting changes --- -## Exportar los cambios a una rama +## Exporting changes to a branch -Al utilizar {% data variables.product.prodname_codespaces %} podrías querer exportar tus cambios a una rama sin lanzarlos a tu codespace. +While using {% data variables.product.prodname_codespaces %}, you may want to export your changes to a branch without launching your codespace. -Esto puede ser útil cuando hayas llegado a un [límite de gastos](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) o tengas un problema general para acceder a tu codespace. +This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace. -Para exportar tus cambios: +To export your changes: -1. Navega a la página de "Tus Codespaces" en [github.com/codespaces](https://github.com/codespaces) o, en el caso de un repositorio individual, haz clic en el menú **{% octicon "code" aria-label="The code icon" %} Código**. -2. Haz clic en los puntos suspensivos (**...**) a la derecha del codespace desde el cuál quieras exportar. -3. Selecciona **{% octicon "git-branch" aria-label="The git branch icon" %} Exportar cambios a la rama**. +1. Browse to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces) or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu. +2. Click the ellipsis (**...**) to the right of the codespace you want to export from. +3. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**. - ![Exportar cambios a una rama](/assets/images/help/codespaces/export-changes-to-a-branch.png) + ![Export changes to a branch](/assets/images/help/codespaces/export-changes-to-a-branch.png) -4. Desde el anuncio emergente, selecciona **Crear rama**. +4. From the popover, select **Create branch**. diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md index cca93fd867..9baf5f7702 100644 --- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -1,6 +1,6 @@ --- -title: Acerca de las wikis -intro: 'Puedes alojar documentación para tu repositorio en una wiki, para que otros puedan usar y colaborar con tu proyecto.' +title: About wikis +intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.' redirect_from: - /articles/about-github-wikis/ - /articles/about-wikis @@ -15,24 +15,24 @@ topics: - Community --- -Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. Puedes usar la wiki de tu repositorio para compartir contenido en forma completa acerca de tu proyecto, como por ejemplo cómo usarlo, cómo lo diseñaste o sus principios básicos. Un archivo README rápidamente dice lo que puede hacer tu proyecto, mientras que puedes usar una wiki para proporcionar documentación adicional. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". +Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)." -Con las wikis, puedes escribir contenido como en cualquier otro lado en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Iniciar con la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)". Usamos [nuestra biblioteca Markup de código abierto](https://github.com/github/markup) para convertir diferentes formatos en HTML, para que puedas elegir escribir en Markdown o en cualquier otro formato admitido. +With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. -{% ifversion fpt or ghes or ghec %}Si creas un wiki en un repositorio público, éste estará disponible para {% ifversion ghes %}cualquiera con acceso a {% data variables.product.product_location %}{% else %}el público en general{% endif %}. {% endif %}Si creas un wiki en un repositorio privado o interno, {% ifversion fpt or ghes or ghec %}las personas{% elsif ghae %}los miembros empresariales{% endif %} con acceso a este también podrán acceder a dicho wiki. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". +{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in an internal or private repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." -Puedes editar las wikis directamente en {% data variables.product.product_name %} o puedes editar los archivos wiki localmente. Predeterminadamente, solo las personas con acceso a tu repositorio podrán hacer cambios a los wikis, aunque podrás permitir que cualquiera en {% data variables.product.product_location %} colabore con un wiki en {% ifversion ghae %}un repositorio interno{% else %}un repositorio público{% endif %}. Para obtener más información, consulta "[Cambiar permisos de acceso para wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)". +You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% ifversion ghae %}an internal{% else %}a public{% endif %} repository. For more information, see "[Changing access permissions for wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)". {% note %} -**Nota:** Los motores de búsqueda no indizarán el contenido de los wikis. Para que tu contenido se indice en los motores de búsqueda, puedes utilizar [{% data variables.product.prodname_pages %}](/pages) en un repositorio público. +**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository. {% endnote %} -## Leer más +## Further reading -- "[Agregar o eliminar páginas wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)" -- "[Crear un pie de página o barra lateral para tu wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" -- "[Editar el contenido de una wiki](/communities/documenting-your-project-with-wikis/editing-wiki-content)" -- "[Ver el historial de cambios de una wiki](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Buscar wikis](/search-github/searching-on-github/searching-wikis)" +- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)" +- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" +- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)" +- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)" +- "[Searching wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 1c21397c92..ceec18560d 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Configurar las plantillas de reporte de problemas para tu repositorio -intro: Puedes personalizar las plantillas disponibles para los colaboradores para que las utilicen cuando abren un nuevo reporte de problema en tu repositorio. +title: Configuring issue templates for your repository +intro: You can customize the templates that are available for contributors to use when they open new issues in your repository. redirect_from: - /github/building-a-strong-community/creating-issue-templates-for-your-repository - /articles/configuring-issue-templates-for-your-repository @@ -12,7 +12,7 @@ versions: ghec: '*' topics: - Community -shortTitle: Configurar +shortTitle: Configure --- {% ifversion fpt or ghes or ghec %} @@ -23,61 +23,70 @@ shortTitle: Configurar {% ifversion fpt or ghae or ghes or ghec %} -## Crear plantillas de reporte de problemas +## Creating issue templates {% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. En la sección "Características", en "Propuestas", haz clic en **Configurar plantillas**. ![Botón Start template setup (Comenzar la configuración de plantilla)](/assets/images/help/repository/set-up-templates.png) -4. Usa el menú desplegable Agregar plantilla y haz clic en el tipo de plantilla que deseas crear. ![Menú desplegable Agregar plantilla](/assets/images/help/repository/add-template-drop-down-menu.png) -5. Para acceder a la vista previa o editar la plantilla antes de confirmarla en el repositorio, haz clic en ** Mostrar la vista previa y editar**. ![Botón para mostrar la vista previa y editar](/assets/images/help/repository/preview-and-edit-button.png) -6. Para editar la plantilla, haz clic en {% octicon "pencil" aria-label="The edit icon" %} y escribe en los campos para editar el contenido. ![Botón Issue template edit (Editar plantilla de propuesta)](/assets/images/help/repository/issue-template-edit-button.png) -7. Para establecer automáticamente un título predeterminado para la propuesta, asigna la propuesta a personas que tengan acceso de lectura al repositorio o aplica etiquetas a tu plantilla de propuesta e ingresa estos detalles en "Información adicional opcional". También puedes agregar estos detalles en la plantilla de propuesta con `título`, `etiquetas` o `asignatario` en un formato de texto preliminar en lenguaje YAML. ![Información adicional de plantilla de propuesta](/assets/images/help/repository/additional-issue-template-info.png) -8. Cuando hayas terminado de editar y visualizar la vista previa de tu plantilla, haz clic en **Proponer cambios** en el ángulo superior derecho de la página. ![Botón para proponer cambios](/assets/images/help/repository/propose-changes-button.png) -9. Escribe un mensaje de confirmación que describa los cambios que realizaste. ![Campo para el mensaje de confirmación de la plantilla de propuesta](/assets/images/help/repository/issue-template-commit-message-field.png) -10. Debajo de los campos del mensaje de confirmación, decide si deseas confirmar tu plantilla directamente en la rama predeterminada o si deseas crear una nueva rama y abrir una solicitud de extracción. Para obtener más información acerca de las solicitudes de extracción, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)". ![Elecciòn de la plantilla de propuesta para mantener o abrir una solicitud de cambios](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png) -11. Haz clic en **Commit changes** (Confirmar cambios). Una vez que estos cambios se fusionen en la rama predeterminada, la plantilla estará disponible para que la usen los colaboradores cuando abran nuevas propuestas en el repositorio. +3. In the "Features" section, under "Issues," click **Set up templates**. +![Start template setup button](/assets/images/help/repository/set-up-templates.png) +4. Use the Add template drop-down menu, and click on the type of template you'd like to create. +![Add template drop-down menu](/assets/images/help/repository/add-template-drop-down-menu.png) +5. To preview or edit the template before committing it to the repository, click **Preview and edit**. +![Preview and edit button](/assets/images/help/repository/preview-and-edit-button.png) +6. To edit the template, click {% octicon "pencil" aria-label="The edit icon" %}, and type in the fields to edit their contents. +![Issue template edit button](/assets/images/help/repository/issue-template-edit-button.png) +7. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to your issue template, enter these details under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, or `assignees` in a YAML frontmatter format. +![Additional info for issue template](/assets/images/help/repository/additional-issue-template-info.png) +8. When you're finished editing and previewing your template, click **Propose changes** in the upper right corner of the page. +![Propose changes button](/assets/images/help/repository/propose-changes-button.png) +9. Enter a commit message describing your changes. +![Issue template commit message field](/assets/images/help/repository/issue-template-commit-message-field.png) +10. Below the commit message fields, decide whether to commit your template directly to the default branch, or to create a new branch and open a pull request. For more information about pull requests, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." +![Issue template commit to main or open pull request choice](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png) +11. Click **Commit changes**. Once these changes are merged into the default branch, the template will be available for contributors to use when they open new issues in the repository. {% ifversion fpt or ghec %} -## Crear formatos de propuestas +## Creating issue forms {% data reusables.community.issue-forms-beta %} -Con los formatos de propuestas, puedes crear plantillas de propuestas que tengan campos de formato web personalizables. Puedes fomentar que los contribuyentes incluyan información específica y estructurada si utilizas formatos de propuestas en tu repositorio. Los formatos de propuesta se escriben en YAML utilizando el modelado de formatos de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Sintaxis para el modelado de formatos de {% data variables.product.prodname_dotcom %}](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)". {% data reusables.actions.learn-more-about-yaml %} +With issue forms, you can create issue templates that have customizable web form fields. You can encourage contributors to include specific, structured information by using issue forms in your repository. Issue forms are written in YAML using the {% data variables.product.prodname_dotcom %} form schema. For more information, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)." {% data reusables.actions.learn-more-about-yaml %} -Para utilizar un formato de propuesta en tu repositorio, debes crear un archivo nuevo y agregarlo a la carpeta `.github/ISSUE_TEMPLATE` en tu repositorio. +To use an issue form in your repository, you must create a new file and add it to the `.github/ISSUE_TEMPLATE` folder in your repository. -Aquí tienes un ejemplo de un archivo de confguración de un formato de propuesta. +Here is an example of an issue form configuration file. {% data reusables.community.issue-forms-sample %} -Aquí está la versión interpretada de un formato de propuesta. ![Un formato de propuesta interpretado](/assets/images/help/repository/sample-issue-form.png) +Here is the rendered version of the issue form. + ![A rendered issue form](/assets/images/help/repository/sample-issue-form.png) -1. Elige un repositorio en donde quieras crear un formato de propuesta. Puedes utilizar un repositorio existente al cual tengas acceso de escritura o puedes crear un repositorio nuevo. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)." -2. En tu repositorio, crea un archivo que se llame `.github/ISSUE_TEMPLATE/FORM-NAME.yml`, reemplazando `FORM-NAME` con el nombre para tu formato de propueta. Para obtener más información acerca de cómo crear archivos nuevos en GitHub, consulta la sección "[Crear archivos nuevos](/github/managing-files-in-a-repository/creating-new-files)". -3. En el campo del archivo nuevo, teclea el contenido de tu formato de propuesta. Para obtener más información, consulta la sección "[Sintaxis para formatos de propuestas](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)". -4. Confirma tu archivo en la rama predeterminada de tu repositorio. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." +1. Choose a repository where you want to create an issue form. You can use an existing repository that you have write access to, or you can create a new repository. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." +2. In your repository, create a file called `.github/ISSUE_TEMPLATE/FORM-NAME.yml`, replacing `FORM-NAME` with the name for your issue form. For more information about creating new files on GitHub, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +3. In the body of the new file, type the contents of your issue form. For more information, see "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)." +4. Commit your file to the default branch of your repository. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." {% endif %} {% ifversion fpt or ghae or ghes or ghec %} -## Configurar el selector de plantillas +## Configuring the template chooser {% data reusables.repositories.issue-template-config %} -Puedes alentar a los colaboradores para que utilicen plantillas de informe de problemas si configuras el parámetro `blank_issues_enabled` como `false`. Si configuras `blank_issues_enabled` como `true`, las personas podrán abrir un reporte de problema en blanco. +You can encourage contributors to use issue templates by setting `blank_issues_enabled` to `false`. If you set `blank_issues_enabled` to `true`, people will have the option to open a blank issue. {% note %} -**Nota:**Si utilizaste el flujo de trabajo tradicional para crear un archivo de `issue_template.md` manualmente en la carpeta de `.github` y habilitar así las propuestas en blanco en tu archivo de *config.yml*, la plantilla en el archivo `issue_template.md` se utilizará cuando las personas decidan abrir una propuesta en blanco. Si inhabilitas los reportes de problemas en blanco, la plantilla nunca se utilizará. +**Note:** If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your *config.yml* file, the template in `issue_template.md` will be used when people chose to open a blank issue. If you disable blank issues, the template will never be used. {% endnote %} -Si prefieres recibir ciertos reportes fuera de {% data variables.product.product_name %}, puedes dirigir a las personas a sitios externos con `contact_links`. +If you prefer to receive certain reports outside of {% data variables.product.product_name %}, you can direct people to external sites with `contact_links`. -Aquí hay un ejemplo del archivo *config.yml*. +Here is an example *config.yml* file. ```shell blank_issues_enabled: false @@ -90,18 +99,20 @@ contact_links: about: Please report security vulnerabilities here. ``` -Tu archivo de configuración personalizará el selector de plantilla cuando el archivo se combina en la rama predeterminada del repositorio. +Your configuration file will customize the template chooser when the file is merged into the repository's default branch. {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. Teclea `.github/ISSUE_TEMPLATE/config.yml` en el campo de nombre de archivo. ![Nombre de archivo de configuración](/assets/images/help/repository/template-config-file-name.png) -4. Teclea el contenido de tu archivo de configuración en el cuerpo del nuevo archivo. ![Contenido de archivo de configuración](/assets/images/help/repository/template-config-file-content.png) +3. In the file name field, type `.github/ISSUE_TEMPLATE/config.yml`. + ![Configuration filename](/assets/images/help/repository/template-config-file-name.png) +4. In the body of the new file, type the contents of your configuration file. + ![Configuration file content](/assets/images/help/repository/template-config-file-content.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} {% endif %} -## Leer más +## Further reading -- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" -- "[Crear de forma manual una plantilla de propuesta única para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)" +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[Manually creating a single issue template for your repository](/articles/manually-creating-a-single-issue-template-for-your-repository)" diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md index d93f8b62aa..6af276cf0f 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md @@ -1,7 +1,6 @@ --- -title: Sintaxis para formatos de propuesta -intro: 'Puedes definir diferentes tipos de entrada, validaciones, asingados predeterminados y etiquetas predeterminadas para tus formatos de propuesta.' -product: 'Los formatos de propuesta están disponibles en beta para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}' +title: Syntax for issue forms +intro: 'You can define different input types, validations, default assignees, and default labels for your issue forms.' versions: fpt: '*' ghec: '*' @@ -11,21 +10,21 @@ topics: {% data reusables.community.issue-forms-beta %} -## Acerca de la sintaxis YAML para formatos de propuesta +## About YAML syntax for issue forms -Puedes crear formatos de propuesta personalizados agregando un archivo de definición de formato YAML a la carpeta `/.github/ISSUE_TEMPLATE` en tu repositorio. {% data reusables.actions.learn-more-about-yaml %} Puedes definir diferentes tipos de entrada, validaciones, asingados predeterminados y etiquetas predeterminadas para tus formatos de propuesta. +You can create custom issue forms by adding a YAML form definition file to the `/.github/ISSUE_TEMPLATE` folder in your repository. {% data reusables.actions.learn-more-about-yaml %} You can define different input types, validations, default assignees, and default labels for your issue forms. -Cuando un colaborador llega un formato de propuesta, sus respuestas para cada entrada se convierten en lenguaje de marcado y se agregan al cuerpo de una propuesta. Los contribuyentes pueden editar las propuestas que se crearon con estos formatos de propuesta y otras personas pueden interactuar con las propuestas como con una de ellas que se creó mediante otros métodos. +When a contributor fills out an issue form, their responses for each input are converted to markdown and added to the body of an issue. Contributors can edit their issues that were created with issue forms and other people can interact with the issues like an issue created through other methods. -Los formatos de propuesta no son compatibles para las solicitudes de cambios. Puedes crear plantillas de solicitudes de cambios en tus repositorios para que las utilicen los colaboradores. Para obtener más información, consulta [Crear plantillas de solicitud de extracción para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)". +Issue forms are not supported for pull requests. You can create pull request templates in your repositories for collaborators to use. For more information, see "[Creating a pull request template for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)." -Este archivo de configuración YAML define un formato de propuesta utilizando varias entradas para reportar un error. +This example YAML configuration file defines an issue form using several inputs to report a bug. {% data reusables.community.issue-forms-sample %} -## Sintaxis de nivel superior +## Top-level syntax -Todos los archivos de configuración de formatos de propuestas deben comenzar con los pares de llave-valor `name`, `description`, y `body`. +All issue form configuration files must begin with `name`, `description`, and `body` key-value pairs. ```YAML{:copy} name: @@ -33,28 +32,28 @@ description: body: ``` -Puedes configurar las siguientes llaves de nivel superior para cada formato de propuesta. +You can set the following top-level keys for each issue form. -| Clave | Descripción | Requerido | Type | -|:--------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------- |:---------------------------------------- | -| `name (nombre)` | Un nombre para la plantilla de formato de propuesta. Debe ser único entre el resto de las plantillas, incluyendo de las plantillas de lenguaje de marcado. | Requerido | Secuencia | -| `descripción` | Una descripción para la plantilla de formato de propuesta, la cual aparece en la interfaz de elección de plantilla. | Requerido | Secuencia | -| `cuerpo` | Definición de los tipos de entrada en el formato. | Requerido | Arreglo | -| `asignatarios` | Las personas que se asignarán automáticamente a las propuestas que se crearán con esta plantilla. | Opcional | Arreglo o secuencia delimitada por comas | -| `etiquetas` | Las etiquetas que se agregarán automáticamente a las propuestas que se crearán con esta plantilla. | Opcional | Secuencia | -| `título` | Un título predeterminado que se pre-llenará en el formato de emisión de propuestas. | Opcional | Secuencia | +| Key | Description | Required | Type | +| :-- | :-- | :-- | :-- | :-- | +| `name` | A name for the issue form template. Must be unique from all other templates, including Markdown templates. | Required | String | +| `description` | A description for the issue form template, which appears in the template chooser interface. | Required | String | +| `body` | Definition of the input types in the form. | Required | Array | +| `assignees` | People who will be automatically assigned to issues created with this template. | Optional | Array or comma-delimited string | +| `labels` | Labels that will automatically be added to issues created with this template. | Optional | String | +| `title` | A default title that will be pre-populated in the issue submission form. | Optional | String | -Para los tipos de entrada de `body` disponibles y sus sintaxis, consulta la sección "[Sintaxis para el modelo de formato de {% data variables.product.prodname_dotcom %}](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)". +For the available `body` input types and their syntaxes, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)." -## Convertir una plantilla de propuesta de lenguaje de marcado en una plantilla de formato de propuesta YAML +## Converting a Markdown issue template to a YAML issue form template -Puedes utilizar plantillas de propuestas tanto de YAML como de lenguaje de marcado en tu repositorio. Si quieres convertir una plantilla de propuesta con lenguaje de marcado en una plantilla de formato de propuesta YAML, debes crear un archivo YAML nuevo para definir el formato de la propuesta. Puedes transponer manualmente una plantilla de propuesta de lenguaje de marcado hacia un formato de propuesta YAML. Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)". +You can use both Markdown and YAML issue templates in your repository. If you want to convert a Markdown issue template to a YAML issue form template, you must create a new YAML file to define the issue form. You can manually transpose an existing Markdown issue template to a YAML issue form. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)." -Si quieres utilizar el mismo nombre de archivo para tu formato de propuesta YAML, debes borrar la plantilla de propuesta en lenguaje de marcado cuando confirmes el archivo nuevo en tu repositorio. +If you want to use the same file name for your YAML issue form, you must delete the Markdown issue template when you commit the new file to your repository. -A continuación podrás encontrar un ejemplo de plantilla de propuesta de lenguaje de marcado y una plantilla de formato de propuesta YAML correspondiente. +An example of a Markdown issue template and a corresponding YAML issue form template are below. -### Plantilla de propuesta de lenguaje de marcado +### Markdown issue template ```markdown{:copy} --- @@ -95,11 +94,11 @@ Example: ### Anything else: {% raw %}<{% endraw %}!-- -Links? Referencias? Anything that will give us more context about the issue that you are encountering! +Links? References? Anything that will give us more context about the issue that you are encountering! --{% raw %}>{% endraw %} ``` -### Plantilla de formato de propuesta YAML +### YAML issue form template ```yaml{:copy} name: 🐞 Bug @@ -156,13 +155,13 @@ body: attributes: label: Anything else? description: | - Links? Referencias? Anything that will give us more context about the issue you are encountering! + Links? References? Anything that will give us more context about the issue you are encountering! - Tip: Puedes adjuntar imágenes o archivos de bitácora si haces clic en esta área para resaltarla y luego arrastrar los archivos hacia ella. + Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. validations: required: false ``` -## Leer más +## Further reading - [YAML](https://yaml.org/) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md index b44bb069cb..bff9c68839 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md @@ -1,27 +1,26 @@ --- -title: Cómo clonar y bifurcar repositorios desde GitHub Desktop -intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para clonar y ramificar los repositorios que están en {% data variables.product.prodname_dotcom %}.' +title: Cloning and forking repositories from GitHub Desktop +intro: 'You can use {% data variables.product.prodname_desktop %} to clone and fork repositories that exist on {% data variables.product.prodname_dotcom %}.' redirect_from: - /desktop/contributing-to-projects/cloning-a-repository-from-github-desktop - /desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop - /desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop versions: fpt: '*' -shortTitle: Clonar & bifurcar desde Desktop +shortTitle: Clone & fork from Desktop --- +## About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. -## Acerca de los repositorios locales -Los repositorios de {% data variables.product.prodname_dotcom %} son remotos. Puedes clonar o bifurcar un repositorio con {% data variables.product.prodname_desktop %} para crear un repositorio local en tu computadora. +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. For more information, see "[Syncing your branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)." -Puedes crear una copia local de cualquier repositorio de {% data variables.product.product_name %} al que tengas acceso si lo clonas. Si un repositorio te pertenece o si tienes permisos de escritura en él, puedes sincronizar la ubicación local y remota del mismo. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)". +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. For more information, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)." -Cuando clonas un repositorio, cualquier cambio que subas a {% data variables.product.product_name %} afectará al original. Para hacer cambios sin afectar al proyecto original, puedes crear una copia separada si bifurcas el repositorio. Puedes crear una solicitud de cambios para proponer que los mantenedores incorporen los cambios de tu bifurcación en el repositorio ascendente original. Para obtener más información, visita "[Acerca de las ramificaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)." +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". -Cuando intentas utilizar {% data variables.product.prodname_desktop %} para clonar un repositorio en el que no tienes acceso de escritura, {% data variables.product.prodname_desktop %} te pedirá crear una bifurcación automáticamente. Puedes elegir utilizar tu bifurcación para contribuir con el repositorio ascendente original o trabajar independientemente en tu propio proyecto. Cualquier bifurcación existente estará predeterminada para contribuir con cambios hacia su repositorio ascendente. Puedes modificar esta elección en cualquier momento. Para obtener más información, consulta la sección "[Administrar el comportamiento de las bifurcaciones](#managing-fork-behavior)". +You can also clone a repository directly from {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". -También puedes clonar un repositorio directamente desde {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. Para obtener más información, visita "[Cómo clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". - -## Clonar un repositorio +## Cloning a repository {% data reusables.desktop.choose-clone-repository %} {% data reusables.desktop.cloning-location-tab %} @@ -29,8 +28,8 @@ También puedes clonar un repositorio directamente desde {% data variables.produ {% data reusables.desktop.choose-local-path %} {% data reusables.desktop.click-clone %} -## Bifurcar un repositorio -Si clonas un repositorio en el cual no tengas acceso de escritura, {% data variables.product.prodname_desktop %} creará una bifurcación. Después de crear o clonar una bifurcación, {% data variables.product.prodname_desktop %} te preguntará cómo piensas utilizarla. +## Forking a repository +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% data reusables.desktop.choose-clone-repository %} {% data reusables.desktop.cloning-location-tab %} @@ -39,19 +38,19 @@ Si clonas un repositorio en el cual no tengas acceso de escritura, {% data varia {% data reusables.desktop.click-clone %} {% data reusables.desktop.fork-type-prompt %} -## Administrar el comportamiento de una bifurcación -Puedes cambiar la forma en la que se comporta una bifurcación con respecto su repositorio ascendente de {% data variables.product.prodname_desktop %}. +## Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. {% data reusables.desktop.open-repository-settings %} {% data reusables.desktop.select-fork-behavior %} -## Crear un alias para un repositorio local -Puedes crear un alias para de un repositorio local para ayudarte a diferenciar entre reposiotorios con el mismo nombre en {% data variables.product.prodname_desktop %}. Crear un alias no afecta el nombre del repositorio en {% data variables.product.prodname_dotcom %}. En la lista de repositorios, los alias aparecen en letra itálica. +## Creating an alias for a local repository +You can create an alias for a local repository to help differentiate between repositories of the same name in {% data variables.product.prodname_desktop %}. Creating an alias does not affect the repository's name on {% data variables.product.prodname_dotcom %}. In the repositories list, aliases appear in italics. -1. En la esquina superior izquierda de {% data variables.product.prodname_desktop %}, a la derecha del nombre del repositorio actual, haz clic en {% octicon "triangle-down" aria-label="The triangle-down icon" %}. -2. Haz clic derecho en el repositorio para el cual quieras crear un alias y luego haz clic en **Crear alias**. -3. Teclea un alias para el repositorio. -4. Haz clic en **Crear alias**. +1. In the upper-left corner of {% data variables.product.prodname_desktop %}, to the right of the current repository name, click {% octicon "triangle-down" aria-label="The triangle-down icon" %}. +2. Right-click the repository you want to create an alias for, then click **Create Alias**. +3. Type an alias for the repository. +4. Click **Create Alias**. -## Leer más -- [Acerca de los repositorios remotos](/github/getting-started-with-github/about-remote-repositories) +## Further reading +- [About remote repositories](/github/getting-started-with-github/about-remote-repositories) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md index 268a74e3d3..e2f50add97 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md @@ -1,6 +1,6 @@ --- -title: Administrar ramas -intro: Puedes crear una rama nueva desde la rama predeterminada de un repositorio para que puedas experimentar con los cambios de forma segura. +title: Managing branches +intro: You can create a branch off of a repository's default branch so you can safely experiment with changes. redirect_from: - /desktop/contributing-to-projects/creating-a-branch-for-your-work - /desktop/contributing-to-projects/switching-between-branches @@ -9,112 +9,115 @@ redirect_from: versions: fpt: '*' --- +## About managing branches +You can use branches to safely experiment with changes to your project. Branches isolate your development work from other branches in the repository. For example, you could use a branch to develop a new feature or fix a bug. -## Acerca de administrar ramas -Puedes utilizar las ramas para experimentar de forma segura con los cambios de tu proyecto. Las ramas aislan tu trabajo de desarrollo de otras ramas en el repositorio. Por ejemplo, puedes utilizar una rama para desarrollar una nueva característica o para corregir un error. +You always create a branch from an existing branch. Typically, you might create a branch from the default branch of your repository. You can then work on this new branch in isolation from changes that other people are making to the repository. -Siempre puedes crear una rama a partir de otra rama existente. Habitualmente, puedes crear una rama desde la rama predeterminada de tu repositorio. Podrás entonces trabajar en esta rama nueva aislado de los cambios que otras personas hacen al repositorio. +You can also create a branch starting from a previous commit in a branch's history. This can be helpful if you need to return to an earlier view of the repository to investigate a bug, or to create a hot fix on top of your latest release. -También puedes crear una rama, comenzando desde una confirmación previa, en el historial de una rama. Esto puede ser útil si necesitas regresar a una vista anterior del repositorio para investigar un error o para crear un hot fix sobre tu lanzamiento más reciente. +Once you're satisfied with your work, you can create a pull request to merge your changes in the current branch into another branch. For more information, see "[Creating an issue or pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" and "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Una vez que estás satisfecho con to trabajo puedes crear una solicitud de extracción para fusionar tus cambios en la rama actual en alguna otra rama. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" y "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)". - -Siempre podrás crear una rama en {% data variables.product.prodname_desktop %} si tienes acceso de lectura en un repositorio, pero solo podrás cargar la rama a {% data variables.product.prodname_dotcom %} si tienes acceso de escritura en el repositorio en cuestión. +You can always create a branch in {% data variables.product.prodname_desktop %} if you have read access to a repository, but you can only push the branch to {% data variables.product.prodname_dotcom %} if you have write access to the repository. {% data reusables.desktop.protected-branches %} -## Cómo crear una rama +## Creating a branch {% tip %} -**Tip:** La primera rama nueva que creas se basará en la rama predeterminada. Si tienes más de una rama, puedes elegir basar la nueva rama en aquella que has revisado actualmente o en la rama predeterminada. +**Tip:** The first new branch you create will be based on the default branch. If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch. {% endtip %} {% mac %} {% data reusables.desktop.click-base-branch-in-drop-down %} - ![Menú desplegable para cambiar tu rama actual](/assets/images/help/desktop/select-branch-from-dropdown.png) + ![Drop-down menu to switch your current branch](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.create-new-branch %} - ![Opción New Branch (Rama nueva) en el menú Branch (Rama)](/assets/images/help/desktop/new-branch-button-mac.png) + ![New Branch option in the Branch menu](/assets/images/help/desktop/new-branch-button-mac.png) {% data reusables.desktop.name-branch %} - ![Campo para crear un nombre para la rama nueva](/assets/images/help/desktop/create-branch-name-mac.png) + ![Field for creating a name for the new branch](/assets/images/help/desktop/create-branch-name-mac.png) {% data reusables.desktop.select-base-branch %} - ![Opciones de rama base](/assets/images/help/desktop/create-branch-choose-branch-mac.png) + ![Base branch options](/assets/images/help/desktop/create-branch-choose-branch-mac.png) {% data reusables.desktop.confirm-new-branch-button %} - ![Botón Create Branch (Crear rama)](/assets/images/help/desktop/create-branch-button-mac.png) + ![Create Branch button](/assets/images/help/desktop/create-branch-button-mac.png) {% endmac %} {% windows %} {% data reusables.desktop.click-base-branch-in-drop-down %} - ![Menú desplegable para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down-win.png) + ![Drop-down menu to switch your current branch](/assets/images/help/desktop/click-branch-in-drop-down-win.png) {% data reusables.desktop.create-new-branch %} - ![Opción New Branch (Rama nueva) en el menú Branch (Rama)](/assets/images/help/desktop/new-branch-button-win.png) + ![New Branch option in the Branch menu](/assets/images/help/desktop/new-branch-button-win.png) {% data reusables.desktop.name-branch %} - ![Campo para crear un nombre para la rama nueva](/assets/images/help/desktop/create-branch-name-win.png) + ![Field for creating a name for the new branch](/assets/images/help/desktop/create-branch-name-win.png) {% data reusables.desktop.select-base-branch %} - ![Opciones de rama base](/assets/images/help/desktop/create-branch-choose-branch-win.png) + ![Base branch options](/assets/images/help/desktop/create-branch-choose-branch-win.png) {% data reusables.desktop.confirm-new-branch-button %} - ![Botón Create Branch (Crear rama)](/assets/images/help/desktop/create-branch-button-win.png) + ![Create branch button](/assets/images/help/desktop/create-branch-button-win.png) {% endwindows %} -## Crear una rama a partir de una confirmación previa +## Creating a branch from a previous commit {% data reusables.desktop.history-tab %} -2. Haz clic derecho en la confirmación desde la cual te gustaría crear una rama nueva y selecciona **Crear rama desde confirmación**. ![Crear una rama de un menú de contexto de confirmación](/assets/images/help/desktop/create-branch-from-commit-context-menu.png) +2. Right-click on the commit you would like to create a new branch from and select **Create Branch from Commit**. + ![Create branch from commit context menu](/assets/images/help/desktop/create-branch-from-commit-context-menu.png) {% data reusables.desktop.name-branch %} {% data reusables.desktop.confirm-new-branch-button %} - ![Crear una rama desde una confirmación](/assets/images/help/desktop/create-branch-from-commit-overview.png) + ![Create branch from commit](/assets/images/help/desktop/create-branch-from-commit-overview.png) -## Publicar una rama +## Publishing a branch -Si creas una rama en {% data variables.product.product_name %}, necesitarás publicarla para que se muestre disponible para colaboración en {% data variables.product.prodname_dotcom %}. +If you create a branch on {% data variables.product.product_name %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.prodname_dotcom %}. -1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego en la rama que quieres publicar. ![Menú desplegable para seleccionar qué rama publicar](/assets/images/help/desktop/select-branch-from-dropdown.png) -2. Da clic en **Publicar rama**. ![El botón de publicar rama](/assets/images/help/desktop/publish-branch-button.png) +1. At the top of the app, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to publish. + ![Drop-down menu to select which branch to publish](/assets/images/help/desktop/select-branch-from-dropdown.png) +2. Click **Publish branch**. + ![The Publish branch button](/assets/images/help/desktop/publish-branch-button.png) -## Alternar entre ramas -Puedes ver y realizar confirmaciones en cualquiera de las ramas de tu repositorio. Si tienes cambios guardados, no confirmados, deberás decidir qué hacer con tus cambios antes de alternar las ramas. Puedes confirmar tus cambios en la rama actual, acumular tus cambios para guardarlos temporalmente en la rama actual, o llevar los cambios a tu rama nueva. Si quieres confirmar tus cambios antes de cambiar de rama, consulta la sección "[Confirmar y revisar los cambios a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)". +## Switching between branches +You can view and make commits to any of your repository's branches. If you have uncommitted, saved changes, you'll need to decide what to do with your changes before you can switch branches. You can commit your changes on the current branch, stash your changes to temporarily save them on the current branch, or bring the changes to your new branch. If you want to commit your changes before switching branches, see "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)." {% tip %} -**Consejo**: Puedes configurar un comportamiento predeterminado para alternar entre ramas en la configuración **Avanzada**. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". +**Tip**: You can set a default behavior for switching branches in the **Advanced** settings. For more information, see "[Configuring basic settings](/desktop/getting-started-with-github-desktop/configuring-basic-settings)." {% endtip %} {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.switching-between-branches %} - ![Lista de ramas en el repositorio](/assets/images/help/desktop/select-branch-from-dropdown.png) -3. Si tienes cambios guardados, sin confirmar, elige **Leave my changes** (Dejar mis cambios) o **Bring my changes** (Traer mis cambios) y luego haz clic en **Switch Branch** (Cambiar rama). ![Alternar ramas con opciones de cambios](/assets/images/help/desktop/stash-changes-options.png) + ![List of branches in the repository](/assets/images/help/desktop/select-branch-from-dropdown.png) +3. If you have saved, uncommitted changes, choose **Leave my changes** or **Bring my changes**, then click **Switch Branch**. + ![Switch branch with changes options](/assets/images/help/desktop/stash-changes-options.png) -## Cómo eliminar una rama +## Deleting a branch -No puedes borrar una rama que esté actualmente asociada con una solicitud de extracción abierta. No puedes revertir el haber borrado una rama. +You can't delete a branch if it's currently associated with an open pull request. You cannot undo deleting a branch. {% mac %} {% data reusables.desktop.select-branch-to-delete %} - ![Menú desplegable para seleccionar qué rama borrar](/assets/images/help/desktop/select-branch-from-dropdown.png) + ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.delete-branch-mac %} - ![Opción de "borrar..." en el menú de la rama](/assets/images/help/desktop/delete-branch-mac.png) + ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-mac.png) {% endmac %} {% windows %} {% data reusables.desktop.select-branch-to-delete %} - ![Menú desplegable para seleccionar qué rama borrar](/assets/images/help/desktop/select-branch-from-dropdown.png) + ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.delete-branch-win %} - ![Opción de "borrar..." en el menú de la rama](/assets/images/help/desktop/delete-branch-win.png) + ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-win.png) {% endwindows %} -## Leer más +## Further reading -- [Clonar un repositorio de {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop) -- "[Rama](/articles/github-glossary/#branch)" en el glosario {% data variables.product.prodname_dotcom %} -- "[Acerca de las ramas](/articles/about-branches)" -- "[Ramas en resumen](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" en la documentación de Git -- "[Acumular cambios](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes)" +- "[Cloning a repository from {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)" +- "[Branch](/articles/github-glossary/#branch)" in the {% data variables.product.prodname_dotcom %} glossary +- "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)" +- "[Branches in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" in the Git documentation +- "[Stashing changes](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes)" diff --git a/translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md index 3e0dfe5151..c7ccfa8b72 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md +++ b/translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md @@ -1,6 +1,6 @@ --- -title: Tipos de eventos de los informes de problemas -intro: 'Para la API de Eventos de Informes de Problemas y la API de Línea de Tiempo, aprende sobre cada tipo de evento, la acción que los activa en {% data variables.product.prodname_dotcom %} y las propiedades exclusivas de cada uno de ellos.' +title: Issue event types +intro: 'For the Issues Events API and Timeline API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.' redirect_from: - /v3/issues/issue-event-types - /developers/webhooks-and-events/issue-event-types @@ -12,28 +12,27 @@ versions: topics: - Events --- +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. -Los eventos de informes de problemas se activan dependiendo de la actividad en las solicitudes de extracción e informes de problemas y se encuentran disponibles en la [API de eventos de informes de problemas](/rest/reference/issues#events) y en la [API de Eventos de la Línea de Tiempo](/rest/reference/issues#timeline). Cada tipo de evento especifica si éste está disponible en la API de Eventos de los Informes de Problemas o en la de Eventos de la Línea de tiempo. +GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. -La API de REST de GitHub considera a cada solicitud de extracción como un informe de problemas, pero no todos los informes de problemas consitutyen una solicitud de extracción. Por esta razón, las terminales de los Eventos de Informes de Problemas y las de Eventos de la Línea de Tiempo podrían devolver tanto informes de problemas como solicitudes de extracción en su respuesta. Las solicitudes de extracción tienen una propiedad de `pull_request` en el objeto del `issue`. Ya que todas las solicitudes de extracción son informes de problemas, las cantidades de unas y de otras no se duplican en un repositorio. Por ejemplo, si abres tu primer informe de problemas en un repositorio, la cantidad será de 1. Si después abres una solicitud de extracción, a cantidad será de 2. Cada tipo de evento especifica si éste ocurre en solicitudes de extracción, informes de problemas, o en ambos. +## Issue event object common properties -## Propiedades comunes del objeto del evento de los informes de problemas - -Los eventos de los informes de problemas tienen la misma estructura de objeto, excepto aquellos eventos que solo se encuentran disponibles en la API de Eventos de la Línea de Tiempo. Algunos eventos también incluyen propiedades adicionales que proporcionan más contexto acerca de los recursos de éstos. Consulta el evento específico para encontrar más detalles sobre cualquier propiedad que difiera de este formato de objeto. +Issue events all have the same object structure, except events that are only available in the Timeline Events API. Some events also include additional properties that provide more context about the event resources. Refer to the specific event to for details about any properties that differ from this object format. {% data reusables.issue-events.issue-event-common-properties %} ## added_to_project -El informe de problemas o solicitud de extracción se agregó a un tablero de proyecto. {% data reusables.projects.disabled-projects %} +The issue or pull request was added to a project board. {% data reusables.projects.disabled-projects %} -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitud de extracción
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull request
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -43,171 +42,171 @@ El informe de problemas o solicitud de extracción se agregó a un tablero de pr ## assigned -El informe de problemas o solicitud de extracción se asignó al usuario. +The issue or pull request was assigned to a user. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.assignee-properties %} ## automatic_base_change_failed -GitHub intentó cambiar la rama base de la solicitud de extracción automáticamente y sin éxito. +GitHub unsuccessfully attempted to automatically change the base branch of the pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## automatic_base_change_succeeded -GitHub intentó cambiar la rama base de la solicitud de extracción automáticamente con éxito. +GitHub successfully attempted to automatically change the base branch of the pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## base_ref_changed -La rama base de referencia de la solicitud de extracción cambió. +The base reference branch of the pull request changed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## closed -Se cerró el informe de problemas o la solicitud de extracción. Cuando está presente la `commit_id`, esta identifica a la confirmación que cerró el informe de problemas utilizando la sintaxis de "cerrados/arreglados". Para obtener más información acerca de la sintaxis, consulta la sección "[Enlazar una solicitud de extracción con un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". +The issue or pull request was closed. When the `commit_id` is present, it identifies the commit that closed the issue using "closes / fixes" syntax. For more information about the syntax, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## commented -Un comentario se agregó al informe de problemas o solicitud de extracción. +A comment was added to the issue or pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nombre | Type | Descripción | -| ------------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `url` | `secuencia` | La URL de la API de REST que recuperará el comentario del informe de problemas. | -| `html_url` | `secuencia` | La URL de HTML para el comentario del informe de problemas. | -| `issue_url` | `secuencia` | La URL de HTML para el informe de problemas. | -| `id` | `número` | El identificador único del evento. | -| `node_id` | `secuencia` | La [ID de Nodo Global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) del evento. | -| `usuario` | `objeto` | La persona que comentó en el informe de problemas. | -| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo se agregó el comentario. | -| `updated_at` | `secuencia` | La marca de tiempo que indica cuándo se actualizó o creó el comentario en caso de que éste jamás se haya actualizado. | -| `author_association` | `secuencia` | Los permisos que tiene el usuario en el repositorio del informe de problemas. Por ejemplo, el valor sería `"OWNER"` si el propietario del repositorio creó un comentario. | -| `cuerpo` | `secuencia` | El cuerpo de texto del comentario. | -| `event` | `secuencia` | El valor del evento es `"commented"`. | -| `actor (actor)` | `objeto` | La persona que generó el evento. | +Name | Type | Description +-----|------|-------------- +`url` | `string` | The REST API URL to retrieve the issue comment. +`html_url` | `string` | The HTML URL of the issue comment. +`issue_url` | `string` | The HTML URL of the issue. +`id` | `integer` | The unique identifier of the event. +`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event. +`user` | `object` | The person who commented on the issue. +`created_at` | `string` | The timestamp indicating when the comment was added. +`updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated. +`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment. +`body` | `string` | The comment body text. +`event` | `string` | The event value is `"commented"`. +`actor` | `object` | The person who generated the event. ## committed -Una confirmación se agregó a la rama `HEAD` de la solicitud de extracción. +A commit was added to the pull request's `HEAD` branch. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nombre | Type | Descripción | -| -------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sha` | `secuencia` | El SHA de la confirmación en la solicitud de extracción. | -| `node_id` | `secuencia` | La [ID de Nodo Global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) del evento. | -| `url` | `secuencia` | La URL de la API de REST que recuperará la confirmación. | -| `html_url` | `secuencia` | La URL de HTML de la confirmación. | -| `autor` | `objeto` | La persona que autorizó la confirmación. | -| `confirmante` | `objeto` | La persona que confirmó la confirmación en nombre del autor. | -| `árbol` | `objeto` | El árbol de Git de la confirmación. | -| `message` | `secuencia` | El mensaje de la confirmación. | -| `parents` | `matriz de objetos` | Una lista de confirmaciones padre. | -| `verificación` | `objeto` | El resultado de verificar la firma de la confirmación. Para obtener más información, consulta la sección "[Objeto de verificación de firmas](/rest/reference/git#get-a-commit)". | -| `event` | `secuencia` | El valor del evento es `"committed"`. | +Name | Type | Description +-----|------|-------------- +`sha` | `string` | The SHA of the commit in the pull request. +`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event. +`url` | `string` | The REST API URL to retrieve the commit. +`html_url` | `string` | The HTML URL of the commit. +`author` | `object` | The person who authored the commit. +`committer` | `object` | The person who committed the commit on behalf of the author. +`tree` | `object` | The Git tree of the commit. +`message` | `string` | The commit message. +`parents` | `array of objects` | A list of parent commits. +`verification` | `object` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#get-a-commit)." +`event` | `string` | The event value is `"committed"`. ## connected -El informe de problemas o solicitud de extracción se vinculó a otro informe de problemas o solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". +The issue or pull request was linked to another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## convert_to_draft -La solicitud de extracción se convirtió a modo borrador. +The pull request was converted to draft mode. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## converted_note_to_issue -El informe de problemas se creó convirtiendo una nota en un tablero de proyecto para un informe de problemas. {% data reusables.projects.disabled-projects %} +The issue was created by converting a note in a project board to an issue. {% data reusables.projects.disabled-projects %} -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -217,272 +216,274 @@ El informe de problemas se creó convirtiendo una nota en un tablero de proyecto ## cross-referenced -El informe de problemas o solicitud de extración se referenció desde otro informe de problemas o solicitud de extracción. +The issue or pull request was referenced from another issue or pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nombre | Type | Descripción | -| ------------------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor (actor)` | `objeto` | La persona que generó el evento. | -| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo se agregó la referencia cruzada. | -| `updated_at` | `secuencia` | La marca de tiempo que indica cuándo se actualizó o creó la referencia cruzada en caso de que ésta jamás se haya actualizado. | -| `source` | `objeto` | La solicitud de extracción o informe de problemas que agregó la referencia cruzada. | -| `source[type]` | `secuencia` | Este valor siempre será `"issue"` ya que las solicitudes de extracción son un tipo de informe de rpoblemas. En la API de Eventos de la Línea de Tiempo solo se devolverán los eventos de referencia cruzada que se activen con informes de problemas o solicitudes de extracción. Puedes verificar si existe el objeto `source[issue][pull_request` para determinar si el informe de problemas que activó el evento es una solicitud de extracción. | -| `source[issue]` | `objeto` | El objeto del `issue` que agregó la referencia cruzada. | -| `event` | `secuencia` | El valor del evento es `"cross-referenced"`. | +Name | Type | Description +-----|------|-------------- +`actor` | `object` | The person who generated the event. +`created_at` | `string` | The timestamp indicating when the cross-reference was added. +`updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated. +`source` | `object` | The issue or pull request that added a cross-reference. +`source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request` object exists. +`source[issue]` | `object` | The `issue` object that added the cross-reference. +`event` | `string` | The event value is `"cross-referenced"`. ## demilestoned -El informe de problemas o solicitud de extracción se elimnó de un hito. +The issue or pull request was removed from a milestone. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`milestone` | `object` | El objeto del hito. `milestone[title]` | `string` | El título del hito. +`milestone` | `object` | The milestone object. +`milestone[title]` | `string` | The title of the milestone. ## deployed -Se desplegó la solicitud de extracción. +The pull request was deployed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## deployment_environment_changed -El ambiente de despliegue de la solicitud de extracción cambió. +The pull request deployment environment was changed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## disconnected -El informe de problemas o solicitud de extracción se desvinculó de otro informe de problemas o solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". +The issue or pull request was unlinked from another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## head_ref_deleted -Se eliminó la rama `HEAD` de la solicitud de extracción. +The pull request's `HEAD` branch was deleted. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## head_ref_restored -Se restauró la rama `HEAD` de la solicitud de extracción a su última confirmación conocida. +The pull request's `HEAD` branch was restored to the last known commit. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## labeled -Se agregó una etiqueta al informe de problemas o solicitud de extracción. +A label was added to the issue or pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.label-properties %} ## locked -Se bloqueó el informe de problemas o la solicitud de extracción. +The issue or pull request was locked. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | La razón por la cual se bloqueó un informe de problemas o solicitud de extracción, si es que se proporcionó alguna. +`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided. ## mentioned -Se `@mentioned` al `actor` en el cuerpo de un informe de problemas o solicitud de extracción. +The `actor` was `@mentioned` in an issue or pull request body. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## marked_as_duplicate -Un usuario con permisos de escritura marcó un informe de problemas como el duplicado de otro, o el mismo caso con alguna solicitud de extracción. +A user with write permissions marked an issue as a duplicate of another issue, or a pull request as a duplicate of another pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## fusionado +## merged -Se fusionó la solicitud de extracción. El atributo de `commit_id` es el SHA1 de la confirmación `HEAD` que se fusionó. El `commit_repository` siempre es el mismo que el repositorio principal. +The pull request was merged. The `commit_id` attribute is the SHA1 of the `HEAD` commit that was merged. The `commit_repository` is always the same as the main repository. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## milestoned -El informe de problemas o solicitud de extracción se agregó a un hito. +The issue or pull request was added to a milestone. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`milestone` | `object` | El objeto del hito. `milestone[title]` | `string` | El título del hito. +`milestone` | `object` | The milestone object. +`milestone[title]` | `string` | The title of the milestone. ## moved_columns_in_project -El informe de problemas o solicitud de extracción se movió entre columnas en un tablero de proyecto. {% data reusables.projects.disabled-projects %} +The issue or pull request was moved between columns in a project board. {% data reusables.projects.disabled-projects %} -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.project-card-properties %} -`previous_column_name` | `string` | El nombre de la columna desde la cual se movió el informe de problemas. +`previous_column_name` | `string` | The name of the column the issue was moved from. ## pinned -Se fijó el informe de problemas. +The issue was pinned. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## ready_for_review -Se creó una solicitud de extracción que no está en modo borrador. +A draft pull request was marked as ready for review. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## referenced -Se referenció al informe de problemas desde un mensaje de confirmación. El atributo `commit_id` es la confirmación de tipo SHA1 de donde eso sucedió y el commit_repository es el lugar donde se cargó esa confirmación. +The issue was referenced from a commit message. The `commit_id` attribute is the commit SHA1 of where that happened and the commit_repository is where that commit was pushed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## removed_from_project -El informe de problemas o solicitud de extracción se eliminó de un tablero de proyecto. {% data reusables.projects.disabled-projects %} +The issue or pull request was removed from a project board. {% data reusables.projects.disabled-projects %} -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -490,236 +491,238 @@ El informe de problemas o solicitud de extracción se eliminó de un tablero de {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.project-card-properties %} -## renombrado +## renamed -Se cambió el informe de problemas o la solicitud de extracción. +The issue or pull request title was changed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`rename` | `object` | Los detalles del nombre. `rename[from]` | `string` | El nombre anterior. `rename[to]` | `string` | El nombre nuevo. +`rename` | `object` | The name details. +`rename[from]` | `string` | The previous name. +`rename[to]` | `string` | The new name. ## reopened -El informe de problemas o solicitud de extracción se reabrió. +The issue or pull request was reopened. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## review_dismissed -Se destituyó la revisión de la solicitud de extracción. +The pull request review was dismissed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-dismissed-properties %} ## review_requested -Se solicitó una revisión de una solicitud de extracción. +A pull request review was requested. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-request-properties %} ## review_request_removed -Se eliminó una solicitud de revisión para una solicitud de extracción. +A pull request review request was removed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-request-properties %} ## reviewed -Se revisió la solicitud de extracción. +The pull request was reviewed. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de cambios
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nombre | Type | Descripción | -| -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `número` | El identificador único del evento. | -| `node_id` | `secuencia` | La [ID de Nodo Global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) del evento. | -| `usuario` | `objeto` | La persona que comentó en el informe de problemas. | -| `cuerpo` | `secuencia` | El texto de resúmen de la revisión. | -| `commit_id` | `secuencia` | El SHA de la última confirmación en la soicitud de extracción al momento de la revisión. | -| `submitted_at` | `secuencia` | La marca de tiempo que indica cuándo se emitió la revisión. | -| `state` | `secuencia` | El estado de la revisión emitida. Puede ser uno de entre: `commented`, `changes_requested`, o `approved`. | -| `html_url` | `secuencia` | La URL de HTML para la revisión. | -| `pull_request_url` | `secuencia` | La URL de la API de REST que recuperará la solicitud de extracción. | -| `author_association` | `secuencia` | Los permisos que tiene el usuario en el repositorio del informe de problemas. Por ejemplo, el valor sería `"OWNER"` si el propietario del repositorio creó un comentario. | -| `_links` | `objeto` | El `html_url` y `pull_request_url`. | -| `event` | `secuencia` | El valor del evento es `"reviewed"`. | +Name | Type | Description +-----|------|-------------- +`id` | `integer` | The unique identifier of the event. +`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event. +`user` | `object` | The person who commented on the issue. +`body` | `string` | The review summary text. +`commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review. +`submitted_at` | `string` | The timestamp indicating when the review was submitted. +`state` | `string` | The state of the submitted review. Can be one of: `commented`, `changes_requested`, or `approved`. +`html_url` | `string` | The HTML URL of the review. +`pull_request_url` | `string` | The REST API URL to retrieve the pull request. +`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment. +`_links` | `object` | The `html_url` and `pull_request_url`. +`event` | `string` | The event value is `"reviewed"`. ## subscribed -Alguien se suscribió para recibir notificaciones para un informe de problemas o solicitud de extracción. +Someone subscribed to receive notifications for an issue or pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## transferred -El informe de problemas se transfirió a otro repositorio. +The issue was transferred to another repository. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## unassigned -De desasignó a un usuario del informe de problemas. +A user was unassigned from the issue. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.assignee-properties %} ## unlabeled -La etiqueta se eliminó del informe de problemas. +A label was removed from the issue. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.label-properties %} ## unlocked -Se desbloqueó el informe de problemas. +The issue was unlocked. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | La razón por la cual se bloqueó un informe de problemas o solicitud de extracción, si es que se proporcionó alguna. +`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided. ## unmarked_as_duplicate -Un informe de problemas que algún usuario había marcado previamente como duplicado de otro informe de problemas ya no se considera como duplicado, o el mismo caso con solicitudes de extracción. +An issue that a user had previously marked as a duplicate of another issue is no longer considered a duplicate, or a pull request that a user had previously marked as a duplicate of another pull request is no longer considered a duplicate. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## unpinned -El informe de problemas dejó de fijarse. +The issue was unpinned. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## unsubscribed -Alguien se desuscribió de recibir notificaciones para un informe de problemas o solicitud de extracción. +Someone unsubscribed from receiving notifications for an issue or pull request. -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% ifversion fpt or ghec %} ## user_blocked -El propietario de una organización bloqueó a un usuario de la misma. Esto se hizo [a través de uno de los comentarios del usuario bloqueado sobre el informe de problemas](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). +An organization owner blocked a user from the organization. This was done [through one of the blocked user's comments on the issue](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). -### Disponibilidad +### Availability -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propiedades del objeto del evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} diff --git a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 02a4ccc4a1..f401cb3648 100644 --- a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -1,49 +1,49 @@ --- -title: Mejores prácticas para las conversaciones comunitarias en GitHub -shortTitle: Mejores prácticas para las conversaciones comunitarias -intro: 'Puedes utilizar los debates para hacer una lluvia de ideas con tu equipo y, en algún momento, migrar la conversación a una propuesta cuando estés listo para delimitar el trabajo.' +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.' versions: fpt: '*' ghec: '*' --- -## Conversaciones comunitarias en {% data variables.product.prodname_discussions %} +## Community conversations in {% data variables.product.prodname_discussions %} -Ya que {% data variables.product.prodname_discussions %} constituye un foro abierto, existe la oportunidad de incorporar colaboraciones diferentes a aquellas de código en el repositorio de un proyecto y recabar retroalimentación e ideas distintas más rápidamente. Puedes ayudar llevar una conversación productiva si: +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: -- Haces preguntas puntuales y preguntas de seguimiento para recabar comentarios específicos -- Capturas experiencias distintas y las simplificas en puntos principales -- Abres una propuesta para que se tome una acción con base en la conversación, si es que aplica +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable -Para obtener más información acerca de abrir propuestas y hacer referencias cruzadas en un debate, consulta la sección [Abrir una propuesta desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." -## Aprender más sobre las conversaciones en GitHub +## Learning about conversations on GitHub -Puedes crear y participar en los debates, propuestas y solicitudes de cambio dependiendo del tipo de conversación que desees tener. +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. -Puedes utilizar lps {% data variables.product.prodname_discussions %} para debatir las ideas más amplias, hacer lluvias de ideas y resaltar los detalles específicos de un proyecto antes de hacer cualquier confirmación en una propuesta, la cual puede aumetar su alcance posteriormente. Los {% data variables.product.prodname_discussions %} son útiles para los equipos si: -- Estás en la fase de descubrimiento de un proyecto y aún estás aprendiendo en qué dirección quiere ir tu equipo. -- Quieres recolectar los comentarios de una comunidad más amplia sobre un proyecto -- Quieres mantener la separación entre las correcciones de errores y las conversaciones generales +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate -Las propuestas son útiles para debatir detalles específicos de un proyecto como registros de errores y mejoras planificadas. Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". Las solicitudes de extracción te permiten comentar directamente en los cambios propuestos. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" y "[Comentar en una solicitud de extracción](/articles/commenting-on-a-pull-request)". +Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" and "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." -{% data reusables.organizations.team-discussions-purpose %} Para obtener más información, consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)". +{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." -## Seguir los lineamientos de contribución +## Following contributing guidelines -Antes de que abras un debate, verifica si el repositorio tiene lineamientos de contribución. El archivo de CONTRIBUCIÓN incluye información sobre cómo el gustaría al mantenedor del repositorio que colabores con ideas para el proyecto. +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. -Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)." +For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." -## Pasos siguientes +## Next steps -Para seguir aprendiendo sobre los {% data variables.product.prodname_discussions %} y crear uno rápidamente para tu comunidad, consulta la sección "[Guía de inicio rápido para los {% data variables.product.prodname_discussions %}](/discussions/quickstart)". +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." -## Leer más +## Further reading -- "[Configurar tu proyecto para contribuciones positivas](/communities/setting-up-your-project-for-healthy-contributions)" -- [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)" -- "[Moderar comentarios y conversaciones](/communities/moderating-comments-and-conversations)" -- "[Escribir en {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" +- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)" +- "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)" +- "[Writing on {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/es-ES/content/discussions/index.md b/translations/es-ES/content/discussions/index.md index 6144e1afd1..d76f770704 100644 --- a/translations/es-ES/content/discussions/index.md +++ b/translations/es-ES/content/discussions/index.md @@ -1,7 +1,7 @@ --- -title: Documentación sobre los debates de GitHub +title: GitHub Discussions Documentation shortTitle: GitHub Discussions -intro: '{% data variables.product.prodname_discussions %} es un foro de comunicación colaborativa para la comunidad que circunda un proyecto de código abierto. Los miembros de la comunidad pueden hacer preguntas y proporcionar respuestas, compartir actualizaciones, tener conversaciones abiertas y dar seguimiento a las decisiones que afectan la forma de trabajar de la misma.' +intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Community members can ask and answer questions, share updates, have open-ended conversations, and follow along on decisions affecting the community''s way of working.' introLinks: quickstart: /discussions/quickstart featuredLinks: diff --git a/translations/es-ES/content/education/guides.md b/translations/es-ES/content/education/guides.md index 1c096ef070..97bdcc76d5 100644 --- a/translations/es-ES/content/education/guides.md +++ b/translations/es-ES/content/education/guides.md @@ -1,48 +1,48 @@ --- -title: Guías de GitHub Education -intro: 'Estas guías de {% data variables.product.prodname_education %} te ayudan a enseñar y aprender tanto {% data variables.product.product_name %} como desarrollo de software.' +title: Guides for GitHub Education +intro: 'These guides for {% data variables.product.prodname_education %} help you teach and learn both {% data variables.product.product_name %} and software development.' allowTitleToDifferFromFilename: true versions: fpt: '*' -shortTitle: Guías +shortTitle: Guides --- -## Inicia con {% data variables.product.product_name %} +## Get started with {% data variables.product.product_name %} -Los maestros, alumnos e investigadores pueden utilizar herramientas de {% data variables.product.product_name %} para enriquecer un currículum de desarrollo de software y desarrollar habilidades colaborativas para el mundo real. +Teachers, students, and researchers can use tools from {% data variables.product.product_name %} to enrich a software development curriculum and develop real-world collaboration skills. -- [Regístrate para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-a-new-github-account) -- [Guía de inicio rápido de Git y {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/quickstart) -- [Acerca de Educación GitHub para estudiantes](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students) -- [Postularse para un descuento de investigador o educador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Aplicar un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) +- [Sign up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account) +- [Git and {% data variables.product.prodname_dotcom %} quickstart ](/github/getting-started-with-github/quickstart) +- [About GitHub Education for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students) +- [Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) -## Ejecuta un curso de desarrollo de software con {% data variables.product.company_short %} +## Run a software development course with {% data variables.product.company_short %} -Administra un aula, asigna y revisa el trabajo de tus alumnos y enseña a la nueva generación de desarrolladores de software con {% data variables.product.prodname_classroom %}. +Administer a classroom, assign and review work from your students, and teach the new generation of software developers with {% data variables.product.prodname_classroom %}. -- [Puntos básicos para configurar {% data variables.product.prodname_classroom %} ](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom) -- [Administrar aulas](/education/manage-coursework-with-github-classroom/manage-classrooms) -- [Utiliza la tarea de inicio de Git y {% data variables.product.company_short %}](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment) -- [Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment) -- [Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment) -- [Crear una tarea desde un repositorio de plantilla](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository) -- [Deja retroalimentación con solicitudes de cambios](/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests) -- [Utiliza las calificaciones automáticas](/education/manage-coursework-with-github-classroom/use-autograding) +- [Basics of setting up {% data variables.product.prodname_classroom %} ](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom) +- [Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms) +- [Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment) +- [Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment) +- [Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment) +- [Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository) +- [Leave feedback with pull requests](/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests) +- [Use autograding](/education/manage-coursework-with-github-classroom/use-autograding) -## Aprende a desarrollar software +## Learn to develop software -Incorpora a {% data variables.product.prodname_dotcom %} en tu educación y utiliza las mismas herramientas que los profesionales. +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. -- [Recursos de aprendizaje para Git y {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/git-and-github-learning-resources) -- [Utiliza {% data variables.product.prodname_dotcom %} para tu trabajo escolar](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork) -- [Prueba {% data variables.product.prodname_desktop %}](/desktop) -- [Prueba {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) +- [Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/git-and-github-learning-resources) +- [Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork) +- [Try {% data variables.product.prodname_desktop %}](/desktop) +- [Try {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) -## Contribuye con la comunidad +## Contribute to the community -Participa en la comunidad, obtén capacitación de {% data variables.product.company_short %} y aprende o enseña nuevas habilidades. +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. - [{% data variables.product.prodname_education_community %}](https://education.github.community) -- [Acerca de Expertos en campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) -- [Acerca de Asesores de campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) +- [About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) +- [About Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md index 31288017c2..100143c690 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -1,6 +1,6 @@ --- -title: Conectar un sistema de administración de aprendizaje a GitHub Classroom -intro: 'Puedes configurar un sistema de administración de aprendizaje (LMS) que cumpla con LTI para conectarte a {% data variables.product.prodname_classroom %} y que puedas importar un registro de alumno para tu aula.' +title: Connect a learning management system to GitHub Classroom +intro: 'You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom.' versions: fpt: '*' redirect_from: @@ -11,130 +11,133 @@ redirect_from: - /education/manage-coursework-with-github-classroom/setup-generic-lms - /education/manage-coursework-with-github-classroom/setup-moodle - /education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom -shortTitle: Conectar un LMS +shortTitle: Connect an LMS --- +## About configuration of your LMS -## Acerca de la configuración de tu LMS +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. -Puedes conectar un sistema de administración de aprendizaje (LMS) a {% data variables.product.prodname_classroom %} y {% data variables.product.prodname_classroom %} puede importar los identificadores de un registro de alumno desde éste. Para conectar tu LMS a {% data variables.product.prodname_classroom %}, debes ingresar sus credenciales de configuración en éste. +## Prerequisites -## Prerrequisitos +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." -Para configurar un LMS para que se conecte con {% data variables.product.prodname_classroom %}, primero debes crear un aula. Para obtener más información, consulta la sección "[Administrar las aulas](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)". +## Supported LMSes -## LMS compatibles +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. -{% data variables.product.prodname_classroom %} es compatible conla importación de datos de registros de alumnos desde los LMS que implementen estándares de Interoperabilidad de Herramientas de Aprendizaje (LTI). +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X -- LTI versión 1.0 o 1.1 -- Aprovisionamiento de Roles y Nombres de LTI 1.X +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. -Utilizar LTI ayuda a mantener tu información segura y protegida. LTI es un protocolo estándar de la industria y GitHub Classroom lo utiliza con una certificación del Consorcio de Aprendizaje Global para el Sistema de Gestión Instruccional (IMS). Para obtener más información, consulta la [interoperabilidad de herramientas para el aprendizaje](https://www.imsglobal.org/activity/learning-tools-interoperability) y la sección [Acerca del Consorcio de Aprendizaje Global del IMS](http://www.imsglobal.org/aboutims.html) en el sitio web del Consorcio de Aprendizaje Global del IMS. - -{% data variables.product.company_short %} ha probado la importación de datos de registro de alumnos desde los siguientes LMS hacia {% data variables.product.prodname_classroom %}. +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. - Canvas - Google Classroom - Moodle - Sakai -Actualmente, {% data variables.product.prodname_classroom %} no es compatible para importar datos de registro de alumnos desde Blackboard o Brightspace. +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace. -## Generar credenciales de configuración para tu aula +## Generating configuration credentials for your classroom {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-students %} -1. Si tu aula ya tiene un registro de alumnos, puedes ya sea actualizarlo o borrarlo y crear uno nuevo. - - Para obtener más información sobre borrar y crear un registro de alumnos, consulta las secciones "[Borrar un registro de alumnos para un aula](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" y "[Crear un registro de alumnos para tu aula](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)". - - Para obtener más información acerca de cómo actualizar un registro de alumnos, consulta la sección "[Agregar alumnos al registro de alumnos de tu aula](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)". -1. En la lista de LMS, da clic en el tuyo. Si tu LMS no es compatible, da clic en **Otro LMS**. ![Lista de LMS](/assets/images/help/classroom/classroom-settings-click-lms.png) -1. Lee sobre cómo conectar tu LMS y luego da clic en **Conectar al _LMS_**. -1. Copia la "Llave de consumidor", "Secreto compartido", y "URL de lanzamiento" para la conexión al aula. ![Copiar credenciales](/assets/images/help/classroom/classroom-copy-credentials.png) +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. + ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. + ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) -## Configurar un LMS genérico +## Configuring a generic LMS -Debes configurar los ajustes de privacidad para que tu LMS permita que las herramientas externas reciban información del registro de alumnos. +You must configure the privacy settings for your LMS to allow external tools to receive roster information. -1. Navega a tu LMS. -1. Configura una herramienta externa. -1. Proporciona las credenciales de configuración que generaste en {% data variables.product.prodname_classroom %}. - - Llave de consumidor - - Secreto compartido - - URL de lanzamiento (a menudo se le llama "URL de herramienta" o similar) +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - Shared secret + - Launch URL (sometimes called "tool URL" or similar) -## Configurar Canvas +## Configuring Canvas -Puedes configurar {% data variables.product.prodname_classroom %} como una app externa para que Canvas importe los datos de la lista de alumnos a tu aula. Para obtener más información acerca de Canvas, consulta el [Sitio web de Canvas](https://www.instructure.com/canvas/). +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). -1. Ingresa en [Canvas](https://www.instructure.com/canvas/#login). -1. Selecciona el curso de Canvas que quieras integrar con {% data variables.product.prodname_classroom %}. -1. En la barra lateral izquierda, da clic en **Configuración**. -1. Da clic en la pestaña **Apps**. -1. Da clic en **Ver configuraciones de la app**. -1. Da clic en **+App**. -1. Selecciona el menú desplegable de **Tipo de configuración** y daclic en **Por URL**. -1. Pega las credenciales deconfiguración desde {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Generar credenciales de configuración para tu aula](#generating-configuration-credentials-for-your-classroom)". +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. In the left sidebar, click **Settings**. +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." - | Campo en la configuración de la app de Canvas | Valor o ajuste | - |:--------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------- | - | **Llave de consumidor** | Llave de consumidor de {% data variables.product.prodname_classroom %} - | **Secreto compartido** | Secreto compartido de {% data variables.product.prodname_classroom %} - | **Permitir que esta herramienta acceda a los nombres de IMS y al servicio de aprovisionamiento de roles** | Habilitado | - | **URL de configuración** | URL de lanzamiento de {% data variables.product.prodname_classroom %} + | Field in Canvas app configuration | Value or setting | + | :- | :- | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} | + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} | + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} | {% note %} - **Nota**: Si no ves una casilla de verificación en Canvas que lleve la etiqueta "Permitir que esta herramienta acceda a los nombres de IMS y al servicio de aprovisionamiento de roles", entonces tu administrador de Canvas debe contactar a soporte de Canvas para habilitar la configuración de servicios de membrecía para tu cuenta de Canvas. Si no se habilita esta característica, no podrás sincronizar el registro de alumnos desde Canvas. Para obtener más información, consulta la sección [¿Cómo contacto al soporte de Canvas?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) en el sitio web de Canvas. + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. {% endnote %} -1. Haz clic en **Submit** (enviar). -1. En la barra lateral izquierda, da clic en **Principal**. -1. Para solicitar a Canvas que envíe un correo electrónico de confirmación, en la barra lateral izquierda, da clic en **GitHub Classroom**. Sigue las instrucciones en el correo electrónico para concluir la vinculación de {% data variables.product.prodname_classroom %}. +1. Click **Submit**. +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. -## Configurar Moodle +## Configuring Moodle -Puedes configurar a {% data variables.product.prodname_classroom %} como una actividad para Moodle para importar datos del registro de alumnos a tu aula. Para obtener más información acerca de Moodle, consulta el [Sitio web de Moodle](https://moodle.org). +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). -Debes utilizar Moodle versión 3.0 o superior. +You must be using Moodle version 3.0 or greater. -1. Inicia sesión en [Moodle](https://moodle.org/login/index.php). -1. Selecciona el curso de Moodle que quieres integrar con {% data variables.product.prodname_classroom %}. -1. Da clic en **Activar la edición**. -1. Da clic en **Agregar una actividad o recurso** en donde quieras que esté disponible {% data variables.product.prodname_classroom %} en Moodle. -1. Elige **Herramienta externa** y da clic en **Agregar**. -1. En el campo de "Nombre de actividad", teclea "GitHub Classroom". -1. En el campo de **Herramienta preconfigurada**, a la derecha del menú desplegable, da clic en **+**. -1. Debajo de "Configuración de herramienta externa", pega las credenciales de configuración de {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Generar credenciales de configuración para tu aula](#generating-configuration-credentials-for-your-classroom)". +1. Sign into [Moodle](https://moodle.org/login/). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." - | Campo en la configuración de la app de Moodle | Valor o ajuste | - |:--------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | **Nombre de la herramienta** | {% data variables.product.prodname_classroom %} - _TU NOMBRE DE AULA_

    **Nota**: Puedes utilizar cualquier nombre, pero te sugerimos este valor para tener más claridad. | - | **URL de la herramienta** | URL de lanzamiento de {% data variables.product.prodname_classroom %} - | **Versión de LTI** | LTI 1.0/1.1 | - | **Contenedor de lanzamiento predeterminado** | Ventana nueva | - | **Llave de consumidor** | Llave de consumidor de {% data variables.product.prodname_classroom %} - | **Secreto compartido** | Secreto compartido de {% data variables.product.prodname_classroom %} + | Field in Moodle app configuration | Value or setting | + | :- | :- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

    **Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} | + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} | + | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} | -1. Desplázate y da clic en **Servicios**. -1. A la derecha de "Nombres de LTI de IMS y Aprovisionamiento de Roles", selecciona el menú desplegable y da clic en **Utilizar este servicio para recuperar la información de los miembros de acuerdo con la configuración de seguridad**. -1. Desplázate y da clic en **Privacidad**. -1. A la derecha de **Compartir el nombre del lanzador con la herramienta** y **Compartir el correo electrónico del lanzador con la herramienta**, selecciona los menús desplegables para dar clic en **Siempre**. -1. En la parte inferior de la página, da clic en **Guardar cambios**. -1. En el menú de **Preconfigurar herramienta** da clic en **GitHub Classroom - _TU NOMBRE DE AULA_**. -1. Debajo de "Configuración común de módulo", a la derecha de "Disponibilidad", selecciona el menú desplegable y da clic en **Ocultar para los alumnos**. -1. En la parte inferior de la página, da clic en **Guardar y regresar al curso**. -1. Navega a donde sea que elijas mostrar tu {% data variables.product.prodname_classroom %} y da dlic en la actividad {% data variables.product.prodname_classroom %}. +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. At the bottom of the page, click **Save changes**. +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. -## Importar un registro de alumnos desde tu LMS +## Importing a roster from your LMS -Para obtener más información acerca de importar el registro de alumnos de tu LMS en {% data variables.product.prodname_classroom %}, consulta la sección "[Administrar aulas](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)". +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." -## Desconectar tu LMS +## Disconnecting your LMS {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-settings %} -1. Debajo de "Conectar a un sistema de administración de aprendizaje (LMS)", da clic en **Configuración de conexión**. ![Enlace de "Configuración de conexión " en los ajustes de aula](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) -1. Debajo de "Borrar la conexión con tu sistema de administración de aprendizaje", da clic en **Desconectarse de tu sistema de administración de aprendizaje**. ![Botón de "Desconectarse de tu sistema de administración de aprendizaje" en los ajustes de conexión para el aula](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. + !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. + !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 7d784aa85a..dd48d29d63 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -1,114 +1,113 @@ --- -title: Crear una tarea de grupo -intro: Puedes crear una tarea colaborativa para que los equipos de alumnos participen en tu curso. +title: Create a group assignment +intro: You can create a collaborative assignment for teams of students who participate in your course. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/create-group-assignments - /education/manage-coursework-with-github-classroom/create-a-group-assignment --- +## About group assignments -## Acerca de las tareas de grupo +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. -{% data reusables.classroom.assignments-group-definition %} Los alumnos pueden trabajar en conjunto en las tareas de grupo dentro de un repositorio compartido, como un equipo de desarrolladores profesionales. - -Cuando un alumno acepta una tarea grupal, los alumnos pueden crear un equipo nuevo o unirse a uno existente. {% data variables.product.prodname_classroom %} guarda los equipos para una tarea como un conjunto. Puedes nombrar el conjunto de equipos para una tarea específica cuando creas dicha tarea y puedes reutilizar ese conjunto de equipos para una tarea más grande. +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. {% data reusables.classroom.classroom-creates-group-repositories %} {% data reusables.classroom.about-assignments %} -Puedes decidir cuántos equipos puede tener una tarea y cuántos miembros puede tener cada equipo. Cada equipo que crea un alumno para una tarea constituye un equipo dentro de tu organización en {% data variables.product.product_name %}. La visibilidad del equipo es secreta. Los equipos que crees en {% data variables.product.product_name %} no aparecerán en {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)". +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." -Para ver un video demostrativo de la creación de una tarea de grupo, consulta la sección "[Conceptos básicos para configurar un {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)". +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." -## Prerrequisitos +## Prerequisites {% data reusables.classroom.assignments-classroom-prerequisite %} -## Crear una tarea +## Creating an assignment {% data reusables.classroom.assignments-guide-create-the-assignment %} -## Configurar lo básico para una tarea +## Setting up the basics for an assignment -Nombra tu tarea, decide si quires asignarle una fecha límite, definir equipos o elegir la visibilidad de los repositorios de la misma. +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. -- [Nombrar una tarea](#naming-an-assignment) -- [Asignar una fecha límita para una tarea](#assigning-a-deadline-for-an-assignment) -- [Elegir un tipo de tarea](#choosing-an-assignment-type) -- [Definir los equipos para una tarea](#defining-teams-for-an-assignment) -- [Elegir un tipo de visibilidad para los repositorios de la tarea](#choosing-a-visibility-for-assignment-repositories) +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) -### Nombrar una tarea +### Naming an assignment -En las tareas grupales, {% data variables.product.prodname_classroom %} nombra a los repositorios de acuerdo con el prefijo de los mismos y el nombre del equipo. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si nombras la tarea "assignment-1" y el nombre del equipo en {% data variables.product.product_name %} es "student-team", el nombre del repositorio de la tarea para los miembros del equipo será `assignment-1-student-team`. +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. {% data reusables.classroom.assignments-type-a-title %} -### Asignar una fecha límita para una tarea +### Assigning a deadline for an assignment {% data reusables.classroom.assignments-guide-assign-a-deadline %} -### Elegir un tipo de tarea +### Choosing an assignment type -Debajo de "Tarea individual o grupal", selecciona el menú desplegable y daclic en **Tarea grupal**. No puedes cambiar el tipo de tarea después de crearla. Si prefieres crear una tarea individual, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)". +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." -### Definir los equipos para una tarea +### Defining teams for an assignment -Si ya creaste una tarea grupal para el aula, puedes reutilizar un conjunto de equipos para la tarea nueva. Para crear un conjunto nuevo con los equipos que crean tus alumnos para la tarea, teclea el nombre de dicho conjunto. Opcionalmente, teclea la cantidad máxima de miembros de los equipos y el total de los equipos. +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. {% tip %} **Tips**: -- Te recomendamos incluir detalles sobre el conjunto de equipos en el nombre de dicho conjunto. Por ejemplo, si quieres utilizar un conjunto de equipos en un segmente, nómbralo como la tarea. Si quieres reutilizar el conjunto a lo largo de un semesre o curso, nombra el conjunto como el semestre o curso. +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. -- Si te gustaría asignar alumnos a un equipo específico, proporciónales un nombre de equipo y una lista de mimebros. +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. {% endtip %} -![Parámetros para los equipos que participan en una tarea grupal](/assets/images/help/classroom/assignments-define-teams.png) +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) -### Elegir un tipo de visibilidad para los repositorios de la tarea +### Choosing a visibility for assignment repositories {% data reusables.classroom.assignments-guide-choose-visibility %} {% data reusables.classroom.assignments-guide-click-continue-after-basics %} -## Agergar un código de inicio y configurar un ambiente de desarrollo +## Adding starter code and configuring a development environment {% data reusables.classroom.assignments-guide-intro-for-environment %} -- [Elegir un repositorio de plantilla](#choosing-a-template-repository) -- [Elegir un ambiente de desarrollo integrado (IDE)](#choosing-an-integrated-development-environment-ide) +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide) -### Elegir un repositorio de plantilla +### Choosing a template repository -Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada equipo que cree el alumno. {% data reusables.classroom.you-can-choose-a-template-repository %} +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} {% data reusables.classroom.assignments-guide-choose-template-repository %} -### Elegir un ambiente de desarrollo integrado (IDE) +### Choosing an integrated development environment (IDE) -{% data reusables.classroom.about-online-ides %} Para obtener más información, consulta la sección "[Integrar el {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)". +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." {% data reusables.classroom.assignments-guide-choose-an-online-ide %} {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} -## Proporcionar retroalimentación +## Providing feedback -Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para debatir cada entrega con el equipo. +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. -- [Probar las tareas automáticamente](#testing-assignments-automatically) -- [Crear una solicitud de cambios para retroalimentación](#preventing-changes-to-important-files) +- [Testing assignments automatically](#testing-assignments-automatically) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) -### Probar las tareas automáticamente +### Testing assignments automatically {% data reusables.classroom.assignments-guide-using-autograding %} -### Crear una solicitud de cambios para retroalimentación +### Creating a pull request for feedback {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} @@ -116,26 +115,26 @@ Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para {% data reusables.classroom.assignments-guide-click-create-assignment-button %} -## Invitar a los alumnos a una tarea +## Inviting students to an assignment {% data reusables.classroom.assignments-guide-invite-students-to-assignment %} -Puedes ver los equipos que están trabajando o que han emitido una tarea en la pestaña de **Equipos** de la misma. {% data reusables.classroom.assignments-to-prevent-submission %} +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
    - Tarea grupal + Group assignment
    -## Pasos siguientes +## Next steps -- Después de que creas una tarea y de que tus alumnos forme equipos, los miembros de dichos equipos pueden comenzar a trabajar en la tarea utilizando las características de Git y de {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el equipo pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta las secciones "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)", "[Repositorios](/repositories)", "[Utilizar git](/github/getting-started-with-github/using-git)" y "[Colaborar con las propuestas y solicitudes de cambio](/github/collaborating-with-issues-and-pull-requests)" y el curso gratuito sobre [cómo administrar los conflictos de fusión](https://lab.github.com/githubtraining/managing-merge-conflicts) de {% data variables.product.prodname_learning %}. +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. -- Cuando un equipo termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y visualizaciones del mismo para entender mejor cómo colaboró el equipo. Para obtener más información, consulta la sección "[Visualizar los datos del repositorio con gráficas](/github/visualizing-repository-data-with-graphs)". +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." -- Puedes proporcionar retroalimentación para una tarea si comentas en confirmaciones o líneas individuales dentro de una solicitud de cambios. Para obtener más información, consulta la sección "[Comentar en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" y "[Abrir una propuesta desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para obtener más información sobre cómo crear respuestas guardadas para proporcionar retroalimentación a los errores comunes, consulta la sección "[Acerca de las respuestas guardadas](/github/writing-on-github/about-saved-replies)". +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." -## Leer más +## Further reading -- "[Utiliza {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" -- "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" -- [Utilizar equipos existentes en tareas grupales](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) en la comunidad de {% data variables.product.prodname_education %} +- "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md index 064207280c..a76f6beeba 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md @@ -1,15 +1,14 @@ --- -title: Crear una tarea individual -intro: Puedes crear una tarea individual para que los alumnos de tu curso la completen individualmente. +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment - /education/manage-coursework-with-github-classroom/create-an-individual-assignment -shortTitle: Tarea individual +shortTitle: Individual assignment --- - -## Acerca de las tareas individuales +## About individual assignments {% data reusables.classroom.assignments-individual-definition %} @@ -17,78 +16,78 @@ shortTitle: Tarea individual {% data reusables.classroom.about-assignments %} -Para ver un video demostrativo de la creación de una tarea individual, consulta la sección "[Conceptos básicos para configurar un {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)". +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." -## Prerrequisitos +## Prerequisites {% data reusables.classroom.assignments-classroom-prerequisite %} -## Crear una tarea +## Creating an assignment {% data reusables.classroom.assignments-guide-create-the-assignment %} -## Configurar lo básico para una tarea +## Setting up the basics for an assignment -Nombra tu tarea, decide si quieres asignar una fecha límite y elige la visibilidad de los repositorios de la misma. +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. -- [Nombrar una tarea](#naming-an-assignment) -- [Asignar una fecha límita para una tarea](#assigning-a-deadline-for-an-assignment) -- [Elegir un tipo de tarea](#choosing-an-assignment-type) -- [Elegir un tipo de visibilidad para los repositorios de la tarea](#choosing-a-visibility-for-assignment-repositories) +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) -### Nombrar una tarea +### Naming an assignment -Para una tarea individual, {% data variables.product.prodname_classroom %} nombra los repositorios de acuerdo con su prefijo y con el nombre de usuario de {% data variables.product.product_name %} del alumno. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si nombras a una tarea "assingment-1" y el nombre de usuario del alumno en {% data variables.product.product_name %} es @octocat, entonces el nombre del repositorio de la tarea para @octocat será `assignment-1-octocat`. +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. {% data reusables.classroom.assignments-type-a-title %} -### Asignar una fecha límita para una tarea +### Assigning a deadline for an assignment {% data reusables.classroom.assignments-guide-assign-a-deadline %} -### Elegir un tipo de tarea +### Choosing an assignment type -Debajo de "Tarea individual o grupal", selecciona el menú desplegable y da clic en **Tarea individual**. No puedes cambiar el tipo de tarea después de crearla. Si prefieres crear una tarea de grupo, consulta la sección "[Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." -### Elegir un tipo de visibilidad para los repositorios de la tarea +### Choosing a visibility for assignment repositories {% data reusables.classroom.assignments-guide-choose-visibility %} {% data reusables.classroom.assignments-guide-click-continue-after-basics %} -## Agergar un código de inicio y configurar un ambiente de desarrollo +## Adding starter code and configuring a development environment {% data reusables.classroom.assignments-guide-intro-for-environment %} -- [Elegir un repositorio de plantilla](#choosing-a-template-repository) -- [Elegir un ambiente de desarrollo integrado (IDE)](#choosing-an-integrated-development-environment-ide) +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide) -### Elegir un repositorio de plantilla +### Choosing a template repository -Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada alumno del registro de alumnos del aula. {% data reusables.classroom.you-can-choose-a-template-repository %} +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} {% data reusables.classroom.assignments-guide-choose-template-repository %} {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} -### Elegir un ambiente de desarrollo integrado (IDE) +### Choosing an integrated development environment (IDE) -{% data reusables.classroom.about-online-ides %} Para obtener más información, consulta la sección "[Integrar el {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)". +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." {% data reusables.classroom.assignments-guide-choose-an-online-ide %} -## Proporcionar retroalimentación para una tarea +## Providing feedback for an assignment -Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para debatir cada entrega con el alumno. +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. -- [Probar las tareas automáticamente](#testing-assignments-automatically) -- [Crear una solicitud de cambios para retroalimentación](#preventing-changes-to-important-files) +- [Testing assignments automatically](#testing-assignments-automatically) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) -### Probar las tareas automáticamente +### Testing assignments automatically {% data reusables.classroom.assignments-guide-using-autograding %} -### Crear una solicitud de cambios para retroalimentación +### Creating a pull request for feedback {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} @@ -96,25 +95,25 @@ Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para {% data reusables.classroom.assignments-guide-click-create-assignment-button %} -## Invitar a los alumnos a una tarea +## Inviting students to an assignment {% data reusables.classroom.assignments-guide-invite-students-to-assignment %} -Puedes ver si un alumno se unió al aula y aceptó o emitió una tarea en la pestaña de **Todos los alumnos** de la misma. {% data reusables.classroom.assignments-to-prevent-submission %} +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
    - Tarea individual + Individual assignment
    -## Pasos siguientes +## Next steps -- Después de que creas la tarea, los alumnos pueden comenzar a trabajar en ella utilizando las características de Git y {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el alumno pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta las secciones "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositorios](/repositories)," y "[Colaborar con las propuestas y solicitudes de cambio](/github/collaborating-with-issues-and-pull-requests)". +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." -- Cuando un alumno termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y las visualizaciones del repositorio para entender mejor su trabajo. Para obtener más información, consulta la sección "[Visualizar los datos del repositorio con gráficas](/github/visualizing-repository-data-with-graphs)". +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." -- Puedes proporcionar retroalimentación para una tarea si comentas en confirmaciones o líneas individuales dentro de una solicitud de cambios. Para obtener más información, consulta la sección "[Comentar en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" y "[Abrir una propuesta desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para obtener más información sobre cómo crear respuestas guardadas para proporcionar retroalimentación a los errores comunes, consulta la sección "[Acerca de las respuestas guardadas](/github/writing-on-github/about-saved-replies)". +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." -## Leer más +## Further reading -- "[Utiliza {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" -- "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md index ab55e3458a..5b12c76c98 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md @@ -1,33 +1,34 @@ --- -title: Deja retroalimentación con solicitudes de cambios -intro: Puedes dejar retroalimentación para tus alumnos en una solicitud de cambio especial dentro del repositorio de cada tarea. +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github - /education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests -shortTitle: Solicitudes de cambios +shortTitle: Pull requests --- - -## Acerca de las solicitudes de cambio de retroalimentación de las tareas +## About feedback pull requests for assignments {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} -Cuando habilitas las solicitudes de cambio para retroalimentación de una tarea, {% data variables.product.prodname_classroom %} crerá una soicitud de cambios especial que se llama **Retroalimentación** en el repositorio de la tarea para cada alumno o equipo. La solicitud de cambios mostrará automáticamente todas las confirmaciones que subió el alumno a la rama predeterminada del repositorio de la tarea. +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. -## Prerrequisitos +## Prerequisites -Para crear y acceder a la solicitud de cambios de retroalimentación, debes habilitarla cuando creas la tarea. {% data reusables.classroom.for-more-information-about-assignment-creation %} +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} -## Dejar retroalimentación en una solicitud de cambios para una tarea +## Leaving feedback in a pull request for an assignment {% data reusables.classroom.sign-into-github-classroom %} -1. En la lista de aulas, da clic en aquella con la tarea que quieres revisar. ![Aula en la lista de aulas de una organización](/assets/images/help/classroom/click-classroom-in-list.png) +1. In the list of classrooms, click the classroom with the assignment you want to review. + ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) {% data reusables.classroom.click-assignment-in-list %} -1. A la derecha de la emisión, da clic en **Revisar**. ![Botón de revisar para la tarea en una lista de emisiones de una tarea](/assets/images/help/classroom/assignments-click-review-button.png) -1. Revisar la solicitud de cambios. Para obtener más información, consulta "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." +1. To the right of the submission, click **Review**. + ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." -## Leer más +## Further reading -- "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index e77827f474..336444f7a6 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -1,211 +1,212 @@ --- -title: Iniciar con GitHub Enterprise Cloud -intro: 'Inicia con la configuración y administración de tu cuenta organizacional o empresarial de {% data variables.product.prodname_ghe_cloud %}.' +title: Getting started with GitHub Enterprise Cloud +intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.' versions: fpt: '*' ghec: '*' --- -Esta guía te mostrará cómo configurar, ajustar y administrar tu cuenta de {% data variables.product.prodname_ghe_cloud %} como organización o empresa. +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner. {% data reusables.enterprise.ghec-cta-button %} -## Parte 1: Elegir tu tipo de cuenta +## Part 1: Choosing your account type -{% data variables.product.prodname_dotcom %} proporciona dos tipos de productos empresariales: +{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -La diferencia principal entre los productos es que {% data variables.product.prodname_dotcom %} hospeda a {% data variables.product.prodname_ghe_cloud %}, mientras que {% data variables.product.prodname_ghe_server %} es auto-hospedado. +The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Con {% data variables.product.prodname_ghe_cloud %}, tienes la opción de utilizar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} -Si en vez de esto eliges permitir a que tus miembros creen y administren sus propias cuentas, hay dos tipos de cuentas que puedes utilizar con {% data variables.product.prodname_ghe_cloud %}: +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: -- Una cuenta de organización simple -- Una cuenta empresarial que contiene varias organizaciones +- A single organization account +- An enterprise account that contains multiple organizations -### 1. Entender las diferencias entre una cuenta organizacional y una cuenta empresarial +### 1. Understanding the differences between an organization account and enterprise account -Tanto las cuentas de empresa como las de organización se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}. Una organización es una cuenta compartida en donde los grupos de personas pueden colaborar a través de varios proyectos a la vez y los propietarios y administradores pueden administrar el acceso a los datos y proyectos. Una cuenta empresarial habilita la colaboración entre organizaciones múltiples y permite a los propietarios administrar políticas centralmente, facturar y proporcionar seguridad a estas organizaciones. Para encontrar más información sobre las diferencias, consulta la sección "[Organizaciones y cuentas empresariales](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)". +Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." -Si eliges una cuenta empresarial, ten en mente que algunas políticas se configuran mejor a nivel organizacional, mientras que otras pueden requerirse para todas las organizaciones en una empresa. +If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. -Una vez que elijas el tipo de cuenta que te gustaría utilizar, puedes proceder a configurarla. En cada sección de esta guía, procede a ya sea la sección de organización simple o de cuenta empresarial de acuerdo con tu tipo de cuenta. +Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. -## Parte 2: Configurar tu cuenta -Para iniciar con {% data variables.product.prodname_ghe_cloud %}, necesitarás crear tu cuenta de organización o de empresa y configurar y ver los ajustes de facturación, suscripciones y uso. -### Configurar una cuenta de organización simple con {% data variables.product.prodname_ghe_cloud %} +## Part 2: Setting up your account +To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage. +### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %} -#### 1. Acerca de las organizaciones -Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. Con {% data variables.product.prodname_ghe_cloud %}, los propietarios y administradores pueden manejar su organización con una administración y autenticación de usuarios sofisticada, así como soporte escalado y opciones de seguridad. Para obtener más información, consulta "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)". -#### 2. Crear o mejorar una cuenta organizacional +#### 1. About organizations +Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." +#### 2. Creating or upgrading an organization account -Para utilizar una cuenta de organización con {% data variables.product.prodname_ghe_cloud %}, primero necesitarás crear una organización. Cuando se te pida elegir un plan, selecciona "Empresa". Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -Como alternativa, si tienes una cuenta organizacional existente que quisieras mejorar, sigue los pasos en "[Mejorar tu suscripción de {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". -#### 3. Configurar y administrar la facturación +Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." +#### 3. Setting up and managing billing -Cuando eliges utilizar una cuenta de organización con {% data variables.product.prodname_ghe_cloud %}, primero necesitarás tener acceso a la [prueba gratuita de 14 días](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). Si no compras {% data variables.product.prodname_enterprise %} o {% data variables.product.prodname_team %} antes de que termine tu periodo de prueba, tu organización bajará de nivel a {% data variables.product.prodname_free_user %} y perderá acceso a cualquier herramienta avanzada y características que solo se incluyan con los productos de pago. Para obtener más información, consulta la sección "[Finalizar tu periodo de prueba](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)". +When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." -La página de configuración de facturación de tu organización te permite administrar los ajustes como tu método de pago y ciclo de facturación, ver la información sobre tu suscripción y mejorar tu almacenamiento y minutos de {% data variables.product.prodname_actions %}. Para obtener más información sobre cómo administrar tu configuración de facturación, consulta la sección "[Administrar tu configuración de facturación de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". +Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." -Solo los miembros de la organización con el rol de *propietario* o *gerente de facturación* pueden acceder o cambiar la configuración de facturación para tu organización. Un gerente de facturación es un usuario que administra la configuración de facturación de tu organización y no utiliza una licencia en la suscripción de tu organización. Para obtener más información sobre cómo agregar a un gerente de facturación a tu organización, consulta la sección "[Agregar a un gerente de facturación a tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -### Configurar una cuenta empresarial con {% data variables.product.prodname_ghe_cloud %} +### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} {% note %} -Para obtener una cuenta empresarial que se creó para ti, contacta al [Equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). +To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). {% endnote %} -#### 1. Acerca de las cuentas de empresa +#### 1. About enterprise accounts -Una cuenta empresarial te permite administrar las políticas y ajustes centralmente para organizaciones múltiples de {% data variables.product.prodname_dotcom %}, incluyendo el acceso de los miembros, la facturación, el uso y la seguridad. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)". -#### 2. Agregar organizaciones en tu cuenta de empresa +An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." +#### 2. Adding organizations to your enterprise account -Puedes crear nuevas organizaciones para administrar dentro de tu cuenta de empresa. Para obtener más información, consulta la sección "[Agregar organizaciones a tu empresa](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". +You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -Contacta a tu representante de cuenta de ventas de {% data variables.product.prodname_dotcom %} su quieres transferir una organización existente a tu cuenta empresarial. -#### 3. Ver la suscripción y el uso de tu cuenta de empresa -Puedes ver tu suscripción actual, uso de licencia, facturas, historial de pagos y otra información de facturación de tu cuenta empresarial en cualquier momento. Tanto los propietarios de empresas como los gerentes de facturación pueden acceder y administrar la configuración de facturación para las cuentas empresariales. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." +Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. +#### 3. Viewing the subscription and usage for your enterprise account +You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## Parte 3: Administrar los equipos y miembros de tu organización o empresa con {% data variables.product.prodname_ghe_cloud %} +## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} -### Administrar a los miembros y equipos de tu organización -Puedes configurar los permisos y roles de los miembros, crear y administrar equipos y darles a las personas acceso a los repositorios de tu organización. -#### 1. Administrar a los miembros de tu organización +### Managing members and teams in your organization +You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. +#### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -#### 2. Permisos y roles de la organización +#### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -#### 3. Acerca de y crear equipos +#### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -#### 4. Administrar la configuración de los equipos +#### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -#### 5. Otorgar acceso a equipos y personas para los repositorios, tableros de proyecto y apps +#### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -### Administrar a los miembros de una cuenta empresarial -Administrar a los miembros de una empresa es algo separado de administrar a los miembros o equipos de una organización. Es importante notar que los propietarios o administradores de una empresa no pueden acceder a los ajustes a nivel organizacional ni administrar a los miembros de las organizaciones en su empresa a menos de que se les haga un propietario de organización. Para obtener más información, consulta la sección anterior: "[Administrar los miembros y equipos de tu organización](#managing-members-and-teams-in-your-organization)". +### Managing members of an enterprise account +Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." -Si tu empresa utiliza {% data variables.product.prodname_emus %}, tus miembros se administrarán integralmente mediante tu proveedor de identidad. Tanto la adición de miembros, hacer cambios a sus membrecías y asignar roles se administra utilizando tu IdP. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -Si tu empresa no utiliza {% data variables.product.prodname_emus %}, sigue estos pasos. +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. -#### 1. Asignar roles en una empresa -Predeterminadamente, cualquiera en una empresa es un miembro de ella. También existen roles administrativos, incluyendo el del propietario y gerente de facturación, que tienen niveles diferentes de acceso a los datos y ajustes de una empresa. Para obtener más información, consulta la sección "[Roles en una empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)". -#### 2. Invitar a las personas para que administren tu empresa -Puedes invitar a personas para que administren tu empresa como propietarios o gerentes de facturación, así como eliminar a los que ya no necesiten acceso. Para obtener más información, consulta la sección "[Invitar a las personas para que administren tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)". +#### 1. Assigning roles in an enterprise +By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." +#### 2. Inviting people to manage your enterprise +You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." -También puedes otorgar a los miembros de la empresa la capacidad para que administren tickets de soporte en el portal de soporte. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". -#### 3. Visualizar a las personas en tu empresa -Para auditar el acceso a los recursos que pertenecen a la empresa o al uso de licencias de los usuarios, puedes ver a todos los administradores, miembros y colaboradores externos de tu empresa. Puedes ver las organizaciones a las cuales pertenece un miembro y especificar los repositorios a los cuales tiene acceso un colaborador. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". +You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." +#### 3. Viewing people in your enterprise +To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)." -## Parte 4: Administrar la seguridad con {% data variables.product.prodname_ghe_cloud %} +## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} -* [Administrar la seguridad para una sola organización](#managing-security-for-a-single-organization) -* [Administrar la seguridad para una {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) -* [Administrar la seguridad para una cuenta empresarial sin {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) -### Administrar la seguridad para una sola organización -Puedes ayudar a que tu organización se mantenga protegida requiriendo autenticación bifactorial, configurando las características de seguridad, revisando las bitácoras de auditoría e integraciones de tu organización y habilitando el inicio de sesión único de SAML y la sincronización de equipos. -#### 1. Requerir autenticación bifactorial +### Managing security for a single organization +You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. +#### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -#### 2. Configurar las características de seguridad de tu organización +#### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -#### 3. Revisar las bitácoras de auditoría e integraciones de tu organización +#### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -#### 4. Habilitar y requerir el inicio de sesión único de SAML en tu organización -Si administras tus aplicaciones y las identidades de tus miembros de la organización con un proveedor de identidad (IdP), puedes configurar el inicio de sesión único (SSO) de SAML para controlar y proteger el acceso a los recursos organizacionales como los repositorios, propuestas y solicitudes de cambio. Cuando los miembros de tu organización acceden a los recursos de la misma que utilicen el SSO de SAML, {% data variables.product.prodname_dotcom %} los redireccionará a tu IdP para autenticarse. Para obtener más información, consulta la sección "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". -Los propietarios de la organización pueden elegir inhabilitar, habilitar pero no requerir o habilitar y requerir el SSO de SAML. Para obtener más información, consulta las secciones "[Habilitar y probar el inicio de sesión único de SAML para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" y "[Requerir el inicio de sesión único de SAML para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)". -#### 5. Administrar la sincronización de equipos para tu organización -Los propietarios de la organización pueden habilitar la sincronización de equipos entre tu proveedor de identidad (IdP) y {% data variables.product.prodname_dotcom %} para permitir que los propietarios organizacionales y mantenedores de equipo conecten equipos en tu organización con los grupos de IdP. Para obtener más información, consulta la sección [Administrar la sincronización de equipos para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". +#### 4. Enabling and enforcing SAML single sign-on for your organization +If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." -### Administrar la seguridad para una {% data variables.product.prodname_emu_enterprise %} +Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." +#### 5. Managing team synchronization for your organization +Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -Con {% data variables.product.prodname_emus %}, el acceso y la identidad se administran centralmente mediante tu proveedor de identidad. La autenticación bifactorial y otros requisitos de inicio de sesión deben habilitarse y requerirse en tu IdP. +### Managing security for an {% data variables.product.prodname_emu_enterprise %} -#### 1. Habilitar el inicio de sesión único de SAML y el aprovisionamiento en tu {% data variables.product.prodname_emu_enterprise %} +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. -En una {% data variables.product.prodname_emu_enterprise %}, tu proveedor de identidad administra y aprovisiona a todos los miembros. Debes habilitar el SSO de SAML y el aprovisionamiento de SCIM antes de que puedas comenzar a utilizar tu empresa. Para obtener más información sobre cómo configurar el SSO de SAML y el aprovisionamiento para una {% data variables.product.prodname_emu_enterprise %}, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados de Enterprise](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} -#### 2. Administrar equipos en tu {% data variables.product.prodname_emu_enterprise %} con tu proveedor de identidad +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." -Puedes conectar equipos en tus organizaciones a grupos de seguridad en tu proveedor de identidad, administrar la membrecía de tus equipos y acceder a repositorios mediante tu IdP. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con los grupos de proveedor de identidades](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider -#### 3. Administrar las direcciones IP permitidas para las organizaciones de tu {% data variables.product.prodname_emu_enterprise %} +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." -Puedes configurar una lista de direcciones permitidas para IP específicas para restringir el acceso a los activos que pertenecen a las organizaciones de tu {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} -#### 4. Reforzar las políticas para las características de Seguridad Avanzada en tu {% data variables.product.prodname_emu_enterprise %} +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." + +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} {% data reusables.getting-started.enterprise-advanced-security %} -### Administrar la seguridad para una cuenta empresarial sin {% data variables.product.prodname_managed_users %} -Para administrar la seguridad de tu empresa, puedes requerir la autenticación bifactorial, administrar las direcciones IP permitidas, habilitar el inicio de sesión único de SAML y la sincronización de equipos a nivel empresaria y darte de alta para y requerir las características de la Seguridad Avanzada de GitHub. +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} +To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. -#### 1. Requerir la autenticación bifactorial y administrar las direcciones IP permitidas para las organizaciones de tu cuenta empresarial -Los propietarios de empresa pueden requerir que los miembros de la organización, gerentes de facturación y colaboradores externos en todas las organizaciones que sean propiedad de una cuenta de empresa usen autenticación de dos factores para proteger sus cuentas personales. Antes de hacerlo, te recomendamos notificar a todos los que tengan acceso a las organizaciones de tu empresa. También puedes configurar una lista de direcciones IP permitidas específicas para restringir el acceso a los activos que pertenecen a las organizaciones en tu cuenta empresarial. +#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account +Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)." -#### 2. Habilitar y requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial -Puedes administrar centralmente el acceso a los recursos de tu empresa, la membrecía organizacional y la de equipo utilizando tu IdP e inicio de sesión único (SSO) de SAML. Los propietarios de empresas pueden habilitar el SSO de SAML a través de todas las organizaciones que pertenezcan a una cuenta empresarial. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidades para tu empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account +You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -#### 3. Administrar la sincronización de equipos -Puedes habilitar y administrar la sincronización de equipos entre un proveedor de identidad (IdP) y {% data variables.product.prodname_dotcom %} para permitir que las organizaciones que pertenezcan a tu cuenta empresarial administren la membrecía de los equipos con grupos de IdP. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)". +#### 3. Managing team synchronization +You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." -#### 4. Requerir políticas para las características de seguridad avanzada en tu cuenta empresarial +#### 4. Enforcing policies for Advanced Security features in your enterprise account {% data reusables.getting-started.enterprise-advanced-security %} -## Parte 5: Administrar políticas y ajustes a nivel de empresa y organización +## Part 5: Managing organization and enterprise level policies and settings -### Administrar los ajustes para una sola organización -Para administrar y moderar tu organización, puedes configurar políticas de organización, administrar permisos para los cambios de repositorio y utilizar archivos de salud comunitaria a nivel de las organizaciones. -#### 1. Administrar las políticas organizacionales +### Managing settings for a single organization +To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files. +#### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -#### 2. Administrar los cambios de repositorio +#### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -#### 3. Utilizar archivos de salud comunitaria y herramientas de moderación a nivel organizacional +#### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -### Administrar los ajustes de una cuenta empresarial -Para administrar y moderar tu empresa, puedes configurar políticas para las organizaciones dentro de la empresa, ver las bitácoras de auditoría, configurar webhooks y restringir las notificaciones por correo electrónico. -#### 1. Administrar políticas para las organizaciones en tu cuenta empresarial +### Managing settings for an enterprise account +To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications. +#### 1. Managing policies for organizations in your enterprise account -Puedes elegir el requerir varias políticas para todas las organizaciones que pertenezcan a tu empresa o elegir permitir que estas políticas se configuren en cada organización. Los tipos de políticas que puedes requerir incluyen la administración de repositorios, tablero de proyectos y políticas de equipo. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)." -#### 2. Ver las bitácoras de auditoría, configurar webhooks y restringir las notificaciones de tu empresa -Puedes ver las acciones de todas las organizaciones que pertenezcan a tu cuenta empresarial en la bitácora de auditoría empresarial. También puedes configurar webhooks para recibir eventos de organizaciones que pertenecen a tu cuenta de empresa. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)." +You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)." +#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise +You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)." -También puedes restringir las notificaciones por correo electrónico de tu cuenta empresarial para que los miembros de tu empresa solo puedan utilizar una dirección de correo electrónico en un dominio aprobado o verificado para recibir notificaciones. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." +You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." -## Parte 6: Personalizar y automatizar el trabajo de tu organización o empresa en {% data variables.product.prodname_dotcom %} +## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %} Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. -### 1. Uso de {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. Crear {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publicar y administrar el {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -### 5. Uso de {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} es un servicio de hospedaje de sitios estáticos que toma archivos de HTML, CSS y JavaScript directamente desde un repositorio y publica un sitio web. Puedes administrar la publicación de los sitios de {% data variables.product.prodname_pages %} a nivel organizacional. Para obtener más información, consulta las secciones "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} en tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" y "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". -## Parte 7: Participar en la comunidad de {% data variables.product.prodname_dotcom %} +### 5. Using {% data variables.product.prodname_pages %} +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." +## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community -Los miembros de tu organización o empresa pueden utilizar los recursos de apoyo y aprendizaje de GitHub para obtener la ayuda que necesitan. También puedes apoyar a la comunidad de código abierto. -### 1. Aprender con {% data variables.product.prodname_learning %} -Los miembros de tu organización o empresa pueden aprender habilidades nuevas completando proyectos divertidos y realistas en tu propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://lab.github.com/). Cada curso es una lección didáctica que creó la comunidad de GitHub y que la enseña el amigable bot del Laboratorio de Aprendizaje. +Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. +### 1. Learning with {% data variables.product.prodname_learning %} +Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. -Para obtener más información, consulta la sección "[Recursos de aprendizaje de Git y de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". -### 2. Apoyar a la comunidad de código abierto +For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." +### 2. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 3. Comunicarse con {% data variables.contact.github_support %} +### 3. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -{% data variables.product.prodname_ghe_cloud %} te permite emitir solicitudes de soporte prioritario con un tiempo de respuesta de ocho horas. Para obtener más información, consulta la sección "[Soporte de {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/github-enterprise-cloud-support)". +{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." diff --git a/translations/es-ES/content/get-started/quickstart/be-social.md b/translations/es-ES/content/get-started/quickstart/be-social.md index 2870c52af3..a301f20548 100644 --- a/translations/es-ES/content/get-started/quickstart/be-social.md +++ b/translations/es-ES/content/get-started/quickstart/be-social.md @@ -1,11 +1,11 @@ --- -title: Ser social +title: Be social redirect_from: - /be-social/ - /articles/be-social - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social -intro: 'Puedes interactuar con personas, repositorios y organizaciones en {% data variables.product.prodname_dotcom %}. Ve en qué están trabajando los demás y con quién se están conectando desde tu tablero personal.' +intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.' permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' @@ -19,63 +19,63 @@ topics: - Notifications - Accounts --- +To learn about accessing your personal dashboard, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." -Para conocer más sobre cómo acceder a tu tablero personal, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". +## Following people -## Seguir a personas +When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." -When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". +Click **Follow** on a person's profile page to follow them. -Haz clic en **Follow** (Seguir) en la página de perfil de una persona para seguirla. +![Follow user button](/assets/images/help/profile/follow-user-button.png) -![Botón Follow user (Seguir usuario)](/assets/images/help/profile/follow-user-button.png) +## Watching a repository -## Ver un repositorio +You can watch a repository to receive notifications for new pull requests and issues. When the owner updates the repository, you'll see the changes in your personal dashboard. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}." -Puedes ver un repositorio para recibir notificaciones para las nuevas solicitudes de extracción y propuestas. Cuando el propietario actualiza el repositorio, verás los cambios en tu tablero personal. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}." +Click **Watch** at the top of a repository to watch it. -Haz clic en **Watch** (Ver) en la parte superior del repositorio que desas ver. +![Watch repository button](/assets/images/help/repository/repo-actions-watch.png) -![Botón Watch repository (Ver repositorio)](/assets/images/help/repository/repo-actions-watch.png) - -## Unirse a la conversación +## Joining the conversation {% data reusables.support.ask-and-answer-forum %} -## Comunicarse con {% data variables.product.product_name %} +## Communicating on {% data variables.product.product_name %} -{% data variables.product.product_name %} proporciona herramientas de comunicación colaborativas integradas, tales como propuestas y solicitudes de cambios, lo que te permite interactuar de cerca con tu comunidad cuando creas un gran software. Para obtener un resumen de estas herramientas y la información sobre la especificidad de cada una de ellas, consulta la sección "[Guía rápida para comunicarte en {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)". +{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)." -## Hacer un poco más +## Doing even more -### Crear solicitudes de extracción +### Creating pull requests - Es posible que desees contribuir al proyecto de otras personas, ya sea para agregar características o para arreglar errores. Luego de realizar cambios, permite que el autor original lo sepa al enviar una solicitud de extracción. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." + You may want to contribute to another person's project, whether to add features or to fix bugs. After making changes, let the original author know by sending a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." - ![Botón Pull request (Solicitud de extracción)](/assets/images/help/repository/repo-actions-pullrequest.png) + ![Pull request button](/assets/images/help/repository/repo-actions-pullrequest.png) -### Usar propuestas +### Using issues -Al colaborar en un repositorio, usa las propuestas para realizar el seguimiento de ideas, mejoras, tareas o errores. Para obtener más información, consulta '[Acerca de las propuestas](/articles/about-issues/)". +When collaborating on a repository, use issues to track ideas, enhancements, tasks, or bugs. For more information, see '[About issues](/articles/about-issues/)." -![Botón Issues (Propuestas)](/assets/images/help/repository/repo-tabs-issues.png) +![Issues button](/assets/images/help/repository/repo-tabs-issues.png) -### Participación en las organizaciones +### Participating in organizations -Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y administradores pueden establecer equipos con permisos especiales, tener un perfil de organización pública y realizar el seguimiento de la actividad dentro de la organización. Para obtener más información, consulta la sección "[Acerca de las organizaciones](/articles/about-organizations/)". +Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can establish teams with special permissions, have a public organization profile, and keep track of activity within the organization. For more information, see "[About organizations](/articles/about-organizations/)." -![Desplegable de contexto para cambiar cuenta](/assets/images/help/overview/dashboard-contextswitcher.png) +![Switch account context dropdown](/assets/images/help/overview/dashboard-contextswitcher.png) -### Explorar otros proyectos en {% data variables.product.prodname_dotcom %} +### Exploring other projects on {% data variables.product.prodname_dotcom %} -Descubre proyectos interesantes al utilizar {% data variables.explore.explore_github %}, [Explorar repositorios](https://github.com/explore), y el {% data variables.explore.trending_page %}. Marca con una estrella los proyectos interesantes y regresa posteriormente. Visita tu {% data variables.explore.your_stars_page %} para ver todos los proyectos marcados con una estrella. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard/)". +Discover interesting projects using {% data variables.explore.explore_github %}, [Explore repositories](https://github.com/explore), and the {% data variables.explore.trending_page %}. Star interesting projects and come back to them later. Visit your {% data variables.explore.your_stars_page %} to see all your starred projects. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard/)." -## Celebrar +## Celebrate -Ahora estás conectado con la comunidad de {% data variables.product.product_name %}. ¿Qué deseas hacer ahora? ![Marcar un proyecto con una estrella](/assets/images/help/stars/star-a-project.png) +You're now connected to the {% data variables.product.product_name %} community. What do you want to do next? +![Star a project](/assets/images/help/stars/star-a-project.png) -- Para sincronizar tus proyectos de {% data variables.product.product_name %} con tu computadora, puedes configurar Git. Para obtener más información, consulta la sección [Configurar Git](/articles/set-up-git)". -- También puedes crear un repositorio en donde puedes poner todos tus proyectos y mantener tus flujos de trabajo. Para obtener más información, consulta la sección "[Crear un repositorio](/articles/create-a-repo)". -- Puedes bifurcar un repositorio para hacer los cambios que quieras ver sin afectar al repositorio original. Para obtener más información, consulta la sección "[Bifurcar un repositorio](/articles/fork-a-repo)". +- To synchronize your {% data variables.product.product_name %} projects with your computer, you can set up Git. For more information see "[Set up Git](/articles/set-up-git)." +- You can also create a repository, where you can put all your projects and maintain your workflows. For more information see, "[Create a repository](/articles/create-a-repo)." +- You can fork a repository to make changes you want to see without affecting the original repository. For more information, see "[Fork a repository](/articles/fork-a-repo)." - {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md index 7168cf58df..f40be52431 100644 --- a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md @@ -1,12 +1,12 @@ --- -title: Bifurcar un repositorio +title: Fork a repo redirect_from: - /fork-a-repo/ - /forking/ - /articles/fork-a-repo - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo -intro: Una ramificación es una copia de un repositorio. Bifurcar un repositorio te permite experimentar libremente con cambios sin afectar el proyecto original. +intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' @@ -19,46 +19,46 @@ topics: - Notifications - Accounts --- +## About forks -## Acerca de las bifurcaciones +Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." -Casi siempre las bifurcaciones se usan para proponer cambios al proyecto de otra persona o para usar el proyecto de otra persona como inicio de tu propia idea. Puedes bifurcar un repositorio para crear una copia del mismo y hacer cambios sin afectar al repositorio ascendente. Para obtener más información, consulta la sección "[Trabajar con las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". +### Propose changes to someone else's project -### Proponer cambios para el proyecto de otra persona +For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you've found, you can: -Por ejemplo, puedes utilizar ramificaciones para proponer cambios relacionados con arreglar un error. En lugar de registrar una propuesta para un error que has encontrado, puedes hacer lo siguiente: +- Fork the repository. +- Make the fix. +- Submit a pull request to the project owner. -- Bifurcar el repositorio. -- Solucionar el problema. -- Emitir solicitudes de cambios al propietario del proyecto. +### Use someone else's project as a starting point for your own idea. -### Usar el proyecto de otra persona como inicio de tu propia idea +Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](http://opensource.org/about)" on the Open Source Initiative. -El software de código abierto se basa en la idea de que, si compartimos el código, podemos crear software más confiable y mejor. Para obtener más información, consulta la sección "[Acerca de la Iniciativa de Código Abierto](http://opensource.org/about)" en la Iniciativa de Código Abierto. - -Para obtener más información acerca de aplicar los principios de código abierto al trabajo de desarrollo de tu organización en {% data variables.product.product_location %}, consulta la documentación técnica de {% data variables.product.prodname_dotcom %} "[Introducción al innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)". +For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% ifversion fpt or ghes or ghec %} -Cuando creas tu repositorio público desde una ramificación del proyecto de alguien más, asegúrate de incluir el archivo de licencia que determine cómo quieres que se comparta tu proyecto con los demás. Para obtener más información, consulta la sección "[Elegir una licencia de código abierto](https://choosealicense.com/)" en choosealicense.com. +When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com. -{% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %} +{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} {% endif %} -## Prerrequisitos +## Prerequisites -Si todavía no lo has hecho, primero debes [configurar Git](/articles/set-up-git). No olvides [configurar la autenticación a {% data variables.product.product_location %} desde Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). +If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.product.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well. -## Bifurcar un repositorio +## Forking a repository {% include tool-switcher %} {% webui %} -Puedes ramificar un proyecto para proponer cambios en los repositorios precedentes u originales. En este caso, es una buena práctica sincronizar tu bifurcación periódicamente con el repositorio ascendente. Para hacerlo, deberás usar Git en la línea de comando. Puedes practicar cómo configurar el repositorio precedente utilizando el mismo repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) que acabas de ramificar. +You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked. 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. -2. En el ángulo superior derecho de la página, haz clic en **Bifurcar**. ![Botón Bifurcar](/assets/images/help/repository/fork_button.jpg) +2. In the top-right corner of the page, click **Fork**. +![Fork button](/assets/images/help/repository/fork_button.jpg) {% endwebui %} @@ -66,13 +66,13 @@ Puedes ramificar un proyecto para proponer cambios en los repositorios precedent {% data reusables.cli.cli-learn-more %} -Para crear una bifurcación de un repositorio, utiliza el subcomando `gh repo fork`. +To create a fork of a repository, use the `gh repo fork` subcommand. ```shell gh repo fork repository ``` -Para crear la bifurcación en una organización, utiliza el marcador `--org`. +To create the fork in an organization, use the `--org` flag. ```shell gh repo fork repository --org "octo-org" @@ -83,9 +83,9 @@ gh repo fork repository --org "octo-org" {% desktop %} {% enddesktop %} -## Clonar tu repositorio bifurcado +## Cloning your forked repository -Ahora mismo, tienes una bifurcación del repositorio Spoon-Knife, pero no tienes los archivos de ese repositorio localmente en tu computadora. +Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer. {% include tool-switcher %} {% webui %} @@ -94,12 +94,12 @@ Ahora mismo, tienes una bifurcación del repositorio Spoon-Knife, pero no tienes {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} -4. Escribe `git clone`, y luego pega la URL que copiaste antes. Se verá así, con tu nombre de usuario de {% data variables.product.product_name %} en lugar de `YOUR-USERNAME`: +4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`: ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife ``` -5. Presiona **Enter** (Intro). Se creará tu clon local. +5. Press **Enter**. Your local clone will be created. ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife > Cloning into `Spoon-Knife`... @@ -115,7 +115,7 @@ Ahora mismo, tienes una bifurcación del repositorio Spoon-Knife, pero no tienes {% data reusables.cli.cli-learn-more %} -Para crear un clon de tu bifurcación, utiliza el marcador `--clone`. +To create a clone of your fork, use the `--clone` flag. ```shell gh repo fork repository --clone=true @@ -133,9 +133,9 @@ gh repo fork repository --clone=true {% enddesktop %} -## Configurar a Git para sincronizar tu bifurcación con el repositorio original +## Configuring Git to sync your fork with the original repository -Cuando bifurcas un proyecto para proponer cambios en el repositorio original, puedes configurar Git para extraer cambios del original, o repositorio ascendente, en el clon local de tu bifurcación. +When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork. {% include tool-switcher %} {% webui %} @@ -143,24 +143,24 @@ Cuando bifurcas un proyecto para proponer cambios en el repositorio original, pu 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} -4. Cambia el directorio de la ubicación de la bifurcación que clonaste. - - Para ir a tu directorio de inicio, escribe solo `cd` sin ningún otro texto. - - Para generar una lista de los archivos y carpetas en tu directorio actual, escribe `ls`. - - Para ir a uno de los directorios de la lista, escribe `cd your_listed_directory`. - - Para subir un directorio, escribe `cd ..`. -5. Escribe `git remote -v` y presiona **Intro**. Verás el repositorio remoto configurado actualmente para tu bifurcación. +4. Change directories to the location of the fork you cloned. + - To go to your home directory, type just `cd` with no other text. + - To list the files and folders in your current directory, type `ls`. + - To go into one of your listed directories, type `cd your_listed_directory`. + - To go up one directory, type `cd ..`. +5. Type `git remote -v` and press **Enter**. You'll see the current configured remote repository for your fork. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) ``` -6. Escribe `git remote add upstream` y luego pega la URL que copiaste en el Paso 2 y presiona **Intro**. Se verá así: +6. Type `git remote add upstream`, and then paste the URL you copied in Step 2 and press **Enter**. It will look like this: ```shell $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git ``` -7. Para verificar el nuevo repositorio ascendente que has especificado para tu bifurcación, escribe nuevamente `git remote -v`. Debes ver la URL para tu bifurcación como `origin` y la URL para el repositorio original como `upstream`. +7. To verify the new upstream repository you've specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) @@ -169,7 +169,7 @@ Cuando bifurcas un proyecto para proponer cambios en el repositorio original, pu > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) ``` -Ahora, puedes mantener tu bifurcación sincronizada con el repositorio ascendente con unos pocos comandos Git. Para obtener más información, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". +Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)." {% endwebui %} @@ -177,13 +177,13 @@ Ahora, puedes mantener tu bifurcación sincronizada con el repositorio ascendent {% data reusables.cli.cli-learn-more %} -Para configurar un repositorio remoto para el repositorio bifurcado, utiliza el marcador `--remote`. +To configure a remote repository for the forked repository, use the `--remote` flag. ```shell gh repo fork repository --remote=true ``` -Para especificar el nombre del repositorio remoto, utiliza el marcador `--remote-name`. +To specify the remote repository's name, use the `--remote-name` flag. ```shell gh repo fork repository --remote-name "main-remote-repo" @@ -191,26 +191,26 @@ gh repo fork repository --remote-name "main-remote-repo" {% endcli %} -### Pasos siguientes +### Next steps -Puedes hacer cualquier cambio a una ramificación, incluyendo: +You can make any changes to a fork, including: -- **Crear ramas:** [Las *ramas*](/articles/creating-and-deleting-branches-within-your-repository/) te permiten diseñar nuevas características o probar ideas sin poner en riesgo tu proyecto principal. -- **Abrir solicitudes de extracción:** Si deseas colaborar con el repositorio original, puedes enviar una solicitud al autor original para extraer tu bifurcación en su repositorio enviando una [solicitud de extracción](/articles/about-pull-requests). +- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk. +- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -## Encontrar otro repositorio para bifurcar -Bifurca un repositorio para comenzar a colaborar con un proyecto. {% data reusables.repositories.you-can-fork %} +## Find another repository to fork +Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %} -{% ifversion fpt or ghec %}Puedes dirigirte a [Explorar](https://github.com/explore) para encontrar proyectos y comenzar a colaborar con repositorios de código abierto. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." +{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." {% endif %} -## Celebrar +## Celebrate -Ahora ya has bifurcado un repositorio, has practicado la clonación de tu bifurcación y has configurado un repositorio ascendente. Para obtener más información sobre cómo clonar la bifurcación y sincronizar los cambios en un repositorio bifurcado desde tu computadora, consulta la sección "[Configurar Git](/articles/set-up-git)". +You have now forked a repository, practiced cloning your fork, and configured an upstream repository. For more information about cloning the fork and syncing the changes in a forked repository from your computer see "[Set up Git](/articles/set-up-git)." -También puedes crear un repositorio nuevo en donde pongas todos tus proyectos y compartir el código en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Crear un repositorio](/articles/create-a-repo)". +You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. For more information see, "[Create a repository](/articles/create-a-repo)." -Cada repositorio en {% data variables.product.product_name %} pertenece a una persona u organización. Puedes interactuar con las personas, repositorios y organizaciones conectándote y siguiéndolos en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Sé sociable ](/articles/be-social)". +Each repository in {% data variables.product.product_name %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)." {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md index b35f11117f..5ce711cfb5 100644 --- a/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md +++ b/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md @@ -1,12 +1,12 @@ --- -title: Recursos de aprendizaje de Git y GitHub +title: Git and GitHub learning resources redirect_from: - /articles/good-resources-for-learning-git-and-github/ - /articles/what-are-other-good-resources-for-learning-git-and-github/ - /articles/git-and-github-learning-resources - /github/getting-started-with-github/git-and-github-learning-resources - /github/getting-started-with-github/quickstart/git-and-github-learning-resources -intro: 'Hay muchos recursos útiles de Git y {% data variables.product.product_name %} disponibles en la web. La siguientes es una pequeña lista de nuestros favoritos.' +intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!' versions: fpt: '*' ghes: '*' @@ -14,51 +14,50 @@ versions: ghec: '*' authors: - GitHub -shortTitle: Recursos de aprendizaje +shortTitle: Learning resources --- +## Using Git -## Utilizar GitHub +Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator. -Para familiarizarte con Git, visita el [sitio oficial del proyecto Git](https://git-scm.com) y lee el [libro de ProGit](http://git-scm.com/book). Puedes revisar la [lista de comandos de Git](https://git-scm.com/docs) o la [referencia para buscar comandos de Git](http://gitref.org) mientras usas el simulador [Try Git](https://try.github.com). - -## Uso de {% data variables.product.product_name %} +## Using {% data variables.product.product_name %} {% ifversion fpt or ghec %} -{% data variables.product.prodname_learning %} ofrece cursos interactivos gratuitos integrados en {% data variables.product.prodname_dotcom %} con evaluación y asistencia instantáneas y automatizadas. Aprende a abrir tu primera solicitud de extracción, hacer tu primera contribución de código abierto, crear un sitio {% data variables.product.prodname_pages %}, y mucho más. Para obtener más información acerca de los cursos ofrecidos, consulta [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). +{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). {% endif %} -Adquiere más conocimientos con {% data variables.product.product_name %} a través de nuestros artículos de [guías de inicio](/categories/getting-started-with-github/). Consulta nuestro [ flujo de {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow) para acceder a una introducción del proceso. Consulta nuestras [guías de descripción general](https://guides.github.com) para conocer nuestros conceptos básicos. +Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts. {% data reusables.support.ask-and-answer-forum %} -### Ramas, bifurcaciones y solicitudes de extracción +### Branches, forks, and pull requests -Conoce más sobre las [ramas de Git](http://learngitbranching.js.org/) usando una herramienta interactiva. Lee más acerca de [bifrucaciones](/articles/about-forks) y [solicitudes de extracción](/articles/using-pull-requests), además de [cómo usar las solicitudes de extracción](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) en {% data variables.product.prodname_dotcom %}. Accede a las referencias sobre cómo utilizar {% data variables.product.prodname_dotcom %} desde la [línea de comandos](https://cli.github.com/). +Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). -### Ponte al día +### Tune in -Nuestro {% data variables.product.prodname_dotcom %} [canal con guías y capacitación de YouTube](https://youtube.com/githubguides) ofrece tutoriales acerca de [solicitudes de extracción](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [ bifurcaciones](https://www.youtube.com/watch?v=5oJHRbqEofs), las funciones de [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22) y [reinicio](https://www.youtube.com/watch?v=BKPjPMVB81g). Cada tema se cubre en menos de 5 minutos. +Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less. -## Capacitación +## Training -### Cursos gratuitos +### Free courses -{% data variables.product.product_name %} ofrece una serie de [cursos interactivos de capacitación bajo pedido](https://lab.github.com/), incluyendo aquellos de [introducción a {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); cursos de lenguajes de programación y herramientas tales como HTML, Python y NodeJS; y cursos sobre las herramientas específicas de {% data variables.product.product_name %}, tales como {% data variables.product.prodname_actions %}. +{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://lab.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); courses on programming languages and tools such as HTML, Python, and NodeJS; and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}. -### Programas educativos basados en la web de {% data variables.product.prodname_dotcom %} +### {% data variables.product.prodname_dotcom %}'s web-based educational programs -{% data variables.product.prodname_dotcom %} ofrece [capacitaciones](https://services.github.com/#upcoming-events) en vivo con un enfoque práctico basado en proyectos tanto para los amantes de la línea de comando como para quienes no están familiarizados con esta herramienta. +{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't. -### Capacitación para tu compañía +### Training for your company -{% data variables.product.prodname_dotcom %} ofrece [clases presenciales](https://services.github.com/#offerings) a cargo de nuestros capacitadores sumamente experimentados. [Contáctanos](https://services.github.com/#contact) para que podamos responder tus preguntas relacionadas con la capacitación. +{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions. ## Extras -An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Adapta libremente nuestras [plantillas .gitignore](https://github.com/github/gitignore) para que resuelvan tus necesidades. +An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs. -Amplía el alcance de tu {% data variables.product.prodname_dotcom %} con[integraciones de {% ifversion fpt or ghec %}](/articles/about-integrations){% else %}integraciones{% endif %}, o instala [{% data variables.product.prodname_desktop %}](https://desktop.github.com) y el poderoso editor de texto [Atom](https://atom.io). +Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [Atom](https://atom.io) text editor. -Descubre cómo lanzar y hacer crecer tu proyecto de código abierto con las [Guías de código abierto](https://opensource.guide/). +Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/). diff --git a/translations/es-ES/content/get-started/quickstart/github-flow.md b/translations/es-ES/content/get-started/quickstart/github-flow.md index 79a02fe860..0db3281778 100644 --- a/translations/es-ES/content/get-started/quickstart/github-flow.md +++ b/translations/es-ES/content/get-started/quickstart/github-flow.md @@ -1,6 +1,6 @@ --- -title: Flujo de GitHub -intro: 'Sigue el flujo de {% data variables.product.prodname_dotcom %} para colaborar en los proyectos.' +title: GitHub flow +intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.' redirect_from: - /articles/creating-and-editing-files-in-your-repository/ - /articles/github-flow-in-the-browser/ @@ -18,85 +18,84 @@ topics: - Fundamentals miniTocMaxHeadingLevel: 3 --- +## Introduction -## Introducción +{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap). -El flujo de {% data variables.product.prodname_dotcom %} es un flujo de trabajo ligero basado en ramas. El flujo de {% data variables.product.prodname_dotcom %} es útil para todos, no solo para los desarrolladores. Por ejemplo, en {% data variables.product.prodname_dotcom %} utilizamos el flujo de {% data variables.product.prodname_dotcom %} para nuestra [política de sitio](https://github.com/github/site-policy), [documentación](https://github.com/github/docs) e [itinerario](https://github.com/github/roadmap). +## Prerequisites -## Prerrequisitos +To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% ifversion fpt or ghec %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %} -Para seguir el flujo de {% data variables.product.prodname_dotcom %}, necesitarás una cuenta de {% data variables.product.prodname_dotcom %} y un repositorio. Para obtener más información sobre cómo crear una cuenta, consulta la sección "[Registrarse para {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)". Para obtener más información sobre cómo crear un repositorio, consulta la sección "[Crear un repositorio](/github/getting-started-with-github/create-a-repo)".{% ifversion fpt or ghec %} Para obtener más información sobre cómo encontrar un repositorio existente en el cual contribuir, consulta la sección "[Encontrar formas para contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".{% endif %} - -## Seguir el flujo de {% data variables.product.prodname_dotcom %} +## Following {% data variables.product.prodname_dotcom %} flow {% tip %} {% ifversion fpt or ghec %} -**Tip:** Puedes completar todos los pasos del flujo de {% data variables.product.prodname_dotcom %} mediante la interface web de {% data variables.product.prodname_dotcom %}, la línea de comandos y el [{% data variables.product.prodname_cli %}](https://cli.github.com), o por [{% data variables.product.prodname_desktop %}](/free-pro-team@latest/desktop). +**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/free-pro-team@latest/desktop). {% else %} -**Tip:** Puedes completar todos los pasos del flujo de {% data variables.product.prodname_dotcom %} a través de la interface web de {% data variables.product.prodname_dotcom %} o a través de la línea de comandos y el [{% data variables.product.prodname_cli %}](https://cli.github.com). +**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com). {% endif %} {% endtip %} -### Crear una rama +### Create a branch - Crear una rama en tu repositorio. Un nombre de rama corto y descriptivo permite que tus colaboradores vean el trabajo contínuo de un vistazo. Por ejemplo, `increase-test-timeout` o `add-code-of-conduct`. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)". + Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)." - Si creas una rama, creas un espacio para trabajar sin afectar a la rama predeterminada. Adicionalmente, otorgas a los colaboradores una oportunidad de revisar tu trabajo. + By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work. -### Hacer cambios +### Make changes -En tu rama, haz cualquier cambio que quieras en el repositorio. Para obtener más información, consulta las secciones "[Crear archivos nuevos](/articles/creating-new-files)", "[Editar archivos](/articles/editing-files)", "[Renombrar un archivo](/articles/renaming-a-file)", "[Migrar un archivo a una ubicación nueva](/articles/moving-a-file-to-a-new-location)" o "[Borrar archivos en un repositorio](/github/managing-files-in-a-repository/deleting-files-in-a-repository)". +On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)." -Tu rama es un lugar seguro para hacer cambios. Si cometes un error, peudes revertir tus cambios o subir cambios adicionales para arreglar el error. Tus cambios no terminrán en la rama predeterminada hasta que fusiones tu rama. +Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch. -Confirmar y subir tus cambios a tu rama. Dale un mensaje descriptivo a cada confirmación para ayudarte a ti mismo y a tus contribuyentes futuros a entender qué cambios contienen dichas confirmaciones. Por ejemplo, `fix typo` o `increase rate limit`. +Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`. -Idealmente, cada confirmación contiene un cambio completo y aislado. Esto facilita que reviertas tus cambios si decides adoptar otro enfoque. Por ejemplo, si quieres renombrar una variable y agregar algunas pruebas, pon el nuevo nombre de la variable en una confirmación y las pruebas en otra. Posteriormente, si quieres mantener las pruebas pero quieres revertir el renombramiento de variable, puedes revertir la confirmación específica que contenía dicho renombramiento. Si pones el renombre de variable y las pruebas en la misma confirmación o si propagas el renombre de variable a través de varias confirmaciones, harías más esfuerzo en revertir tus cambios. +Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes. -Si confirmas y subes tus cambios, respaldas tu trabajo en un almacenamiento remoto. Esto significa que puedes acceder a tu trabajo desde cualquier dispositivo. Esto también significa que tus colaboradores pueden ver tu trabajo, responder tus preguntas y hacer sugerencias o contribuciones. +By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions. -Sigue haciando, confirmando y subiendo cambios a tu rama hasta que estés listo para solicitar retroalimentación. +Continue to make, commit, and push changes to your branch until you are ready to ask for feedback. {% tip %} -**Tip:** Haz una rama separada para cada conjunto de cambios no relacionados. Esto facilita a los revisores dar retroalimentación. También te facilita tanto a ti mismo como alos colaboradores futuros entender los cambios y revertir o compilar sobre ellos. Adicionalmente, si hay un retraso en un conjunto de cambios, tus otros cambios tampoco se retrasarán. +**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed. {% endtip %} -### Crear una solicitud de extracción +### Create a pull request -Crea una solicitud de cambios para pedir a los colaboradores retroalimentación sobre ellos. La revisión de solicitude sde cambios es tan valiosa que algunos repositorios requieren una revisión aprobatoria antes de que estas se puedan fusionar. Si quieres tener retroalimentación o consejos tempranos antes de que completes tus cambios, peudes marcar tu solicitud de cambios como borrador. Para obtener más información, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request)". +Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)." -Cuando creas una solicitud de cambios, incluye un resumen de estos, así como la explicación del problema que solucionan. Puedes incluir imágenes, enlaces y tablas para ayudar a transmitir esta información. Si tu solicitud de cambios aborda un problema, vincula la propuesta para que los interesados en ella estén conscientes de la solicitud de cambios y viceversa. Si la enlazas con una palabra clave, la propuesta se cerrará automáticamente cuando se fusione la solicitud de cambios. Para obtener más información, consulta las secciones "[Sintaxis de formato y escritura básica](/github/writing-on-github/basic-writing-and-formatting-syntax)" y "[Enlazar una solicitud de cambios a una propuesta](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". +When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." -![cuerpo de la solicitud de cambios](/assets/images/help/pull_requests/pull-request-body.png) +![pull request body](/assets/images/help/pull_requests/pull-request-body.png) -Adicionalmente a llenar el cuerpo de la solicitud de cambios, puedes agregar comentarios a las líneas específicas de la solicitud de cambios para señalar algo explícitamente para los revisores. +In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers. -![comentario de la solicitud de cambios](/assets/images/help/pull_requests/pull-request-comment.png) +![pull request comment](/assets/images/help/pull_requests/pull-request-comment.png) -Tu repositorio podría estar configurado para solicitar una revisión de usuarios o equipos específicos automáticamente cuando se crea una solicitud de cambios. También puedes @mencionar manualmente o solicitar una revisión de personas o equipos específicos. +Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams. -Si tu repositorio tiene verificaciones configuradas para que se ejecuten en las solicitudes de cambios, verás cualquier verificación que falló en tu solicitud de cambios. Esto te ayuda a detectar errores antes de fusionar tu rama. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/github/collaborating-with-issues-and-pull-requests/about-status-checks)". +If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." -### Abordar comentarios de revisión +### Address review comments -Los revisores deben dejar preguntas, comentarios y sugerencias. Los revisores pueden comentar en toda la solicitud de cambios o agregar comentarios en líneas específicas. Tanto tú como los revisores pueden insertar imágenes o sugerencias de código para clarificar los comentarios. Para obtener más información, consulta la sección "[Revisar los cambios en una sollicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)". +Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." -Puedes seguir confirmando y subiendo cambios como respuesta a las revisiones. Tu solicitud de extracción se actualizará de manera automática. +You can continue to commit and push changes in response to the reviews. Your pull request will update automatically. -### Fusiona tu solicitud de cambios +### Merge your pull request -Una vez que se apruebe tu solicitud de cambios, fusiónala. Esto fusionará tu rama automáticamente para que tus cambios aparezcan en la rama predeterminada. {% data variables.product.prodname_dotcom %} retiene el historial de comentarios y confirmaciones en la solicitud de cambios para ayudar a los contribuyentes futuros a entender tus cambios. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)". +Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." -{% data variables.product.prodname_dotcom %} te dirá si tu solicitud de cambios tiene conflictos que se deban resolver antes de fusionarse. Para obtener más información, consulta "[Abordar conflictos de fusión](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)." +{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. For more information, see "[Addressing merge conflicts](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)." -La configuación de protección de rama podría bloquear la fusión si tu solicitud de cambios no cumple con algunos de los requisitos. Por ejemplo, necesitas cierto número de revisiones de aprobación o una revisión de aprobación de algún equipo específico. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". +Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." -### Borra tu rama +### Delete your branch -Después de que fusiones tu solicitud de cambios, borra tu rama. Esto indica que se ha completado el trabajo en la rama y te previene tanto a tí como a otras personas de que utilices ramas antiguas por acidente. Para obtener más información, consulta la sección "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)." +After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)." -No te preocupes por perder la información. No se borrará tu solicitud de cambios ni tu historial de confirmación. Siempre puedes restablecer la rama que borraste o revertir tu solicitud de cambios en caso de que lo necesites. +Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed. diff --git a/translations/es-ES/content/get-started/using-git/about-git-rebase.md b/translations/es-ES/content/get-started/using-git/about-git-rebase.md index 1e2682bef4..0fe4205bad 100644 --- a/translations/es-ES/content/get-started/using-git/about-git-rebase.md +++ b/translations/es-ES/content/get-started/using-git/about-git-rebase.md @@ -1,5 +1,5 @@ --- -title: Acerca del cambio de base de Git +title: About Git rebase redirect_from: - /rebase/ - articles/interactive-rebase/ @@ -7,69 +7,68 @@ redirect_from: - /github/using-git/about-git-rebase - /github/getting-started-with-github/about-git-rebase - /github/getting-started-with-github/using-git/about-git-rebase -intro: 'El comando `git rebase` te permite cambiar fácilmente una serie de confirmaciones, modificando el historial de tu repositorio. Puedes reordenar, editar o combinar confirmaciones.' +intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +Typically, you would use `git rebase` to: -Generalmente, usarás `git rebase` para: - -* Editar mensajes de confirmación previos. -* Combinar varias confirmaciones en una. -* Eliminar o revertir confirmaciones que ya no son necesarias. +* Edit previous commit messages +* Combine multiple commits into one +* Delete or revert commits that are no longer necessary {% warning %} -**Advertencia**: Como cambiar el historial de tu confirmación puede hacer las cosas difíciles para todos los que usan el repositorio, se considera una mala práctica cambiar de base las confirmaciones cuando ya las subiste a un repositorio. Para aprender cómo cambiar de base de forma segura en {% data variables.product.product_location %}, consulta "[Acerca de las fusiones de solicitud de extracción](/articles/about-pull-request-merges)". +**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.product.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." {% endwarning %} -## Cambiar de base las confirmaciones con una rama +## Rebasing commits against a branch -Para cambiar de base todas las confirmaciones entre otra rama y el estado de rama actual, puedes ingresar el siguiente comando en tu shell (ya sea el símbolo del sistema para Windows o la terminal para Mac y Linux): +To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux): ```shell $ git rebase --interactive other_branch_name ``` -## Cambiar de base las confirmaciones en un momento específico +## Rebasing commits against a point in time -Para cambiar de base las últimas confirmaciones en tu rama actual, puedes ingresar el siguiente comando en tu shell: +To rebase the last few commits in your current branch, you can enter the following command in your shell: ```shell $ git rebase --interactive HEAD~7 ``` -## Comandos disponibles mientras se cambia de base +## Commands available while rebasing -Hay seis comandos disponibles mientras se cambia la base: +There are six commands available while rebasing:
    pick
    -
    pick simplemente significa que la confirmación está incluida. Reordenar los comandos pick cambia el orden de las confirmaciones cuando el cambio de base está en progreso. Si eliges no incluir una confirmación, debes eliminar la línea completa.
    +
    pick simply means that the commit is included. Rearranging the order of the pick commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line.
    reword
    -
    El comando reword es similar a pick, pero después de usarlo, el proceso de cambio de base se pausará y te dará una oportunidad de alterar el mensaje de confirmación. Cualquier cambio hecho por la confirmación no se ve afectado.
    +
    The reword command is similar to pick, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected.
    edit
    -
    Si eliges edit una confirmación, se te dará la oportunidad de modificar la confirmación, lo que significa que puedes agregar o cambiar la confirmación por completo. También puedes realizar más confirmaciones antes de continuar con el cambio de base. Esto te permite dividir una confirmación grande en otras más pequeñas o eliminar cambios erróneos hechos en una confirmación.
    +
    If you choose to edit a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit.
    -
    combinar
    -
    Este comando te permite combinar dos o más confirmaciones en una única confirmación. Una confirmación se combina en la confirmación de arriba. Git te da la oportunidad de escribir un mensaje de confirmación nuevo describiendo ambos cambios.
    +
    squash
    +
    This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.
    fixup
    -
    Esto es similar a squash, pero se descarta el mensaje de la confirmación que se fusiona. La confirmación simplemente se fusiona en la confirmación de arriba y el mensaje de la confirmación anterior se usa para describir ambos cambios.
    +
    This is similar to squash, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.
    exec
    -
    Esto te permite ejecutar comandos shell de forma arbitraria con una confirmación.
    +
    This lets you run arbitrary shell commands against a commit.
    -## Un ejemplo del uso de `git rebase` +## An example of using `git rebase` -Sin importar qué comando uses, Git iniciará [tu editor de texto predeterminado](/github/getting-started-with-github/associating-text-editors-with-git) y abrirá un archivo que detalla las confirmaciones en el rango que has elegido. Ese archivo se ve así: +No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this: ``` pick 1fc6c95 Patch A @@ -80,33 +79,33 @@ pick fa39187 something to add to patch A pick 4ca2acc i cant' typ goods pick 7b36971 something to move before patch B -# Cambiar de base 41a72e6..7b36971 a 41a72e6 +# Rebase 41a72e6..7b36971 onto 41a72e6 # -# Commandos: -# p, pick = usar la confirmación -# r, reword = usar la confirmación, pero editar el mensaje de confirmación -# e, edit = usar la confirmación, pero detenerse para correcciones -# s, squash = usar la confirmación, pero unirla con la confirmación anterior -# f, fixup = como "squash", pero descartar el mensaje de registro de esta confirmación -# x, exec = ejecutar comando (el resto de la línea) usando shell +# Commands: +# p, pick = use commit +# r, reword = use commit, but edit the commit message +# e, edit = use commit, but stop for amending +# s, squash = use commit, but meld into previous commit +# f, fixup = like "squash", but discard this commit's log message +# x, exec = run command (the rest of the line) using shell # -# Si eliminas una línea aquí, ESA CONFIRMACIÓN SE PERDERÁ. -# Sin embargo, si eliminas todo, este cambio de base será interrumpido. +# If you remove a line here THAT COMMIT WILL BE LOST. +# However, if you remove everything, the rebase will be aborted. # ``` -Desglosando esta información, de principio a fin, vemos que: +Breaking this information, from top to bottom, we see that: -- Se enumeran siete confirmaciones, lo que indica que hubo siete cambios entre nuestro punto de partida y el estado de nuestra rama actual. -- Las confirmaciones que eliges cambiar de base se clasifican en el orden de los cambios más antiguos (arriba) a los cambios más nuevos (abajo). -- Cada línea detalla un comando (por defecto, `pick`), la confirmación SHA y el mensaje de confirmación. Todo el procedimiento `git rebase` se centra en tu manipulación de estas tres columnas. Los cambios que realizas se *rebasan* en tu repositorio. -- Después de las confirmaciones, Git te dice el rango de confirmaciones con las que estamos trabajando (`41a72e6..7b36971`). -- Finalmente, Git te ayuda diciéndote los comandos que están disponibles para ti cuando cambias de base las confirmaciones. +- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state. +- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom). +- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository. +- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`). +- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits. -## Leer más +## Further reading -- "[Usar Git rebase](/articles/using-git-rebase)" -- [El capítulo "Ramificación de Git" del libro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing) -- [El capítulo "Rebase interactivo" del libro _Pro Git_](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) -- "[Combinar confirmaciones con cambio de base](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" -- "[Sincronizar tu rama](/desktop/contributing-to-projects/syncing-your-branch)" en la documentación de {% data variables.product.prodname_desktop %} +- "[Using Git rebase](/articles/using-git-rebase)" +- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing) +- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) +- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" +- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md index 50c54bd8d6..209c0beb0e 100644 --- a/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md +++ b/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md @@ -1,6 +1,6 @@ --- -title: Obtener cambios de un repositorio remoto -intro: Puedes usar los comandos Git más frecuentes para acceder a repositorios remotos. +title: Getting changes from a remote repository +intro: You can use common Git commands to access remote repositories. redirect_from: - /articles/fetching-a-remote/ - /articles/getting-changes-from-a-remote-repository @@ -12,71 +12,76 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Obtener cambios desde un remoto +shortTitle: Get changes from a remote --- +## Options for getting changes -## Opciones para obtener cambios +These commands are very useful when interacting with [a remote repository](/github/getting-started-with-github/about-remote-repositories). `clone` and `fetch` download remote code from a repository's remote URL to your local computer, `merge` is used to merge different people's work together with yours, and `pull` is a combination of `fetch` and `merge`. -Estos comandos son muy útiles cuando interactúas con [un repositorio remoto](/github/getting-started-with-github/about-remote-repositories). `clone` y `fetch` descargan código remoto de la URL de un repositorio remoto en tu computadora local, `merge` se usa para fusionar el trabajo de diferentes personas con el tuyo, y `pull` es una combinación de `fetch` y `merge`. +## Cloning a repository -## Clonar un repositorio - -Para obtener una copia completa del repositorio de otro usuario, usa `git clone` de la siguientes manera: +To grab a complete copy of another user's repository, use `git clone` like this: ```shell $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git -# Clona el repositorio en tu computadora +# Clones a repository to your computer ``` -Puedes elegir entre [distintas URL](/github/getting-started-with-github/about-remote-repositories) cuando clonas un repositorio. Cuando inicias sesión en {% data variables.product.prodname_dotcom %}, estas URL están disponibles debajo de los detalles del repositorio: +You can choose from [several different URLs](/github/getting-started-with-github/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available below the repository details: -![Lista de URL remotas](/assets/images/help/repository/remotes-url.png) +![Remote URL list](/assets/images/help/repository/remotes-url.png) -Cuando ejecutas `git clone`, se producen las siguientes acciones: -- Se forma una nueva carpeta llamada `repo`. -- Esta carpeta se inicializa como un repositorio de Git. -- Se crea un remoto llamado `origin` que apunta a la URL desde donde clonaste. -- Todos los archivos y confirmaciones del repositorio se descargan aquí. -- La rama predeterminada está desmarcada +When you run `git clone`, the following actions occur: +- A new folder called `repo` is made +- It is initialized as a Git repository +- A remote named `origin` is created, pointing to the URL you cloned from +- All of the repository's files and commits are downloaded there +- The default branch is checked out -Para cada rama `foo` en el repositorio remoto, se crea la rama de seguimiento remoto correspondiente `refs/remotes/origin/foo` en tu repositorio local. Por lo general, puedes abreviar estos nombres de rama de seguimiento remoto como `origin/foo`. +For every branch `foo` in the remote repository, a corresponding remote-tracking branch +`refs/remotes/origin/foo` is created in your local repository. You can usually abbreviate +such remote-tracking branch names to `origin/foo`. -## Extraer cambios de un repositorio remoto +## Fetching changes from a remote repository -Usa `git fetch` para recuperar trabajo nuevo realizado por otras personas. Extraer desde un repositorio permite obtener todas las etiquetas y ramas de seguimiento remoto *sin* fusionar estos cambios en tus propias ramas. +Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags *without* merging those changes into your own branches. -Si ya tienes un repositorio local con una URL remota configurada para el proyecto deseado, puedes tomar toda la información nueva si utilizas `git fetch *remotename*` en la terminal: +If you already have a local repository with a remote URL set up for the desired project, you can grab all the new information by using `git fetch *remotename*` in the terminal: ```shell $ git fetch remotename -# Extrae las actualizaciones realizadas en un repositorio remoto +# Fetches updates made to a remote repository ``` -De otra forma, siempre puedes agregar un remoto nuevo y luego recuperarlo. Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)." +Otherwise, you can always add a new remote and then fetch. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Fusionar cambios en tu rama local +## Merging changes into your local branch -La fusión combina tus cambios locales con los cambios realizados por otros. +Merging combines your local changes with changes made by others. -Por lo general, fusionas una rama de seguimiento remoto (es decir, una rama extraída desde un repositorio remoto) con tu rama local: +Typically, you'd merge a remote-tracking branch (i.e., a branch fetched from a remote repository) with your local branch: ```shell $ git merge remotename/branchname -# Fusiona actualizaciones realizadas en línea con tu trabajo local +# Merges updates made online with your local work ``` -## Extraer cambios de un repositorio remoto +## Pulling changes from a remote repository -`git pull` es un atajo conveniente para realizar tanto `git fetch` y `git merge` en el mismo comando: +`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command: ```shell $ git pull remotename branchname -# Obtiene actualizaciones en línea y las fusiona con tu trabajo local. +# Grabs online updates and merges them with your local work ``` -Como `pull` realiza una fusión en los cambios recuperados, debes asegurarte de que tu trabajo local esté confirmado antes de ejecutar el comando `pull`. Si se produce un [conflicto de fusión](/articles/resolving-a-merge-conflict-using-the-command-line) que no puedes resolver, o si decides abandonar la fusión, puedes usar `git merge --abort` para hacer que la rama vuelva al estado anterior antes de que extrajeras. +Because `pull` performs a merge on the retrieved changes, you should ensure that +your local work is committed before running the `pull` command. If you run into +[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line) +you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort` +to take the branch back to where it was in before you pulled. -## Leer más +## Further reading -- "[Trabajar con remotos" desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes){% ifversion fpt or ghec %} -- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)"{% endif %} +- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %} +- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"{% endif %} diff --git a/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md index 670f409de7..8303fb27d5 100644 --- a/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md @@ -1,6 +1,6 @@ --- -title: Subir confirmaciones de cambios a un repositorio remoto -intro: Utiliza `git push` para subir confirmaciones de cambios realizadas en tu rama local a un repositorio remoto. +title: Pushing commits to a remote repository +intro: Use `git push` to push commits made on your local branch to a remote repository. redirect_from: - /articles/pushing-to-a-remote/ - /articles/pushing-commits-to-a-remote-repository @@ -12,96 +12,108 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Subir confirmaciones a un remoto +shortTitle: Push commits to a remote --- +## About `git push` +The `git push` command takes two arguments: -## Acerca de `git push` -El comando `git push` toma dos argumentos: +* A remote name, for example, `origin` +* A branch name, for example, `main` -* Un nombre remoto, por ejemplo, `origin` -* Un nombre de rama, por ejemplo, `main` - -Por ejemplo: +For example: ```shell git push <REMOTENAME> <BRANCHNAME> ``` -Como ejemplo, habitualmente ejecutas `git push origin main` para subir tus cambios locales a tu repositorio en línea. +As an example, you usually run `git push origin main` to push your local changes +to your online repository. -## Renombrar ramas +## Renaming branches -Para renombrar una rama, utilizarías el mismo comando `git push`, pero agregarías un argumento más: el nombre de la nueva rama. Por ejemplo: +To rename a branch, you'd use the same `git push` command, but you would add +one more argument: the name of the new branch. For example: ```shell git push <REMOTENAME> <LOCALBRANCHNAME>:<REMOTEBRANCHNAME> ``` -Esto sube `LOCALBRANCHNAME` a tu `REMOTENAME`, pero es renombrado a `REMOTEBRANCHNAME`. +This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`. -## Abordar errores sin avance rápido +## Dealing with "non-fast-forward" errors -Si tu copia local de un repositorio está desincronizada, o "atrasada", con respecto al repositorio ascendente al que estás subiendo, recibirás un mensaje que dice que `non-fast-forward updates were rejected (las actualizaciones sin avance rápido se rechazaron)`. Esto significa que debes recuperar, o "extraer", los cambios ascendentes, antes de poder subir tus cambios locales. +If your local copy of a repository is out of sync with, or "behind," the upstream +repository you're pushing to, you'll get a message saying `non-fast-forward updates were rejected`. +This means that you must retrieve, or "fetch," the upstream changes, before +you are able to push your local changes. -Para obtener más información sobre este error, consulta "[Resolver errores sin avance rápido](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)." +For more information on this error, see "[Dealing with non-fast-forward errors](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)." -## Subir etiquetas +## Pushing tags -Por defecto, y sin parámetros adicionales, `git push` envía todas las ramas que coinciden para que tengan el mismo nombre que las ramas remotas. +By default, and without additional parameters, `git push` sends all matching branches +that have the same names as remote branches. -Para subir una etiqueta única, puedes emitir el mismo comando que al subir una rama: +To push a single tag, you can issue the same command as pushing a branch: ```shell git push <REMOTENAME> <TAGNAME> ``` -Para subir todas tus etiquetas, puede escribir el comando: +To push all your tags, you can type the command: ```shell git push <REMOTENAME> --tags ``` -## Eliminar una etiqueta o rama remota +## Deleting a remote branch or tag -La sintaxis para borrar una rama es un poco críptica a primera vista: +The syntax to delete a branch is a bit arcane at first glance: ```shell git push <REMOTENAME> :<BRANCHNAME> ``` -Nota que hay un espacio antes de los dos puntos. El comando se parece a los mismos pasos que tomarías para renombrar una rama. Sin embargo, aquí estás informándole a Git que no suba _nada_ dentro de `BRANCHNAME` en `REMOTENAME`. Debido a esto, `git push` elimina la rama en el repositorio remoto. +Note that there is a space before the colon. The command resembles the same steps +you'd take to rename a branch. However, here, you're telling Git to push _nothing_ +into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch +on the remote repository. -## Remotos y bifurcaciones +## Remotes and forks -Posiblemente ya sepas que [puedes "bifurcar" repositorios](https://guides.github.com/overviews/forking/) en GitHub. +You might already know that [you can "fork" repositories](https://guides.github.com/overviews/forking/) on GitHub. -Cuando clonas un repositorio de tu propiedad, le proporcionas una URL remota que le indica a Git dónde extraer y subir actualizaciones. Si deseas colaborar con el repositorio original, agregarías una nueva a URL remota, normalmente llamada `upstream` (ascendente), a tu clon de Git local: +When you clone a repository you own, you provide it with a remote URL that tells +Git where to fetch and push updates. If you want to collaborate with the original +repository, you'd add a new remote URL, typically called `upstream`, to +your local Git clone: ```shell git remote add upstream <THEIR_REMOTE_URL> ``` -Ahora, puedes extraer actualizaciones y ramas de *sus* bifurcaciones: +Now, you can fetch updates and branches from *their* fork: ```shell -git extrae ascendente -# Toma las ramas de los remotos ascendentes -> remoto: Contando objetos: 75, realizado. +git fetch upstream +# Grab the upstream remote's branches +> remote: Counting objects: 75, done. > remote: Compressing objects: 100% (53/53), done. -> remoto: Total 62 (delta 27), reutilizados 44 (delta 9) -> Descompimiendo objetos: 100 % (62/62), realziado. +> remote: Total 62 (delta 27), reused 44 (delta 9) +> Unpacking objects: 100% (62/62), done. > From https://{% data variables.command_line.codeblock %}/octocat/repo > * [new branch] main -> upstream/main ``` -Cuando hayas finalizado tus cambios locales, puedes subir tu rama local a GitHub e [iniciar una solicitud de extracción](/articles/about-pull-requests). +When you're done making local changes, you can push your local branch to GitHub +and [initiate a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -Para obtener más información sobre cómo trabajar con bifurcaciones, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". +For more information on working with forks, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)". -## Leer más +## Further reading -- [El capítulo "Remotos" del libro "Pro Git"](https://git-scm.com/book/ch5-2.html) -- [Página principal de `git remote`](https://git-scm.com/docs/git-remote.html) -- "[Git cheatsheet](/articles/git-cheatsheet)" (Hoja introductoria de Git) -- "[Flujos de trabajo de Git](/github/getting-started-with-github/git-workflows)" -- "[Manual de Git](https://guides.github.com/introduction/git-handbook/)" +- [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html) +- [`git remote` main page](https://git-scm.com/docs/git-remote.html) +- "[Git cheatsheet](/articles/git-cheatsheet)" +- "[Git workflows](/github/getting-started-with-github/git-workflows)" +- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" diff --git a/translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md b/translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md index 95462520eb..390f14f937 100644 --- a/translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md +++ b/translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md @@ -1,6 +1,6 @@ --- -title: Resolver conflictos de fusión después de una rebase de Git -intro: 'Cuando realizas una operación `git rebase`, normalmente mueves confirmaciones de un lado a otro. Por este motivo, puedes generar una situación en la que se introduzca un conflicto de fusión. Esto implica que dos de tus confirmaciones modificaron la misma línea del mismo archivo, y Git no sabe qué cambio aplicar.' +title: Resolving merge conflicts after a Git rebase +intro: 'When you perform a `git rebase` operation, you''re typically moving commits around. Because of this, you might get into a situation where a merge conflict is introduced. That means that two of your commits modified the same line in the same file, and Git doesn''t know which change to apply.' redirect_from: - /articles/resolving-merge-conflicts-after-a-git-rebase - /github/using-git/resolving-merge-conflicts-after-a-git-rebase @@ -11,24 +11,23 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Resolver conflictos después de rebasar +shortTitle: Resolve conflicts after rebase --- - -Después de reordenar y manipular confirmaciones utilizando `git rebase`, si ocurre un conflicto de fusión, Git te lo informará con el siguiente mensaje impreso en el terminal: +After you reorder and manipulate commits using `git rebase`, should a merge conflict occur, Git will tell you so with the following message printed to the terminal: ```shell -error: no se pudo aplicar fa39187... algo para agregar al parte A +error: could not apply fa39187... something to add to patch A -Cuando hayas resuelto este problema, ejecuta "git rebase --continue". -Si prefieres saltear este parche, ejecuta "git rebase --skip". -Para revisar la rama original y detener el proceso de rebase, ejecuta "git rebase --abort". -No se pudo aplicar fa39187f3c3dfd2ab5faa38ac01cf3de7ce2e841... Cambia el archivo falso +When you have resolved this problem, run "git rebase --continue". +If you prefer to skip this patch, run "git rebase --skip" instead. +To check out the original branch and stop rebasing, run "git rebase --abort". +Could not apply fa39187f3c3dfd2ab5faa38ac01cf3de7ce2e841... Change fake file ``` -Aquí Git te está diciendo qué confirmación está causando el conflicto (`fa39187`). Se te ofrecen tres opciones: +Here, Git is telling you which commit is causing the conflict (`fa39187`). You're given three choices: -* Puedes ejecutar `git rebase --abort` para deshacer por completo la rebase. Git te regresará al estado de tu rama tal como estaba antes de haber pedido `git rebase`. -* Puedes ejecutar `git rebase --skip` para saltear por completo la confirmación. Esto significa que no se incluirá ninguno de los cambios introducidos por la confirmación problemática. Es muy poco común que elijas esta opción. -* Puedes corregir el conflicto. +* You can run `git rebase --abort` to completely undo the rebase. Git will return you to your branch's state as it was before `git rebase` was called. +* You can run `git rebase --skip` to completely skip the commit. That means that none of the changes introduced by the problematic commit will be included. It is very rare that you would choose this option. +* You can fix the conflict. -Para corregir el conflicto, puedes seguir [los procedimientos estándar para resolver conflictos de fusión desde la línea de comando](/articles/resolving-a-merge-conflict-using-the-command-line). Cuando termines, tendrás que pedir `git rebase --continue` para que Git continúe procesando el resto de la rebase. +To fix the conflict, you can follow [the standard procedures for resolving merge conflicts from the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line). When you're finished, you'll need to call `git rebase --continue` in order for Git to continue processing the rest of the rebase. diff --git a/translations/es-ES/content/get-started/using-github/github-command-palette.md b/translations/es-ES/content/get-started/using-github/github-command-palette.md index 528004b5dc..37b977176b 100644 --- a/translations/es-ES/content/get-started/using-github/github-command-palette.md +++ b/translations/es-ES/content/get-started/using-github/github-command-palette.md @@ -4,13 +4,13 @@ intro: 'Use the command palette in {% data variables.product.product_name %} to versions: fpt: '*' ghec: '*' - feature: command-palette + feature: 'command-palette' shortTitle: GitHub Command Palette --- {% data reusables.command-palette.beta-note %} -## Acerca de {% data variables.product.prodname_command_palette %} +## About the {% data variables.product.prodname_command_palette %} You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard. @@ -26,31 +26,31 @@ The ability to run commands directly from your keyboard, without navigating thro ![Command palette change theme](/assets/images/help/command-palette/command-palette-command-change-theme.png) -## Abrir el {% data variables.product.prodname_command_palette %} +## Opening the {% data variables.product.prodname_command_palette %} Open the command palette using one of the following keyboard shortcuts: -- Windows and Linux: Ctlk or Ctlaltk +- Windows and Linux: Ctrlk or Ctrlaltk - Mac: ⌘k or ⌘optionk -When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). +When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png) {% note %} -**Notas:** -- If you are editing Markdown text, open the command palette with Ctlaltk (Windows and Linux) or ⌘optionk (Mac). -- If you are working on a project (beta), a project-specific command palette is displayed instead. Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)". +**Notes:** +- If you are editing Markdown text, open the command palette with Ctrlaltk (Windows and Linux) or ⌘optionk (Mac). +- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." {% endnote %} ## Navigating with the {% data variables.product.prodname_command_palette %} -You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. +You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. {% data reusables.command-palette.open-palette %} -2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. +2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png) @@ -60,22 +60,22 @@ You can use the command palette to navigate to any page that you have access to 4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions. -5. Use Enter to jump to your chosen location. Alternatively, use CtlEnter (Windows and Linx) or ⌘Enter (Mac) to open the location in a new browser tab. +5. Use Enter to jump to your chosen location. Alternatively, use CtrlEnter (Windows and Linux) or ⌘Enter (Mac) to open the location in a new browser tab. ## Searching with the {% data variables.product.prodname_command_palette %} -You can use the command palette to search for anything on {% data variables.product.product_location %}. +You can use the command palette to search for anything on {% data variables.product.product_location %}. {% data reusables.command-palette.open-palette %} {% data reusables.command-palette.change-scope %} -3. Optionally, use keystrokes to find specific types of resource: +3. Optionally, use keystrokes to find specific types of resource: - # Search for issues, pull requests, discussions, and projects - ! Search for projects - @ Search for users, organizations, and repositories - - / Search for files within a repository scope + - / Search for files within a repository scope ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png) @@ -87,16 +87,16 @@ You can use the command palette to search for anything on {% data variables.prod {% endtip %} -5. Use the arrow keys to highlight the search result you want and use Enter to jump to your chosen location. Alternatively, use CtlEnter (Windows and Linx) or ⌘Enter (Mac) to open the location in a new browser tab. +5. Use the arrow keys to highlight the search result you want and use Enter to jump to your chosen location. Alternatively, use CtrlEnter (Windows and Linux) or ⌘Enter (Mac) to open the location in a new browser tab. ## Running commands from the {% data variables.product.prodname_command_palette %} You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette. - Pull request and issue commands always run on the underlying page. -- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. +- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. -For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](##github-command-palette-reference)." +For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)." 1. Use CtrlShiftk (Windows and Linux) or ⌘Shiftk (Mac) to open the command palette in command mode. If you already have the command palette open, press > to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location. @@ -108,106 +108,113 @@ For a full list of supported commands, see "[{% data variables.product.prodname_ 4. Use the arrow keys to highlight the command you want and use Enter to run it. +## Closing the command palette + +When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette: + +- Search and navigation mode: esc or Ctrlk (Windows and Linux) ⌘k (Mac) +- Command mode: esc or CtrlShiftk (Windows and Linux) ⌘Shiftk (Mac) + ## {% data variables.product.prodname_command_palette %} reference ### Keystroke functions These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode. -| Keystroke | Función | -|:--------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| > | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." | -| # | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| @ | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| / | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| ! | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| Ctrlc or ⌘c | Copy the search or navigation URL for the highlighted result to the clipboard. | -| Enter | Jump to the highlighted result or run the highlighted command. | -| CtrlEnter or ⌘Enter | Open the highlighted search or navigation result in a new brower tab. | -| ? | Display help within the command palette. | +| Keystroke | Function | +| :- | :- | +|>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." | +|#| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|@| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|/| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | +|!| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|Ctrlc or ⌘c| Copy the search or navigation URL for the highlighted result to the clipboard.| +|Enter| Jump to the highlighted result or run the highlighted command.| +|CtrlEnter or ⌘Enter| Open the highlighted search or navigation result in a new brower tab.| +|?| Display help within the command palette.| ### Global commands These commands are available from all scopes. -| Command | Behavior | -|:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Import repository` | Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | -| `New gist` | Open a new gist. For more information, see "[Creating a gist](/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | -| `New organization` | Create a new organization. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". | -| `Proyecto nueuvo` | Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | -| `New repository` | Create a new repository from scratch. Para obtener más información, consulta la sección "[Crear un nuevo repositorio](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | -| `Switch theme to ` | Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | +| Command | Behavior| +| :- | :- | :- | +|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | +|`New gist`|Open a new gist. For more information, see "[Creating a gist](/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | +|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | +|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | +|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | ### Organization commands These commands are available only within the scope of an organization. -| Command | Behavior | -|:---------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `New team` | Create a new team in the current organization. Para obtener más información, consulta la sección "[Crear un equipo](/organizations/organizing-members-into-teams/creating-a-team)". | +| Command | Behavior| +| :- | :- | +| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." ### Repository commands Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column. -| Command | Behavior | -|:------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Clone repository: ` | Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. Para obtener más información, consulta "[Clonar un repositorio](/repositories/creating-and-managing-repositories/cloning-a-repository)". | -| `New discussion` | Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)." | -| `New file` | Create a new file from any page in the repository. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." | -| `New issue` | Open a new issue from any page in the repository. Para obtener más información, consulta la sección "[Crear una propuesta](/issues/tracking-your-work-with-issues/creating-an-issue)". | -| `Open in new codespace` | Create and open a codespace for this repository. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | -| `Open in github.dev editor` | Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)." | +| Command | Behavior| +| :- | :- | +|`Clone repository: `|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."| +|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."| +|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." +|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."| +|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."| +|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| ### File commands These commands are available only when you open the command palette from a file in a repository. -| Command | Behavior | -|:--------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Copy permalink` | Create a link to the file that includes the current commit SHA and copy the link to the clipboard. Para obtener más información, consulta "[Obtener enlaces permanentes a los archivos](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)". | -| `Open in github.dev editor` | Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)." | +| Command | Behavior| +| :- | :- | +|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)." +|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| ### Discussion commands These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette. -| Command | Behavior | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Delete discussion...` | Permanently delete the discussion. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)". | -| `Edit discussion body` | Open the main body of the discussion ready for editing. | -| `Subscribe`/`unsubscribe` | Opt in or out of notifications for additions to the discussion. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". | -| `Transfer discussion...` | Move the discussion to a different repository. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)". | +| Command | Behavior| +| :- | :- | +|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." +|`Edit discussion body`|Open the main body of the discussion ready for editing. +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)." ### Issue commands These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette. -| Command | Behavior | -|:-------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Close`/`reopen issue` | Close or reopen the current issue. Para obtener más información, consulta "[Acerca de las propuestas](/issues/tracking-your-work-with-issues/about-issues)". | -| `Convert issue to discussion...` | Convert the current issue into a discussion. Para obtener más información, consulta la sección "[Moderar los debates](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)". | -| `Delete issue...` | Delete the current issue. Para obtener más información, consulta la sección "[Borrar una propuesta](/issues/tracking-your-work-with-issues/deleting-an-issue)". | -| `Edit issue body` | Open the main body of the issue ready for editing. | -| `Edit issue title` | Open the title of the issue ready for editing. | -| `Lock issue` | Limit new comments to users with write access to the repository. Para obtener más información, consulta "[Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations)." | -| `Pin`/`unpin issue` | Change whether or not the issue is shown in the pinned issues section for the repository. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)". | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this issue. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". | -| `Transfer issue...` | Transfer the issue to another repository. Para obtener más información, consulta "[Transferir una propuesta a otro repositorio](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." | +| Command | Behavior| +| :- | :- | +|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."| +|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." +|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."| +|`Edit issue body`|Open the main body of the issue ready for editing. +|`Edit issue title`|Open the title of the issue ready for editing. +|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." +|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."| +|`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."| ### Pull request commands These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette. -| Command | Behavior | -|:---------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Close`/`reopen pull request` | Close or reopen the current pull request. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." | -| `Convert to draft`/`Mark pull request as ready for review` | Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." | -| `Copy current branch name` | Add the name of the head branch for the pull request to the clipboard. | -| `Edit pull request body` | Open the main body of the pull request ready for editing. | -| `Edit pull request title` | Open the title of the pull request ready for editing. | -| `Open in new codespace` | Create and open a codespace for the head branch of the pull request. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this pull request. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". | -| `Update current branch` | Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. Para obtener más información, consulta "[Acerca de las ramas](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)." | +| Command | Behavior| +| :- | :- | +|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."| +|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."| +|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard. +|`Edit pull request body`|Open the main body of the pull request ready for editing. +|`Edit pull request title`|Open the title of the pull request ready for editing. +|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +|`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."| diff --git a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md index 8e9b0bb273..bc0dfabdb6 100644 --- a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md @@ -1,6 +1,6 @@ --- -title: Atajos del teclado -intro: 'Prácticamente todas las páginas de {% data variables.product.prodname_dotcom %} tienen atajos del teclado para realizar acciones más rápido.' +title: Keyboard shortcuts +intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.' redirect_from: - /articles/using-keyboard-shortcuts/ - /categories/75/articles/ @@ -14,211 +14,209 @@ versions: ghae: '*' ghec: '*' --- +## About keyboard shortcuts -## Acerca de los atajos del teclado +Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate. -Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. Puedes aprovechar estos atajos del teclado para realizar acciones en todo el sitio sin recurrir al mouse para navegar. +{% if keyboard-shortcut-accessibility-setting %} +You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %} -A continuación aparece una lista de algunos de los atajos del teclado disponibles. +Below is a list of some of the available keyboard shortcuts. {% if command-palette %} The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} -## Atajos en todo el sitio +## Site wide shortcuts -| Atajo del teclado | Descripción | -| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s o / | Se concentra en la barra de búsqueda. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". | -| g n | Dirige a tus notificaciones. Para obtener más información, consulta la sección {% ifversion fpt or ghes or ghae or ghec %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciones](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}". | -| esc | Cuando se concentra en la hovercard de un usuario, de una propuesta o de una solicitud de extracción, se cierra la hovercard y se vuelve a centrar en el elemento en el que está la hovercard | +| Keyboard shortcut | Description +|-----------|------------ +|s or / | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." +|g n | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +|esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in +{% if command-palette %}|controlk or commandk | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Ctlaltk or ⌘optionk. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} -{% if command-palette %} +## Repositories -controlk or commandk | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Ctlaltk or ⌘optionk. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +| Keyboard shortcut | Description +|-----------|------------ +|g c | Go to the **Code** tab +|g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." +|g p | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %} +|g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} +|g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." +|g w | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %} +|g g | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %} -## Repositorios +## Source code editing -| Atajo del teclado | Descripción | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | Dirige a la pestaña **Code** (Código) | -| g i | Dirige a la pestaña **Issues** (Propuestas). Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". | -| g p | Dirige a la pestaña **Pull requests** (Solicitudes de extracción). Para obtener más información, consulta la sección "[Acerca de las solicitudes de cambios](/articles/about-pull-requests)".{% ifversion fpt or ghes or ghec %} -| g a | Ve a la pestaña de **Acciones**. Para obtener más información, consulta la sección "[Acerca de las acciones](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %} -| g b | Dirige a la pestaña **Projects** (Proyectos). Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)." | -| g w | Dirige a la pestaña **Wiki**. Para obtener más información, consulta la sección "[Acerca de los wikis](/communities/documenting-your-project-with-wikis/about-wikis)".{% ifversion fpt or ghec %} -| g g | Dirígete a la pestaña de **Debates**. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".{% endif %} +| Keyboard shortcut | Description +|-----------|------------{% ifversion fpt or ghec %} +|.| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %} +| control b or command b | Inserts Markdown formatting for bolding text +| control i or command i | Inserts Markdown formatting for italicizing text +| control k or command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %} +| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list +| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list +| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %} +|e | Open source code file in the **Edit file** tab +|control f or command f | Start searching in file editor +|control g or command g | Find next +|control shift g or command shift g | Find previous +|control shift f or command option f | Replace +|control shift r or command shift option f | Replace all +|alt g | Jump to line +|control z or command z | Undo +|control y or command y | Redo +|command shift p | Toggles between the **Edit file** and **Preview changes** tabs +|control s or command s | Write a commit message -## Edición del código fuente +For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands). -| Atajo del teclado | Descripción | -| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} -| . | Abre un repositorio o solicitud de cambio en el editor basado en la web. Para obtener más información, consulta la sección "[Editor basado en la web](/codespaces/developing-in-codespaces/web-based-editor)".{% endif %} -| control b o comando b | Inserta el formato Markdown para el texto en negrita | -| control i o comando i | Inserta el formato Markdown para el texto en cursiva | -| control k o comando k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %} -| control shift 7 o command shift 7 | Inserta formato de lenguaje de marcado para una lista ordenada | -| control shift 8 o command shift 8 | Inserts Markdown formatting for an unordered list | -| control shift . o command shift. | Inserts Markdown formatting for a quote{% endif %} -| e | Abre el archivo de código fuente en la pestaña **Editar archivo** | -| control f o comando f | Comienza la búsqueda en el editor de archivos | -| control g o comando g | Busca el siguiente | -| control shift g or command shift g | Busca el anterior | -| control shift f or command option f | Reemplaza | -| control shift r or command shift option f | Reemplaza todo | -| alt g | Salta la línea | -| control z o comando z | Deshace | -| control y o comando y | Rehace | -| command shift p | Alterna entre las pestañas **Edit file** (Editar comentario) y **Preview changes** (Vista previa de cambios) | -| control s o command s | Escribir un mensaje de confirmación | +## Source code browsing -Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror](https://codemirror.net/doc/manual.html#commands). +| Keyboard shortcut | Description +|-----------|------------ +|t | Activates the file finder +|l | Jump to a line in your code +|w | Switch to a new branch or tag +|y | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)." +|i | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)." +|a | Show or hide annotations on diffs +|b | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)." -## Exploración del código fuente +## Comments -| Atajo del teclado | Descripción | -| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| t | Activa el buscador de archivos | -| l | Salta a una línea de tu código | -| w | Cambia a una rama o etiqueta nueva | -| y | Expande una URL a su forma canónica. Para obtener más información, consulta "[Obtener enlaces permanentes a los archivos](/articles/getting-permanent-links-to-files)". | -| i | Muestra u oculta comentarios en diferencias. Para obtener más información, consulta "[Comentar en la diferencia de una solicitud de extracción](/articles/commenting-on-the-diff-of-a-pull-request)". | -| a | Muestra u oculta las anotaciones en los diffs | -| b | Abre la visualización del último responsable. Para obtener más información, consulta "[Rastrear las modificaciones de un archivo](/articles/tracing-changes-in-a-file)". | +| Keyboard shortcut | Description +|-----------|------------ +| control b or command b | Inserts Markdown formatting for bolding text +| control i or command i | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} +| control e or command e | Inserts Markdown formatting for code or a command within a line{% endif %} +| control k or command k | Inserts Markdown formatting for creating a link +| control shift p or command shift p| Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} +| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list +| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} +| control enter | Submits a comment +| control . and then control [saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} +| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} +|control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} +| r | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | -## Comentarios +## Issue and pull request lists -| Atajo del teclado | Descripción | -| ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| control b o comando b | Inserta el formato Markdown para el texto en negrita | -| control i o comando i | Inserta formateo de lenguaje de marcado para poner el texto en itálicas{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} -| control e o command e | Insterta formato de lenguaje de marcado para código o un comando dentro de una línea{% endif %} -| control k o comando k | Inserta el formato Markdown para crear un enlace | -| control shift p o comando shift p | Alterna entre las pestañas de comentarios de **Escritura** y **Vista previa **{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} -| control shift 7 o command shift 7 | Inserta formato de lenguaje de marcado para una lista ordenada | -| control shift 8 o command shift 8 | Inserta formato de lenguaje de marcado para una lista no ordenada{% endif %} -| control enter | Envía un comentario | -| control . y luego control [número de respuesta guardada] | Abre el menú de respuestas guardadas y luego completa automáticamente el campo de comentarios con una respuesta guardada. Para obtener más información, consulta "[Acerca de las respuestas guardadas](/articles/about-saved-replies)".{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} -| control shift . o command shift. | Inserta formato de lenguaje de marcado para una cita{% endif %}{% ifversion fpt or ghec %} -| control g o comando g | Inserta una sugerencia. Para obtener más información, consulta "[Revisar las modificaciones propuestas en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)." -{% endif %} -| r | Cita el texto seleccionado en tu respuesta. Para obtener más información, consulta "[Escritura básica y sintaxis de formato](/articles/basic-writing-and-formatting-syntax#quoting-text)". | +| Keyboard shortcut | Description +|-----------|------------ +|c | Create an issue +| control / or command / | Focus your cursor on the issues or pull requests search bar. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."|| +|u | Filter by author +|l | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." +| alt and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." +|m | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)." +|a | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)." +|o or enter | Open issue -## Listas de propuestas y solicitudes de extracción +## Issues and pull requests +| Keyboard shortcut | Description +|-----------|------------ +|q | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)." +|m | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)." +|l | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)." +|a | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)." +|cmd + shift + p or control + shift + p | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %} +|alt and click | When creating an issue from a task list, open the new issue form in the current tab by holding alt and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." +|shift and click | When creating an issue from a task list, open the new issue form in a new tab by holding shift and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." +|command or control + shift and click | When creating an issue from a task list, open the new issue form in the new window by holding command or control + shift and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %} -| Atajo del teclado | Descripción | -| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Crear un informe de problemas | -| control / o comando / | Hace que el cursor se concentre en la barra de propuestas o solicitudes de respuesta. Para obtener más información, consulta la sección "[Filtrar y buscar las propuestas y solicitudes de cambio](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)".| | -| u | Filtra por autor | -| l | Filtra por etiquetas o edita etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| alt y haz clic | Al filtrar por etiquetas, excluye etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| m | Filtra por hitos o edita hitos. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por hito](/articles/filtering-issues-and-pull-requests-by-milestone)". | -| a | Filtra por asignatario s o edita asignatarios. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)". | -| o o enter | Abre una propuesta | +## Changes in pull requests -## Propuestas y solicitudes de extracción -| Atajo del teclado | Descripción | -| ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| q | Solicita un revisor. Para obtener más información, consulta "[Solicitar una revisión de solicitud de extracción](/articles/requesting-a-pull-request-review/)". | -| m | Establece un hito. Para obtener más información, consulta "[Asociar hitos a propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests/)". | -| l | Aplica una etiqueta. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests/)". | -| a | Establece un asignatario. Para obtener más información, consulta "[Asignar propuestas y solicitudes de extracción a otros{% data variables.product.company_short %} usuarios](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". | -| cmd + shift + p or control + shift + p | Alterna entre las pestañas de **Escritura** y **Vista previa** {% ifversion fpt or ghec %} -| alt y haz clic | Cuando creas una propuesta desde una lista de tareas, abre el formato de propuesta nueva en la pestaña actual sosteniendo la tecla alt y haciendo clic en el {% octicon "issue-opened" aria-label="The issue opened icon" %} de la parte superior derecha de la tarea. Para obtener más información, consulta "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". | -| shift y clic | Cuando creas una propuesta desde una lista de tareas, abre el formato de propuesta nueva en una pestaña nueva sosteniendo la tecla shift y haciendo clic en el {% octicon "issue-opened" aria-label="The issue opened icon" %} de la parte superior derecha de la tarea. Para obtener más información, consulta "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". | -| command o control + shift y clic | Cuando creas una propuesta desde una lista de tareas, abre el formato de propuesta nueva en una ventana nueva sosteniendo command o control + shift y haciendo clic en el {% octicon "issue-opened" aria-label="The issue opened icon" %} en la esquina superior derecha de la tarea. Para obtener más información, consulta la sección "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".{% endif %} +| Keyboard shortcut | Description +|-----------|------------ +|c | Open the list of commits in the pull request +|t | Open the list of changed files in the pull request +|j | Move selection down in the list +|k | Move selection up in the list +| cmd + shift + enter | Add a single comment on a pull request diff | +| alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %} +| Click, then shift and click | Comment on multiple lines of a pull request by clicking a line number, holding shift, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} -## Modificaciones en las solicitudes de extracción +## Project boards -| Atajo del teclado | Descripción | -| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Abre la lista de confirmaciones de la solicitud de extracción | -| t | Abre la lista de archivos modificados de la solicitud de extracción | -| j | Mueve la selección hacia abajo en la lista | -| k | Mueve la selección hacia arriba en la lista | -| cmd + shift + enter | Agrega un comentario simple en una diferencia de solicitud de extracción | -| alt y haz clic | Alterna entre colapsar y expandir todos los comentarios de revisión desactualizados en una solicitud de extracción sosteniendo `alt` y dando clic en **Mostrar desactualizados** or **Ocultar desactualizados**.|{% ifversion fpt or ghes or ghae or ghec %} -| Da clic, luego shift y clic | Comenta en líneas múltiples de una solicitud de extracción dando clic en un número de línea, sosteniendo shift, y luego dando clic en otro número de línea. Para obtener más información, consulta "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." -{% endif %} +### Moving a column -## Tableros de proyecto +| Keyboard shortcut | Description +|-----------|------------ +|enter or space | Start moving the focused column +|escape | Cancel the move in progress +|enter | Complete the move in progress +|← or h | Move column to the left +|command + ← or command + h or control + ← or control + h | Move column to the leftmost position +|→ or l | Move column to the right +|command + → or command + l or control + → or control + l | Move column to the rightmost position -### Mover una columna +### Moving a card -| Atajo del teclado | Descripción | -| ------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| enter o space | Comienza a mover la columna enfocada | -| escape | Cancela el movimiento en curso | -| enter | Completa el movimiento en curso | -| ← o h | Mueve la columna hacia la izquierda | -| command + ← o command + h o control + ← o control + h | Mueve la columna hacia la posición más a la izquierda | -| → o l | Mueve la columna hacia la derecha | -| command + → o command + l o control + → o control + l | Mueve la columna hacia la posición más a la derecha | +| Keyboard shortcut | Description +|-----------|------------ +|enter or space | Start moving the focused card +|escape | Cancel the move in progress +|enter | Complete the move in progress +|↓ or j | Move card down +|command + ↓ or command + j or control + ↓ or control + j | Move card to the bottom of the column +|↑ or k | Move card up +|command + ↑ or command + k or control + ↑ or control + k | Move card to the top of the column +|← or h | Move card to the bottom of the column on the left +|shift + ← or shift + h | Move card to the top of the column on the left +|command + ← or command + h or control + ← or control + h | Move card to the bottom of the leftmost column +|command + shift + ← or command + shift + h or control + shift + ← or control + shift + h | Move card to the top of the leftmost column +|→ | Move card to the bottom of the column on the right +|shift + → or shift + l | Move card to the top of the column on the right +|command + → or command + l or control + → or control + l | Move card to the bottom of the rightmost column +|command + shift + → or command + shift + l or control + shift + → or control + shift + l | Move card to the bottom of the rightmost column -### Mover una tarjeta +### Previewing a card -| Atajo del teclado | Descripción | -| --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -| enter o space | Comienza a mover la tarjeta focalizada | -| escape | Cancela el movimiento en curso | -| enter | Completa el movimiento en curso | -| ↓ o j | Mueve la tarjeta hacia abajo | -| command + ↓ o command + j o control + ↓ o control + j | Mueve una tarjeta hacia la parte de abajo de la columna | -| ↑ o k | Mueve una tarjeta hacia arriba | -| command + ↑ o command + k o control + ↑ o control + k | Mueve una tarjeta hacia la parte de arriba de la columna | -| ← o h | Mueve una tarjeta hacia la parte de abajo de la columna de la izquierda | -| shift + ← o shift + h | Mueve una tarjeta hacia la parte de arriba de la columna de la izquierda | -| command + ← o command + h o control + ← o control + h | Mueve una tarjeta hacia la parte de abajo de la columna de más a la izquierda | -| command + shift + ← o command + shift + h o control + shift + ← o control + shift + h | Mueve una tarjeta hacia la parte de arriba de la columna de más a la izquierda | -| → | Mueve una tarjeta hacia la parte de abajo de la columna de la derecha | -| shift + → o shift + l | Mueve una tarjeta hacia la parte de arriba de la columna de la derecha | -| command + → o command + l o control + → o control + l | Mueve una tarjeta hacia la parte de abajo de la columna de más a la derecha | -| command + shift + → o command + shift + l o control + shift + → o control + shift + l | Mueve una tarjeta hacia la parte de abajo de la columna de más a la derecha | - -### Previsualizar una tarjeta - -| Atajo del teclado | Descripción | -| ----------------- | -------------------------------------------- | -| esc | Elige el panel de vista previa de la tarjeta | +| Keyboard shortcut | Description +|-----------|------------ +|esc | Close the card preview pane {% ifversion fpt or ghec %} ## {% data variables.product.prodname_actions %} -| Atajo del teclado | Descripción | -| -------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -| command + space o control + space | En el editor del flujo de trabajo, obtén las sugerencias para tu archivo de flujo de trabajo. | -| g f | Ir al archivo de flujo de trabajo | -| shift + t or T | Activa las marcas de tiempo en las bitácoras | -| shift + f or F | Activa las bitácoras de pantalla completa | -| esc | Sal de las bitácoras de pantalla completa | +| Keyboard shortcut | Description +|-----------|------------ +|command + space or control + space | In the workflow editor, get suggestions for your workflow file. +|g f | Go to the workflow file +|shift + t or T | Toggle timestamps in logs +|shift + f or F | Toggle full-screen logs +|esc | Exit full-screen logs {% endif %} -## Notificaciones +## Notifications + {% ifversion fpt or ghes or ghae or ghec %} -| Atajo del teclado | Descripción | -| -------------------- | ---------------------- | -| e | Marcar como completado | -| shift + u | Marcar como no leído | -| shift + i | Marca como leído | -| shift + m | Unsubscribe | +| Keyboard shortcut | Description +|-----------|------------ +|e | Mark as done +| shift + u| Mark as unread +| shift + i| Mark as read +| shift + m | Unsubscribe {% else %} -| Atajo del teclado | Descripción | -| ------------------------------------------ | ---------------- | -| e o I o y | Marca como leído | -| shift + m | Silencia el hilo | +| Keyboard shortcut | Description +|-----------|------------ +|e or I or y | Mark as read +|shift + m | Mute thread {% endif %} -## Gráfico de red +## Network graph -| Atajo del teclado | Descripción | -| ------------------------------------------- | -------------------------------- | -| ← o h | Desplaza hacia la izquierda | -| → o l | Desplaza hacia la derecha | -| ↑ o k | Desplaza hacia arriba | -| ↓ o j | Desplaza hacia abajo | -| shift + ← o shift + h | Desplaza todo hacia la izquierda | -| shift + → o shift + l | Desplaza todo hacia la derecha | -| shift + ↑ o shift + k | Desplaza todo hacia arriba | -| shift + ↓ o shift + j | Desplaza todo hacia abajo | +| Keyboard shortcut | Description +|-----------|------------ +|← or h | Scroll left +|→ or l | Scroll right +|↑ or k | Scroll up +|↓ or j | Scroll down +|shift + ← or shift + h | Scroll all the way left +|shift + → or shift + l | Scroll all the way right +|shift + ↑ or shift + k | Scroll all the way up +|shift + ↓ or shift + j | Scroll all the way down diff --git a/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md b/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md index c81633778f..8ebd76264c 100644 --- a/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md +++ b/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md @@ -1,6 +1,6 @@ --- -title: Referencia del CLI de GitHub -intro: 'Puedes ver todos los comandos de {% data variables.product.prodname_cli %} en tu terminal o en el manual del {% data variables.product.prodname_cli %}.' +title: GitHub CLI reference +intro: 'You can view all of the {% data variables.product.prodname_cli %} commands in your terminal or in the {% data variables.product.prodname_cli %} manual.' versions: fpt: '*' ghes: '*' @@ -11,19 +11,25 @@ topics: type: reference --- -Para ver todos los comandos del {% data variables.product.prodname_cli %}, consulta el [manual del {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_reference) o utiliza el comando `reference`. +To view all top-level {% data variables.product.prodname_cli %} commands, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh) or call `gh` without arguments. ```shell -gh reference +gh ``` -Para ver las variables de ambiente que se pueden utilizar con el {% data variables.product.prodname_cli %}, consulta el [manual del {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_environment) o utiliza el comando `environment`. +To list all commands under a specific group, use the top-level command without arguments. For example, to list [commands for managing repositories](https://cli.github.com/manual/gh_repo): + +```shell +gh repo +``` + +To view the environment variables that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_environment) or use the `environment` command. ```shell gh environment ``` -Para ver los ajustes de configuración que pueden utilizarse con el {% data variables.product.prodname_cli %}, consulta el [manual del {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_config) o utiliza el comando`config`. +To view the configuration settings that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_config) or use the `config` command. ```shell gh config diff --git a/translations/es-ES/content/github/copilot/index.md b/translations/es-ES/content/github/copilot/index.md index 242e225330..2e967d1c26 100644 --- a/translations/es-ES/content/github/copilot/index.md +++ b/translations/es-ES/content/github/copilot/index.md @@ -1,6 +1,6 @@ --- -title: Copiloto de GitHub -intro: 'Puedes utilizar al Copiloto de {% data variables.product.prodname_dotcom %} para que te ayude con tu programación en Visual Studio Code.' +title: GitHub Copilot +intro: 'You can use {% data variables.product.prodname_dotcom %} Copilot to assist with your programming in your editor' versions: fpt: '*' children: diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md index f851afbc52..15156bc2c1 100644 --- a/translations/es-ES/content/github/index.md +++ b/translations/es-ES/content/github/index.md @@ -4,7 +4,7 @@ redirect_from: - /articles/ - /common-issues-and-questions/ - /troubleshooting-common-issues/ -intro: 'Documentación, guías y temas de ayuda para programadores de software, diseñadores y gerentes de proyectos. Cubre el uso de Git, solicitudes de extracción, propuestas, wikis, gists y todo lo necesario para sacar el máximo provecho de GitHub para programación.' +intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.' versions: fpt: '*' ghec: '*' @@ -13,8 +13,6 @@ versions: children: - /copilot - /writing-on-github - - /committing-changes-to-your-project - - /collaborating-with-pull-requests - /importing-your-projects-to-github - /customizing-your-github-workflow - /extending-github diff --git a/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index 4b11b35791..687fba4885 100644 --- a/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -1,5 +1,5 @@ --- -title: Disposición de seguridad legal del programa de recompensas de errores de GitHub +title: GitHub Bug Bounty Program Legal Safe Harbor redirect_from: - /articles/github-bug-bounty-program-legal-safe-harbor versions: @@ -9,29 +9,29 @@ topics: - Legal --- -## Resumen -1. Deseamos que divulgues responsablemente a través de nuestro programa de recompensa de errores y no queremos que los investigadores se atemoricen por las consecuencias legales debido a sus intentos de buena fe para cumplir con nuestra política de recompensas por errores. No podemos vincular a ningún tercero, por lo que no presuponemos que esta protección se extiende a ningún tercero. Si tienes dudas, pregúntanos antes de participar en cualquier acción específica que consideres que _Podría_ vaya fuera de los límites de nuestra política. -2. Dado que tanto la información de identificación como la no identificativa pueden poner a un investigador en riesgo, limitamos lo que compartimos con terceros. Es posible que proporcionemos información sustantiva no identificativa de tu informe a un tercero afectado, pero solo después de notificarte a ti y de recibir un compromiso de que el tercero no perseguirá acciones legales en tu contra. Solo compartiremos la información de identificación (nombre, dirección de correo electrónico, número de teléfono, etc.) con un tercero si le proporcionas tu permiso por escrito. -3. Si tu investigación de seguridad como parte del programa de recompensas por errores viola ciertas restricciones en nuestras políticas del sitio, los términos del puerto seguro permiten una exención limitada. +## Summary +1. We want you to coordinate disclosure through our bug bounty program, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with our bug bounty policy. We cannot bind any third party, so do not assume this protection extends to any third party. If in doubt, ask us before engaging in any specific action you think _might_ go outside the bounds of our policy. +2. Because both identifying and non-identifying information can put a researcher at risk, we limit what we share with third parties. We may provide non-identifying substantive information from your report to an affected third party, but only after notifying you and receiving a commitment that the third party will not pursue legal action against you. We will only share identifying information (name, email address, phone number, etc.) with a third party if you give your written permission. +3. If your security research as part of the bug bounty program violates certain restrictions in our site policies, the safe harbor terms permit a limited exemption. -## 1. Condiciones de la disposición de seguridad +## 1. Safe Harbor Terms -Para alentar la investigación y la divulgación responsable de las vulnerabilidades de seguridad, no perseguiremos acciones civiles o penales, o enviaremos un aviso a la aplicación de la ley por violaciones fortuitas o de buena fe de esta política. Consideramos que las investigaciones de seguridad y las actividades de divulgación de vulnerabilidades llevadas a cabo de acuerdo con esta política son conductas "autorizadas" conforme a la ley de fraude y abuso informático, la DMCA y otras leyes aplicables de uso informático, como Código Penal de Cal. 502(c). Renunciamos a cualquier demanda potencial de DMCA en tu contra por eludir las medidas tecnológicas que hemos utilizado para proteger las aplicaciones en este alcance del programa de recompensas de errores. +To encourage research and coordinated disclosure of security vulnerabilities, we will not pursue civil or criminal action, or send notice to law enforcement for accidental or good faith violations of this policy. We consider security research and vulnerability disclosure activities conducted consistent with this policy to be “authorized” conduct under the Computer Fraud and Abuse Act, the DMCA, and other applicable computer use laws such as Cal. Penal Code 502(c). We waive any potential DMCA claim against you for circumventing the technological measures we have used to protect the applications in this bug bounty program's scope. -Por favor, entiende que si tu investigación de seguridad involucra las redes, sistemas, información, aplicaciones, productos o servicios de un tercero (que no seamos nosotros), no podemos vincular a ese tercero y pueden perseguir acciones legales o aviso de cumplimiento de la ley. No podemos y no autorizamos la investigación de seguridad en el nombre de otras entidades, y de ninguna manera podemos ofrecer defenderte, indemnizarte o protegerte de ninguna manera de cualquier acción de terceros en base a sus acciones. +Please understand that if your security research involves the networks, systems, information, applications, products, or services of a third party (which is not us), we cannot bind that third party, and they may pursue legal action or law enforcement notice. We cannot and do not authorize security research in the name of other entities, and cannot in any way offer to defend, indemnify, or otherwise protect you from any third party action based on your actions. -Se espera, como siempre, cumplir con todas las leyes aplicables a ti, y no interrumpir o comprometer ningún dato más allá de lo que este programa de recompensas de errores permite. +You are expected, as always, to comply with all laws applicable to you, and not to disrupt or compromise any data beyond what this bug bounty program permits. -Ponte en contacto con nosotros antes de participar en una conducta que puede ser incompatible con esta política o no ser tratada por esta. Nos reservamos el derecho exclusivo de hacer la determinación de si una violación de esta política es accidental o de buena fe y el contacto proactivo con nosotros antes de participar en cualquier acción es un factor significativo en esa decisión. Si tienes dudas, ¡Pregúntanos primero! +Please contact us before engaging in conduct that may be inconsistent with or unaddressed by this policy. We reserve the sole right to make the determination of whether a violation of this policy is accidental or in good faith, and proactive contact to us before engaging in any action is a significant factor in that decision. If in doubt, ask us first! -## 2. Disposición de seguridad de terceros +## 2. Third Party Safe Harbor -Si envías un informe a través de nuestro programa de recompensas de errores que afecta a un servicio de terceros, limitaremos lo que compartamos con cualquier tercero afectado. Es posible que compartamos contenido no identificable de tu informe con un tercero afectado, pero solo después de notificarte que tenemos la intención de hacerlo y de obtener el compromiso por escrito del tercero de que no perseguirán acciones legales en tu contra o de iniciar contacto con las fuerzas del orden de las leyes en base a tu informe. No compartiremos tu información de identificación con ningún tercero afectado sin obtener primero tu permiso por escrito para hacerlo. +If you submit a report through our bug bounty program which affects a third party service, we will limit what we share with any affected third party. We may share non-identifying content from your report with an affected third party, but only after notifying you that we intend to do so and getting the third party's written commitment that they will not pursue legal action against you or initiate contact with law enforcement based on your report. We will not share your identifying information with any affected third party without first getting your written permission to do so. -Ten en cuenta que no podemos autorizar pruebas fuera de alcance en nombre de terceros y dichas pruebas están fuera del alcance de nuestra política. Consulta la política de recompensas de errores de ese tercer, si tiene una, o comunícate directamente con el tercero o a través de un representante legal antes de iniciar cualquier prueba en ese tercero o en sus servicios. Esto no es, y no debe entenderse como, cualquier acuerdo de nuestra parte para defender, indemnizar o de cualquier otra manera protegerte de cualquier acción de terceros con base a tus acciones. +Please note that we cannot authorize out-of-scope testing in the name of third parties, and such testing is beyond the scope of our policy. Refer to that third party's bug bounty policy, if they have one, or contact the third party either directly or through a legal representative before initiating any testing on that third party or their services. This is not, and should not be understood as, any agreement on our part to defend, indemnify, or otherwise protect you from any third party action based on your actions. -Dicho esto, si un tercero inicia una acción legal, incluyendo las fuerzas del orden, en tu contra por tu participación en este programa de recompensa de errores y has cumplido suficientemente con nuestra política de recompensas por errores (es decir, no has hecho violaciones intencionales o de mala fe), tomaremos las medidas para hacer que se conozca que tus acciones se realizaron de conformidad con esta política. Si bien consideramos que los informes presentados son documentos confidenciales y potencialmente privilegiados y protegidos frente a la divulgación forzada en la mayoría de las circunstancias, ten en cuenta que un tribunal puede, a pesar de nuestras objeciones, ordenarnos que compartamos información con un tercero. +That said, if legal action is initiated by a third party, including law enforcement, against you because of your participation in this bug bounty program, and you have sufficiently complied with our bug bounty policy (i.e. have not made intentional or bad faith violations), we will take steps to make it known that your actions were conducted in compliance with this policy. While we consider submitted reports both confidential and potentially privileged documents, and protected from compelled disclosure in most circumstances, please be aware that a court could, despite our objections, order us to share information with a third party. -## 3. Exención limitada de otras políticas del sitio +## 3. Limited Waiver of Other Site Polices -En medida en que tus actividades de investigación de seguridad sean inconsistentes con ciertas restricciones en nuestras [políticas relevantes de sitio](/categories/site-policy/) pero consistentes con las condiciones de nuestro programa de recompensas por errores, renunciamos a estas restricciones por el solo y único propósito de permitir tu investigación de seguridad bajo este programa. De la misma forma que se menciona anteriormente, si tienes dudas, ¡Pregúntanos primero! +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first! diff --git a/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md index d9f06bec2c..3fe119cf44 100644 --- a/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -1,5 +1,5 @@ --- -title: Condiciones de GitHub para las características y productos adicionales +title: GitHub Terms for Additional Products and Features redirect_from: - /github/site-policy/github-additional-product-terms versions: @@ -9,114 +9,109 @@ topics: - Legal --- -Fecha de entrada en vigor de la versión: 10 de agosto de 2021 +Version Effective Date: August 10, 2021 -Cuando utilices GitHub, podría que se te otorgue acceso a muchos productos y características adicionales ("Características y Productos Adicionales"). Ya que muchas de las Características y Productos Adicionales ofrecen funcionalidades diferentes, las condiciones específicas para dicho producto o característica podrán aplicarse adicionalmente a tu contrato principal con nosotros—las Condiciones de Servicio de GitHub, las Condiciones de Servicio Corporativo de GitHub, las Condiciones Generales de GitHub o el acuerdo de licenciamiento por volumen de Microsoft (cada uno de ellos conocidos como el "Acuerdo"). A continuación, listamos aquellos productos y características jutno con las condiciones adicionales correspondientes que aplican al uso que les des. +When you use GitHub, you may be given access to lots of additional products and features ("Additional Products and Features"). Because many of the Additional Products and Features offer different functionality, specific terms for that product or feature may apply in addition to your main agreement with us—the GitHub Terms of Service, GitHub Corporate Terms of Service, GitHub General Terms, or Microsoft volume licensing agreement (each, the "Agreement"). Below, we've listed those products and features, along with the corresponding additional terms that apply to your use of them. -Al utilizar las características y productos adicionales, también estás de acuerdo con las Condiciones aplicables de GitHub para las características y productos adicionales que se listan a continuación. El violar estas condiciones de GitHub para obtener características y productos adicionales constituye una violación del Acuerdo. Las condiciones en mayúsculas que no se definen aquí tienen el significado que se les otorga en el Acuerdo. +By using the Additional Products and Features, you also agree to the applicable GitHub Terms for Additional Products and Features listed below. A violation of these GitHub terms for Additional Product and Features is a violation of the Agreement. Capitalized terms not defined here have the meaning given in the Agreement. -**Para usuarios empresariales** -- Los usuarios de **GitHub Enterprise Cloud** Podrían tener acceso a los siguientes productos y características adicionales: Acciones, Seguridad Avanzada, Base de Datos de Asesorías, Codespaces, Vista Previa del Dependabot, Laboratorio de Aprendizaje, Octoshift, Paquetes y Páginas. +**For Enterprise users** +- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, and Pages. -- Los usuarios de **GitHub Enterprise Server** podrían tener acceso a los siguientes productos y características adicionales: Acciones, Seguridad Avanzada, Base de Datos de Asesorías, Connect, Vista Previa del Dependabot, Laboratorio de Aprendizaje, Octoshift, Paquetes, Páginas e Imágenes de SQL Server. +- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images. -- Los usuarios de **GitHub AE** podrían tener acceso a los siguientes productos y características adicionales: Acciones, Seguridad Avanzada, Base de Datos de Asesorías, {% ifversion ghae-next %}Connect, {% endif %}Vista Previa del Dependabot, Octoshift, Paquetes y Páginas. +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages. -## Acciones -Acciones de GitHub te permiten crear flujos de trabajo de ciclo de vida de desarrollo del software personalizado directamente en tu repositorio de GitHub. Las acciones se facturan conforme se utilizan. La [Documentación de las acciones](/actions) incluye detalles como las cantidades de procesamiento y almacenamiento (dependiendo del plan de tu cuenta), y el cómo monitorear el uso de minutos de tus acciones y configurar los límites de uso. +## Actions +GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -No podrán utilizarse las acciones ni cualquier elemento del servicio de este producto para violar el acuerdo, las [Políticas de uso aceptable de GitHub](/github/site-policy/github-acceptable-use-policies), ni las limitaciones del servicio de Github, las cuales se establecen en la [Documentación de las acciones](/actions/reference/usage-limits-billing-and-administration). Adicionalmente, sin importar si la acción utiliza ejecutores auto-hospedados, estas no deben utilizarse para: -- criptominería; -- perturbar, ganar o intentar ganar acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (diferentes a aquellos que autoriza el [programa de Recompensas por Errores de GitHub](https://bounty.github.com)); -- la provisión de un servicio o aplicación integrado o independiente que ofrezca el producto o servicio de las acciones o cualquier elemento del servicio o producto de las acciones para propósitos comerciales; -- cualquier actividad que coloque un peso en nuestros servidores, ya sea que dicho peso sea excesivo para los beneficios que se proporcionan a los usuarios (por ejemplo, no utilizamos acciones como una red de entrega de contenido o como parte de una aplicación sin servidores, pero una acción de beneficio mínimo podría estar bien si también implica un peso mínimo); o -- si estás utilizando los ejecutores hospedados en GitHub, cualquier otra actividad sin relación a la producción, pruebas, despliegue o publicación del proyecto de software asociado con el repositorio en donde se utilizan las GitHub Actions. +Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/reference/usage-limits-billing-and-administration). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for: +- cryptomining; +- disrupting, gaining, or attempting to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); +- the provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes; +- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or +- if using GitHub-hosted runners, any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used. -Para evitar violaciones de estas limitaciones y abuso de las Acciones de GitHub, GitHub puede controlar tu uso de Acciones de GitHub. El mal uso de las GitHub Actions podría dar como resultado la terminación de jobs, restricciones en tu capacidad para utilizar las GitHub Actions, o inhabilitar los repositorios que se crearon para ejecutar las acciones de una forma que viole estas condiciones. +In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, or the disabling of repositories created to run Actions in a way that violates these Terms. ## Advanced Security -GitHub hace características de seguridad adicionales para los clientes bajo una licencia de Seguridad Avanzada. Estas características incluyen el escaneo de código, escaneo de secretos y revisión de dependencias. La [Documentación de la seguridad avanzada](/github/getting-started-with-github/about-github-advanced-security) proporciona más detalles. +GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details. -Se otorgan licencias para la Seguridad Avanzada con base en "Confirmantes únicos". Un "Confirmador único" es un usuario con licencia de GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, o GitHub AE, quien realizó una confirmación en los últimos 90 días para cualquier repositorio con cualquier funcionalidad de GitHub Advanced Security activada. Debes adquirir una licencia de usuario de GitHub Advanced Security para cada uno de tus Confirmadores Únicos. Solo puedes utilizar GitHub Advanced Security en las bases de código que desarrollas o que se desarrollan para ti. En el caso de los usuarios de GitHub Enterprise Cloud, algunas características de la Seguridad Avanzada también requieren utilizar las GitHub Actions. +Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. -## Base de datos consultiva -La base de datos de asesorías de GitHub te permite buscar manualmente o por coincidencia las vulnerabilidades que afectan los proyectos de código abierto en GitHub. +## Advisory Database +The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub. -_Licencia otorgada_ +_License Grant to Us_ -Necesitamos el derecho legal de enviar tus contribuciones a la base de datos consultiva de GitHub a los conjuntos de datos de dominio público como la [Base de datos nacional de vulnerabilidad](https://nvd.nist.gov/) y para licenciar la base de datos consultiva de GitHub bajo condiciones abiertas para su uso por investigadores de seguridad, la comunidad de código abierto, la industria y el público. Aceptas publicar tus contribuciones a la base de datos consultiva de GitHub bajo la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). +We need the legal right to submit your contributions to the GitHub Advisory Database into public domain datasets such as the [National Vulnerability Database](https://nvd.nist.gov/) and to license the GitHub Advisory Database under open terms for use by security researchers, the open source community, industry, and the public. You agree to release your contributions to the GitHub Advisory Database under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). -_Licencia para la base de datos consultiva de GitHub_ +_License to the GitHub Advisory Database_ -La base de datos consultiva de GitHub está bajo la licencia [Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/). La condición de la atribución se puede cumplir enlazando a la base de datos consultiva de GitHub en [https://github. om/advisories](https://github.com/advisories) o a registros individuales de la base de datos consultiva de GitHub usada, con la calificación de . +The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . ## Codespaces -_Nota: El servicio de github.dev, el cual se encuentra disponible al presionar `.` en un repositorio o navegando directamente a github.dev se rige mediante los [Términos de Servicio de GitHub Beta](/github/site-policy/github-terms-of-service#j-beta-previews)._ +_Note: The github.dev service, available by pressing `.` on a repo or navigating directly to github.dev, is governed by [GitHub's Beta Terms of service](/github/site-policy/github-terms-of-service#j-beta-previews)._ -Los Codespaces de GitHub te permiten desarrollar código directamente desde tu buscador utilizando el código dentro de tu repositorio de GitHub. Los Codespaces y cualquier elemento de este servicio no podrán utilizarse en violación del Acuerdo o de las Políticas de Uso Aceptable. Adicionalmente, los Codespaces no deben utilizarse para: -- criptominería; -- utilizar nuestros servidores para perturbar o ganar o intentar ganar acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (diferentes a aquellos que autoriza el Programa de Recompensas por Errores de GitHub); -- la provisión de una aplicación o servicio integrado o independiente que ofrezca Codespaces o cualquier elemento de estos para propósitos comerciales; -- cualquier actividad que coloque una carga en nuestros servidores, ya sea que esta sea desproporcional a los beneficios que se proporcionan a los usuarios (por ejemplo, no utilices los Codespaces como una red de entrega de contenido, como parte de una aplicación sin servidor, ni para hospedar algun tipo de aplicació de cara a producción); o -- cualquier otra actividad sin relación al desarrollo o pruebas del proyecto de software asociado con el repositorio en donde se inicia GitHub Codespaces. +GitHub Codespaces enables you to develop code directly from your browser using the code within your GitHub repository. Codespaces and any elements of the Codespaces service may not be used in violation of the Agreement or the Acceptable Use Policies. Additionally, Codespaces should not be used for: +- cryptomining; +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to any service, device, data, account or network (other than those authorized by the GitHub Bug Bounty program); +- the provision of a stand-alone or integrated application or service offering Codespaces or any elements of Codespaces for commercial purposes; +- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Codespaces as a content delivery network, as part of a serverless application, or to host any kind of production-facing application); or +- any other activity unrelated to the development or testing of the software project associated with the repository where GitHub Codespaces is initiated. -Para prevenir las violaciones de estas limitaciones y el abuso de GitHub Codespaces, GitHub podría monitorear tu uso de este servicio. El mal uso de GitHub Codespaces podría resultar en la terminación de tu acceso a este servicio, en restricciones en tu capacidad de utilizarlo o en inhabilitar los repositorios que se crean para ejecutar los Cdespaces en la forma en la que se violen estos Términos. +In order to prevent violations of these limitations and abuse of GitHub Codespaces, GitHub may monitor your use of GitHub Codespaces. Misuse of GitHub Codespaces may result in termination of your access to Codespaces, restrictions in your ability to use GitHub Codespaces, or the disabling of repositories created to run Codespaces in a way that violates these Terms. -Los Codespaces te permiten cargar extensiones de Microsfot Visual Studio Marketplace ("Extensiones de Marketplace") para utilizar en tu ambiente de desarrollo, por ejemplo, para procesar los lenguajes de programación en los que está escrito tu código. Las extensiones de Marketplace se licencian bajo sus propios términos de uso de acuerdo como se describe en Visual Studio Marketplace y los términos de uso se ubican en https://aka.ms/vsmarketplace-ToU. GitHub no otorga garantías de ningún tipo en relación con las Extensiones de Marketplace y no es responsable por las acciones de autores terceros de estas, a quienes se les otorgue acceso a tu contenido. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. El uso que hagas de cualquier solicitud de terceros corre por tu cuenta y riesgo. +Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. Your use of any third-party applications is at your sole risk. -La versión generalmente disponible de los Codespaces no está disponible actualmente para los clientes del gobierno de los EE.UU. Los clientes del gobierno de los EE.UU. pueden seguir utilizando la Vista Previa Beta de los Codespaces bajo términos independientes. Consulta los [Términos de la Vista Previa Beta](/github/site-policy/github-terms-of-service#j-beta-previews). +The generally available version of Codespaces is not currently available for U.S. government customers. U.S. government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews). -## Conexión -Con GitHub Connect, puedes compartir algunas características y datos entre tu instancia de GitHub Enterprise Server {% ifversion ghae-next %}o de GitHub AE {% endif %} y tu cuenta empresarial u organizacional de GitHub Enterprise Cloud en GitHub.com. Para habilitar GitHub Connect, debes tener por lo menos una (1) cuenta en GitHub Enterprise Cloud o en GitHub.com y una (1) instancia con licencia de GitHub Enterprise Server{% ifversion ghae-next %} o de GitHub AE{% endif %}. Ti isp de GitHub Enterprise Cloud o de GitHub.com a través de Connect se rige por los términos bajo los cuales obtengas la licencia de GitHub Enterprise Cloud o GitHub.com. El uso de los datos personales se rige de acuerdo con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement). +## Connect +With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% ifversion ghae-next %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% ifversion ghae-next %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). -## Laboratorio de aprendizaje -El Laboratorio de Aprendizaje de GiThub ofrece cursos interactivos gratuitos que se incorporan en GitHub con retroalimentación automática y ayuda instantáneas. +## GitHub Enterprise Importer +Importer is a framework for exporting data from other sources to be imported to the GitHub platform. Importer is provided “AS-IS”. -*Materiales del curso.* GitHub es el propietario de los materiales de los cursos que proporciona y te garantiza una licencia sin sujeción a regalías, no transferible, por tiempo limitado, no exclusiva para copiar, mantener, utilizar y ejecutar dichos materiales para tus necesidades de negocio internas asociadas con el uso del Laboratorio de Aprendizaje. +## Learning Lab +GitHub Learning Lab offers free interactive courses that are built into GitHub with instant automated feedback and help. -Las condiciones de licencia de código abierto podrían aplicar a porciones del código fuente que se proporcionan en los materiales del curso. +*Course Materials.* GitHub owns course materials that it provides and grants you a worldwide, non-exclusive, limited-term, non-transferable, royalty-free license to copy, maintain, use and run such course materials for your internal business purposes associated with Learning Lab use. -Eres el propietario de los materiales del curso que tú mismo crees y para los cuales proporciones a GitHub una licencia mundial, no exclusiva, perpetua, no transferible y sin regalías para copiarlos, mantenerlos, utilizarlos, hospedarlos y ejecutarlos. +Open source license terms may apply to portions of source code provided in the course materials. -El utilizar los materiales del curso de GitHub y crear y almacenar los materiales de tu propio curso no constituyen una propiedad conjunta de ninguna propiedad intelectual respectiva de las partes. +You own course materials that you create and grant GitHub a worldwide, non-exclusive, perpetual, non-transferable, royalty-free license to copy, maintain, use, host, and run such course materials. -El uso de los datos personales se rige de acuerdo con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement). +The use of GitHub course materials and creation and storage of your own course materials do not constitute joint ownership to either party's respective intellectual property. + +Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ## npm -npm es un servicio de hospedaje de paquetes de software que te permite hospedar tus paquetes de software de forma privada o pública y utilizarlos como dependencias en tus proyectos. npm es el registro de registros para el ecosistema de JavaScript. Utilizar el registro público es gratuito, pero se facturará a los clientes si quieren publicar o administrar paquetes privados que utilicen equipos. La [documentación de npm](https://docs.npmjs.com/) incluye los detalles sobre la limitación de los tipos de cuenta y de como administrar los [paquetes privados](https://docs.npmjs.com/about-private-packages) y [organizaciones](https://docs.npmjs.com/organizations). El uso aceptable del registrio npm se detalla en las [condiciones de código abierto](https://www.npmjs.com/policies/open-source-terms). Hay condiciones adicionales tanto para los planes [solo](https://www.npmjs.com/policies/solo-plan) y [org](https://www.npmjs.com/policies/orgs-plan) de npm. Las [Condiciones de uso](https://www.npmjs.com/policies/terms) de npm aplican a tu uso de este. +npm is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. npm is the registry of record for the JavaScript ecosystem. The npm public registry is free to use but customers are billed if they want to publish private packages or manage private packages using teams. The [npm documentation](https://docs.npmjs.com/) includes details about the limitation of account types and how to manage [private packages](https://docs.npmjs.com/about-private-packages) and [organizations](https://docs.npmjs.com/organizations). Acceptable use of the npm registry is outlined in the [open-source terms](https://www.npmjs.com/policies/open-source-terms). There are supplementary terms for both the npm [solo](https://www.npmjs.com/policies/solo-plan) and [org](https://www.npmjs.com/policies/orgs-plan) plans. The npm [Terms of Use](https://www.npmjs.com/policies/terms) apply to your use of npm. -## Octoshift -Octoshift es un marco de trabajo para exportar datos desde otras fuentes e importarlos en la plataforma de GitHub. Se proporciona Octoshift "TAL COMO ESTÁ". - -## Paquetes -GitHub Packages es un servicio de hospedaje de paquetes de software que te permite hospedar tus paquetes de software de forma privada o pública y utilizar los paquetes como dependencias en tus proyectos. GitHub Packages se factura de acuerdo con su uso. La [Documentación de paquetes](/packages/learn-github-packages/introduction-to-github-packages) incluye los detalles como las cantidades de ancho de banda y almacenamiento (dependiendo del plan de tu cuenta), y la forma en la que puedes monitorear el uso de los paquetes y configurar los límites de uso. El uso de ancho de banda de los paquetes se limita por las [Políticas de uso aceptable de GitHub](/github/site-policy/github-acceptable-use-policies). +## Packages +GitHub Packages is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. GitHub Packages is billed on a usage basis. The [Packages documentation](/packages/learn-github-packages/introduction-to-github-packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ## Pages -Cada cuenta incluye acceso al [servicio de hospedaje estático de GitHub pages](/github/working-with-github-pages/about-github-pages). Se pretende que GitHub pages hospede páginas web estáticas, pero es primeramente para mostrar proyectos organizacionales y personales. +Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects. -No se pretende ni se permite que las Páginas de GitHub se utilicen como un servicio de alojamiento web gratuito para ejecutar tus negocios en línea, ni como un sitio de comercio electrónico ni ningún otro tipo de sitio web que se dirija principalmente ya sea a facilitartransacciones comerciales o a proporcionar software comercial como un servicio (SaaS). Se permiten algunas iniciativas de monetización en las Páginas, tales como botones de donación y enlaces de financiación colectiva. +GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links. -### a. Límites de uso y de ancho de banda -Las páginas de GitHub están sujetas a algunos límites específicos de ancho de banda y de uso, y podrían no ser adecuadas para algunos usos de ancho de banda alto. Consulte nuestras [directrices de páginas de GitHub](/github/working-with-github-pages/about-github-pages) para obtener más información. +_Bandwidth and Usage Limits_ -### b. Usos prohibidos -Los usos prohiubidos de las Páginas de GitHub incluyen -- Contenido o actividad que es prohibida o ilegal de acuerdo con nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service), [Políticas de Uso Aceptable](/github/site-policy/github-acceptable-use-policies) o [Lineamientos Comunitarios](/github/site-policy/github-community-guidelines) -- el contenido o la actividad violentas o amenazadoras -- la actividad masiva automatizada excesiva (por ejemplo, envío de spam) -- la actividad que comprometa a los usuarios o los servicios de GitHub -- los esquemas del tipo 'hágase rico rápidamente' -- el contenido sexualmente obsceno -- el contenido que falsea de manera fraudulenta tu identidad o el propósito del sitio +GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Please see our [GitHub Pages limits](/github/working-with-github-pages/about-github-pages) for more information. -Su tuebes dudas sobre si tu uso o intención de uso cae en las siguientes categorías, por favor, contacta al [Soporte de GitHub](https://support.github.com/contact?tags=docs-policy). GitHub se reserva el derecho en todo momento de reclamar cualquier subdominio de GitHub sin responsabilidad. +_Prohibited Uses_ -## Programa de patrocinadores +GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies), or the GitHub Pages service limitations set forth in the [Pages documentation](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages). -GitHub Sponsors permite a la comunidad de desarrolladores apoyar financieramente al personal y organizaciones que diseñan, crean y mantienen los proyectos de código abierto de los cuales dependen, directamente en GitHub. Para convertirse en un Desarrollador Patrocinado, debes aceptar los [Términos Adicionales del Programa de Patrocinadores de GitHub](/github/site-policy/github-sponsors-additional-terms). +If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability. -## Imagenes de SQL Server +## Sponsors Program -Puedes descargar la imagen de contenedor de la Edición Estándar de Microsoft SQL Server para archivos Linux ("SQL Server Images"). Debes desinstalar las imagenes de SQL Server cuando termine tu derecho de utilizar el software. Microsoft Corporation puede inhabilitar las imágenes de SQL Server en cualquier momento. +GitHub Sponsors allows the developer community to financially support the people and organizations who design, build, and maintain the open source projects they depend on, directly on GitHub. In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors Program Additional Terms](/github/site-policy/github-sponsors-additional-terms). + +## SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time. diff --git a/translations/es-ES/content/github/site-policy/index.md b/translations/es-ES/content/github/site-policy/index.md index 465afca13a..abb63c7a33 100644 --- a/translations/es-ES/content/github/site-policy/index.md +++ b/translations/es-ES/content/github/site-policy/index.md @@ -1,5 +1,5 @@ --- -title: Política del sitio +title: Site policy redirect_from: - /categories/61/articles/ - /categories/site-policy @@ -27,7 +27,7 @@ children: - /github-private-information-removal-policy - /github-subprocessors-and-cookies - /github-bug-bounty-program-legal-safe-harbor - - /responsible-disclosure-of-security-vulnerabilities + - /coordinated-disclosure-of-security-vulnerabilities - /guidelines-for-legal-requests-of-user-data - /github-government-takedown-policy - /github-acceptable-use-policies diff --git a/translations/es-ES/content/github/working-with-github-support/about-github-support.md b/translations/es-ES/content/github/working-with-github-support/about-github-support.md index e96bca3ea3..b5e542661a 100644 --- a/translations/es-ES/content/github/working-with-github-support/about-github-support.md +++ b/translations/es-ES/content/github/working-with-github-support/about-github-support.md @@ -1,6 +1,6 @@ --- -title: Acerca del Soporte de GitHub -intro: '{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas con los que te encuentres cuando utilices {% data variables.product.prodname_dotcom %}.' +title: About GitHub Support +intro: '{% data variables.contact.github_support %} can help you troubleshoot issues you run into while using {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/about-github-support versions: @@ -10,30 +10,30 @@ topics: - Jobs --- -## Acerca de {% data variables.contact.github_support %} +## About {% data variables.contact.github_support %} -Las opciones de soporte varían dependiendo de tu producto de {% data variables.product.prodname_dotcom_the_website %}. Si cuentas con un producto pagado, puedes contactar a {% data variables.contact.github_support %} en inglés. Tu cuenta también puede incluir {% data variables.contact.premium_support %}. +Support options vary depending on your {% data variables.product.prodname_dotcom_the_website %} product. If you have any paid product, you can contact {% data variables.contact.github_support %}, in English. Your account may also include {% data variables.contact.premium_support %}. -| | {% data variables.product.prodname_gcf %} | Soporte estándar | Soporte premium | -| -------------------------------------------------- | ----------------------------------------- | ---------------- | --------------- | -| {% data variables.product.prodname_free_user %} | X | | | -| {% data variables.product.prodname_pro %} | X | X | | -| {% data variables.product.prodname_team %} | X | X | | -| {% data variables.product.prodname_ghe_cloud %} | X | X | X | -| {% data variables.product.prodname_ghe_server %} | X | X | X | +| | {% data variables.product.prodname_gcf %} | Standard support | Premium support | +|----|---------------|-------|---------------| +| {% data variables.product.prodname_free_user %} | X | | | +| {% data variables.product.prodname_pro %} | X | X | | +| {% data variables.product.prodname_team %} | X | X | | +| {% data variables.product.prodname_ghe_cloud %} | X | X | X | +| {% data variables.product.prodname_ghe_server %} | X | X | X | -Para ver si actualmente hay algún incidente que afecte los servicios en {% data variables.product.prodname_dotcom %}, o para suscribirse y recibir notificaciones de actualizaciones de estado futuras, visita la [Página de Estado](https://www.githubstatus.com/) de {% data variables.product.prodname_dotcom %}. +To see if there are currently any incidents affecting services on {% data variables.product.prodname_dotcom %}, or to subscribe and receive notifications of future status updates, visit {% data variables.product.prodname_dotcom %}'s [Status Page](https://www.githubstatus.com/). -## Comunicarse con {% data variables.contact.github_support %} +## Contacting {% data variables.contact.github_support %} -{% data reusables.support.zendesk-deprecation %} +{% data reusables.support.zendesk-old-tickets %} -Puedes utilizar el {% data variables.contact.community_support_forum %} para buscar temas, hacer preguntas, compartir soluciones e interactuar directamente con {% data variables.contact.community_support %}. +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. -Para reportar incidentes de cuenta, seguridad y abuso, o para recibir soporte asistido para una cuenta de pago, visita el {% data variables.contact.contact_support_portal %}. Si eres un administrador de {% data variables.product.prodname_ghe_server %} sin una cuenta de usuario en {% data variables.product.prodname_dotcom_the_website %}, vista el {% data variables.contact.contact_enterprise_portal %}. Las comunicaciones de correo electrónico de GitHub Support siempre se enviarán ya sea desde una dirección de `github.com` o de `githubsupport.com`. +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. Email communication from GitHub Support will always be sent from either a `github.com` or `githubsupport.com` address. -## Otorgar a {% data variables.contact.github_support %} acceso temporario a un repositorio privado +## Granting {% data variables.contact.github_support %} temporary access to a private repository -Si {% data variables.contact.github_support %} necesita acceder a un repositorio privado para abordar tu solicitud de soporte técnico, el propietario del repositorio recibirá un correo electrónico con un enlace para aceptar o rechazar el acceso temporario. El propietario tendrá 20 días para aceptar o rechazar la solicitud antes de que ésta caduque. Si el propietario acepta la solicitud, {% data variables.contact.github_support %} tendrá acceso al repositorio por cinco días. +If {% data variables.contact.github_support %} needs to access a private repository to address your support request, the owner of the repository will receive an email with a link to accept or decline temporary access. The owner will have 20 days to accept or decline the request before the request expires. If the owner accepts the request, {% data variables.contact.github_support %} will have access the repository for five days. -{% data variables.contact.github_support %} nunca accederá a tus repositorios privados sin tu consentimiento explícito. Para obtener más información, consulta los [Términos de servicio](/free-pro-team@latest/github/site-policy/github-terms-of-service#3-access). +{% data variables.contact.github_support %} will never access your private repositories without your explicit consent. For more information, see the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service#3-access). diff --git a/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md b/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md index 7aad4d8b9a..7c198a59d3 100644 --- a/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md +++ b/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md @@ -1,54 +1,54 @@ --- -title: Asistencia para Enterprise Cloud de GitHub +title: GitHub Enterprise Cloud support redirect_from: - /articles/business-plan-support/ - /articles/github-business-cloud-support/ - /articles/github-enterprise-cloud-support -intro: '{% data variables.product.prodname_ghe_cloud %} incluye un tiempo de respuesta objetivo de ocho horas para las solicitudes de asistencia prioritarias, de lunes a viernes en tu zona horaria local.' +intro: '{% data variables.product.prodname_ghe_cloud %} includes a target eight-hour response time for priority support requests, Monday to Friday in your local time zone.' versions: fpt: '*' ghec: '*' topics: - Jobs -shortTitle: Nube de GitHub Enterprise +shortTitle: GitHub Enterprise Cloud --- {% note %} -**Notq:** Los clientes de {% data variables.product.prodname_ghe_cloud %} pueden registrarse para {% data variables.contact.premium_support %}. Para obtener más información, consulta "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)". +**Note:** {% data variables.product.prodname_ghe_cloud %} customers can sign up for {% data variables.contact.premium_support %}. For more information, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)." {% endnote %} -{% data reusables.support.zendesk-deprecation %} +{% data reusables.support.zendesk-old-tickets %} -Puedes enviar preguntas prioritarias si has comprado {% data variables.product.prodname_ghe_cloud %} o si eres miembro, colaborador externo o gerente de facturación de una organización {% data variables.product.prodname_dotcom %} actualmente suscrita en {% data variables.product.prodname_ghe_cloud %}. +You can submit priority questions if you have purchased {% data variables.product.prodname_ghe_cloud %} or if you're a member, outside collaborator, or billing manager of a {% data variables.product.prodname_dotcom %} organization currently subscribed to {% data variables.product.prodname_ghe_cloud %}. -Preguntas que califican para recibir respuestas prioritarias: -- Incluyen preguntas relacionadas con tu imposibilidad para acceder o usar la funcionalidad de control de la versión principal de {% data variables.product.prodname_dotcom %} -- Incluyen situaciones relacionadas con la seguridad de tu cuenta -- No incluyen servicios y funciones periféricos, como preguntas acerca de Gists, {% data variables.product.prodname_pages %} o notificaciones de correo electrónico -- Incluyen preguntas acerca de organizaciones que actualmente usan {% data variables.product.prodname_ghe_cloud %} +Questions that qualify for priority responses: +- Include questions related to your inability to access or use {% data variables.product.prodname_dotcom %}'s core version control functionality +- Include situations related to your account security +- Do not include peripheral services and features, such as questions about Gists, {% data variables.product.prodname_pages %}, or email notifications +- Include questions only about organizations currently using {% data variables.product.prodname_ghe_cloud %} -Para calificar para una respuesta prioritaria, debes hacer lo siguiente: -- Enviar tu pregunta a [{% data variables.contact.enterprise_support %}](https://enterprise.githubsupport.com/hc/en-us/requests/new?github_product=cloud) desde una dirección de correo verificada que esté asociada con la organización que actualmente usa {% data variables.product.prodname_ghe_cloud %} -- Enviar un ticket de asistencia nuevo para cada situación prioritaria particular -- Enviar tu pregunta de lunes a viernes en tu zona horaria local -- Comprender que la respuesta a una pregunta prioritaria será recibida por correo electrónico -- Colaborar con {% data variables.contact.github_support %} y proporcionar toda la información que solicite {% data variables.contact.github_support %} +To qualify for a priority response, you must: +- Submit your question to [{% data variables.contact.enterprise_support %}](https://support.github.com/contact?tags=docs-generic) from a verified email address that's associated with an organization currently using {% data variables.product.prodname_ghe_cloud %} +- Submit a new support ticket for each individual priority situation +- Submit your question from Monday-Friday in your local time zone +- Understand that the response to a priority question will be received via email +- Cooperate with {% data variables.contact.github_support %} and provide all of the information that {% data variables.contact.github_support %} asks for {% tip %} -**Consejo:** Las preguntas no califican para recibir respuestas prioritarias si se envían durante un feriado local de tu jurisdicción. +**Tip:** Questions do not qualify for a priority response if they are submitted on a local holiday in your jurisdiction. {% endtip %} -El tiempo de respuesta objetivo de ocho horas: -- Comienza cuando {% data variables.contact.github_support %} recibe tu pregunta que califica -- No comienza hasta que hayas proporcionada la suficiente información para responder la pregunta, a menos que específicamente indiques que no cuentas con la información suficiente -- No aplica durante los fines de semana de tu zona horaria local o durante los feriados locales de tu jurisdicción +The target eight-hour response time: +- Begins when {% data variables.contact.github_support %} receives your qualifying question +- Does not begin until you have provided sufficient information to answer the question, unless you specifically indicate that you do not have sufficient information +- Does not apply on weekends in your local timezone or local holidays in your jurisdiction {% note %} -**Nota:** {% data variables.contact.github_support %} no garantiza una resolución para tu pregunta prioritaria. {% data variables.contact.github_support %} puede escalar problemas al estado de pregunta prioritaria o bajarlos en función de nuestra evaluación razonable de la información que nos proporcionas. +**Note:** {% data variables.contact.github_support %} does not guarantee a resolution to your priority question. {% data variables.contact.github_support %} may escalate or deescalate issues to or from priority question status, based on our reasonable evaluation of the information you give to us. {% endnote %} diff --git a/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md b/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md index 859990d98f..ee1785cc2a 100644 --- a/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md @@ -1,6 +1,6 @@ --- -title: Envío de ticket -intro: 'Puedes enviar un ticket a {% data variables.contact.github_support %} utilizando el portal de soporte.' +title: Submitting a ticket +intro: 'You can submit a ticket to {% data variables.contact.github_support %} using the support portal.' redirect_from: - /articles/submitting-a-ticket versions: @@ -9,37 +9,34 @@ versions: topics: - Jobs --- - -## Acerca de la emisión de tickets -Si tu cuenta utiliza un producto pagado de {% data variables.product.prodname_dotcom %}, puedes contactar directamente a {% data variables.contact.github_support %}. Si tu cuenta utiliza {% data variables.product.prodname_free_user %} para cuentas y organizaciones de usuario, puedes contactar a {% data variables.contact.github_support %} para reportar los problemas con las cuentas, la seguridad y el abuso. Para obtener más informaciónm, consulta la sección "[Acerca de GitHub Support](/github/working-with-github-support/about-github-support)". +## About ticket submission +If your account uses a paid {% data variables.product.prodname_dotcom %} product, you can directly contact {% data variables.contact.github_support %}. If your account uses {% data variables.product.prodname_free_user %} for user accounts and organizations, you can use contact {% data variables.contact.github_support %} to report account, security, and abuse issues. For more information, see "[About GitHub Support](/github/working-with-github-support/about-github-support)." {% data reusables.enterprise-accounts.support-entitlements %} -Si no tienes una cuenta empresarial, por favor, utiliza el {% data variables.contact.enterprise_portal %} para emitir tickets. Para obtener más información sobre las cuentas empresariales, consulta la sección "[Acerca de las cuentas empresariales](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)". +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." -## Enviar un ticket mediante el {% data variables.contact.support_portal %} +## Submitting a ticket using the {% data variables.contact.support_portal %} -1. Navega por el {% data variables.contact.contact_support_portal %}. -2. Debajo de "Nombre", ingresa tu nombre. ![Campo de nombre](/assets/images/help/support/name-field.png) -3. Utiliza el menú desplegable de correo electrónico y selecciona la dirección de correo electrónico que deseas contacte {% data variables.contact.github_support %}.![Campo de correo electrónico](/assets/images/help/support/email-field.png) -4. Debajo de "Tema", teclea un título descriptivo para el problema que estás experimentando. ![Campo de asuto](/assets/images/help/support/subject-field.png) -5. Debajo de "Cómo podemos ayudar", proporciona cualquier tipo de información adicional que ayudará al equipo de soporte a solucionar el problema. La información útil podría incluir: ![Campo de cómo podemos ayudar](/assets/images/help/support/how-can-we-help-field.png) - - Pasos para reproducir el incidente - - Cualquier circunstancia especial relacionada con el descubrimiento del problema (por ejemplo, la primera vez que se suscitó, o su materialización después de cierto evento, frecuencia en la que se presenta, impacto al negocio, y urgencia sugerida) - - Redacción exacta de los mensajes de error -6. Opcionalmente, adjunta archivos arrastrando y soltando, cargando, o pegando desde el portapapeles. -7. Da clic en **Enviar solicitud**. ![Botón de eenviar solicitud](/assets/images/help/support/send-request-button.png) +{% data reusables.support.zendesk-old-tickets %} -## Emitir un ticket utilizando el {% data variables.contact.enterprise_portal %} +1. Navigate to the {% data variables.contact.contact_support_portal %}. +2. Select the **Account or organization** drop-down menu and click the name of the account, organization, or enterprise your ticket is regarding. +![Account field](/assets/images/help/support/account-field.png) +2. Select the **From** drop-down menu and click the email address you'd like {% data variables.contact.github_support %} to contact. +![Email field](/assets/images/help/support/from-field.png) +4. Under "Subject", type a descriptive title for the issue you're having. +![Subject field](/assets/images/help/support/subject-field.png) +5. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. Helpful information may include: + ![How can we help field](/assets/images/help/support/how-can-we-help-field.png) + - Steps to reproduce the issue + - Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency) + - Exact wording of error messages +6. Optionally, attach files by dragging and dropping, uploading, or pasting from the clipboard. +7. Click **Send request**. +![Send request button](/assets/images/help/support/send-request-button.png) -{% data reusables.support.zendesk-deprecation %} - -1. Navegar por el {% data variables.contact.contact_enterprise_portal %}. -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} - -## Leer más -- "[Productos de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)" -- "[Acerca de {% data variables.contact.github_support %}](/articles/about-github-support)" -- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)." +## Further reading +- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)" +- "[About {% data variables.contact.github_support %}](/articles/about-github-support)" +- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)." diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 34c91efb11..b1ca69a0dc 100644 --- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -1,6 +1,6 @@ --- -title: Sintaxis de escritura y formato básicos -intro: Crear formatos sofisticados para tu prosa y código en GitHub con sintaxis simple. +title: Basic writing and formatting syntax +intro: Create sophisticated formatting for your prose and code on GitHub with simple syntax. redirect_from: - /articles/basic-writing-and-formatting-syntax - /github/writing-on-github/basic-writing-and-formatting-syntax @@ -9,65 +9,64 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Sintaxis de formato básica +shortTitle: Basic formatting syntax --- +## Headings -## Encabezados - -Para crear un encabezado, agrega uno a seis símbolos `#` antes del encabezado del texto. La cantidad de `#` que usas determinará el tamaño del ecanbezado. +To create a heading, add one to six `#` symbols before your heading text. The number of `#` you use will determine the size of the heading. ```markdown -# El encabezado más largo -## El segundo encabezado más largo -###### El encabezado más pequeño +# The largest heading +## The second largest heading +###### The smallest heading ``` -![Encabezados H1, H2 y H6 representados](/assets/images/help/writing/headings-rendered.png) +![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png) -## Estilo de texto +## Styling text -Puedes indicar énfasis con texto en negritas, itálicas o tachadas en los campos de comentario y archivos `.md`. +You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files. -| Estilo | Sintaxis | Atajo del teclado | Ejemplo | Resultado | -| ---------------------------- | ----------------- | ------------------- | ----------------------------------------------- | --------------------------------------------- | -| Negrita | `** **` o `__ __` | command/control + b | `**Este texto está en negrita**` | **Este texto está en negrita** | -| Cursiva | `* *` o `_ _` | command/control + i | `*Este texto está en cursiva*` | *Este texto está en cursiva* | -| Tachado | `~~ ~~` | | `~~Este texto está equivocado~~` | ~~Este texto está equivocado~~ | -| Cursiva en negrita y anidada | `** **` y `_ _` | | `**Este texto es _extremadamente_ importante**` | **Este texto es _extremadamente_ importante** | -| Todo en negrita y cursiva | `*** ***` | | `***Todo este texto es importante***` | ***Todo este texto es importante*** | +| Style | Syntax | Keyboard shortcut | Example | Output | +| --- | --- | --- | --- | --- | +| Bold | `** **` or `__ __` | command/control + b | `**This is bold text**` | **This is bold text** | +| Italic | `* *` or `_ _` | command/control + i | `*This text is italicized*` | *This text is italicized* | +| Strikethrough | `~~ ~~` | | `~~This was mistaken text~~` | ~~This was mistaken text~~ | +| Bold and nested italic | `** **` and `_ _` | | `**This text is _extremely_ important**` | **This text is _extremely_ important** | +| All bold and italic | `*** ***` | | `***All this text is important***` | ***All this text is important*** | -## Cita de texto +## Quoting text -Puedes citar texto con un `>`. +You can quote text with a `>`. ```markdown -Texto que no es una cita +Text that is not a quote -> Texto que es una cita +> Text that is a quote ``` -![Texto citado representado](/assets/images/help/writing/quoted-text-rendered.png) +![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png) {% tip %} -**Sugerencia:** Al revisar una conversación, puedes citar un texto automáticamente en un comentario al resaltar el texto y luego escribir el código `r`. Puedes citar un comentario completo al hacer clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, y luego en **Quote reply** (Citar respuesta). Para obtener más información sobre atajo del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)". +**Tip:** When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing `r`. You can quote an entire comment by clicking {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Quote reply**. For more information about keyboard shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts/)." {% endtip %} -## Código de cita +## Quoting code -Puedes indicar un código o un comando dentro de un enunciado con comillas simples. El texto entre las comillas simples no se formateará.{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} También puedes presionar el atajo de teclado `command` o `Ctrl` + `e` para insertar las comillas simples para un bloque de código dentro de una línea o texto de marcado.{% endif %} +You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %} ```markdown -Usa `git status` para enumerar todos los archivos nuevos o modificados que aún no han sido confirmados. +Use `git status` to list all new or modified files that haven't yet been committed. ``` -![Bloque de código en línea representado](/assets/images/help/writing/inline-code-rendered.png) +![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png) -Para formatear código o texto en su propio bloque distintivo, usa comillas triples. +To format code or text into its own distinct block, use triple backticks. 
    -Algunos de los comandos de Git básicos son:
+Some basic Git commands are:
 ```
 git status
 git add
@@ -75,70 +74,82 @@ git commit
 ```
    -![Bloque de código representado](/assets/images/help/writing/code-block-rendered.png) +![Rendered code block](/assets/images/help/writing/code-block-rendered.png) -Para obtener más información, consulta "[Crear y resaltar bloques de código](/articles/creating-and-highlighting-code-blocks)". +For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)." -## Enlaces +## Links -Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes `[ ]`, y luego encerrar la URL entre paréntesis `( )`. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}También puedes utilizar el atajo de teclado `command + k` para crear un enlace.{% endif %} +You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %} -`Este sitio se construyó usando [GitHub Pages](https://pages.github.com/).` +`This site was built using [GitHub Pages](https://pages.github.com/).` -![Enlace representado](/assets/images/help/writing/link-rendered.png) +![Rendered link](/assets/images/help/writing/link-rendered.png) {% tip %} -**Sugerencias:** {% data variables.product.product_name %} automáticamente crea enlaces cuando las direcciones URL válidas están escritas en un comentario. Para obtener más información, consulta "[Referencias y direcciones URL autovinculadas](/articles/autolinked-references-and-urls)". +**Tip:** {% data variables.product.product_name %} automatically creates links when valid URLs are written in a comment. For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)." {% endtip %} -## Enlaces de sección +## Section links {% data reusables.repositories.section-links %} -## Enlaces relativos +## Relative links {% data reusables.repositories.relative-links %} -## Imágenes +## Images -Puedes mostrar una imagen si agregas un `!` y pones el texto alternativo entre `[ ]`. Entonces encierra el enlace de la imagen entre paréntesis `()`. +You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then wrap the link for the image in parentheses `()`. -`![Esta es una imagen](https://myoctocat.com/assets/images/base-octocat.svg)` +`![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)` -![Imagen interpretada](/assets/images/help/writing/image-rendered.png) +![Rendered Image](/assets/images/help/writing/image-rendered.png) -{% data variables.product.product_name %} es compatible con incrustar imágenes en tus propuestas, solicitudes de cambio{% ifversion fpt or ghec %}, debates{% endif %}, comentarios y archivos `.md`. Puedes mostrar una imagen desde tu repositorio, agregar un enlace a una imagen en línea o cargar una imagen. Para obtener más información, consulta la sección "[Cargar activos](#uploading-assets)". +{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt or ghec %}, discussions{% endif %}, comments and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)." {% tip %} -**Tip:** Cuando quieras mostrar una imagen que esté en tu repositorio, deberías utilizar enlaces relativos en vez de absolutos. +**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. {% endtip %} -Aquí tienes algunos ejemplos para utilizar enlaces relativos para mostrar una imagen. +Here are some examples for using relative links to display an image. -| Contexto | Enlace Relativo | -| ----------------------------------------------------------------------- | ---------------------------------------------------------------------- | -| En un archivo `.md` en la misma rama | `/assets/images/electrocat.png` | -| En un archivo `.md` en otra rama | `/../main/assets/images/electrocat.png` | -| En propuestas, solicitudes de cambio y comentarios del repositorio | `../blob/main/assets/images/electrocat.png` | -| En un archivo `.md` en otro repositorio | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | -| En propuestas, solicitudes de cambios y comentarios de otro repositorio | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | +| Context | Relative Link | +| ------ | -------- | +| In a `.md` file on the same branch | `/assets/images/electrocat.png` | +| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` | +| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` | +| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | +| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | {% note %} -**Nota**: Los últimos dos enlaces relativos en la tabla anterior funcionarán únicamente para las imágenes en repositorios privados solo si el lector tiene por lo menos acceso de lectura a este. +**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images. {% endnote %} -Para obtener más información, consulta la sección "[Enlaces relativos](#relative-links)". +For more information, see "[Relative Links](#relative-links)." +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5559 %} +### Specifying the theme an image is shown to -## Listas +You can specify the theme an image is displayed to by appending `#gh-dark-mode-only` or `#gh-light-mode-only` to the end of an image URL, in Markdown. -Puedes realizar una lista desordenada al anteceder una o más líneas de texto con `-` o `*`. +We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images. + +| Context | URL | +|--------|--------| +| Dark Theme | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` | +| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)` | +{% endif %} + +## Lists + +You can make an unordered list by preceding one or more lines of text with `-` or `*`. ```markdown - George Washington @@ -146,9 +157,9 @@ Puedes realizar una lista desordenada al anteceder una o más líneas de texto c - Thomas Jefferson ``` -![Lista desordenada representada](/assets/images/help/writing/unordered-list-rendered.png) +![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png) -Para ordenar tu lista, antecede cada línea con un número. +To order your list, precede each line with a number. ```markdown 1. James Madison @@ -156,126 +167,126 @@ Para ordenar tu lista, antecede cada línea con un número. 3. John Quincy Adams ``` -![Lista ordenada representada](/assets/images/help/writing/ordered-list-rendered.png) +![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png) -### Listas anidadas +### Nested Lists -Puedes crear una lista anidada al dejar sangría en uno o más elementos de la lista debajo de otro elemento. +You can create a nested list by indenting one or more list items below another item. -Para crear una lista anidada mediante el editor web en {% data variables.product.product_name %} o un editor de texto que usa una fuente monoespaciada, como [Atom](https://atom.io/), puedes alinear tu lista visualmente. Escribe los caracteres con espacio frente a tu elemento de la lista anidada hasta que el carácter del marcador de lista (`-` or `*`) se encuentre directamente debajo del primer carácter del texto en el elemento que se encuentra por debajo. +To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [Atom](https://atom.io/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (`-` or `*`) lies directly below the first character of the text in the item above it. ```markdown -1. Primer elemento de la lista - - Primer elemento de la lista anidado - - Segundo elemento de la lista anidado +1. First list item + - First nested list item + - Second nested list item ``` -![Lista anidada con alineación resaltada](/assets/images/help/writing/nested-list-alignment.png) +![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png) -![Lista con dos niveles de elementos anidados](/assets/images/help/writing/nested-list-example-1.png) +![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png) -Para crear una lista anidada en el editor de comentarios en {% data variables.product.product_name %}, que no usa una fuente monoespaciada, puedes observar el elemento de la lista inmediatamente anterior a la lista anidada y contar el número de caracteres que aparecen antes del contenido del elemento. Luego escribe ese número de caracteres de espacio frente al elemento de la lista anidada. +To create a nested list in the comment editor on {% data variables.product.product_name %}, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item. -En este ejemplo, puedes agregar un elemento de la lista anidada debajo del elemento de la lista `100. Primer elemento de la lista` con una sangría mínima de cinco espacios para el elemento de la lista anidada, dado que hay cinco caracteres (`100.`) antes del `Primer elemento de la lista`. +In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100. `) before `First list item`. ```markdown -100. Primer elemento de la lista - - Primer elemento de la lista anidada +100. First list item + - First nested list item ``` -![Lista con un elemento de lista anidado](/assets/images/help/writing/nested-list-example-3.png) +![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png) -Puedes crear múltiples niveles de listas anidadas mediante el mismo método. Por ejemplo, ya que el primer elemento de la lista anidada tiene siete caracteres (`␣␣␣␣␣-␣`) antes del contenido `First nested list item` de la misma, necesitarás colocar sangría de siete espacios en el segundo elemento de esta. +You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown -100. Primer elemento de la lista - - Primer elemento de la lista anidada - - Segundo elemento de la lista anidada +100. First list item + - First nested list item + - Second nested list item ``` -![Lista con dos niveles de elementos anidados](/assets/images/help/writing/nested-list-example-2.png) +![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png) -Para conocer más ejemplos, consulta las [Especificaciones de formato Markdown de GitHub](https://github.github.com/gfm/#example-265). +For more examples, see the [GitHub Flavored Markdown Spec](https://github.github.com/gfm/#example-265). -## Listas de tareas +## Task lists {% data reusables.repositories.task-list-markdown %} -Si una descripción de los elementos de la lista de tareas comienza con un paréntesis, necesitarás colocar una `\`: +If a task list item description begins with a parenthesis, you'll need to escape it with `\`: -`- [ ] \(Optional) Abre una propuesta de seguimiento` +`- [ ] \(Optional) Open a followup issue` -Para obtener más información, consulta "[Acerca de las listas de tareas](/articles/about-task-lists)". +For more information, see "[About task lists](/articles/about-task-lists)." -## Mencionar personas y equipos +## Mentioning people and teams -Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir `@` más el nombre de usuario o el nombre del equipo. Esto activará una notificación y llamará su atención hacia la conversación. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. Para obtener más información acerca de las notificaciones, consulta la sección {% ifversion fpt or ghes or ghae or ghec %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciones](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}". +You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing `@` plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." -`@github/support ¿Qué piensas sobre estas actualizaciones?` +`@github/support What do you think about these updates?` -![@mention representado](/assets/images/help/writing/mention-rendered.png) +![Rendered @mention](/assets/images/help/writing/mention-rendered.png) -Cuando mencionas a un equipo padre, los miembros de los equipos hijo también reciben notificaciones, simplificando la comunicación con múltiples grupos de personas. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". +When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "[About teams](/articles/about-teams)." -Si escribes un símbolo `@` aparecerá una lista de personas o equipos en el proyecto. La lista filtra a medida que escribes, por lo que una vez que escribes el nombre de la persona o del equipo que estás buscando, puedes usar las teclas de flecha para seleccionarlos y presionar cada pestaña para ingresar para completar el nombre. En el caso de los equipos, escribe el nombre de la @organización/equipo y todos los miembros del equipo que se suscribirán a la conversación. +Typing an `@` symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation. -Los resultados autocompletados se restringen a los colaboradores del repositorio y a otros participantes en el hilo. +The autocomplete results are restricted to repository collaborators and any other participants on the thread. -## Hacer referencia a propuestas y solicitudes de extracción +## Referencing issues and pull requests -Puedes mencionar una lista de las propuestas y las solicitudes de extracción sugeridas dentro del repositorio al escribir `#`. Escribe el número o el título de la propuesta o la solicitud de extracción para filtrar la lista, y luego presiona cada pestaña o ingresa para completar el resultado resaltado. +You can bring up a list of suggested issues and pull requests within the repository by typing `#`. Type the issue or pull request number or title to filter the list, and then press either tab or enter to complete the highlighted result. -Para obtener más información, consulta "[Referencias y direcciones URL autovinculadas](/articles/autolinked-references-and-urls)". +For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)." -## Hacer referencia a recursos externos +## Referencing external resources {% data reusables.repositories.autolink-references %} -## Adjuntos de contenido +## Content attachments -Algunas {% data variables.product.prodname_github_apps %} proporcionan información en {% data variables.product.product_name %} para las URL que enlazan a sus dominios registrados. {% data variables.product.product_name %} presenta la información suministrada por la app debajo de la URL en el cuerpo o comentario de una propuesta o solicitud de extracción. +Some {% data variables.product.prodname_github_apps %} provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} renders the information provided by the app under the URL in the body or comment of an issue or pull request. -![Adjunto de contenido](/assets/images/github-apps/content_reference_attachment.png) +![Content attachment](/assets/images/github-apps/content_reference_attachment.png) -Para ver los adjuntos de contenido, debes tener una {% data variables.product.prodname_github_app %} que use la API de los adjuntos de contenido instalada en el repositorio.{% ifversion fpt or ghec %} Para obtener más información, consulta las secciones "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)" y "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)".{% endif %} +To see content attachments, you must have a {% data variables.product.prodname_github_app %} that uses the Content Attachments API installed on the repository.{% ifversion fpt or ghec %} For more information, see "[Installing an app in your personal account](/articles/installing-an-app-in-your-personal-account)" and "[Installing an app in your organization](/articles/installing-an-app-in-your-organization)."{% endif %} -Los adjuntos de contenido no se mostrarán para las URL que son parte de un enlace de Markdown. +Content attachments will not be displayed for URLs that are part of a markdown link. -Para obtener más información sobre el desarrollo de una {% data variables.product.prodname_github_app %} que utilice adjuntos de contenido, consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments)". +For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)." -## Cargar activos +## Uploading assets -Puedes cargar activos como imágenes si las arrastras y sueltas, las seleccionas de un buscador de archivos o si las pegas. Puedes cargar activos a las propuestas, solicitudes de cambios, comentarios y archivos `.md` en tu repositorio. +You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and `.md` files in your repository. -## Usar emojis +## Using emoji -Puedes agregar emojis a tu escritura al escribir `:EMOJICODE:`. +You can add emoji to your writing by typing `:EMOJICODE:`. `@octocat :+1: This PR looks great - it's ready to merge! :shipit:` -![Emoji representado](/assets/images/help/writing/emoji-rendered.png) +![Rendered emoji](/assets/images/help/writing/emoji-rendered.png) -Si escribes `:` aparecerá una lista con los emojis sugeridos. La lista filtrará a medida que escribes; por lo tanto, una vez que encuentres el emoji que estás buscando, presiona **Tab** (Tabulador) o **Enter** (Intro) para completar el resultado resaltado. +Typing `:` will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result. -Para encontrar una lista completa de emojis y códigos disponibles, consulta el [listado de emojis](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). -## Párrafos +## Paragraphs -Puedes crear un nuevo párrafo al dejar una línea en blanco entre las líneas de texto. +You can create a new paragraph by leaving a blank line between lines of text. -{% ifversion fpt or ghae-next or ghes > 3.3 or ghec %} -## Notas al pie +{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +## Footnotes -Puedes agregar notas al pie para tu contenido si utilizas esta sintaxis de corchetes: +You can add footnotes to your content by using this bracket syntax: ``` -Esta es una nota al pie sencilla[^1]. +Here is a simple footnote[^1]. A footnote can also have multiple lines[^2]. You can also use words, to fit your writing style more closely[^note]. -[^1]: Mi referencia. +[^1]: My reference. [^2]: Every new line should be prefixed with 2 spaces. This allows you to have a footnote with multiple lines. [^note]: @@ -283,9 +294,9 @@ You can also use words, to fit your writing style more closely[^note]. This footnote also has been made with a different syntax using 4 spaces for new lines. ``` -La nota al pie se verá así: +The footnote will render like this: -![Nota al pie interpretada](/assets/images/site/rendered-footnote.png) +![Rendered footnote](/assets/images/site/rendered-footnote.png) {% tip %} @@ -294,35 +305,35 @@ La nota al pie se verá así: {% endtip %} {% endif %} -## Ocultar el contenido con comentarios +## Hiding content with comments -Puedes decirle a {% data variables.product.product_name %} que oculte el contenido del lenguaje de marcado interpretado colocando el contenido en un comentario de HTML. +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. 
     <!-- This content will not appear in the rendered Markdown -->
    -## Importar formato de Markdown +## Ignoring Markdown formatting -Puedes pedirle a {% data variables.product.product_name %} que ignore (o evada) el formato de Markdown usando `\` antes del carácter de Markdown. +You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character. -`Cambiemos el nombre de \*our-new-project\* a \*our-old-project\*.` +`Let's rename \*our-new-project\* to \*our-old-project\*.` -![Carácter evadido representado](/assets/images/help/writing/escaped-character-rendered.png) +![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png) -Para obtener más información, consulta "[Sintaxis de Markdown" de Daring Fireball](https://daringfireball.net/projects/markdown/syntax#backslash), +For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)." {% ifversion fpt or ghes > 3.2 or ghae-issue-5232 or ghec %} -## Inhabilitar la representación del lenguaje de marcado +## Disabling Markdown rendering {% data reusables.repositories.disabling-markdown-rendering %} {% endif %} -## Leer más +## Further reading -- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) -- "[Acerca de escritura y formato en GitHub](/articles/about-writing-and-formatting-on-github)" -- "[Trabajar con formato avanzado](/articles/working-with-advanced-formatting)" -- "[Dominar Markdown](https://guides.github.com/features/mastering-markdown/)" +- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) +- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)" +- "[Working with advanced formatting](/articles/working-with-advanced-formatting)" +- "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/)" diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md index 8eba3fa1fe..48cb432198 100644 --- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md @@ -1,6 +1,6 @@ --- -title: Trabajar con formato avanzado -intro: 'Los formatos como tablas, resaltado de la sintaxis y enlace automático te permiten organizar la información compleja claramente en tus solicitudes de extracción, propuestas y comentarios.' +title: Working with advanced formatting +intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.' redirect_from: - /articles/working-with-advanced-formatting versions: @@ -10,11 +10,12 @@ versions: ghec: '*' children: - /organizing-information-with-tables + - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet - /using-keywords-in-issues-and-pull-requests -shortTitle: Trabajar con formato avanzado +shortTitle: Work with advanced formatting --- diff --git a/translations/es-ES/content/graphql/guides/index.md b/translations/es-ES/content/graphql/guides/index.md index 3b109b788d..7311e5cf39 100644 --- a/translations/es-ES/content/graphql/guides/index.md +++ b/translations/es-ES/content/graphql/guides/index.md @@ -1,6 +1,6 @@ --- -title: Guías -intro: 'Aprende sobre como emepzar con GraphQL, migrarte desde REST hacia GraphQL, y cómo utilizar la API de GraphQL de GitHub para tareas diversas.' +title: Guides +intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.' redirect_from: - /v4/guides versions: @@ -18,5 +18,6 @@ children: - /using-the-explorer - /managing-enterprise-accounts - /using-the-graphql-api-for-discussions + - /migrating-graphql-global-node-ids --- diff --git a/translations/es-ES/content/graphql/overview/breaking-changes.md b/translations/es-ES/content/graphql/overview/breaking-changes.md index f57c660b95..80fdc34c11 100644 --- a/translations/es-ES/content/graphql/overview/breaking-changes.md +++ b/translations/es-ES/content/graphql/overview/breaking-changes.md @@ -1,6 +1,6 @@ --- -title: Cambios sustanciales -intro: 'Aprende sobre los cambios sustanciales recientes y venideros a la API de GraphQL de {% data variables.product.prodname_dotcom %}.' +title: Breaking changes +intro: 'Learn about recent and upcoming breaking changes to the {% data variables.product.prodname_dotcom %} GraphQL API.' redirect_from: - /v4/breaking_changes versions: @@ -12,27 +12,27 @@ topics: - API --- -## Acerca de los cambios sustanciales +## About breaking changes -Los cambios sustanciales son aquellos que pudieran necesitar que nuestros integradores realicen alguna acción al respecto. Dividimos estos cambios en dos categorías: +Breaking changes are any changes that might require action from our integrators. We divide these changes into two categories: - - **Sustanciales:** Cambios que modificarán consultas existentes a la API de GraphQL. Por ejemplo, eliminar un campo sería un cambio sustancial. - - **Peligrosos:** Cambios que no modificaran las consultas existentes, pero podrían afectar el comportamiento del tiempo de ejecución de los clientes. Agregar un valor de enumerador es un ejemplo de un cambio peligroso. + - **Breaking:** Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change. + - **Dangerous:** Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change. -Nos esforzamos por proporcionar API estables para nuestros integradores. Cuando alguna característica nueva está evolucionando aún, la lanzamos detrás de una [vista previa del modelo](/graphql/overview/schema-previews). +We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a [schema preview](/graphql/overview/schema-previews). -Anunciaremos los cambios sustanciales por venir por lo menos tres meses antes de aplicarlos al modelo de GraphQL, para proporcionar a los integradores tiempo para realizar los ajustes necesarios. Los cambios toman efecto en el primer día de un trimestre (1 de enero, 1 de abril, 1 de julio, o 1 de octubre). Por ejemplo, si anunciamos un cambio en el 15 de enero, se aplicará en el 1 de julio. +We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st. {% for date in graphql.upcomingChangesForCurrentVersion %} -## Cambios programados para {{ date[0] }} +## Changes scheduled for {{ date[0] }} {% for change in date[1] %}
      -
    • {% if change.criticality == 'breaking' %}Sustancial{% else %}Peligroso{% endif %}Se hará un cambio a {{ change.location }}. +
    • {% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %} A change will be made to {{ change.location }}. -

      Descripción: {{ change.description }}

      +

      Description: {{ change.description }}

      -

      Razón:{{ change.reason }}

      +

      Reason: {{ change.reason }}

    diff --git a/translations/es-ES/content/index.md b/translations/es-ES/content/index.md index 339c148a59..f861c24f86 100644 --- a/translations/es-ES/content/index.md +++ b/translations/es-ES/content/index.md @@ -1,17 +1,17 @@ --- -title: '{% data variables.product.product_name %}{% ifversion fpt or ghec%}.com{% endif %} Documentación de Ayuda' +title: '{% data variables.product.product_name %}{% ifversion fpt or ghec%}.com{% endif %} Help Documentation' featuredLinks: gettingStarted: - - /github/getting-started-with-github/set-up-git + - /get-started/quickstart/set-up-git - /github/authenticating-to-github/connecting-to-github-with-ssh - /repositories/creating-and-managing-repositories - /github/writing-on-github/basic-writing-and-formatting-syntax popular: - - /github/collaborating-with-issues-and-pull-requests/about-pull-requests - - /github/authenticating-to-github + - /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests + - /authentication - /github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line - - /github/getting-started-with-github/managing-remote-repositories - - /github/working-with-github-pages + - /get-started/getting-started-with-git/managing-remote-repositories + - /pages versions: '*' children: - get-started @@ -23,6 +23,7 @@ children: - billing - organizations - code-security + - pull-requests - issues - actions - codespaces @@ -41,55 +42,56 @@ children: - early-access childGroups: - name: Get started - octicon: RocketIcon + octicon: 'RocketIcon' children: - - get-started - - account-and-profile - - authentication - - billing + - get-started + - account-and-profile + - authentication + - billing - name: Collaborative coding - octicon: CommentDiscussionIcon + octicon: 'CommentDiscussionIcon' children: - - codespaces - - repositories - - discussions + - codespaces + - repositories + - pull-requests + - discussions - name: CI/CD and DevOps - octicon: GearIcon + octicon: 'GearIcon' children: - - actions - - packages - - pages + - actions + - packages + - pages - name: Security - octicon: ShieldLockIcon + octicon: 'ShieldLockIcon' children: - - code-security + - code-security - name: Client apps - octicon: DeviceMobileIcon + octicon: 'DeviceMobileIcon' children: - - github-cli - - desktop + - github-cli + - desktop - name: Project management - octicon: ProjectIcon + octicon: 'ProjectIcon' children: - - issues - - search-github + - issues + - search-github - name: Developers - octicon: MarkGithubIcon + octicon: 'MarkGithubIcon' children: - - developers - - rest - - graphql + - developers + - rest + - graphql - name: Enterprise and Teams - octicon: OrganizationIcon + octicon: 'OrganizationIcon' children: - - organizations - - admin + - organizations + - admin - name: Community - octicon: GlobeIcon + octicon: 'GlobeIcon' children: - - communities - - sponsors - - education + - communities + - sponsors + - education externalProducts: atom: id: atom @@ -112,4 +114,3 @@ externalProducts: href: 'https://docs.npmjs.com/' external: true --- - diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md index 904f850b70..117c5eadfc 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md @@ -1,6 +1,6 @@ --- -title: Acerca de las listas de tareas -intro: Puedes utilizar listas de tareas para desglosar el trabajo de una propuesta o solicitud de cambios en tareas más pequeñas y luego rastrear el conjunto de trabajos completo hasta que se finalicen. +title: About task lists +intro: 'You can use task lists to break the work for an issue or pull request into smaller tasks, then track the full set of work to completion.' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-task-lists - /articles/about-task-lists @@ -19,50 +19,56 @@ topics: {% ifversion fpt or ghec %} {% note %} -**Nota:** Las listas de tareas mejoradas se encuentran actualmente en beta y están sujetas a cambios. +**Note:** Improved task lists are currently in beta and subject to change. {% endnote %} {% endif %} -## Acerca de las listas de tareas +## About task lists -Una lista de tareas es un conjunto de tareas que se interpretan independientemente en una lína separada con una casilla de verificación seleccionable. Puedes seleccionar o deseleccionar estas casillas de verificación para marcar las tareas como completas o incompletas. +A task list is a set of tasks that each render on a separate line with a clickable checkbox. You can select or deselect the checkboxes to mark the tasks as complete or incomplete. -Puedes utilizar el lenguaje de marcado para crear una lista de tareas en cualquier comentario en {% data variables.product.product_name %}. {% ifversion fpt or ghec %}Si referencias una propuesta, solicitud de cambios o debate en una lista de tareas, la referencia se desplegará para mostrar le título y el estado.{% endif %} +You can use Markdown to create a task list in any comment on {% data variables.product.product_name %}. {% ifversion fpt or ghec %}If you reference an issue, pull request, or discussion in a task list, the reference will unfurl to show the title and state.{% endif %} -{% ifversion not fpt or ghec %} -Puedes ver la información del resúmen de la lista de tareas en las listas de una propuesta y una solicitud de extracción, cuando la lista de tareas está en el comentario inicial. +{% ifversion not fpt or ghec %} +You can view task list summary information in issue and pull request lists, when the task list is in the initial comment. {% else %} -## Acerca de las listas de tareas para propuestas +## About issue task lists -Si agregas una lista al cuerpo de una tarea, esta tendrá una funcionalidad agregada. +If you add a task list to the body of an issue, the list has added functionality. -- Para ayudarte a rastrear el trabajo de tu equipo en una propueta, el rpogreso de una lista de tareas de dicha propuesta aparecerá en varios lugares en {% data variables.product.product_name %}, tal como la lista de propuesta de un repositorio. -- Si una tarea referencia otra propuesta y alguien cierra dicha propuesta, la casilla de verificación de la tarea se marcará como completa automáticamente. -- Si se requiere más rastreo o debate, puedes convertir la tarea en una propuesta si deslizas el puntero del mouse sobre la tarea y haces clic en {% octicon "issue-opened" aria-label="The issue opened icon" %} en la esquina superior derecha de la misma. Para agregar más detalles antes de crear la propuesta, puedes utilizar los atajos de teclado para abrir un formato de propuesta nuevo. Para obtener más información, consulta "[Atajos del teclado](/github/getting-started-with-github/using-github/keyboard-shortcuts#issues-and-pull-requests)". -- Cualquier propuesta que se referencia en la lista de tareas especificará que se rastrean en la propuesta de referencia. +- To help you track your team's work on an issue, the progress of an issue's task list appears in various places on {% data variables.product.product_name %}, such as a repository's list of issues. +- If a task references another issue and someone closes that issue, the task's checkbox will automatically be marked as complete. +- If a task requires further tracking or discussion, you can convert the task to an issue by hovering over the task and clicking {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. To add more details before creating the issue, you can use keyboard shortcuts to open the new issue form. For more information, see "[Keyboard shortcuts](/github/getting-started-with-github/using-github/keyboard-shortcuts#issues-and-pull-requests)." +- Any issues referenced in the task list will specify that they are tracked in the referencing issue. -![Lista de tareas generada](/assets/images/help/writing/task-list-rendered.png) +![Rendered task list](/assets/images/help/writing/task-list-rendered.png) {% endif %} -## Crear listas de tareas +## Creating task lists {% data reusables.repositories.task-list-markdown %} -## Volver a ordenar tareas +## Reordering tasks -Puedes reordenar los elementos en una lista de tareas si haces clic a la izquierda de la casilla de verificación de la tarea, arrastrándola a una ubicación nueva y soltándola. Puedes reordenar las tareas a lo largo de listas diferentes en el mismo comentario, pero no puedes volver a ordenar las tareas a lo largo de comentarios diferentes. +You can reorder the items in a task list by clicking to the left of a task's checkbox, dragging the task to a new location, and dropping the task. You can reorder tasks across different lists in the same comment, but you can not reorder tasks across different comments. -![Volver a ordenar lista de tareas](/assets/images/help/writing/task-list-reordered.gif) +{% ifversion fpt %} ![Reordered task list](/assets/images/help/writing/task-list-reordered.gif) +{% else %} ![Reordered task list](/assets/images/enterprise/writing/task-lists-reorder.gif) {% endif %} -## Navegar en las propuestas rastreadas +{% ifversion fpt %} -Cualquier propuesta que se referencie en una lista de tareas especificará que se rastrean por la propuesta que contiene la lista de tareas. Para navegar a la propuesta rastreadora desde la propuesta rastreada, haz clic en el número de la propuesta rastreadora en la sección **Rastreándose en** junto al estado de la propuesta. +## Navigating tracked issues -![Ejemplo de rastreado en](/assets/images/help/writing/task_list_tracked.png) +Any issues that are referenced in a task list specify that they are tracked by the issue that contains the task list. To navigate to the tracking issue from the tracked issue, click on the tracking issue number in the **Tracked in** section next to the issue status. -## Leer más +![Tracked in example](/assets/images/help/writing/task_list_tracked.png) -* [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" +{% endif %} + +## Further reading + +* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %} +* "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md index d4ef2deff4..cb346ba181 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,6 +1,6 @@ --- -title: Crear una propuesta -intro: 'Las propuestas pueden crearse de varias formas, así que puedes elegir el método más conveniente para tu flujo de trabajo.' +title: Creating an issue +intro: 'Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.' permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue @@ -27,122 +27,141 @@ topics: - Pull requests - Issues - Project management -shortTitle: Crear un informe de problemas +shortTitle: Create an issue type: how_to --- -Las propuestas se pueden usar para hacer un seguimiento de los errores, mejoras u otras solicitudes. Para obtener más información, consulta "[Acerca de las propuestas](/issues/tracking-your-work-with-issues/about-issues)". +Issues can be used to keep track of bugs, enhancements, or other requests. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)." {% data reusables.repositories.administrators-can-disable-issues %} -## Crear una propuesta desde un repositorio +## Creating an issue from a repository {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} {% data reusables.repositories.new_issue %} -1. Si tu repositorio utiliza plantillas, haz clic en **Iniciar** junto al tipo de propuesta que te gustaría abrir. ![Select the type of issue you want to create](/assets/images/help/issues/issue_template_get_started_button.png)O haz clic en **Abrir una propuesta en blanco** si el tipo de propuesta que te gustaría abrir no se incluye en las opciones disponibles. ![Enlace para abrir una propuesta en blanco](/assets/images/help/issues/blank_issue_link.png) +1. If your repository uses issue templates, click **Get started** next to the type of issue you'd like to open. + ![Select the type of issue you want to create](/assets/images/help/issues/issue_template_get_started_button.png) + Or, click **Open a blank issue** if the type of issue you'd like to open isn't included in the available options. + ![Link to open a blank issue](/assets/images/help/issues/blank_issue_link.png) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -## Crear una propuesta con {% data variables.product.prodname_cli %} +## Creating an issue with {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} Para aprender más sobre el {% data variables.product.prodname_cli %}, consulta la sección "[Acerca del {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -Para crear una propuesta, utiliza el subcomando `gh issue create`. Para omitir los mensajes interactivos, incluye los marcadores `--body` y `--title`. +To create an issue, use the `gh issue create` subcommand. To skip the interactive prompts, include the `--body` and the `--title` flags. ```shell -gh issue create --title "My new issue" --body "Here are more details". +gh issue create --title "My new issue" --body "Here are more details." ``` -También puedes especificar asignados, etiquetas, hitos y proyectos. +You can also specify assignees, labels, milestones, and projects. ```shell -gh issue create --title "My new issue" --body "Here are more details". --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase" +gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase" ``` -## Crear una propuesta desde un comentario +## Creating an issue from a comment -Puedes abrir una propuesta nueva desde un comentario en otra propuesta o solicitud de cambios. Cuando abres un informe de problemas desde un comentario, este informe contiene un fragmento de código que muestra en dónde se hizo el comentario originalmente. +You can open a new issue from a comment in an issue or pull request. When you open an issue from a comment, the issue contains a snippet showing where the comment was originally posted. -1. Navega al comentario desde el cual te gustaría abrir una propuesta. -2. Dentro del comentario, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Botón Kebab en el comentario de la revisión de solicitud de extracción](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png) -3. Haz clic en **Reference in new issue** (Referencia en la propuesta nueva). ![Referencia en el elemento del menú de propuestas nuevas](/assets/images/help/pull_requests/reference-in-new-issue.png) -4. Usa el menú desplegable "Repository" (Repositorio) y selecciona el repositorio donde desees abrir la propuesta. ![Repositorio desplegable para nueva propuesta](/assets/images/help/pull_requests/new-issue-repository.png) -5. Escribe un título descriptivo y un cuerpo para la propuesta. ![Título y cuerpo para la nueva propuesta](/assets/images/help/pull_requests/new-issue-title-and-body.png) -6. Haz clic en **Create issue** (Crear propuesta). ![Botón para crear la nueva propuesta](/assets/images/help/pull_requests/create-issue.png) +1. Navigate to the comment that you would like to open an issue from. +2. In that comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + ![Kebab button in pull request review comment](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png) +3. Click **Reference in new issue**. + ![Reference in new issue menu item](/assets/images/help/pull_requests/reference-in-new-issue.png) +4. Use the "Repository" drop-down menu, and select the repository you want to open the issue in. + ![Repository dropdown for new issue](/assets/images/help/pull_requests/new-issue-repository.png) +5. Type a descriptive title and body for the issue. + ![Title and body for new issue](/assets/images/help/pull_requests/new-issue-title-and-body.png) +6. Click **Create issue**. + ![Button to create new issue](/assets/images/help/pull_requests/create-issue.png) {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -## Crear una propuesta desde el código +## Creating an issue from code -Puedes abrir una nueva propuesta desde una línea específica o líneas de código en un archivo o solicitud de extracción. Cuando abres una propuesta desde el código, la propuesta contiene un fragmento de código que muestra la línea o rango de código que elegiste. Solo puedes abrir una propuesta en el mismo repositorio donde se almacena el código. +You can open a new issue from a specific line or lines of code in a file or pull request. When you open an issue from code, the issue contains a snippet showing the line or range of code you chose. You can only open an issue in the same repository where the code is stored. -![Fragmento de código representado en una propuesta abierta desde el código](/assets/images/help/repository/issue-opened-from-code.png) +![Code snippet rendered in an issue opened from code](/assets/images/help/repository/issue-opened-from-code.png) {% data reusables.repositories.navigate-to-repo %} -1. Ubica el código que deseas hacer referencia en una propuesta: - - Para abrir una propuesta acerca de un código en un archivo, navega hasta el archivo. - - Para abrir una propuesta acerca de un código en una solicitud de extracción, navega hasta la solicitud de extracción y haz clic en {% octicon "diff" aria-label="The file diff icon" %} **Files changed (Archivos modificados)**. Luego, desplázate hasta el archivo que contiene el código que deseas incluir en tu comentario y haz clic en **Ver**. +1. Locate the code you want to reference in an issue: + - To open an issue about code in a file, navigate to the file. + - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**. {% data reusables.repositories.choose-line-or-range %} -4. Hacia la izquierda del rango de código, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. En el menú desplegable, da clic en **Referenciar en nuevo informe de problemas**. ![Menú Kebab con opción para abrir una propuesta nueva desde una línea seleccionada](/assets/images/help/repository/open-new-issue-specific-line.png) +4. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. In the drop-down menu, click **Reference in new issue**. + ![Kebab menu with option to open a new issue from a selected line](/assets/images/help/repository/open-new-issue-specific-line.png) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} {% ifversion fpt or ghec %} -## Crear una propuesta a partir de un debate +## Creating an issue from discussion -Las personas con permiso de clasificación en un repositorio pueden crear una propuesta a partir de un debate. +People with triage permission to a repository can create an issue from a discussion. -Cuando creas una propuesta a partir de un debate, el contenido de la publicación del debate se incluirá automáticamente en el cuerpo de la propuesta y cualquier etiqueta se retendrá. El crear una propuesta a partir de un debate no convertirá el debate en una propuesta ni borrará el debate existente. Para obtener más información sobre los {% data variables.product.prodname_discussions %}, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +When you create an issue from a discussion, the contents of the discussion post will be automatically included in the issue body, and any labels will be retained. Creating an issue from a discussion does not convert the discussion to an issue or delete the existing discussion. For more information about {% data variables.product.prodname_discussions %}, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. En la barra lateral derecha, haz clic en {% octicon "issue-opened" aria-label="The issues icon" %} **Crear propuesta a partir de un debate**. ![Botón para crear una propuesta a partir de un debate](/assets/images/help/discussions/create-issue-from-discussion.jpg) +1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**. + ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} {% endif %} -## Crear una propuesta desde una nota de un tablero de proyecto +## Creating an issue from a project board note -Si utilizas un tablero de proyecto para rastrear y priorizar tu trabajo, puedes convertir las notas del mismo en informes de problemas. Para obtener más información, consulta la sección "[Acerca de los tableros de proyecto](/github/managing-your-work-on-github/about-project-boards)" y "[Agregar notas a un tablero de proyecto](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)". +If you're using a project board to track and prioritize your work, you can convert project board notes to issues. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)" and "[Adding notes to a project board](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)." {% ifversion fpt or ghec %} -## Crear una propuesta desde un elemento de lista de tareas +## Creating an issue from a task list item -Dentro de una propuesta, puedes utilizar las listas de tareas para desglosar el trabajo en tareas más pequeñas y rastrear todo el conjunto del trabajo hasta que se complete. Si se requiere más rastreo o debate, puedes convertir la tarea en una propuesta si deslizas el puntero del mouse sobre la tarea y haces clic en {% octicon "issue-opened" aria-label="The issue opened icon" %} en la esquina superior derecha de la misma. Para obtener más información, consulta "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". +Within an issue, you can use task lists to break work into smaller tasks and track the full set of work to completion. If a task requires further tracking or discussion, you can convert the task to an issue by hovering over the task and clicking {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %} -## Crear una propuesta desde una consulta de URL +## Creating an issue from a URL query -Puedes consultar parámetros para abrir propuestas. Los parámetros de consulta son partes opcionales de una URL que puedes personalizar para compartir una vista de página web específica, como los resultados de filtro de búsqueda o una plantilla de propuestas en {% data variables.product.prodname_dotcom %}. Para crear tus propios parámetros de consulta, debes hacer coincidir el par de clave y valor. +You can use query parameters to open issues. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or an issue template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair. {% tip %} -**Sugerencia:** También puedes crear plantillas de propuestas que se abran con etiquetas, asignatarios y un título de propuesta predeterminados. Para obtener más información, consulta la sección "[Utilizar plantillas para fomentar las propuestas y solicitudes de cambio útiles](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". +**Tip:** You can also create issue templates that open with default labels, assignees, and an issue title. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)." {% endtip %} -Debes tener los permisos adecuados para cualquier acción para usar el parámetro de consulta equivalente. Por ejemplo, debes tener permiso para agregar una etiqueta a una propuesta para usar el parámetro de consulta `labels`. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +You must have the proper permissions for any action to use the equivalent query parameter. For example, you must have permission to add a label to an issue to use the `labels` query parameter. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -Si creas una URL inválida utilizando parámetros de consulta o si no tienes los permisos adecuados, la URL devolverá una página de error `404 Not Found`. Si creas una URL que exceda el límite del servidor, esta devolverá una página de error `414 URI Too Long`. +If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page. -| Parámetro de consulta | Ejemplo | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `título` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` crea una propuesta en la etiqueta "error" y el título "Nuevo informe de error". | -| `cuerpo` | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.` crea una propuesta con el título "New bug report" y el comentario "Describe de problem" en el cuerpo de la misma. | -| `etiquetas` | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug` crea una propuesta con las etiquetas "help wanted" y "bug". | -| `hito` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` crea una propuesta con el hito "probando hitos". | -| `asignatarios` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` crea una propuesta y la asigna a @octocat. | -| `proyectos` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` crea una propuesta con el título "Solución del problema" y la agrega al tablero de proyecto 1 de la organización. | -| `plantilla` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` crea una propuesta con una plantilla en el cuerpo de la propuesta. El parámetro de consulta `template` funciona con plantillas almacenadas en un subdirectorio de `ISSUE_TEMPLATE` dentro de la raíz, el directorio `docs/` o el directorio `.github/` en un repositorio. Para obtener más información, consulta la sección "[Utilizar plantillas para fomentar las propuestas y solicitudes de cambio útiles](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". | +Query parameter | Example +--- | --- +`title` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` creates an issue with the label "bug" and title "New bug report." +`body` | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.` creates an issue with the title "New bug report" and the comment "Describe the problem" in the issue body. +`labels` | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug` creates an issue with the labels "help wanted" and "bug". +`milestone` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` creates an issue with the milestone "testing milestones." +`assignees` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` creates an issue and assigns it to @octocat. +`projects` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` creates an issue with the title "Bug fix" and adds it to the organization's project board 1. +`template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` creates an issue with a template in the issue body. The `template` query parameter works with templates stored in an `ISSUE_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)." -## Leer más +{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %} +## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert -- "[Escribir en GitHub](/github/writing-on-github)" +{% data reusables.code-scanning.beta-alert-tracking-in-issues %} +If you're using issues to track and prioritize your work, you can use issues to track {% data variables.product.prodname_code_scanning %} alerts. +{% data reusables.code-scanning.alert-tracking-link %} + +{% endif %} + +## Further reading + +- "[Writing on GitHub](/github/writing-on-github)" diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index e3e77781c6..40398276a0 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Filtrar y buscar propuestas y solicitudes de cambios -intro: 'Para encontrar información detallada sobre un repositorio en {% data variables.product.product_name %}, puedes filtrar, clasificar y buscar propuestas y solicitudes de cambios que sean relevantes para el repositorio.' +title: Filtering and searching issues and pull requests +intro: 'To find detailed information about a repository on {% data variables.product.product_name %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.' redirect_from: - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees - /articles/filtering-issues-and-pull-requests-by-assignees @@ -41,95 +41,100 @@ versions: topics: - Issues - Pull requests -shortTitle: Filtrar y buscar +shortTitle: Filter and search type: how_to --- {% data reusables.cli.filter-issues-and-pull-requests-tip %} -## Filtrar propuestas y solicitudes de extracción +## Filtering issues and pull requests -Las propuestas y las solicitudes de extracción vienen con un conjunto de filtros predeterminados que puedes aplicar para organizar tus listas. +Issues and pull requests come with a set of default filters you can apply to organize your listings. {% data reusables.search.requested_reviews_search %} -Puedes filtrar propuestas y solicitudes de extracción para buscar: -- Todas las propuestas y solicitudes de extracción abiertas -- Las propuestas y solicitudes de extracción creadas por ti -- Las propuestas y solicitudes de extracción que se te han asignado -- Las propuestas y solicitudes de extracción en las que eres [**@mencionado**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) +You can filter issues and pull requests to find: +- All open issues and pull requests +- Issues and pull requests that you've created +- Issues and pull requests that are assigned to you +- Issues and pull requests where you're [**@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) {% data reusables.cli.filter-issues-and-pull-requests-tip %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} -3. Haz clic en **Filtros** para elegir el tipo de filtro que te interesa. ![Usar el menú desplegable Filtros](/assets/images/help/issues/issues_filter_dropdown.png) +3. Click **Filters** to choose the type of filter you're interested in. + ![Using the Filters drop-down](/assets/images/help/issues/issues_filter_dropdown.png) -## Filtrar propuestas y solicitudes de extracción por asignatarios +## Filtering issues and pull requests by assignees -Una vez que hayas [asignado una propuesta o solicitud de cambios a alguien](/articles/assigning-issues-and-pull-requests-to-other-github-users), puedes encontrar los elementos con base en quién está trabajando en ellos. +Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} -3. En el ángulo superior derecho, selecciona el menú desplegable Asignatario. -4. El menú desplegable Asignatario menciona a todos los usuarios que tienen acceso de escritura a tu repositorio. Haz clic en el nombre de la persona cuyos elementos asignados deseas ver, o haz clic en **No asignado a nadie** para ver qué propuestas no están asignadas. ![Utilizar la pestaña desplegable Asignatarios](/assets/images/help/issues/issues_assignee_dropdown.png) +3. In the upper-right corner, select the Assignee drop-down menu. +4. The Assignee drop-down menu lists everyone who has write access to your repository. Click the name of the person whose assigned items you want to see, or click **Assigned to nobody** to see which issues are unassigned. +![Using the Assignees drop-down tab](/assets/images/help/issues/issues_assignee_dropdown.png) {% tip %} -Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. +To clear your filter selection, click **Clear current search query, filters, and sorts**. {% endtip %} -## Filtrar propuestas y solicitudes de extracción por etiquetas +## Filtering issues and pull requests by labels -Una vez que hayas [aplicado etiquetas a una propuesta o solicitud de cambios](/articles/applying-labels-to-issues-and-pull-requests), puedes encontrar los elementos con base en sus etiquetas. +Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} -4. En la lista de etiquetas, haz clic en una etiqueta para ver las propuestas y solicitudes de extracción a las que se ha aplicado. ![Lista de etiquetas de repositorio](/assets/images/help/issues/labels-page.png) +4. In the list of labels, click a label to see the issues and pull requests that it's been applied to. + ![List of a repository's labels](/assets/images/help/issues/labels-page.png) {% tip %} -**Sugerencia:** Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. +**Tip:** To clear your filter selection, click **Clear current search query, filters, and sorts**. {% endtip %} -## Filtrar solicitudes de extracción por estado de revisión +## Filtering pull requests by review status -Puedes usar filtros para ver en una lista las solicitudes de extracción por estado de revisión y buscar las solicitudes de extracción que has revisado o que otras personas te han pedido que revises. +You can use filters to list pull requests by review status and to find pull requests that you've reviewed or other people have asked you to review. -Puedes filtrar la lista de solicitudes de extracción de un repositorio para buscar: -- Solicitudes de extracción que no han sido [revisadas](/articles/about-pull-request-reviews) todavía -- Solicitudes de extracción que [requieren una revisión](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de que puedan fusionarse -- Solicitudes de extracción que ha aprobado un revisor -- Solicitudes de extracción en las que un revisor ha pedido cambios -- Solicitudes de cambios que revisaste{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -- Solicitudes de cambios que alguien te pidió que revisaras directamente{% endif %} -- Solicitudes de extracción que [alguien te ha pedido a ti que revises o a un equipo del que eres miembro](/articles/requesting-a-pull-request-review) +You can filter a repository's list of pull requests to find: +- Pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet +- Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged +- Pull requests that a reviewer has approved +- Pull requests in which a reviewer has asked for changes +- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +- Pull requests that someone has asked you directly to review{% endif %} +- Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -3. En el ángulo superior derecho, selecciona el menú desplegable Revisiones. ![Menú desplegable Revisiones en el menú de filtros sobre la lista de solicitudes de extracción](/assets/images/help/pull_requests/reviews-filter-dropdown.png) -4. Elige un filtro para buscar todas las solicitudes de extracción con ese estado de filtro. ![Lista de filtros en el menú desplegable Revisiones](/assets/images/help/pull_requests/pr-review-filters.png) +3. In the upper-right corner, select the Reviews drop-down menu. + ![Reviews drop-down menu in the filter menu above the list of pull requests](/assets/images/help/pull_requests/reviews-filter-dropdown.png) +4. Choose a filter to find all of the pull requests with that filter's status. + ![List of filters in the Reviews drop-down menu](/assets/images/help/pull_requests/pr-review-filters.png) -## Utilizar búsqueda para filtrar propuestas y solicitudes de extracción +## Using search to filter issues and pull requests -Puedes utilizar filtros avanzados para buscar propuestas y solicitudes de cambio que cumplan criterios específicos. +You can use advanced filters to search for issues and pull requests that meet specific criteria. -### Buscar propuestas y solicitudes de cambio +### Searching for issues and pull requests {% include tool-switcher %} {% webui %} -La barra de búsqueda de propuestas y solicitudes de extracción te permite definir tus propios filtros personalizados y clasificar por una amplia variedad de criterios. Puedes encontrar la barra de búsqueda en las pestañas **Issues** (Propuestas) y **Pull requests** (Solicitudes de extracción) de cada repositorio y en tus [tableros de Issues (Propuestas) y Pull requests (Solicitudes de extracción)](/articles/viewing-all-of-your-issues-and-pull-requests). +The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/articles/viewing-all-of-your-issues-and-pull-requests). -![La barra de búsqueda de propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) +![The issues and pull requests search bar](/assets/images/help/issues/issues_search_bar.png) {% tip %} -**Sugerencia:** {% data reusables.search.search_issues_and_pull_requests_shortcut %} +**Tip:** {% data reusables.search.search_issues_and_pull_requests_shortcut %} {% endtip %} @@ -139,15 +144,15 @@ La barra de búsqueda de propuestas y solicitudes de extracción te permite defi {% data reusables.cli.cli-learn-more %} -Puedes utilizar el {% data variables.product.prodname_cli %} para buscar propuestas o solicitudes de cambio. Utiliza el subcomando `gh issue list` o `gh pr list` junto con el argumento `--search` y consulta de búsqueda. +You can use the {% data variables.product.prodname_cli %} to search for issues or pull requests. Use the `gh issue list` or `gh pr list` subcommand along with the `--search` argument and a search query. -Por ejemplo, puedes listar, en orden de fecha en la que se creó, todas las propuestas que no tengan asignado a alguien y que tengan la etiqueta `help wanted` o `bug`. +For example, you can list, in order of date created, all issues that have no assignee and that have the label `help wanted` or `bug`. ```shell gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc' ``` -También puedes listar todas las solicitudes de cambio que mencionen al equipo `octo-org/octo-team`. +You can also list all pull requests that mention the `octo-org/octo-team` team. ```shell gh pr list --search "team:octo-org/octo-team" @@ -155,77 +160,78 @@ gh pr list --search "team:octo-org/octo-team" {% endcli %} -### Acerca de los términos de búsqueda +### About search terms -Con los términos de búsqueda de propuestas y solicitudes de extracción, puedes hacer lo siguiente: +With issue and pull request search terms, you can: -- Filtrar propuestas y solicitudes de extracción por autor: `state:open type:issue author:octocat` -- Filtrar propuestas y solicitudes de extracción que involucren, aunque no necesariamente [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) (mencionen), determinadas personas: `state:open type:issue involves:octocat` -- Filtrar propuestas y solicitudes de extracción por asignatario: `state:open type:issue assignee:octocat` -- Filtrar propuestas y solicitudes de extracción por etiqueta: `state:open type:issue label:"bug"` -- Filtra los términos de búsqueda utilizando `-` antes del término: `state:open type:issue -author:octocat` +- Filter issues and pull requests by author: `state:open type:issue author:octocat` +- Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat` +- Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat` +- Filter issues and pull requests by label: `state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} {% tip %} -**Tip:** Puedes filtrar propuestas y solicitudes de cambio por etiqueta utilizando el componente lógico OR o el AND. -- Para filtrar propuestas utilizando el componente lógico OR, utiliza la sintaxis con coma: `label:"bug","wip"`. -- Para filtrar propuestas utilizando el componente lógico AND, utiliza filtros de etiqueta separados: `label:"bug" label:"wip"`. +**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND. +- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. +- To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`. {% endtip %} {% endif %} {% ifversion fpt or ghes or ghae or ghec %} -Para el caso de informes de problemas, también puedes utilizar la búsqueda para: +For issues, you can also use search to: -- Filtrar los informes de problemas enlazados a una solicitud de extracción mediante una referencia de cierre: `linked:pr` +- Filter for issues that are linked to a pull request by a closing reference: `linked:pr` {% endif %} -Para las solicitudes de cambios, también puedes utilizar la búsqueda para: -- Filtrar solicitudes de extracción [en borrador](/articles/about-pull-requests#draft-pull-requests): `is:draft` -- Filtrar solicitudes de extracción que aún no hayan sido [revisadas](/articles/about-pull-request-reviews): `state:open type:pr review:none` -- Filtrar solicitudes de extracción que [requieran una revisión](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de que se puedan fusionar: `state:open type:pr review:required` -- Filtrar solicitudes de extracción que haya aprobado un revisor: `state:open type:pr review:approved` -- Filtrar solicitudes de extracción en las que un revisor haya solicitado cambios: `state:open type:pr review:changes_requested` -- Filtrar solicitudes de extracción por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` -- Filtrar solicitudes de cambios por usuario específico [al que se le solicitó la revisión](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -- Filtrar solicitudes de cambio que alguien te pidió revisar directamente: `state:open type:pr user-review-requested:@me`{% endif %} -- Filtrar solicitudes de extracción por el equipo que se solicita para revisión: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} -- Filtrar por las solicitudes de extracción enlazadas con un informe de problemas que se pudiera cerrar con dicha solicitud: `linked:issue`{% endif %} +For pull requests, you can also use search to: +- Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft` +- Filter pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet: `state:open type:pr review:none` +- Filter pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged: `state:open type:pr review:required` +- Filter pull requests that a reviewer has approved: `state:open type:pr review:approved` +- Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested` +- Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` +- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %} +- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} +- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %} -## Clasificar propuestas y solicitudes de extracción +## Sorting issues and pull requests -Los filtros pueden ser clasificados para ofrecer mejor información durante un período de tiempo específico. +Filters can be sorted to provide better information during a specific time period. -Puedes clasificar cualquier vista filtrada por: +You can sort any filtered view by: -* Las propuestas y solicitudes de extracción creadas más recientemente -* Las propuestas y solicitudes de extracción creadas con mayor antigüedad -* Las propuestas y solicitudes de extracción más comentadas -* Las propuestas y solicitudes de extracción menos comentadas -* Las propuestas y solicitudes de extracción actualizadas más recientemente -* Las propuestas y solicitudes de extracción actualizadas con mayor antigüedad -* La reacción más agregada a las propuestas o solicitudes de cambio +* The newest created issues or pull requests +* The oldest created issues or pull requests +* The most commented issues or pull requests +* The least commented issues or pull requests +* The newest updated issues or pull requests +* The oldest updated issues or pull requests +* The most added reaction on issues or pull requests {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} -1. En el ángulo superior derecho, selecciona el menú desplegable de Clasificación. ![Utilizar la pestaña desplegable de Clasificación](/assets/images/help/issues/issues_sort_dropdown.png) +1. In the upper-right corner, select the Sort drop-down menu. + ![Using the Sort drop-down tab](/assets/images/help/issues/issues_sort_dropdown.png) -Para borrar tu selección de clasificación, haz clic en **Sort** > (Clasificar); **Newest** (Más reciente). +To clear your sort selection, click **Sort** > **Newest**. -## Compartir filtros +## Sharing filters -Cuando filtras o clasificas propuestas y solicitudes de extracción, la URL de tu navegador se actualiza automáticamente para coincidir con la nueva vista. +When you filter or sort issues and pull requests, your browser's URL is automatically updated to match the new view. -Puedes enviar la URL que genera esa propuesta a cualquier usuario, que podrá ver el mismo filtro que tú ves. +You can send the URL that issues generates to any user, and they'll be able to see the same filter view that you see. -Por ejemplo, si filtras propuestas asignadas a Hubot, y clasificas las propuestas abiertas más antiguas, tu URL se actualizaría a algo similar a esto: +For example, if you filter on issues assigned to Hubot, and sort on the oldest open issues, your URL would update to something like the following: ``` /issues?q=state:open+type:issue+assignee:hubot+sort:created-asc ``` -## Leer más +## Further reading -- "[Buscar propuestas y solicitudes de cambio](/articles/searching-issues)"" +- "[Searching issues and pull requests](/articles/searching-issues)"" diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 9fa211eb90..739677adb9 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -1,6 +1,6 @@ --- -title: Vincular una solicitud de cambios a una propuesta -intro: Puedes vincular una solicitud de cambios a una propuesta para mostrar que una solución está en progreso y para cerrar automáticamente la propuesta cuando se fusione la solicitud de cambios. +title: Linking a pull request to an issue +intro: You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when the pull request is merged. redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue - /articles/closing-issues-via-commit-message/ @@ -16,26 +16,25 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Enlace a la solicitud de cambios o propuesta +shortTitle: Link PR to issue --- - {% note %} -**Nota:** Las palabras clave especiales en una descripción de una solicitud de cambios se interpretan cuando la solicitud de cambios apunte a la rama *predeterminada* del repositorio. Sin embargo, si la base de la solicitud es *cualquier otra rama*, entonces estas palabras clave se ignorarán, no se creará ningún enlace, y el fusionar la solicitud no tendrá efecto alguno en las propuestas. **Si quieres vincular una solicitud de cambios con una propuesta utilizando una palabra clave, la solicitud debe estar en la rama predeterminada.** +**Note:** The special keywords in a pull request description are interpreted when the pull request targets the repository's *default* branch. However, if the PR's base is *any other branch*, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. **If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.** {% endnote %} -## Acerca de las propuestas y solicitudes de cambios vinculadas +## About linked issues and pull requests -Puedes enlazar un informe de problemas a una solicitud de extracción {% ifversion fpt or ghes or ghae or ghec %} manualmente o {% endif %}utilizando una palabra clave compatible en la descripción de esta solicitud. +You can link an issue to a pull request {% ifversion fpt or ghes or ghae or ghec %}manually or {% endif %}using a supported keyword in the pull request description. -Cuando enlazas una solicitud de extracción al informe de problemas al que ésta hace referencia, los colaboradores pueden ver si alguien está trabajando en dicho informe. +When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue. -Cuando fusionas una solicitud de cambios que se ha vinculado y se encuentra en la rama predeterminada de un repositorio, su propuesta vinculada se cierra automáticamente. Para obtener más información acerca de la rama predeterminada, consulta la sección "[Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch)". +When you merge a linked pull request into the default branch of a repository, its linked issue is automatically closed. For more information about the default branch, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." -## Vincular una solicitud de cambios a una propuesta utilizando una palabra clave +## Linking a pull request to an issue using a keyword -Puedes vincular una solicitud de cambios con una propuesta si utilizas una palabra clave compatible en la descripción de la solicitud o en un mensaje de confirmación (por favor, considera que la solicitud de cambios debe estar en la rama predeterminada). +You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message (please note that the pull request must be on the default branch). * close * closes @@ -43,37 +42,41 @@ Puedes vincular una solicitud de cambios con una propuesta si utilizas una palab * fix * fixes * fixed -* resolver -* resuelve -* resuelto +* resolve +* resolves +* resolved -La sintaxis para palabras clave de cierre dependerá de si el informe de problemas se encuentra en el mismo repositorio que la solicitud de extracción. +If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request will also close the referenced pull request. -| Informe vinculado | Sintaxis | Ejemplo | -| ------------------------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------- | -| Propuesta en el mismo repositorio | Closes #10 | `Closes #10` | -| Propuesta en un repositorio diferente | *PALABRA CLAVE* *PROPIETARIO*/*Repositorio*#*NÚMERO DE PROPUESTA* | `Fixes octo-org/octo-repo#100` | -| Propuestas múltiples | Utilizar la sintaxis completa para cada informe | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | +The syntax for closing keywords depends on whether the issue is in the same repository as the pull request. -{% ifversion fpt or ghes or ghae or ghec %}Solo las solicitudes de extracción enlazadas manualmente se podrán desenlazar de la misma forma. Para desenlazar un informe de problemas que hayas enlazado previamente utilizando una palabra clave, deberás editar la descripción de la solicitud de extracción y así poder eliminar la palabra clave.{% endif %} +Linked issue | Syntax | Example +--------------- | ------ | ------ +Issue in the same repository | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10` +Issue in a different repository | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` +Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` -También puedes utilizar palabras clave de cierre en un mensaje de confirmación. La propuesta se cerrará cuando fusiones la confirmación en la rama predeterminada, pero la solicitud de cambios que contiene la confirmación no se listará como una solicitud de cambios enlazada. +{% ifversion fpt or ghes or ghae or ghec %}Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.{% endif %} + +You can also use closing keywords in a commit message. The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request. {% ifversion fpt or ghes or ghae or ghec %} -## Vincular una solicitud de cambios manualmente a una propuesta +## Manually linking a pull request to an issue -Cualquiera con permisos de escritura en un repositorio puede enlazar una solicitud de extracción a un problema manualmente. +Anyone with write permissions to a repository can manually link a pull request to an issue. -Puedes enlazar hasta diez informes de problemas a cada solicitud de extracción manualmente. El informe de problemas y la solicitud de extracción deberán encontrarse en el mismo repositorio. +You can manually link up to ten issues to each pull request. The issue and pull request must be in the same repository. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -3. En la lista de solicitudes de extracción, da clic en aquella que quieras enlazar a un informe de problemas. -4. En la barra lateral derecha, da clic en **Propuestas vinculadas**. ![Informes de problemas enlazados en la barra lateral derecha](/assets/images/help/pull_requests/linked-issues.png) -5. Da clic en la propuesta que quieras enlazar a la solicitud de cambios. ![Menú desplegable para enlazar un informe de problemas](/assets/images/help/pull_requests/link-issue-drop-down.png) +3. In the list of pull requests, click the pull request that you'd like to link to an issue. +4. In the right sidebar, click **Linked issues**. + ![Linked issues in the right sidebar](/assets/images/help/pull_requests/linked-issues.png) +5. Click the issue you want to link to the pull request. + ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png) {% endif %} -## Leer más +## Further reading -- "[URL y referencias auto-enlazadas](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" +- "[Autolinked references and URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index f7062c6336..a8af117ca4 100644 --- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -1,6 +1,6 @@ --- -title: Acerca de las organizaciones -intro: Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. +title: About organizations +intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. redirect_from: - /articles/about-organizations - /github/setting-up-and-managing-organizations-and-teams/about-organizations @@ -16,23 +16,23 @@ topics: {% data reusables.organizations.about-organizations %} -{% data reusables.organizations.organizations_include %} +{% data reusables.organizations.organizations_include %} + +{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." {% ifversion fpt or ghec %} -## Organizaciones y cuentas de empresa +## Organizations and enterprise accounts -Las cuentas de empresa le permiten a los propietarios administrar en forma centralizada las políticas y la facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. +Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. -Para las organizaciones que pertenecen a una cuenta de empresa, la facturación se administra en el nivel de cuenta de empresa y los parámetros de facturación no están disponibles en el nivel de organización. Los propietarios de la empresa pueden establecer políticas para todas las organizaciones en la cuenta de empresa o permitirle a los propietarios de la organización establecer las políticas en el nivel de organización. Los propietarios de la organización no pueden cambiar los parámetros implementados para tu organización en el nivel de cuenta de empresa. Si tienes consultas sobre una política o la configuración para tu organización, comunícate con el propietario de tu cuenta de empresa. +For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account. + +{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/creating-an-enterprise-account){% ifversion ghec %}."{% else %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %} {% data reusables.enterprise-accounts.invite-organization %} -{% data reusables.gated-features.enterprise-accounts %} +## Terms of service and data protection for organizations -{% data reusables.organizations.org-ownership-recommendation %} Para obtener más información, consulta la sección "[Mantener la continuidad de propiedad para tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". - -## Términos de servicio y protección de datos para organizaciones - -Una entidad, como una empresa, una organización sin fines de lucro o un grupo, puede aceptar los Términos de servicio estándar o los Términos de servicio corporativos para su organización. Para obtener más información, consulta "[Actualizarse a los Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)". +An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)." {% endif %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md index 1b72f4a248..89c5918d0c 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Administrar los parámetros de seguridad y análisis para tu organización -intro: 'Puedes controlar las características que aseguran y analizan el código en los proyectos de tu organización en {% 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 @@ -13,140 +13,152 @@ versions: topics: - Organizations - Teams -shortTitle: Administrar el análisis & seguridad +shortTitle: Manage security & analysis --- -## Acerca de la administración de los parámetros de seguridad y análisis +## About management of security and analysis settings -{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar los repositorios en tu organización. Puedes administrar las características de seguridad y de análisis para todos los repositorios existentes que los miembros creen en tu organización. {% ifversion fpt or ghec %}Si tienes una licencia para {% data variables.product.prodname_GH_advanced_security %}, entonces también podrás administrar el acceso a estas características. {% data reusables.advanced-security.more-info-ghas %}{% endif %} +{% 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 fpt or 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 %} {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} -## Mostrar la configuración de seguridad y de análisis +## Displaying the security and analysis settings {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} -La página que se muestra te permite habilitar o inhabilitar todas las características de seguridad y de análisis para los repositorios de tu organización. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. -{% ifversion fpt or ghec %}Si tu organización pertenece a una empresa que tiene una licencia para {% data variables.product.prodname_GH_advanced_security %}, la págna también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %} +{% ifversion fpt or 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 ghes > 3.0 %}Si tienes una licencia para {% data variables.product.prodname_GH_advanced_security %}, la página también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %} +{% ifversion ghes > 3.0 %}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 %}La página también contendrá opciones para habilitar e inhabilitar las características de la {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% 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 %} -## Habilitar o inhabilitar una característica para todos los repositorios existentes +## Enabling or disabling a feature for all existing repositories -Puedes habilitar o inhabilitar las características para todos los repositorios. {% ifversion fpt or ghec %}El impacto de tus cambios en los repositorios de tu organización se determina de acuerdo con su visibilidad: +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: -- **Gráfica de dependencias** - Tus cambios solo afectan a repositorios privados porque la característica siempre está habilitada para los repositorios públicos. -- **{% data variables.product.prodname_dependabot_alerts %}** - Tus cambios afectan a todos los repositorios. -- **{% data variables.product.prodname_dependabot_security_updates %}** - Tus cambios afectan a todos los repositorios. -- **{% data variables.product.prodname_GH_advanced_security %}** - Tus cambios afectan únicamente a los repositorios privados, ya que la {% data variables.product.prodname_GH_advanced_security %} y las características relacionadas siempre se encuentran habilitadas para los repositorios públicos. -- **{% data variables.product.prodname_secret_scanning_caps %}** - Tus cambios afectan únicamente a los repositorios privados en donde la {% data variables.product.prodname_GH_advanced_security %} también se encuentra habilitada. El {% data variables.product.prodname_secret_scanning_caps %} siempre se encuentra habilitado para los repositorios públicos.{% endif %} +- **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. +- **{% 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 only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} {% data reusables.advanced-security.note-org-enable-uses-seats %} -1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". -2. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. {% ifversion fpt or ghes > 3.0 or ghec %}El control para "{% data variables.product.prodname_GH_advanced_security %}" se encontrará inhabilitado si no tienes plazas disponibles en tu licencia de {% data variables.product.prodname_GH_advanced_security %}.{% 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 "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% ifversion fpt or ghes > 3.0 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 or ghec %} - ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) {% endif %} - {% ifversion ghes > 3.0 %} - ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png) + {% 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.1 or 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 ghes = 3.0 %} - ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png) + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png) {% endif %} {% ifversion ghae %} - ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + !["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 ghes = 3.0 or ghec %} -3. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. +3. Optionally, enable the feature by default for new repositories in your organization. {% ifversion fpt or ghec %} - ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) {% endif %} {% ifversion ghes = 3.0 %} - ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png) + !["Enable by default" option for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png) {% endif %} {% endif %} {% ifversion fpt or ghes = 3.0 or ghec %} -4. Da clic en **Inhabilitar CARACTERÍSTICA** o en **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios en tu organización. +4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. {% ifversion fpt or ghec %} - ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) {% endif %} {% ifversion ghes = 3.0 %} - ![Botón para inhabilitar o habilitar la característica](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png) + ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png) {% endif %} {% endif %} {% ifversion ghae or ghes > 3.0 %} -3. Haz clic en **Habilitar/Inhabilitar todas** o en **Habilitar/Inhabilitar para los repositorios elegibles** para confirmar el cambio. ![Botón para habilitar característica para todos los repositorios elegibles de la organización](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) +3. 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 o inhabilitar una característica automáticamente cuando se agregan repositorios nuevos +## Enabling or disabling a feature automatically when new repositories are added -1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". -2. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la características, habilita o inhabilitala predeterminadamente para los repositorios nuevos{% ifversion fpt or ghec %} o para todos los repositorios privados{% endif %} de tu organización. +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 "Configure security and analysis features", 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 %} - ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) {% endif %} - {% ifversion ghes > 3.0 %} - ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% ifversion ghes > 3.2 %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + {% endif %} + {% ifversion ghes = 3.1 or ghes = 3.2 %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} {% ifversion ghes = 3.0 %} - ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png) + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png) {% endif %} {% ifversion ghae %} - ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + ![Checkbox for enabling or disabling 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 %} +{% ifversion fpt or ghec or ghes > 3.2 %} -## Permitir que el {% data variables.product.prodname_dependabot %} acceda a las dependencias privadas +## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies -El {% data variables.product.prodname_dependabot %} puede verificar si hay referencias obsoletas de las dependencias en un proyecto y generar automáticamente una solicitud de cambios para actualizarlas. Para hacerlo, el {% data variables.product.prodname_dependabot %} debe tener acceso a todos los archivos de dependencia que sean el objetivo. Habitualmente, las actualizaciones de versión fallarán si una o más dependencias son inaccesibles. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del {% 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)." -Predeterminadamente, el {% data variables.product.prodname_dependabot %} no puede actualizar las dependencias que se ubican en los repositorios o en los registros de paquetes privados. Sin embargo, si una dependencia se encuentra en un repositorio privado de {% data variables.product.prodname_dotcom %} dentro de la misma organización que el proyecto que la utiliza, puedes permitir al {% data variables.product.prodname_dependabot %} actualizar la versión exitosamente si le otorgas acceso al repositorio en el que se hospeda. +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. -Si tu código depende de paquetes en un registro privado, puedes permitir que el {% data variables.product.prodname_dependabot %} actualice las versiones de estas dependencias si configuras esto a nivel del repositorio. Puedes hacer esto si agregas los detalles de autenticación al archivo _dependabot.yml_ para el repositorio. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/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 dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." -Para permitir que el {% data variables.product.prodname_dependabot %} acceda a un repositorio 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. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". -1. Debajo de "Acceso del {% data variables.product.prodname_dependabot %} a repositorios privados", haz clic en **Agregar repositorios privados** o **Agregar repositorios internos y privados**. ![Botón para agregar repositorios](/assets/images/help/organizations/dependabot-private-repository-access.png) -1. Comienza a teclear el nombre del repositorio que quieras permitir. ![El campo de búsqueda del repositorio con el menú desplegable filtrado](/assets/images/help/organizations/dependabot-private-repo-choose.png) -1. Haz clic en el repositorio que quieras 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 eliminar un repositorio de la lista, a la derecha de este, haz clic en {% octicon "x" aria-label="The X icon" %}. ![Botón "X" para eliminar un repositorio](/assets/images/help/organizations/dependabot-private-repository-list.png) +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 fpt or ghes > 3.0 or ghec %} -## Eliminar el acceso a {% data variables.product.prodname_GH_advanced_security %} desde los repositorios individuales de una organización +## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization -Puedes administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} para un repositorio desde su pestaña de "Configuración". Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". Sin embargo, también puedes inhabilitar las características de la {% data variables.product.prodname_GH_advanced_security %} para un reositorio desde la pestaña de "Configuración" de la organización. +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. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". -1. Para encontrar una lista de todos los repositorios de tu organización que tengan habilitada la {% data variables.product.prodname_GH_advanced_security %}, desplázate hasta la sección "repositorios con {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) La tabla lista la cantidad de confirmantes únicos para cada repositorio. Esta es la cantidad de plazas que puedes liberar en tus licencias si eliminas el acceso a {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". -1. Para eliminar el acceso a la {% data variables.product.prodname_GH_advanced_security %} desde un repositorio y liberar plazas que utilice cualquier confirmante y que son únicas en ese repositorio, haz clic en el {% octicon "x" aria-label="X symbol" %} adyacente. -1. En el diálogo de confirmación, da clic en **Eliminar repositorio** para eliminar el acceso a las características de la {% 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 %} -**Nota:** Si eliminas el acceso de un repositorio a la {% data variables.product.prodname_GH_advanced_security %}, deberás comunicarte con el equipo de desarrollo afectado para que sepan que este cambio se hizo apropósito. Esto garantiza que no pierdan tiempo en depurar las ejecuciones fallidas del escaneo 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 %} -## Leer más +## Further reading -- "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)" -- "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)"{% ifversion fpt or ghec %} -- "[Mantener tus dependencias actualizadas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% ifversion not ghae %} -- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Administrar las vulnerabilidades en tus dependencias de proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %} +- "[Securing your repository](/code-security/getting-started/securing-your-repository)" +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% ifversion fpt or ghec %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% ifversion not ghae %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index 0378c03653..669dce5a6d 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Revisar el registro de auditoría para tu organización -intro: 'El registro de auditoría les permite a los administradores de la organización revisar rápidamente las acciones que realizaron los miembros de la organización. Incluye detalles como quién realizó la acción, de qué acción se trata y cuándo se realizó.' +title: Reviewing the audit log for your organization +intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' miniTocMaxHeadingLevel: 3 redirect_from: - /articles/reviewing-the-audit-log-for-your-organization @@ -13,739 +13,741 @@ versions: topics: - Organizations - Teams -shortTitle: Revisar las bitácoras de auditoría +shortTitle: Review audit log --- -## Acceder al registro de auditoría +## Accessing the audit log -La bitácora de auditoría lista los eventos que activan las actividades, los cuales afectan tu organización, dentro de los últimos 90 días. Solo los propietarios pueden acceder al registro de auditoría de una organización. +The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Only owners can access an organization's audit log. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.audit_log.audit_log_sidebar_for_org_admins %} -## Buscar el registro de auditoría +## Searching the audit log {% data reusables.audit_log.audit-log-search %} -### Búsqueda basada en la acción realizada +### Search based on the action performed -Para buscar eventos específicos, utiliza el calificador `action` en tu consulta. Las acciones detalladas en el registro de auditoría se agrupan dentro de las siguientes categorías: +To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: -| Nombre de la categoría | Descripción | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} -| [`cuenta`](#account-category-actions) | Contiene todas las actividades relacionadas con tu cuenta de organización. | -| [`advisory_credit`](#advisory_credit-category-actions) | Contiene todas las actividades relacionadas con darle crédito a un contribuyente por una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | -| [`facturación`](#billing-category-actions) | Contiene todas las actividades relacionadas con la facturación de tu organización. | -| [`business`](#business-category-actions) | Contiene actividades relacionadas con los ajustes de negocios para una empresa. | -| [`codespaces`](#codespaces-category-actions) | Contiene todas las actividades relacionadas con los codespaces de tu organización. | -| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contiene las actividades de configuración a nivel de organización para las alertas del {% data variables.product.prodname_dependabot %} en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | -| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para las alertas del {% data variables.product.prodname_dependabot %} en los repositorios nuevos que se crean en la organización. | -| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_security_updates %} en los repositorios existentes. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". | -| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para las {% data variables.product.prodname_dependabot_security_updates %} para los repositorios nuevos que se crean en ella. | -| [`dependency_graph`](#dependency_graph-category-actions) | Contiene las actividades de configuración a nivel de organización para las gráficas de dependencia de los repositorios. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | -| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para los repositorios nuevos que se crean en ella.{% endif %} -| [`discussion_post`](#discussion_post-category-actions) | Contiene todas las actividades relacionadas con los debates publicados en una página de equipo. | -| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contiene todas las actividades relacionadas con las respuestas a los debates que se publican en una página de equipo.{% ifversion fpt or ghes or ghec %} -| [`empresa`](#enterprise-category-actions) | Contiene las actividades relacionadas con la configuración de la empresa. |{% endif %} -| [`gancho`](#hook-category-actions) | Contiene todas las actividades relacionadas con los webhooks. | -| [`integration_installation_request`](#integration_installation_request-category-actions) | Contiene todas las actividades relacionadas con las solicitudes de los miembros de la organización para que los propietarios aprueben las integraciones para el uso en la organización. | -| [`ip_allow_list`](#ip_allow_list) | Contiene las actividades relacionadas con habilitar o inhabilitar la lista de direcciones IP permitidas para una organización. | -| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contiene las actividades relacionadas con la creación, borrado y edición de una entrada en una lista de direcciones IP permitidas para una organización. | -| [`propuesta`](#issue-category-actions) | Contiene las actividades relacionadas con borrar una propuesta. |{% ifversion fpt or ghec %} -| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}. | -| [`marketplace_listing`](#marketplace_listing-category-actions) | Contiene todas las actividades relacionadas con el listado de apps en {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contiene todas las actividades relacionadas con administrar la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |{% endif %} -| [`org`](#org-category-actions) | Contiene actividades relacionadas con la membrecía organizacional.{% ifversion fpt or ghec %} -| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contiene todas las actividades relacionadas con la autorización de credenciales para su uso con el inicio de sesión único de SAML. {% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contiene todas las actividades relacionadas con las etiquetas predeterminadas para los repositorios de tu organización.{% endif %} -| [`oauth_application`](#oauth_application-category-actions) | Contiene todas las actividades relacionadas con las Apps de OAuth.{% ifversion fpt or ghes > 3.0 or ghec %} -| [`paquetes`](#packages-category-actions) | Contiene todas las actividades relacionadas con el {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %} -| [`payment_method`](#payment_method-category-actions) | Contiene todas las actividades relacionadas con la manera en que tu organización le paga a GitHub.{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Contiene todas las actividades relacionadas con la foto de perfil de tu organización. | -| [`project`](#project-category-actions) | Contiene todas las actividades relacionadas con los tableros de proyecto. | -| [`rama_protegida`](#protected_branch-category-actions) | Contiene todas las actividades relacionadas con las ramas protegidas. | -| [`repo`](#repo-category-actions) | Contiene las actividades relacionadas con los repositorios que le pertenecen a tu organización.{% ifversion fpt or ghec %} -| [`repository_advisory`](#repository_advisory-category-actions) | Contiene actividades a nivel de repositorio relacionadas con las asesorías de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | -| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contiene todas las actividades relacionadas con [habilitar o inhabilitar el uso de datos para un repositorio privado](/articles/about-github-s-use-of-your-data){% endif %}{% ifversion fpt or ghec %} -| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contiene las actividades a nivel de repositorio para habilitar o inhabilitar la gráfica de dependencias para un | -| repositorio {% ifversion fpt or ghec %}privado{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %} | | -| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contiene actividades a nivel de repositorio relacionadas con el escaneo de secretos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contiene todas las actividades relacionadas con [las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts.{% endif %}{% ifversion ghec %} -| [`rol`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %} -| [`secret_scanning`](#secret_scanning-category-actions) | Contiene las actividades de configuración a nivel de organización para el escaneo de secretos en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | -| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para el escane de secretos para los repositorios nuevos que se crean en ella. |{% ifversion fpt or ghec %} -| [`sponsors`](#sponsors-category-actions) | Contiene todas los eventos relacionados con los botones del patrocinador (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} -| [`equipo`](#team-category-actions) | Contiene todas las actividades relacionadas con los equipos en tu organización. | -| [`team_discussions`](#team_discussions-category-actions) | Contiene las actividades relacionadas con administrar los debates de equipos para una organización. | +| Category name | Description +|------------------|-------------------{% ifversion fpt or ghec %} +| [`account`](#account-category-actions) | Contains all activities related to your organization account. +| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. +| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization. +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %} +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %} +| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %} +| [`hook`](#hook-category-actions) | Contains all activities related to webhooks. +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`ip_allow_list`](#ip_allow_list) | Contains activitites related to enabling or disabling the IP allow list for an organization. +| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. +| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% ifversion fpt or ghec %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion fpt or ghec %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion fpt or ghes or ghae or ghec %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes > 3.0 or ghec %} +| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %} +| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. +| [`project`](#project-category-actions) | Contains all activities related to project boards. +| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. +| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %} +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts.{% endif %}{% ifversion ghec %} +| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %} +| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% ifversion fpt or ghec %} +| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} +| [`team`](#team-category-actions) | Contains all activities related to teams in your organization. +| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization. -Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: +You can search for specific sets of actions using these terms. For example: - * `action:team` encuentra todos los eventos agrupados dentro de la categoría de equipo. - * `-action:hook` excluye todos los eventos en la categoría de webhook. + * `action:team` finds all events grouped within the team category. + * `-action:hook` excludes all events in the webhook category. -Cada categoría tiene un conjunto de acciones asociadas que puedes filtrar. Por ejemplo: +Each category has a set of associated actions that you can filter on. For example: - * `action:team.create` encuentra todos los eventos donde se creó un equipo. - * `-action:hook.events_changed` excluye todos los eventos en que se modificaron los eventos sobre un webhook. + * `action:team.create` finds all events where a team was created. + * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. -### Búsqueda basada en el momento de la acción +### Search based on time of action -Utiliza el calificador `created` para filtrar los eventos en la bitácora de auditoría con base en su fecha de ocurrencia. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -Por ejemplo: +For example: - * `created:2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014. - * `created:>=2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014 o después. - * `created:<=2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014 o antes. - * `created:2014-07-01..2014-07-31` encuentra todos los eventos ocurridos en el mes de julio de 2014. + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. -El registro de auditoría contiene datos de los últimos 90 días, pero puedes utilizar el calificador `created` para buscar eventos anteriores a ese momento. -### Búsqueda basada en la ubicación +{% note %} -Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora de auditoría con base en el país en donde se originaron. Puedes utilizar un código corto de dos letras del país o el nombre completo. Ten presente que los países con espacios en sus nombres se deben poner entre comillas. Por ejemplo: +**Note**: The audit log contains data for the current month and every day of the previous six months. - * `country:de` encuentra todos los eventos ocurridos en Alemania. - * `country:Mexico` encuentra todos los eventos ocurridos en México. - * `country:"United States"` encuentra todos los eventos que ocurrieron en Estados Unidos. +{% endnote %} + +### Search based on location + +Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example: + + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. {% ifversion fpt or ghec %} -## Exportar el registro de auditoría +## Exporting the audit log {% data reusables.audit_log.export-log %} {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -## Utilizar la API de bitácoras de auditoría +## Using the audit log API -Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{% ifversion fpt or ghec %} o la API de REST{% endif %}. +You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}. {% ifversion fpt or ghec %} The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} -### Utilizar la API de GraphQL +### Using the GraphQL API {% endif %} {% note %} -**Nota**: La API de bitácora de auditoría de GraphQL está disponible para las organizaciones que utilizan {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} +**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} {% endnote %} -Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu organización, puedes utilizar la API de GraphQL para bitácoras de auditoría para mantener copias de tus datos de bitácoras de auditoría y monitorear: +To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: {% data reusables.audit_log.audit-log-api-info %} {% ifversion fpt or ghec %} -Ten en cuenta que no puedes recuperar los eventos de Git utilizando la API de GraphQL. Para recuperar eventos de Git, utiliza mejor la API de REST. Para obtener más información, consulta las "[acciones de la categoría `git`](#git-category-actions)". +Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)." {% endif %} -La respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. +The GraphQL response can include data for up to 90 to 120 days. -Por ejemplo, puedes hacer una solicitud de GraphQL para ver todos los miembros nuevos de la organización agregados a tu organización. Para obtener más información, consulta la "[Bitácora de Auditoría de la API de GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)". +For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)." {% ifversion fpt or ghec %} -### Utilizar la API de REST +### Using the REST API {% note %} -**Nota:** La API de REST de la bitácora de auditoría se encuentra disponible únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. {% endnote %} -Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu organización, puedes utilizar la API de REST de bitácoras de auditoría para mantener copias de tus bitácoras de auditoría y monitorear: +To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: {% data reusables.audit_log.audited-data-list %} {% data reusables.audit_log.audit-log-git-events-retention %} -Para obtener más información sobre la API de REST del log de auditoría, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)". +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." {% endif %} -## Acciones de la bitácora de auditoría +## Audit log actions -Un resumen de algunas de las acciones más comunes que se registran como eventos en la bitácora de auditoría. +An overview of some of the most common actions that are recorded as events in the audit log. {% ifversion fpt or ghec %} -### Acciones de la categoría `account` +### `account` category actions -| Acción | Descripción | -| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `billing_plan_change (cambio del plan de facturación)` | Se activa cuando cambia el [ciclo de facturación](/articles/changing-the-duration-of-your-billing-cycle) de una organización. | -| `plan_change (cambio de plan)` | Se activa cuando cambia la [suscripción](/articles/about-billing-for-github-accounts) de una organización. | -| `pending_plan_change (cambio de plan pendiente)` | Se activa cuando un propietario de la organización o gerente de facturación [cancela o baja de categoría una suscripción paga](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | -| `pending_subscription_change (cambio de suscripción pendiente)` | Se activa cuando comienza o se vence una [{% data variables.product.prodname_marketplace %} prueba gratuita](/articles/about-billing-for-github-marketplace/). | +| Action | Description +|------------------|------------------- +| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes. +| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes. +| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). +| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). {% endif %} {% ifversion fpt or ghec %} -### Acciones de la categoría `advisory_credit` +### `advisory_credit` category actions -| Acción | Descripción | -| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `accept` | Se activa cuando alguien acepta el crédito de una asesoría de seguridad. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory)". | -| `create (crear)` | Se activa cuando el administrador de una asesoría de seguridad agrega a alguien a la sección de crédito. | -| `decline` | Se activa cuando alguien rechaza el crédito para una asesoría de seguridad. | -| `destroy (destruir)` | Se activa cuando el administrador de una asesoría de seguridad elimina a alguien de la sección de crédito. | +| Action | Description +|------------------|------------------- +| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." +| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. +| `decline` | Triggered when someone declines credit for a security advisory. +| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. {% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `billing` +### `billing` category actions -| Acción | Descripción | -| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `change_billing_type (cambiar tipo de facturación)` | Se activa cuando tu organización [cambia la manera en que paga {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). | -| `change_email (cambiar correo electrónico)` | Se activa cuando cambia la [dirección de correo electrónico de facturación](/articles/setting-your-billing-email) de tu organización. | +| Action | Description +|------------------|------------------- +| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). +| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. {% endif %} -### Acciones de la categoría `business` +### `business` category actions -| Acción | Descripción | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Se activa cuando el ajuste para solicitar aprobaciones para los flujos de trabajo desde las bifurcaciones públicas se cambia en una empresa. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %} -| `set_actions_retention_limit` | Se activa cuando el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %} se cambian en una empresa. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | Se activa cuando se cambia la política de flujos de trabajo sobre las bifurcaciones de repositorios privados. For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %} +| Action | Description +|------------------|-------------------{% ifversion fpt or ghec %} +| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %} +| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} +| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `codespaces` +### `codespaces` category actions -| Acción | Descripción | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando un usuario [crea un codespace](/github/developing-online-with-codespaces/creating-a-codespace). | -| `resume` | Se activa cuando un usuario reanuda un codesapce suspendido. | -| `delete` | Se activa cuando un usuario [borra un codespace](/github/developing-online-with-codespaces/deleting-a-codespace). | -| `create_an_org_secret` | Se activ cuando un usuario crea un [secreto para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel de la organización | -| `update_an_org_secret` | Se activa cuando un usuario actualiza un [secreto para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional. | -| `remove_an_org_secret` | Se activa cuando un usuario elimina un [secreto para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional. | -| `manage_access_and_security` | Se activa cuando un usuario actualiza [a cuáles repositorios puede acceder un codespace](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace). +| `resume` | Triggered when a user resumes a suspended codespace. +| `delete` | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace). +| `create_an_org_secret` | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) +| `update_an_org_secret` | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). +| `remove_an_org_secret` | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). +| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). +{% endif %} + +{% ifversion fpt or ghec or ghes > 3.2 %} +### `dependabot_alerts` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. + +### `dependabot_alerts_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. + +### `dependabot_security_updates` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. + +### `dependabot_security_updates_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. {% endif %} {% ifversion fpt or ghec %} -### Acciones de la categoría `dependabot_alerts` +### `dependency_graph` category actions -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `inhabilitar` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | -| `habilitar` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories. + +### `dependency_graph_new_repos` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. {% endif %} -{% ifversion fpt or ghec %} -### Acciones de la categoría `dependabot_alerts_new_repos` +### `discussion_post` category actions -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | -| `habilitar` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. | +| Action | Description +|------------------|------------------- +| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). +| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). -### Acciones de la categoría `dependabot_security_updates` +### `discussion_post_reply` category actions -| Acción | Descripción | -| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | -| `habilitar` | Se activa cuando un propietario de organización habilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios existentes. | - -### Acciones de la categoría `dependabot_security_updates_new_repos` - -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | -| `habilitar` | Se activa cuando un propietario de la organización habilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios nuevos. | -{% endif %} - -{% ifversion fpt or ghec %} -### Acciones de la categoría `dependency_graph` - -| Acción | Descripción | -| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita la gráfica de dependencias para todos los repositorios existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | -| `habilitar` | Se activa cuando un propietario de la organización habilita la gráfica de dependencias para todos los repositorios existentes. | - -### Acciones de la categoría `dependency_graph_new_repos` - -| Acción | Descripción | -| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita la gráfica de dependencias para todos los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | -| `habilitar` | Se activa cuando un propietario de la organización habilita la gráfica de dependencias para todos los repositorios nuevos. | -{% endif %} - -### acciones de la categoría `discussion_post` - -| Acción | Descripción | -| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `actualización` | Se activa cuando se edita [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). | -| `destroy (destruir)` | Se activa cuando se elimina [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). | - -### acciones de la categoría `discussion_post_reply` - -| Acción | Descripción | -| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| `actualización` | Se activa cuando se edita [una respuesta a una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). | -| `destroy (destruir)` | Se activa cuando se elimina [una respuesta a una publicación de debate de equipo](/articles/managing-disruptive-comments/#deleting-a-comment). | +| Action | Description +|------------------|------------------- +| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). +| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). {% ifversion fpt or ghes or ghec %} -### acciones de la categoría `enterprise` +### `enterprise` category actions {% data reusables.actions.actions-audit-events-for-enterprise %} {% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `environment` +### `environment` category actions -| Acción | Descripción | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create_actions_secret` | Se activa cuando se crea un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | -| `delete` | Se activa cuando se borra un ambiente. Para obtener más información, consulta la sección "[Borrar un ambiente](/actions/reference/environments#deleting-an-environment)". | -| `remove_actions_secret` | Se activa cuando se elimina a un secreto de un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | -| `update_actions_secret` | Se activa cuando se actualiza a un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +| Action | Description +|------------------|------------------- +| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." +| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." +| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." +| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." {% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `git` +### `git` category actions {% note %} -**Nota:** Para acceder a los eventos de Git en la bitácora de auditoría, debes utilizar la API de la bitácora de auditoría de REST. La API de REST de la bitácora de auditoría se encuentra disponible únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)". +**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." {% endnote %} {% data reusables.audit_log.audit-log-git-events-retention %} -| Acción | Descripción | -| ----------- | -------------------------------------------------------- | -| `clon` | Se activa cuando se clona un repositorio. | -| `recuperar` | Se activa cuando se recuperan cambios de un repositorio. | -| `subir` | Se activa cuando se suben cambios a un repositorio. | +| Action | Description +|---------|---------------------------- +| `clone` | Triggered when a repository is cloned. +| `fetch` | Triggered when changes are fetched from a repository. +| `push` | Triggered when changes are pushed to a repository. {% endif %} -### acciones de la categoría `hook` +### `hook` category actions -| Acción | Descripción | -| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando [se agregó un enlace nuevo](/articles/creating-webhooks)a un repositorio que le pertenece a tu organización. | -| `config_changed (configuración modificada)` | Se activa cuando se modifica la configuración de un enlace existente. | -| `destroy (destruir)` | Se activa cuando se eliminó un enlace existente de un repositorio. | -| `events_changed (eventos modificados)` | Se activa cuando se modificaron los eventos en un enlace. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization. +| `config_changed` | Triggered when an existing hook has its configuration altered. +| `destroy` | Triggered when an existing hook was removed from a repository. +| `events_changed` | Triggered when the events on a hook have been altered. -### Acciones de la categoría`integration_installation_request` +### `integration_installation_request` category actions -| Acción | Descripción | -| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando un miembro de la organización solicita que un propietario de la organización instale una integración para utilizar en la organización. | -| `close` | Se activa cuando un propietario de la organización aprueba o rechaza una solicitud para instalar una integración para que se utilice en una organización, o cuando la cancela el miembro de la organización que abrió la solicitud. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. +| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. ### `ip_allow_list` category actions -| Acción | Descripción | -| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| `habilitar` | Se activa cuando se habilita una lista de direcciones IP permitidas para una organización. | -| `inhabilitar` | Se activa cuando se inhabilita una lista de direcciones IP permitidas para una organización. | -| `enable_for_installed_apps` | Se activa cuando una lista de IP permitidas se habilitó para las {% data variables.product.prodname_github_apps %} instaladas. | -| `disable_for_installed_apps` | Se activa cuando se inhabilitó una lista de direcciones IP permitidas para las {% data variables.product.prodname_github_apps %} instaladas. | +| Action | Description +|------------------|------------------- +| `enable` | Triggered when an IP allow list was enabled for an organization. +| `disable` | Triggered when an IP allow list was disabled for an organization. +| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. +| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. -### Acciones de la categoría `ip_allow_list_entry` +### `ip_allow_list_entry` category actions -| Acción | Descripción | -| -------------------- | --------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando una dirección IP se agregó a una lista de direcciones IP permitidas. | -| `actualización` | Se activa cuando una dirección IP o su descripción se cambió. | -| `destroy (destruir)` | Se activa cuando una dirección IP se eliminó de una lista de direcciones IP permitidas. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when an IP address was added to an IP allow list. +| `update` | Triggered when an IP address or its description was changed. +| `destroy` | Triggered when an IP address was deleted from an IP allow list. -### acciones de la categoría `issue` +### `issue` category actions -| Acción | Descripción | -| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `destroy (destruir)` | Se activa cuando un propietario de la organización o alguna persona con permisos de administrador en un repositorio elimina una propuesta de un repositorio que le pertenece a la organización. | +| Action | Description +|------------------|------------------- +| `destroy` | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository. {% ifversion fpt or ghec %} -### acciones de la categoría `marketplace_agreement_signature` +### `marketplace_agreement_signature` category actions -| Acción | Descripción | -| ---------------- | ----------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando firmas el {% data variables.product.prodname_marketplace %} Acuerdo del programador. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. -### acciones de la categoría `marketplace_listing` +### `marketplace_listing` category actions -| Acción | Descripción | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `aprobar` | Se activa cuando se aprueba tu lista para ser incluida en {% data variables.product.prodname_marketplace %}. | -| `create (crear)` | Se activa cuando creas una lista para tu app en {% data variables.product.prodname_marketplace %}. | -| `delist (quitar de la lista)` | Se activa cuando se elimina tu lista de {% data variables.product.prodname_marketplace %}. | -| `redraft` | Se activa cuando tu lista se vuelve a colocar en estado de borrador. | -| `reject (rechazar)` | Se activa cuando no se acepta la inclusión de tu lista en {% data variables.product.prodname_marketplace %}. | +| Action | Description +|------------------|------------------- +| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. +| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. +| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. +| `redraft` | Triggered when your listing is sent back to draft state. +| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. {% endif %} {% ifversion fpt or ghes > 3.0 or ghec %} -### Acciones de la categoría `members_can_create_pages` +### `members_can_create_pages` category actions -Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". +For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." -| Acción | Descripción | -|:------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `habilitar` | Se activa cuando el propietario de una organización habilita la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. | -| `inhabilitar` | Se activa cuando el propietario de una organización inhabilita la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. | +| Action | Description | +| :- | :- | +| `enable` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | +| `disable` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | {% endif %} -### acciones de la categoría `org` +### `org` category actions -| Acción | Descripción | -| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member (agregar miembro)` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -| `advanced_security_policy_selected_member_disabled` | Se activa cuando un propietario de empresa previene que las carcaterísticas de la {% data variables.product.prodname_GH_advanced_security %} se habiliten para los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %} -| `advanced_security_policy_selected_member_enabled` | Se activa cuando un propietario de empresa permite que se habiliten las características de la {% data variables.product.prodname_GH_advanced_security %} en los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %} -| `audit_log_export` | Se activa cuando un administrador de la organización [crea una exportación del registro de auditoría de la organización](#exporting-the-audit-log). Si la exportación incluía una consulta, el registro detallará la consulta utilizada y la cantidad de entradas en el registro de auditoría que coinciden con esa consulta. | -| `block_user` | Se activa cuando un propietario de la organización [bloquea a un usuario para que no pueda acceder a los repositorios de la organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). | -| `cancel_invitation` | Se activa cuando se revocó una invitación de la organización. |{% endif %}{% ifversion fpt or ghes or ghec %} -| `create_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se crea para una organización. Para obtener más información, consulta la sección "[Crear secretos cifrados para una organización](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)".{% endif %} |{% ifversion fpt or ghec %} -| `disable_oauth_app_restrictions` | Se activa cuando un propietario [inhabilita {% data variables.product.prodname_oauth_app %} restricciones de acceso](/articles/disabling-oauth-app-access-restrictions-for-your-organization) para tu organización. | -| `disable_saml` | Se activa cuando un administrador de la organización inhabilita el inicio de sesión único de SAML para una organización{% endif %} -| `disable_member_team_creation_permission` | Se activa cuando un propietario de la organización limita la creación de equipos para los propietarios. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} -| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} -| `enable_oauth_app_restrictions` | Se activa cuando un propietario [habilita restricciones de acceso de {% data variables.product.prodname_oauth_app %} ](/articles/enabling-oauth-app-access-restrictions-for-your-organization) para tu organización. | -| `enable_saml` | Se activa cuando un administrador de la organización [habilita el inicio de sesión único de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para una organización.{% endif %} -| `enable_member_team_creation_permission` | Se activa cuando un propietario de la organización permite que los miembros creen equipos. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} -| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} -| `invite_member` | Se activa cuando [se invitó a un usuario nuevo a unirse a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). | -| `oauth_app_access_approved` | Se activa cuando un propietario [le otorga acceso a la organización a una {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). | -| `oauth_app_access_denied` | Se activa cuando un propietario [inhabilita un acceso de {% data variables.product.prodname_oauth_app %} anteriormente aprobado](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) para tu organización. | -| `oauth_app_access_requested` | Se activa cuando un miembro de la organización solicita que un propietario otorgue un acceso de {% data variables.product.prodname_oauth_app %} para tu organización.{% endif %} -| `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | -| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt or ghec %} -| `remove_billing_manager` | Se activa cuando un [propietario elimina un gerente de facturación de una organización](/articles/removing-a-billing-manager-from-your-organization/) o cuando [se requiere autenticación de dos factores en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no usa la 2FA o inhabilita la 2FA. -{% endif %} -| `remove_member (eliminar miembro)` | Se activa cuando un [propietario elimina a un miembro de una organización](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. También se activa cuando un [miembro de la organización se elimina a sí mismo](/articles/removing-yourself-from-an-organization/) de una organización. | -| `remove_outside_collaborator` | Se activa cuando un propietario elimina a un colaborador externo de una organización{% ifversion not ghae %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no utiliza la 2FA o la inhabilita{% endif %}. | -| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)". |{% ifversion fpt or ghec %} -| `revoke_external_identity` | Se actuva cuando un dueño de una organización retira la identidad vinculada de un mimebro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". | -| `revoke_sso_session` | Se activa cuando el dueño de una organización retira la sesión de SAML de un miembro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". |{% endif %} -| `runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | -| `runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | -| `runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". | -| `runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección [Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | -| `runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %} -| `self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} -| `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Se activa cuando se cambia el ajuste para requerir aprobaciones para los flujos de trabajo desde las bifurcaciones públicas en una organización. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."{% endif %} -| `set_actions_retention_limit` | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | Se activa cuando se cambia la política de flujos de trabajo sobre las bifurcaciones de repositorios privados. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."{% endif %}{% ifversion fpt or ghec %} -| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %} -| `update_actions_secret` | Se activa cuando se actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %} -| `update_new_repository_default_branch_setting` | Se activa cuando el propietario cambia el nombre de la rama predeterminada para los repositorios nuevos de la organización. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." | -| `update_default_repository_permission` | Se activa cuando un propietario cambia el nivel de permiso al repositorio predeterminado para los miembros de la organización. | -| `update_member` | Se activa cuando un propietario cambia el rol de una persona de propietario a miembro o de miembro a propietario. | -| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% ifversion fpt or ghec %} -| `update_saml_provider_settings` | Se activa cuando se actualizan las configuraciones del proveedor SAML de una organización. | -| `update_terms_of_service` | Se activa cuando una organización cambia de los Términos de servicio estándar a los Términos de servicio corporativos. Para obtener más información, consulta "[Subir de categoría a Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".{% endif %} +| Action | Description +|------------------|------------------- +| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %} +| `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. +| `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). +| `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% ifversion fpt or ghes or ghec %} +| `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} {% ifversion fpt or ghec %} +| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. +| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} +| `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} +| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} +| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization. +| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %} +| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} +| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} +| `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). +| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). +| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization. +| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %} +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt or ghec %} +| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %} +| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.| +| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. | +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion fpt or ghec %} +| `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." +| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." {% endif %} +| `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." +| `runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." +| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." +| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). +| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." +| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %} +| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." +| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} +| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."{% endif %} +| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} +| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."{% endif %}{% ifversion fpt or ghec %} +| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %} +| `update_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %} +| `update_new_repository_default_branch_setting` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." +| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members. +| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner. +| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% ifversion fpt or ghec %} +| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. +| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `org_credential_authorization` +### `org_credential_authorization` category actions -| Acción | Descripción | -| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `grant` | Se activa cuando un miembro [autoriza credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | -| `deauthorized` | Se activa cuando un miembro [quita la autorización de credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | -| `revoke` | Se activa cuando un propietario [revoca las credenciales autorizadas](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). | +| Action | Description +|------------------|------------------- +| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). +| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). +| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). {% endif %} {% ifversion fpt or ghes or ghae or ghec %} -### Acciones de la categoría `organization_label` +### `organization_label` category actions -| Acción | Descripción | -| -------------------- | ----------------------------------------------------- | -| `create (crear)` | Se activa cuando se crea una etiqueta por defecto. | -| `actualización` | Se activa cuando se edita una etiqueta por defecto. | -| `destroy (destruir)` | Se activa cuando se elimina una etiqueta por defecto. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a default label is created. +| `update` | Triggered when a default label is edited. +| `destroy` | Triggered when a default label is deleted. {% endif %} -### acciones de la categoría `oauth_application` +### `oauth_application` category actions -| Acción | Descripción | -| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | -| `create (crear)` | Se activa cuando se crea una {% data variables.product.prodname_oauth_app %} nueva. | -| `destroy (destruir)` | Se activa cuando se elimina una {% data variables.product.prodname_oauth_app %} existente. | -| `reset_secret (restablecer secreto)` | Se activa cuando se restablece un secreto de cliente de {% data variables.product.prodname_oauth_app %}. | -| `revoke_tokens (revocar tokens)` | Se activa cuando se revocan los tokens de usuario de una {% data variables.product.prodname_oauth_app %}. | -| `transferencia` | Se activa cuando se transfiere una {% data variables.product.prodname_oauth_app %} existente a una organización nueva. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. +| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. +| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. +| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. +| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. {% ifversion fpt or ghes > 3.0 or ghec %} -### Acciones de la categoría `packages` +### `packages` category actions -| Acción | Descripción | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `package_version_published` | Se activa cuando se publica una versión del paquete. | -| `package_version_deleted` | Se activa cuando se borra una versión de paquete específica. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | -| `package_deleted` | Se activa cuando se borra un paquete completo. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | -| `package_version_restored` | Se activa cuando se borra una versión de paquete específica. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | -| `package_restored` | Se activa cuando se restablece un paquete completo. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| Action | Description | +|--------|-------------| +| `package_version_published` | Triggered when a package version is published. | +| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." {% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `payment_method` +### `payment_method` category actions -| Acción | Descripción | -| ------------------ | ------------------------------------------------------------------------------------------------------------- | -| `clear (eliminar)` | Se activa cuando un método de pago archivado se [elimina](/articles/removing-a-payment-method). | -| `create (crear)` | Se activa cuando se agrega un método de pago nuevo, como una tarjeta de crédito nueva o una cuenta de PayPal. | -| `actualización` | Se activa cuando se actualiza un método de pago existente. | +| Action | Description +|------------------|------------------- +| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method). +| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. +| `update` | Triggered when an existing payment method is updated. {% endif %} -### acciones de la categoría `profile_picture` -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------ | -| actualización | Se activa cuando estableces o actualizas la foto de perfil de tu organización. | +### `profile_picture` category actions +| Action | Description +|------------------|------------------- +| update | Triggered when you set or update your organization's profile picture. -### acciones de la categoría `project` +### `project` category actions -| Acción | Descripción | -| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create (crear)` | Se activa cuando se crear un tablero de proyecto. | -| `link` | Se activa cuando un repositorio se vincula a un tablero de proyecto. | -| `rename (renombrar)` | Se activa cuando se renombra un tablero de proyecto. | -| `actualización` | Se activa cuando se actualiza un tablero de proyecto. | -| `delete` | Se activa cuando se elimina un tablero de proyecto. | -| `unlink (desvincular)` | Se activa cuando se anula el enlace a un repositorio desde un tablero de proyecto. | -| `update_org_permission (actualizar permiso de la organización)` | Se activa cuando se cambia o elimina el permiso al nivel de base para todos los miembros de la organización. | -| `update_team_permission (actualizar permiso del equipo)` | Se activa cuando se cambia el nivel de permiso del tablero de proyecto de un equipo o cuando se agrega un equipo a un tablero de proyecto o se elimina de este. | -| `update_user_permission` | Se activa cuando un miembro de la organización o colaborador externo se agrega a un tablero de proyecto o se elimina de este, o cuando se le cambia su nivel de permiso. | +| Action | Description +|--------------------|--------------------- +| `create` | Triggered when a project board is created. +| `link` | Triggered when a repository is linked to a project board. +| `rename` | Triggered when a project board is renamed. +| `update` | Triggered when a project board is updated. +| `delete` | Triggered when a project board is deleted. +| `unlink` | Triggered when a repository is unlinked from a project board. +| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. | +| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | +| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.| -### acciones de la categoría `protected_branch` +### `protected_branch` category actions -| Acción | Descripción | -| --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando se habilita la protección de rama en una rama. | -| `destroy (destruir)` | Se activa cuando se inhabilita la protección de rama en una rama. | -| `update_admin_enforced (actualizar administrador aplicado)` | Se activa cuando se aplica la protección de rama para los administradores del repositorio. | -| `update_require_code_owner_review (actualizar requerir revisión del propietario del código)` | Se activa cuando se actualiza en una rama la aplicación de revisión del propietario del código requerida. | -| `dismiss_stale_reviews (descartar revisiones en espera)` | Se activa cuando se actualiza en una rama la aplicación de las solicitudes de extracción en espera descartadas. | -| `update_signature_requirement_enforcement_level (actualizar nivel de aplicación del requisito de firma)` | Se activa cuando se actualiza la aplicación de la firma de confirmación requerida en una rama. | -| `update_pull_request_reviews_enforcement_level (actualizar nivel de aplicación de revisiones de solicitudes de extracción)` | Se activa cuando se actualiza el cumplimiento de las revisiones de solicitudes de extracción requeridas en una rama. | -| `update_required_status_checks_enforcement_level (actualizar nivel de aplicación de verificaciones de estado requeridas)` | Se activa cuando se actualiza en una rama la aplicación de verificaciones de estado requeridas. | -| `update_strict_required_status_checks_policy` | Se activa cuando se cambia el requisito para que una rama se encuentre actualizada antes de la fusión. | -| `rejected_ref_update (actualización de referencia rechazada)` | Se activa cuando se rechaza el intento de actualización de una rama. | -| `policy_override (anulación de política)` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} -| `update_allow_force_pushes_enforcement_level` | Se activa cuando se habilitan o inhabilitan las subidas de información forzadas en una rama protegida. | -| `update_allow_deletions_enforcement_level` | Se activa cuando se habilita o inhabilita el borrado de ramas en una rama protegida. | -| `update_linear_history_requirement_enforcement_level` | Se activa cuando se habilita o inhabilita el historial de confirmaciones linear requerido para una rama protegida. | +| Action | Description +|--------------------|--------------------- +| `create ` | Triggered when branch protection is enabled on a branch. +| `destroy` | Triggered when branch protection is disabled on a branch. +| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators. +| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch. +| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch. +| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch. +| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. +| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. +| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. +| `rejected_ref_update ` | Triggered when a branch update attempt is rejected. +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. +| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. +| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -### Acciones de la categoría `pull_request` +### `pull_request` category actions -| Acción | Descripción | -| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando se crea una solicitud de cambios. | -| `close` | Se activa cuando se cierra una solicitud de cambios sin haberse fusionado. | -| `reopen` | Se activa cuando se vuelve a abrir una solicitud de cambios después de haberse cerrado previamente. | -| `fusionar` | Se activa cuando se fusiona una solicitud de cambios. | -| `indirect_merge` | Se activa cuando una solicitud de cambios se considera como fusionada porque sus confirmaciones se fusionaron en la rama destino. | -| `ready_for_review` | Se activa cuando una solicitud de cambios se marca como lista para revisión. | -| `converted_to_draft` | Se activa cuando una solicitud de cambios se convierte en borrador. | -| `create_review_request` | Se activa cuando se solicita una revisión. | -| `remove_review_request` | Se activa cuando se elimina una solicitud de revisión. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a pull request is created. +| `close` | Triggered when a pull request is closed without being merged. +| `reopen` | Triggered when a pull request is reopened after previously being closed. +| `merge` | Triggered when a pull request is merged. +| `indirect_merge` | Triggered when a pull request is considered merged because its commits were merged into the target branch. +| `ready_for_review` | Triggered when a pull request is marked as ready for review. +| `converted_to_draft` | Triggered when a pull request is converted to a draft. +| `create_review_request` | Triggered when a review is requested. +| `remove_review_request` | Triggered when a review request is removed. -### Acciones de la categoría `pull_request_review` +### `pull_request_review` category actions -| Acción | Descripción | -| ----------- | ------------------------------------------ | -| `enviar` | Se activa cuando se envía una revisión. | -| `descartar` | Se activa cuando se descarta una revisión. | -| `delete` | Se activa cuando se borra una revisión. | +| Action | Description +|------------------|------------------- +| `submit` | Triggered when a review is submitted. +| `dismiss` | Triggered when a review is dismissed. +| `delete` | Triggered when a review is deleted. -### Acciones de la categoría `pull_request_review_comment` +### `pull_request_review_comment` category actions -| Acción | Descripción | -| ---------------- | ----------------------------------------------------- | -| `create (crear)` | Se activa cuando se agrega un comentario de revisión. | -| `actualización` | Se activa cuando se cambia un comentario de revisión. | -| `delete` | Se activa cuando se borra un comentario de revisión. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a review comment is added. +| `update` | Triggered when a review comment is changed. +| `delete` | Triggered when a review comment is deleted. {% endif %} -### acciones de la categoría `repo` +### `repo` category actions -| Acción | Descripción | -| --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `access (acceder)` | Se activa cuando un usuario [cambia la visibilidad](/github/administering-a-repository/setting-repository-visibility) de un repositorio en la organización. | -| `actions_enabled` | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no se incluye cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". | -| `add_member (agregar miembro)` | Se activa cuando un usuario acepta una [invitación para tener acceso de colaboración a un repositorio](/articles/inviting-collaborators-to-a-personal-repository). | -| `add_topic (agregar tema)` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -| `advanced_security_disabled` | Se activa cuando un adminsitrador de repositorio inhabilita las características de {% data variables.product.prodname_GH_advanced_security %} en este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". | -| `advanced_security_enabled` | Se activa cuando un administrador de repositorio habilita las características de la {% data variables.product.prodname_GH_advanced_security %} para este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} -| `archived (archivado)` | Se activa cuando un administrador del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% ifversion ghes %} -| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | -| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)` | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | -| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)` | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | -| `config.unlock_anonymous_git_access (configurar desbloquear acceso de git anónimo)` | Se activa cuando se desbloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| `create (crear)` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %} -| `create_actions_secret` | Se crea cuando un secreto de {% data variables.product.prodname_actions %} se crea para un repositorio. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".{% endif %} -| `destroy (destruir)` | Se activa cuando [se elimina un repositorio](/articles/deleting-a-repository).{% ifversion fpt or ghec %} -| `inhabilitar` | Se activa cuando se inhabilita un repositorio (p. ej., por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %} -| `habilitar` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes or ghec %} -| `remove_actions_secret` | Se activa cuando se elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %} -| `remove_member (eliminar miembro)` | Se activa cuando un usuario se [elimina de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository). | -| `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | -| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | -| `remove_topic (eliminar tema)` | Se activa cuando un administrador del repositorio elimina un tema de un repositorio. | -| `rename (renombrar)` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %} -| `self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} -| `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Se activa cuando se cambia la configuración para requerir aprobaciones para los flujos de trabajo de las bifurcaciones públicas. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %} -| `set_actions_retention_limit` | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | Se activa cuando se cambia la política para flujos de trabajo en las bifurcaciones de los repositorios privados. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %} -| `transferencia` | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository). | -| `transfer_start (comienzo de transferencia)` | Se activa cuando está por ocurrir una transferencia de repositorio. | -| `unarchived (desarchivado)` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes or ghec %} -| `update_actions_secret` | Se activa cuando se actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %} +| Action | Description +|------------------|------------------- +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. +| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." +| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".{% endif %} +| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %} +| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). +| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %} +| `create_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} +| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %} +| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %} +| `enable` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes or ghec %} +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %} +| `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." +| `remove_topic` | Triggered when a repository admin removes a topic from a repository. +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %} +| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." +| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} +| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %} +| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %} +| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). +| `transfer_start` | Triggered when a repository transfer is about to occur. +| `unarchived` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes or ghec %} +| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %} {% ifversion fpt or ghec %} -### acciones de la categoría `repository_advisory` +### `repository_advisory` category actions -| Acción | Descripción | -| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `close` | Se activa cuando alguien cierra una asesoría de seguridad. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | -| `cve_request` | Se activa cuando alguien solicita un número de CVE (Vulnerabilidades y Exposiciones Comunes) de {% data variables.product.prodname_dotcom %} para un borrador de asesoría de seguridad. | -| `github_broadcast` | Se activa cuando {% data variables.product.prodname_dotcom %} hace pública una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. | -| `github_withdraw` | Se activa cuando {% data variables.product.prodname_dotcom %} retira una asesoría de seguridad que se publicó por error. | -| `open` | Se activa cuando alguien abre un borrador de asesoría de seguridad. | -| `publish` | Se activa cuando alguien publica una asesoría de seguridad. | -| `reopen` | Se activa cuando alguien vuelve a abrir un borrador de asesoría de seguridad. | -| `actualización` | Se activa cuando alguien edita un borrador de asesoría de seguridad o una asesoría de seguridad publicada. | +| Action | Description +|------------------|------------------- +| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. +| `open` | Triggered when someone opens a draft security advisory. +| `publish` | Triggered when someone publishes a security advisory. +| `reopen` | Triggered when someone reopens as draft security advisory. +| `update` | Triggered when someone edits a draft or published security advisory. -### Acciones de la categoría `repository_content_analysis` +### `repository_content_analysis` category actions -| Acción | Descripción | -| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `habilitar` | Se activa cuando un propietario de la organización o persona con acceso administrativo al repositorio [habilita la configuración de uso de datos para un repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | -| `inhabilitar` | Se habilita cuando un propietario de la organización o una persona con acceso administrativo en el repositorio [inhabilita la configuración de uso de datos para un repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | +| Action | Description +|------------------|------------------- +| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). +| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). {% endif %}{% ifversion fpt or ghec %} -### Acciones de la categoría `repository_dependency_graph` +### `repository_dependency_graph` category actions -| Acción | Descripción | -| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | -| `habilitar` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. {% endif %} -### Acciones de la categoría `repository_secret_scanning` +### `repository_secret_scanning` category actions -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `inhabilitar` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | -| `habilitar` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -### acciones de la categoría `repository_vulnerability_alert` +### `repository_vulnerability_alert` category actions -| Acción | Descripción | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Triggered when {% data variables.product.product_name %} creates a {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | -| `descartar` | Triggered when an organization owner or person with admin access to the repository dismisses a {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. | -| `resolver` | Se activa cuando alguien con acceso de escritura en un repositorio sube cambios para actualizar y resolver una vulnerabilidad en una dependencia de proyecto. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when {% data variables.product.product_name %} creates a {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. +| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. {% endif %}{% ifversion fpt or ghec %} -### acciones de la categoría `repository_vulnerability_alerts` +### `repository_vulnerability_alerts` category actions -| Acción | Descripción | -| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `authorized_users_teams` | Se activa cuando un propietario de la organización o un miembro con permisos de administrador en el repositorio actualiza la lista de personas o equipos autorizados para recibir las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en dicho repositorio. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". | -| `inhabilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este inhabilita las {% data variables.product.prodname_dependabot_alerts %}. | -| `habilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este habilita las {% data variables.product.prodname_dependabot_alerts %}. | +| Action | Description +|------------------|------------------- +| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. +| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}. {% endif %}{% ifversion ghec %} ### `role` category actions -| Acción | Descripción | -| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." | -| `destroy (destruir)` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." | -| `actualización` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." | +| Action | Description +|------------------|------------------- +|`create` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." +|`destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." +|`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." {% endif %} -### Acciones de la categoría `secret_scanning` +### `secret_scanning` category actions -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Triggered when an organization owner disables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | -| `habilitar` | Triggered when an organization owner enables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. -### Acciones de la categoría `secret_scanning_new_repos` +### `secret_scanning_new_repos` category actions -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Triggered when an organization owner disables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | -| `habilitar` | Triggered when an organization owner enables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. {% ifversion fpt or ghec %} -### acciones de la categoría `sponsors` +### `sponsors` category actions -| Acción | Descripción | -| ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `custom_amount_settings_change` | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | -| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)` | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | -| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)` | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)` | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_payment_complete` | Se activa después de que patrocinas una cuenta y se procesa tu pago (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si quieres recibir actualizaciones de una cuenta patrocinada por correo electrónico (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | -| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)` | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | -| `sponsored_developer_approve (aprobación de programador patrocinado)` | Se activa cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_create (creación de programador patrocinado)` | Se activa cuando se crea la cuenta de {% data variables.product.prodname_sponsors %} (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_disable` | Se activa cuando se inhabilita tu cuenta de {% data variables.product.prodname_sponsors %} -| `sponsored_developer_redraft` | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado | -| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Se activa cuando editas tu perfil de organización patrocinada (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | -| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)` | Se activa cuando emites tu solicitud para {% data variables.product.prodname_sponsors %} para su aprobación (consulta la sección "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | -| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)` | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | -| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)` | Se activa cuando te invitan a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `waitlist_join (incorporación a la lista de espera)` | Se activa cuando te unes a la lista de espera para convertirte en una organización patrocinada (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| Action | Description +|------------------|------------------- +| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") +| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") +| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") +| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") +| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") +| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") +| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") +| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled +| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") +| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") {% endif %} -### acciones de la categoría `team` +### `team` category actions -| Acción | Descripción | -| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member (agregar miembro)` | Se activa cuando un miembro de una organización se [agrega a un equipo](/articles/adding-organization-members-to-a-team). | -| `add_repository (agregar repositorio)` | Se activa cuando se le otorga el control de un repositorio a un equipo. | -| `change_parent_team (cambiar equipo padre)` | Se activa cuando se crea un equipo hijo o [se modifica el padre de un equipo hijo](/articles/moving-a-team-in-your-organization-s-hierarchy). | -| `change_privacy (cambiar privacidad)` | Se activa cuando se modifica el nivel de privacidad de un equipo. | -| `create (crear)` | Se activa cuando se crea un equipo nuevo. | -| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." | -| `destroy (destruir)` | Se activa cuando se elimina un equipo de la organización. | -| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." | -| `remove_member (eliminar miembro)` | Se activa cuando un miembro de una organización se [elimina de un equipo](/articles/removing-organization-members-from-a-team). | -| `remove_repository (eliminar repositorio)` | Se activa cuando un repositorio deja de estar bajo el control de un equipo. | +| Action | Description +|------------------|------------------- +| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). +| `add_repository` | Triggered when a team is given control of a repository. +| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). +| `change_privacy` | Triggered when a team's privacy level is changed. +| `create` | Triggered when a new team is created. +| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." +| `destroy` | Triggered when a team is deleted from the organization. +| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." +| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). +| `remove_repository` | Triggered when a repository is no longer under a team's control. -### acciones de la categoría `team_discussions` +### `team_discussions` category actions -| Acción | Descripción | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita los debates de equipo para una organización. Para obtener más información, consulta "[Desactivar los debates del equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)". | -| `habilitar` | Se activa cuando un propietario de la organización habilita los debates de equipo para una organización. | +| Action | Description +|---|---| +| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." +| `enable` | Triggered when an organization owner enables team discussions for an organization. -### Acciones de la categoría `workflows` +### `workflows` category actions {% data reusables.actions.actions-audit-events-workflow %} -## Leer más +## Further reading -- "[Mantener segura tu organización](/articles/keeping-your-organization-secure)" +- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %} +- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index fd29987bf2..3ea8d68c5d 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Agregar colaboradores externos a los repositorios en tu organización -intro: Un *colaborador externo* es una persona que no es explícitamente un miembro en tu organización pero tiene premisos de lectura. +title: Adding outside collaborators to repositories in your organization +intro: 'An *outside collaborator* is a person who isn''t explicitly a member of your organization, but who has Read, Write, or Admin permissions to one or more repositories in your organization.' redirect_from: - /articles/adding-outside-collaborators-to-repositories-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization @@ -12,36 +12,46 @@ versions: topics: - Organizations - Teams -shortTitle: Agregar un colaborador externo +shortTitle: Add outside collaborator +permissions: People with admin access to a repository can add an outside collaborator to the repository. --- -## Acerca de los colaboradores externos - -{% data reusables.organizations.owners-and-admins-can %} agregar colaboradores externos a un repositorio, a menos que un propietario de la organización haya restringido la capacidad para invitar colaboradores. Para obtener más información, consulta "[Establecer permisos para agregar colaboradores externos](/articles/setting-permissions-for-adding-outside-collaborators)". +## About outside collaborators {% data reusables.organizations.outside-collaborators-use-seats %} +An organization owner can restrict the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/articles/setting-permissions-for-adding-outside-collaborators)." + +{% ifversion ghes %} +Before you can add someone as an outside collaborator on a repository, the person must have a user account on {% data variables.product.product_location %}. If your enterprise uses an external authentication system such as SAML or LDAP, the person you want to add must sign in through that system to create an account. If the person does not have access to the authentication system and built-in authentication is enabled for your enterprise, a site admin can create a user account for the person. For more information, see "[Using built-in authentication](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication#inviting-users)." +{% endif %} + {% ifversion not ghae %} -Si tu organización [requiere miembros y colaboradores externos para usar la autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), deben habilitar la autenticación de dos factores antes de que puedan aceptar tu invitación para colaborar en el repositorio de una organización. +If your organization [requires members and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), they must enable two-factor authentication before they can accept your invitation to collaborate on an organization repository. {% endif %} {% data reusables.organizations.outside_collaborator_forks %} {% ifversion fpt %} -Para apoyar aún más las capacidades de colaboración de tu equipo, puedes mejorar a {% data variables.product.prodname_ghe_cloud %}, el cual incluye características como las ramas protegidas y los propietarios de código en los repositorios privados. {% data reusables.enterprise.link-to-ghec-trial %} +To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} -## Agregar colaboradores externos a un repositorio +## Adding outside collaborators to a repository {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% ifversion fpt or ghec %} {% data reusables.repositories.navigate-to-manage-access %} {% data reusables.organizations.invite-teams-or-people %} -5. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Debajo de "Selecciona un rol", selecciona los permisos que quieres otorgar a la persona, luego da clic en **"Añadir NOMBRE a REPOSITORIO**. ![Seleccionar los permisos para la persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches. + ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Under "Choose a role", select the permissions to grant to the person, then click **Add NAME to REPOSITORY**. + ![Selecting permissions for the person](/assets/images/help/repository/manage-access-invite-choose-role-add.png) {% else %} -5. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). ![Barra lateral de configuraciones del repositorio con Colaboradores y equipos resaltados](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) -6. En "Collaborators" (Colaboradores), escribe el nombre de la persona a la que te gustaría brindar acceso al repositorio, luego haz clic en **Add collaborator** (Agregar colaborador). ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/repository/org-repo-collaborators-find-name.png) -7. Junto al nombre del colaborador, escribe el nivel de permiso correspondiente: *Write* (Escritura) *Read* (Lectura) o *Admin* (Administración). ![El recolector de permisos del repositorio](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +5. In the left sidebar, click **Collaborators & teams**. + ![Repository settings sidebar with Collaborators & teams highlighted](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**. +![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. Next to the new collaborator's name, choose the appropriate permission level: *Write*, *Read*, or *Admin*. +![The repository permissions picker](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) {% endif %} diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 4fd1f65b35..22b6b0342e 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -23,11 +23,11 @@ shortTitle: Repository roles You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need. From least access to most access, the roles for an organization repository are: -- **Lectura**: Recomendado para los contribuyentes sin código que quieren ver tu proyecto u opinar sobre él -- **Prueba**: Recomendado para los contribuyentes que necesiten administrar propuestas y solicitudes de extracción de manera proactiva sin acceso de escritura -- **Escritura**: Recomendado para los contribuyentes que suben contenido a tu proyecto de manera activa -- **Mantenimiento (beta)**: Recomendado para los gerentes del proyecto que necesiten administrar el repositorio sin acceder a las acciones confidenciales o destructivas -- **Administrador**: Recomendado para las personas que necesitan acceso total al proyecto, incluidas las acciones conflictivas y destructivas, como gestionar la seguridad o eliminar un repositorio +- **Read**: Recommended for non-code contributors who want to view or discuss your project +- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access +- **Write**: Recommended for contributors who actively push to your project +- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions +- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository {% ifversion fpt %} If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation. @@ -35,22 +35,22 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c You can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." {% endif %} -Los dueños de las organizaciones pueden configurar permisos base que apliquen a todos los miembros de la misma cuando accedan a cualquiera de los repositorios que le pertenezcan a dicha organización. Para obtener más información, consulta la sección "[Configurar los permisos base para una organización](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)". +Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." -Los propietarios de la organización también pueden decidir limitar más el acceso a determinados parámetros y acciones de la organización. Para obtener más información sobre las opciones de parámetros específicos, consulta "[Administrar los parámetros de la organización](/articles/managing-organization-settings)". +Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)." In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% warning %} -**Advertencia:** Cuando una persona agrega una llave de implementación a un repositorio, cualquier usuario que tenga la llave privada puede leer o escribir en el repositorio (según los parámetros de la llave), incluso si luego es eliminada de la organización. +**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization. {% endwarning %} ## Permissions for each role {% ifversion fpt %} -Algunas de las características que se listan a continuación se limitan a las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} {% ifversion fpt or ghes or ghec %} @@ -59,133 +59,118 @@ Algunas de las características que se listan a continuación se limitan a las o **Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below. {% endnote %} +{% endif %} -{% endif %} -| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:---------:|:-------------:|:-------------------------------------------------------------:| -| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** | -| Extraer desde los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | -| Bifurcar los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | -| Editar y eliminar sus propios comentarios | **X** | **X** | **X** | **X** | **X** | -| Abrir propuestas | **X** | **X** | **X** | **X** | **X** | -| Cerrar propuestas que ellos mismos abrieron | **X** | **X** | **X** | **X** | **X** | -| Reabrir propuestas que ellos mismos cerraron | **X** | **X** | **X** | **X** | **X** | -| Recibir la asignación de una propuesta | **X** | **X** | **X** | **X** | **X** | -| Enviar solicitudes de extracción desde las bifurcaciones de los repositorios asignados del equipo | **X** | **X** | **X** | **X** | **X** | -| Enviar revisiones sobre solicitudes de extracción | **X** | **X** | **X** | **X** | **X** | -| Ver los lanzamientos publicados | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| Ver las [Ejecuciones de flujo de trabajo de GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** -{% endif %} -| Editar los wikis en los repositorios públicos | **X** | **X** | **X** | **X** | **X** | -| Editar los wikis en los repositorios privados | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [Informar contenido abusivo o de spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** -{% endif %} -| Aplicar/descartar etiquetas | | **X** | **X** | **X** | **X** | -| Crear, editar, borrar etiquetas | | | **X** | **X** | **X** | -| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %} -| [Habilitar e inhabilitar la fusión automática en una solicitud de cambios](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** -{% endif %} -| Aplicar hitos | | **X** | **X** | **X** | **X** | -| Marcar [duplicar propuestas y solicitudes de extracción](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Solicitar [revisiones de solicitudes de extracción](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Fusionar una [solicitud de cambios](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Subir a (escribir en) los repositorios asignados de la persona o el equipo | | | **X** | **X** | **X** | -| Editar y eliminar comentarios o confirmaciones, solicitudes de extracción y propuestas de cualquier persona | | | **X** | **X** | **X** | -| [Ocultar los comentarios de cualquier persona](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transferir propuestas (consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)" para obtener detalles) | | | **X** | **X** | **X** | -| [Actuar como propietario del código designado para un repositorio](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Marcar un borrador de solicitud de extracción como listo para revisión](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Enviar revisiones que afecten la capacidad de fusión de una solicitud de extracción | | | **X** | **X** | **X** | -| [Aplicar cambios sugeridos](/articles/incorporating-feedback-in-your-pull-request) a las solicitudes de extracción | | | **X** | **X** | **X** | -| Crear [comprobaciones de estado](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| Crear, editar, ejecutar, volver a ejecutar y cancelar [Flujos de trabajo de Acciones de GitHub](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** -{% endif %} -| Crear y editar lanzamientos | | | **X** | **X** | **X** | -| Ver lanzamientos en borrador | | | **X** | **X** | **X** | -| Editar la descripción de un repositorio | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [Ver e instalar paquetes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publicar paquetes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 or ghec %}[Borrar y restablecer paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Borrar paquetes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| Administrar [temas](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Habilitar wikis y restringir editores de wikis | | | | **X** | **X** | -| Habilitar tableros de proyecto | | | | **X** | **X** | -| Configurar las [fusiones de la solicitud de extracción](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configurar [una fuente de publicaciones para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Subir a ramas protegidas](/articles/about-protected-branches) | | | | **X** | **X** | -| [Crear y editar las tarjetas sociales del repositorio](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| Limitar las [interacciones en un repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** -{% endif %} -| Eliminar una propuesta (consulta "[Eliminar una propuesta](/articles/deleting-an-issue)") | | | | | **X** | -| Fusionar solicitudes de extracción en ramas protegidas, incluso si no existen revisiones en aprobación | | | | | **X** | -| [Definir propietarios del código para un repositorio](/articles/about-code-owners) | | | | | **X** | -| Añadir un repositorio a un equipo (consulta la sección "[Administrar el acceso de un equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obtener más detalles) | | | | | **X** | -| [Gestionar el acceso de un colaborador externo a un repositorio](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Cambiar la visibilidad de un repositorio](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)") | | | | | **X** | -| Cambiar los parámetros de un repositorio | | | | | **X** | -| Administrar el acceso de un equipo o colaborador al repositorio | | | | | **X** | -| Editar la rama predeterminada del repositorio | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -| Renombrar la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Renombrar una rama diferente a la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** -{% endif %} -| Administrar webhooks y desplegar llaves | | | | | **X** |{% ifversion fpt or ghec %} -| [Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** -{% endif %} -| [Administrar la política de bifurcación de un repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transferir repositorios a la organización](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Eliminar o transferir repositorios fuera de la organización](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archivar repositorios](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| Mostrar el botón de un patrocinador (consulta "[Mostrar el botón de un patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** -{% endif %} -| Crear referencias de enlace automático a recursos externos, como JIRA o Zendesk (consulta "[Configurar enlaces automáticos para referenciar recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt or ghec %} -| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) en un repositorio | | | | **X** | **X** | -| [Crear y editar categorías](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Mover un debate a una categoría diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transferir un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) a un repositorio nuevo | | | **X** | **X** | **X** | -| [Administrar debates fijados](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Converitr propuestas en debates por lote](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Bloquear y desbloquear los debates](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Convertir las propuestas en debates individualmente](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Crear debates nuevos y comentar sobre los debates existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| Crear [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** -{% endif %} +| Repository action | Read | Triage | Write | Maintain | Admin | +|:---|:---:|:---:|:---:|:---:|:---:| +| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** | +| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | +| Open issues | **X** | **X** | **X** | **X** | **X** | +| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | +| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | +| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | +| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | +| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} +| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| Apply milestones | | **X** | **X** | **X** | **X** | +| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **X** | **X** | **X** | **X** | +| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | +| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Create and edit releases | | | **X** | **X** | **X** | +| View draft releases | | | **X** | **X** | **X** | +| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| {% ifversion fpt or ghes > 3.0 or ghec %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} +| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **X** | **X** |{% endif %} +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | +| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | +| Change a repository's settings | | | | | **X** | +| Manage team and collaborator access to the repository | | | | | **X** | +| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} +| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %} +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt or ghec %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository| | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} +| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %} ### Access requirements for security features In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features. -| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:------------------------------------------------------:|:------------------------------------------------------:|:--------------------------------------------------------------------------------------:| -| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} | | | | | | -| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) en un repositorio | | | | | **X** | -| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designar a personas o equipos adicionales para que reciban alertas de seguridad](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| Crear [asesorías de seguridad](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** -{% endif %} -| Administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} (consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% ifversion fpt or ghec %} -| -| [Habilitar el gráfico de dependencias](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) de un repositorio privado | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -| [Ver las revisiones de las dependencias](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** -{% endif %} -| [Ver las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [Listar, descartar y borrar las alertas del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -| [Ver las alertas del {% data variables.product.prodname_secret_scanning %} en un repositorio](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** | -| [Resolver, revocar o reabrir las alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %} -| [Ver las alertas del {% data variables.product.prodname_secret_scanning %} en un repositorio](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [Resolver, revocar o reabrir las alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| [Designar personas o equipos adicionales para recibir alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) en los repositorios | | | | | **X** -{% endif %} +| Repository action | Read | Triage | Write | Maintain | Admin | +|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% ifversion fpt or ghec %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -[1] Los escritores y mantenedores de los repositorios solo pueden ver la información de las alertas de sus propias confirmaciones. +[1] Repository writers and maintainers can only see alert information for their own commits. {% endif %} -## Leer más +## Further reading -- [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)" -- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" +- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)" +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index b71393b76b..835e187a8a 100644 --- a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -1,6 +1,6 @@ --- -title: Acerca de las autoridades de certificación de SSH -intro: 'Con una autoridad de certificación de SSH, tu cuenta de empresa u organización puede ofrecer certificados SSH que los miembros pueden usar para aceder a tus recursos con Git.' +title: About SSH certificate authorities +intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.' product: '{% data reusables.gated-features.ssh-certificate-authorities %}' redirect_from: - /articles/about-ssh-certificate-authorities @@ -13,39 +13,47 @@ versions: topics: - Organizations - Teams -shortTitle: Autoridades de certificados SSH +shortTitle: SSH certificate authorities --- -Un certificado SSH es un mecanismo para que una clave SSH firme otra clave SSH. Si usas una autoridad de certificación de SSH (CA) para ofrecerle a los miembros de tu organización certificados SSH firmados, puedes agregar la CA a tu cuenta de empresa u organización para permitirle a los miembros de la organización usar sus certificados para acceder a los recursos de la organización. Para obtener más información, consulta [Administrar las autoridades de certificación de SSH de tu organización ](/articles/managing-your-organizations-ssh-certificate-authorities)". +## About SSH certificate authorities -Una vez que agregas una CA de SSH a tu cuenta de empresa u organización, puedes usar la CA para firmar certificados de SSH de clientes para los miembros de la organización. Los miembros de la organización pueden usar los certificados firmados para acceder a los repositorios de tu organización (y solo los repositorios de tu organización) con Git. Puedes solicitar que los miembros usen los certificados de SSH para acceder a los recursos de la organización. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." +An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. -Por ejemplo, puedes crear un sistema interno que emita un nuevo certificado para tus programadores cada mañana. Cada programador puede usar su certificado diario para trabajar en los repositorios de tu organización en {% data variables.product.product_name %}. Al finalizar el día, el certificado puede expirar automáticamente, protegiendo tus repositorios si el certificado más tarde se ve comprometido. +After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." -Members will not be able to use their certificates to access forks of your repositories that are owned by their user accounts. - -Cuando emites cada certificado, debes incluir una extensión que especifique para qué usuario de {% data variables.product.product_name %} es el certificado. Por ejemplo, puedes usar el comando `ssh-keygen` de OpenSSH, reemplazando _KEY-IDENTITY_ por tu identidad de clave y _USERNAME_ por un nombre de usuario de {% data variables.product.product_name %}. El certificado que generes se autorizará para actuar en nombre de ese usuario para cualquiera de los recursos de tu organización. Asegúrate de validar la identidad de los usuarios antes de que emitas el certificado. - -```shell -$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub -``` - -Para emitir un certificado para alguien que utilice SSH para acceder a varios productos de {% data variables.product.company_short %}, puedes incluir dos extensiones de inicio de sesión para especificar el nombre de usuario para cada producto. Por ejemplo, el siguiente comando emitirá un certificado para el _USERNAME-1_ de la cuenta de {% data variables.product.prodname_ghe_cloud %} del usuario, y para el _USERNAME-2_ de la cuenta de {% data variables.product.prodname_ghe_managed %} del usuario o de {% data variables.product.prodname_ghe_server %} en _HOSTNAME_. - -```shell -$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub -``` - -Puedes restringir las direcciones IP desde las que un miembro de la organización puede acceder a los recursos de tu organización usando una extensión `source-address`. La extensión acepta una dirección IP específica o una gama de direcciones IP con la notación CIDR. Puedes especificar múltiples direcciones o rangos separando los valores con comas. Para obtener más información, consulta "[Enrutamiento entre dominios sin clases](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" en Wikipedia. - -```shell -$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub -``` +For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. {% ifversion fpt or ghec %} - -Los miembros de la organización pueden usar sus certificados firmados para la autenticación, incluso si has aplicado el inicio de sesión único de SAML. A menos que hagas que los certificados SSH sean un requisito, los miembros de la organización pueden seguir usando otros medios para la autenticación para acceder a los recursos de tu organización con Git, incluyendo sus nombre de usuario y contraseña, tokens de acceso personales y sus propias claves SSH. - +Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys. {% endif %} -Para evitar errores de autenticación, los miembros de la organización deben usar una URL especial que incluya el ID de la organización para clonar los repositorios mediante certificados firmados. Cualquier persona con acceso de lectura al repositorio puede buscar esta URL en la página del repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". +Members will not be able to use their certificates to access forks of your repositories that are owned by their user accounts. + +To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." + +## Issuing certificates + +When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate. + +```shell +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +{% warning %} + +**Warning**: After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -`V` flag to configure a lifetime for the certificate, or the certificate can be used indefinitely. + +{% endwarning %} + +To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_. + +```shell +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia. + +```shell +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md index 836e20e45f..344036e617 100644 --- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md @@ -1,6 +1,6 @@ --- -title: Administrar la membresía en tu organización -intro: 'Después de crear tu organización, puedes {% ifversion fpt %}invitar a personas para que se conviertan en {% else %}agregar personas como{% endif %} miembros de la organización. También puedes eliminar a miembros de la organización y reinstalar a miembros antiguos.' +title: Managing membership in your organization +intro: 'After you create your organization, you can {% ifversion fpt %}invite people to become{% else %}add people as{% endif %} members of the organization. You can also remove members of the organization, and reinstate former members.' redirect_from: - /articles/removing-a-user-from-your-organization/ - /articles/managing-membership-in-your-organization @@ -19,8 +19,8 @@ children: - /adding-people-to-your-organization - /removing-a-member-from-your-organization - /reinstating-a-former-member-of-your-organization + - /exporting-member-information-for-your-organization - /can-i-create-accounts-for-people-in-my-organization -shortTitle: Administrar la membrecía +shortTitle: Manage membership --- - diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md index 6f341d8684..e59468af96 100644 --- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -1,6 +1,6 @@ --- -title: Invitar a usuarios para que se unan a tu organización -intro: 'Puedes invitar a cualquier persona a que se convierta en miembro de tu organización usando su nombre de usuario o dirección de correo electrónico {% data variables.product.product_name %}.' +title: Inviting users to join your organization +intro: 'You can invite anyone to become a member of your organization using their {% data variables.product.product_name %} username or email address.' permissions: Organization owners can invite users to join an organization. redirect_from: - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ @@ -12,16 +12,18 @@ versions: topics: - Organizations - Teams -shortTitle: Invitar a los usuarios para que se unan +shortTitle: Invite users to join --- -{% tip %} +## About organization invitations -**Tips**: -- Si tu organización tiene una suscripción de pago por usuario, debe de existir una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro para que se una a la organización o antes de reinstaurar a algún miembro previo de la misma. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-scim %} -- Si tu organización requiere que los miembros utilicen autenticación bifactorial, los usuarios que invites deben habilitarla antes de aceptar la invitación. Para obtener más información, consulta las secciones "[Requerir autenticación bifactorial en tu organización](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" y "[Asegurar tu cuenta con la autenticación bifactorial (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". +If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." -{% endtip %} +{% data reusables.organizations.org-invite-scim %} + +If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." + +## Inviting a user to join your organization {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} @@ -34,5 +36,5 @@ shortTitle: Invitar a los usuarios para que se unan {% data reusables.organizations.send-invitation %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -## Leer más -- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" +## Further reading +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index 1c40c758c0..c303abd963 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -1,6 +1,6 @@ --- -title: Convertir una organización en un usuario -intro: 'No es posible convertir una organización en una cuenta de usuario personal, pero puedes crear una nueva cuenta de usuario y transferirle los repositorios de la organización.' +title: Converting an organization into a user +intro: 'It''s not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization''s repositories to it.' redirect_from: - /articles/converting-an-organization-into-a-user - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user @@ -11,25 +11,33 @@ versions: topics: - Organizations - Teams -shortTitle: Convertir la organización en un usuario +shortTitle: Convert organization to user --- {% ifversion fpt or ghec %} -1. [Regístrate](/articles/signing-up-for-a-new-github-account) para una nueva cuenta de usuario de GitHub. -2. [Cambia el rol de usuario a un propietario](/articles/changing-a-person-s-role-to-owner). -3. {% data variables.product.signin_link %} para la nueva cuenta de usuario. -4. [Transfiere cada repositorio de la organización](/articles/how-to-transfer-a-repository) a la nueva cuenta de usuario. -5. [Elimina la organización](/articles/deleting-an-organization-account). -6. [Cambia el nombre del usuario](/articles/changing-your-github-username) por el nombre de la organización. +{% note %} + +**Note**: After an account is deleted, the username at the time of deletion becomes unavailable for reuse for 90 days. To reuse an organization's username immediately, you must change the username before you delete the organization. + + {% endnote %} + +1. [Sign up](/articles/signing-up-for-a-new-github-account) for a new GitHub user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to make the current username available. +6. [Rename the user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to the organization's name. +7. [Delete the organization](/organizations/managing-organization-settings/deleting-an-organization-account). + {% else %} -1. Inicia sesión para una nueva cuenta de usuario de GitHub Enterprise. -2. [Cambia el rol de usuario a un propietario](/articles/changing-a-person-s-role-to-owner). -3. {% data variables.product.signin_link %} para la nueva cuenta de usuario. -4. [Transfiere cada repositorio de la organización](/articles/how-to-transfer-a-repository) a la nueva cuenta de usuario. -5. [Elimina la organización](/articles/deleting-an-organization-account). -6. [Cambia el nombre del usuario](/articles/changing-your-github-username) por el nombre de la organización. +1. Sign up for a new GitHub Enterprise user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Delete the organization](/articles/deleting-an-organization-account). +6. [Rename the user](/articles/changing-your-github-username) to the organization's name. {% endif %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md index c3a41b58cd..661bb8ab17 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Administrar la política de bifurcación para tu organización -intro: 'Puedes permitir o prevenir la bifurcación de cualquier repositorio privado {% ifversion fpt or ghes or ghae or ghec %} e interno{% endif %} que pertenezca a tu organización.' +title: Managing the forking policy for your organization +intro: 'You can allow or prevent the forking of any private{% ifversion fpt or ghes or ghae or ghec %} and internal{% endif %} repositories owned by your organization.' redirect_from: - /articles/allowing-people-to-fork-private-repositories-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization @@ -14,22 +14,23 @@ versions: topics: - Organizations - Teams -shortTitle: Administrar la política de bifurcación +shortTitle: Manage forking policy --- -Predeterminadamente, las organizaciones nuevas se configuran para impedir la bifurcación de repositorios privados{% ifversion fpt or ghes or ghae or ghec %} e internos{% endif %}. +By default, new organizations are configured to disallow the forking of private{% ifversion fpt or ghes or ghae or ghec %} and internal{% endif %} repositories. -Si permites la bifurcación de repositorios privados {% ifversion fpt or ghes or ghae or ghec %} e internos{% endif %} a nivel organizacional, también puedes configurar la capacidad para bifurcar repositorios privados {% ifversion fpt or ghes or ghae or ghec %} o internos{% endif %} específicos. Para obtener más información, consulta la sección "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". +If you allow forking of private{% ifversion fpt or ghes or ghae or ghec %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% ifversion fpt or ghes or ghae or ghec %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% data reusables.organizations.internal-repos-enterprise %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. Debajo de "Bifurcación de repositorios", selecciona **Permitir la bifurcación de repositorios privados** o **Permitir la bifurcación de repositorios privados e internos**. ![Casilla de verificación para permitir o prohibir la bifurcación en la organización](/assets/images/help/repository/allow-disable-forking-organization.png) -6. Haz clic en **Save ** (guardar). +5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**. + ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Click **Save**. -## Leer más +## Further reading -- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md index 2d087af6fc..0af0a54c8d 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -1,6 +1,6 @@ --- -title: Renombrar una organización -intro: 'Si tu proyecto o empresa cambió de nombre, puedes actualizar el nombre de tu organización para que coincida.' +title: Renaming an organization +intro: 'If your project or company has changed names, you can update the name of your organization to match.' redirect_from: - /articles/what-happens-when-i-change-my-organization-s-name/ - /articles/renaming-an-organization @@ -17,34 +17,35 @@ topics: {% tip %} -**Sugerencia:** Solo los propietarios de la organización pueden renombrar una organización. {% data reusables.organizations.new-org-permissions-more-info %} +**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %} {% endtip %} -## ¿Qué sucede cuando cambio el nombre de mi organización? +## What happens when I change my organization's name? -Después de cambiar el nombre de tu organización, el nombre antiguo de tu organización se pone a disposición para quien lo quiera utilizar. Cuando cambias el nombre de tu organización, la mayoría de las referencias a los repositorios bajo el nombre antiguo de tu organización se cambiarán automáticamente al nombre nuevo. Sin embargo, algunos enlaces a tu perfil no se redirigirán automáticamente. +After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect. -### Cambios que ocurren automáticamente +### Changes that occur automatically -- {% data variables.product.prodname_dotcom %} redirige automáticamente las referencias a tus repositorios. Los enlaces web a los **repositorios** existentes de tu organización seguirán funcionando. Puede tomar algunos minutos para que se complete luego de que inicies el cambio. -- Puedes continuar subiendo tus repositorios locales a la URL de seguimiento del remoto antiguo sin actualizarla. Sin embargo, recomendamos que actualices todas las URL de repositorios remotos existentes después de cambiar el nombre de tu organización. Como el nombre antiguo de tu organización queda disponible para que lo utilice cualquier otra persona después de que lo cambies, el propietario de la organización nuevo puede crear repositorios que remplacen las entradas redirigidas a tu repositorio. Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)." -- Las confirmaciones de Git anteriores también se atribuirán según corresponda a los usuarios de tu organización. +- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories. Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change. +- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- Previous Git commits will also be correctly attributed to users within your organization. -### Cambios que no son automáticos +### Changes that aren't automatic -Después de cambiar el nombre de tu organización: -- Los enlaces a la página de perfil de tu organización anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, generarán un error 404. Recomendamos que actualices los enlaces a tu organización desde otros sitios{% ifversion fpt or ghec %}, como tus perfiles de LinkedIn o Twitter{% endif %}. -- Las solicitudes API que utilizan el nombre de la organización antiguo generarán un error 404. Recomendamos que actualices el nombre de la organización antiguo en tus solicitudes API. -- No hay redireccionamientos automáticos de [@mención](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) para los equipos que utilizan el nombre antiguo de la organización.{% ifversion fpt or ghec %} -- Si se habilita el inicio de sesión único (SSO) para la organización, debes actualizar el nombre de la misma en la aplicación para {% data variables.product.prodname_ghe_cloud %} en tu proveedor de identidad (IdP). Si no actualizas el nombre de organización en tu IdP, los miembros de esta ya no podrán autenticarse con tu IdP para acceder a los recursos de la organización. Para obtener más información, consulta la sección "[Conectar a tu proveedor de identidad con tu organización](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} +After changing your organization's name: +- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. We recommend you update links to your organization from other sites{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profiles{% endif %}. +- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% ifversion fpt or ghec %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} -## Cambiar el nombre de tu organización +## Changing your organization's name {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. Cerca de la parte de abajo de la página de parámetros, en "Rename organization" (Renombrar organización), haz clic en **Rename Organization** (Renombrar organización). ![Botón Rename organization (Renombrar organización)](/assets/images/help/settings/settings-rename-organization.png) +4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**. + ![Rename organization button](/assets/images/help/settings/settings-rename-organization.png) -## Leer más +## Further reading -* "[¿Por qué mis confirmaciones están vinculadas al usuario incorrecto?](/articles/why-are-my-commits-linked-to-the-wrong-user)" +* "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md index 9af545a5c9..dcf8751104 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Verificar o aprobar un dominio para tu organización -intro: 'Puedes verificar tu propiedad de dominios con {% data variables.product.company_short %} para confirmar la identidad de tu organización. También puedes aprobar los dominios a los cuales {% data variables.product.company_short %} puede enviar notificaciones de correo electrónico para los miembros de tu organización.' +title: Verifying or approving a domain for your organization +intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.' product: '{% data reusables.gated-features.verify-and-approve-domain %}' redirect_from: - /articles/verifying-your-organization-s-domain @@ -18,34 +18,36 @@ topics: - Notifications - Organizations - Policy -shortTitle: Verificar o aprobar un dominio +shortTitle: Verify or approve a domain --- -## Acerca de la verificación de dominios +## About domain verification -Después de verificar la propiedad de los dominios de tu organización, se mostrará un distintivo "Verified" (Verificado) en el perfil de la organización. {% ifversion fpt or ghec %}Si tu organización está en {% data variables.product.prodname_ghe_cloud %} y firmó el acuerdo de los Términos de Servicio Corporativo, los propietarios de la organización podrán verificar la identidad de los miembros organizacionales viendo sus direcciones de correo electrónico dentro del dominio verificado. Para obtener más información, consulta las secciones "[Acerca de la página de perfil de tu organización](/articles/about-your-organization-s-profile/)" y "Actualizar a los Términos de servicio corporativos".{% endif %} +After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. {% ifversion fpt or ghec %}If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "Upgrading to the Corporate Terms of Service."{% endif %} -{% ifversion fpt or ghec %}Si tu organización le pertenece a una cuenta empresarial, se mostrará una{% elsif ghes %}Se mostrará una{% endif %} insignia de "Verificada" en el perfil de esta en todos los dominios verificados de la cuenta empresarial, adicionalmente a cualquier dominio verificado de la organización. Los propietarios de las organizaciones pueden ver cualquier dominio que haya verificado o aprobado el propietario de la empresa y pueden editar los dominios si el propietario de la organización es también un propietario de la empresa. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +{% ifversion fpt or ghec %}If your organization is owned by an enterprise account, a{% elsif ghes %}A{% endif %} "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owner. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} {% data reusables.organizations.verified-domains-details %} -{% ifversion fpt or ghec %}En {% data variables.product.prodname_ghe_cloud %}, después de verificar la propiedad del dominio de tu organización, puedes restringir las notificaciones por correo electrónico para la organización de dicho dominio. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %} +{% ifversion fpt or ghec %}On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %} -## Acerca de la probación de dominios +{% ifversion fpt or ghec %}You can also verify custom domains used for {% data variables.product.prodname_pages %} to prevent domain takeovers when a custom domain remains configured but your {% data variables.product.prodname_pages %} site is either disabled or no longer uses the domain. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."{% endif %} + +## About domain approval {% data reusables.enterprise-accounts.approved-domains-beta-note %} {% data reusables.enterprise-accounts.approved-domains-about %} -Después de que apruebas dominios para tu organización, puedes restringir las notificaciones por correo electrónico de toda la actividad dentro de la organización para que solo lleguen a las direcciones de correo electrónico verificadas dentro de los dominios aprobados o verificados. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". +After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." -Los propietarios de empresas no pueden ver qué miembros de las organizaciones o direcciones de correo electrónico reciben notificaciones dentro de los dominios aprobados. +Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains. -Los propietarios de las empresas también pueden aprobar dominios adicionales para las organizaciones que pertenezcan a la empresa. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +Enterprise owners can also approve additional domains for organizations owned by the enterprise. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} -## Verificar un dominio para tu organización +## Verifying a domain for your organization -Para verificar un dominio, debes tener acceso apra modificar registros de dominio con tu servicio de hospedaje de dominios. +To verify a domain, you must have access to modify domain records with your domain hosting service. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -53,15 +55,16 @@ Para verificar un dominio, debes tener acceso apra modificar registros de domini {% data reusables.organizations.add-a-domain %} {% data reusables.organizations.add-domain %} {% data reusables.organizations.add-dns-txt-record %} -1. Espera a que cambie la configuración de tu DNS, lo cual puede llevar hasta 72 horas. Puedes confirmar que tu configuración de DNS cambió si ejecutas el comando `dig` en la línea de comandos, reemplazando `ORGANIZATION` con el nombre de tu organización y `example.com` con el dominio que te gustaría verificar. Deberías ver tu nuevo registro TXT enumerado en el resultado del comando. +1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output. ```shell $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT ``` -1. Después de confirmar, tu registro de TXT se agrega a tu DNS, sigue los pasos uno a tres que se mencionan anteriormente para navegar a los dominios verificados y aprobados de tu organización. +1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains. {% data reusables.organizations.continue-verifying-domain %} -11. Como alternativa, una vez que la insignia "Verified" (Verificado) es visible en la página de perfil de tu organización, puedes eliminar la entrada de TXT desde el registro de DNS en tu servicio de alojamiento de dominio. ![Insignia Verificado](/assets/images/help/organizations/verified-badge.png) +11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service. +![Verified badge](/assets/images/help/organizations/verified-badge.png) -## Aprobar un dominio para tu organización +## Approving a domain for your organization {% ifversion fpt or ghes > 3.1 or ghec %} @@ -77,9 +80,10 @@ Para verificar un dominio, debes tener acceso apra modificar registros de domini {% data reusables.organizations.domains-approve-it-instead %} {% data reusables.organizations.domains-approve-domain %} -## Eliminar un dominio verificado o aprobado +## Removing an approved or verified domain {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.verified-domains %} -1. A la derecha del dominio a eliminar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Borrar**. !["Borrar" para un dominio](/assets/images/help/organizations/domains-delete.png) +1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. + !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png) diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 14a629f98c..5e52b05048 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -1,7 +1,7 @@ --- title: Managing custom repository roles for an organization -intro: You can more granularly control access to your organization's repositories by creating custom repository roles. -permissions: Organization owners can manage custom repository roles. +intro: "You can more granularly control access to your organization's repositories by creating custom repository roles." +permissions: 'Organization owners can manage custom repository roles.' versions: ghec: '*' topics: @@ -20,7 +20,7 @@ To perform any actions on {% data variables.product.product_name %}, such as cre Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. A custom repository role is a configurable set of permissions with a custom name you choose. After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](https://docs-internal-21729--see-chang.herokuapp.com/en/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. A custom repository role is a configurable set of permissions with a custom name you choose. After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" {% data reusables.enterprise.link-to-ghec-trial %} @@ -30,22 +30,22 @@ When you create a custom repository role, you start by choosing an inherited rol Your options for the inherited role are standardized for different types of contributors in your repository. -| Inherited role | Designed for | -| ----------------- | ------------------------------------------------------------------------------------------------------ | -| **Read** | Non-code contributors who want to view or discuss your project. | -| **Clasificación** | Contributors who need to proactively manage issues and pull requests without write access. | -| **Escritura** | Organization members and collaborators who actively push to your project. | -| **Mantenimiento** | Project managers who need to manage the repository without access to sensitive or destructive actions. | +| Inherited role | Designed for | +|----|----| +| **Read** | Non-code contributors who want to view or discuss your project. | +| **Triage** | Contributors who need to proactively manage issues and pull requests without write access. | +| **Write** | Organization members and collaborators who actively push to your project. | +| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions. ## Custom role examples Here are some examples of custom repository roles you can configure. -| Custom repository role | Resumen | Inherited role | Additional permissions | -| ---------------------- | ----------------------------------------------------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Security engineer | Able to contribute code and maintain the security pipeline | **Mantenimiento** | Delete code scanning results | -| Contractor | Able to develop webhooks integrations | **Escritura** | Manage webhooks | -| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate
    - Manage GitHub Page settings
    - Manage wiki settings
    - Set the social preview
    - Edit repository metadata
    - Triage discussions | +| Custom repository role | Summary | Inherited role | Additional permissions | +|----|----|----|----| +| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results | +| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks | +| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate
    - Manage GitHub Page settings
    - Manage wiki settings
    - Set the social preview
    - Edit repository metadata
    - Triage discussions | ## Additional permissions for custom roles @@ -58,38 +58,38 @@ You can only choose an additional permission if it's not already included in the - **Assign or remove a user**: Assign a user to an issue or pull request, or remove a user from an issue or pull request. - **Add or remove a label**: Add a label to an issue or a pull request, or remove a label from an issue or pull request. -### Informe de Problemas +### Issue - **Close an issue** - **Reopen a closed issue** - **Delete an issue** - **Mark an issue as a duplicate** -### Solicitud de Extracción +### Pull Request - **Close a pull request** - **Reopen a closed pull request** - **Request a pull request review**: Request a review from a user or team. -### Repositorio +### Repository - **Set milestones**: Add milestones to an issue or pull request. - **Manage wiki settings**: Turn on wikis for a repository. - **Manage project settings**: Turning on projects for a repository. - **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase. -- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)". +- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." - **Manage webhooks**: Add webhooks to the repository. - **Manage deploy keys**: Add deploy keys to the repository. - **Edit repository metadata**: Update the repository description as well as the repository topics. - **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." -- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. Para obtener más información, consulta "[Personalizar la vista preliminar de las redes sociales de tu repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)." +- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. For more information, see "[Customizing your repository's social media preview](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)." - **Push commits to protected branches**: Push to a branch that is marked as a protected branch. -### Seguridad +### Security -- **Read {% data variables.product.prodname_code_scanning %} results** -- **Write {% data variables.product.prodname_code_scanning %} results** -- **Delete {% data variables.product.prodname_code_scanning %} results** +- **Read {% data variables.product.prodname_code_scanning %} results**: Provide users with read permissions for {% data variables.product.prodname_code_scanning %} alerts. +- **Write {% data variables.product.prodname_code_scanning %} results**: Provide users with write permissions for {% data variables.product.prodname_code_scanning %} alerts. +- **Delete {% data variables.product.prodname_code_scanning %} results**: Provide users with delete permissions for {% data variables.product.prodname_code_scanning %} alerts. ## Precedence for different levels of access @@ -97,9 +97,9 @@ If a person is given different levels of access through different avenues, such If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**. -To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. Para obtener más información, consulta: - - "[Configurar los permisos básicos para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" - - "[Administrar el acceso del equipo al repositorio de una organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" +To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see: + - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" + - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" - "[Editing a repository role](#editing-a-repository-role)" ## Creating a repository role @@ -111,12 +111,18 @@ To create a new repository role, you add permissions to an inherited role and gi {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) -4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) -5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) -6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) -7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) -7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) +5. Click **Create a Role**. + ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) +4. Under "Name", type the name of your repository role. + ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) +5. Under "Description", type a description of your repository role. + ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) +6. Under "Choose a role to inherit", select the role you want to inherit. + ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) +7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. + ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) +7. Click **Create role**. + ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) ## Editing a repository role @@ -125,8 +131,10 @@ To create a new repository role, you add permissions to an inherited role and gi {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) -4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) +3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. + ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) +4. Edit, then click **Update role**. + ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) ## Deleting a repository role @@ -137,5 +145,7 @@ If you delete an existing repository role, all pending invitations, teams, and u {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) -4. Review changes for the role you want to remove, then click **Delete role**. ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png) +3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. + ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) +4. Review changes for the role you want to remove, then click **Delete role**. + ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png) diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 29d251e9b4..f45688150f 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -16,7 +16,6 @@ topics: - Teams shortTitle: Roles in an organization --- - ## About roles {% data reusables.organizations.about-roles %} @@ -31,14 +30,14 @@ Organization-level roles are sets of permissions that can be assigned to individ You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)." ### Organization owners -Organization owners have complete administrative access to your organization. Este rol debe limitarse a dos personas, por lo mucho, en tu organización. Para obtener más información, consulta la sección "[Mantener la continuidad de la propiedad para tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". +Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." -### Miembros de la organización +### Organization members The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards. {% ifversion fpt or ghec %} -### Gerentes de facturación -Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. Para obtener más información, consulta "[Agregar un gerente de facturación a tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." +### Billing managers +Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." {% endif %} @@ -51,178 +50,174 @@ Billing managers are users who can manage the billing settings for your organiza If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." {% endif %} -### {% data variables.product.prodname_github_app %} administadores -Predeterminadamente, solo los propietarios de la organización pueden administrar la configuración de las {% data variables.product.prodname_github_apps %} que pertenezcan a una organización. Para permitir que más usuarios administren las {% data variables.product.prodname_github_apps %} que le pertenecen a una organización, un propietario puede otorgarles permisos de administrador de {% data variables.product.prodname_github_app %}. +### {% data variables.product.prodname_github_app %} managers +By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions. -Cuando designas un usuario como administrador de {% data variables.product.prodname_github_app %} en tu organización, puedes otorgarle acceso para administrar las configuraciones de algunas o todas las {% data variables.product.prodname_github_apps %} que le pertenecen a la organización. Para obtener más información, consulta: +When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. For more information, see: -- "[Agregar administradores de GitHub App en tu organización](/articles/adding-github-app-managers-in-your-organization)" -- "[Eliminar administradores de GitHub App de tu organización](/articles/removing-github-app-managers-from-your-organization)" +- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)" +- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)" -### Colaboradores externos -Para mantener seguros los datos de tu organización mientras que permites el acceso a los repositorios, puedes agregar *colaboradores externos*. {% data reusables.organizations.outside_collaborators_description %} +### Outside collaborators +To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %} ## Permissions for organization roles {% ifversion fpt %} -Algunas de las características que se listan a continuación se limitan a las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} {% ifversion fpt or ghec %} -| Organization permission | Propietarios | Miembros | Gerentes de facturación | Security managers | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------:|:--------:|:-----------------------:|:-----------------:| -| Crear repositorios (consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)" para obtener más detalles) | **X** | **X** | | **X** | -| Ver y editar la información de facturación | **X** | | **X** | | -| Invitar personas para que se unan a la organización | **X** | | | | -| Editar y cancelar invitaciones para unirse a la organización | **X** | | | | -| Eliminar miembros de tu organización | **X** | | | | -| Reinstalar antiguos miembros a la organización | **X** | | | | -| Agregar o eliminar personas de **todos los equipos** | **X** | | | | -| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | | | | -| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | -| Configurar los recordatorios programados (consulta la sección "[Administrar los recordatorios programados para solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | -| Agregar colaboradores a **todos los repositorios** | **X** | | | | -| Acceder al registro de auditoría de la organización | **X** | | | | -| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para obtener más detalles) | **X** | | | | -| Verificar los dominios de la organización (consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)" para obtener más detalles) | **X** | | | | -| Restringir las notificaciones por correo electrónico para los dominios aprobados o verificados (consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para encontrar más detalles) | **X** | | | | -| Eliminar **todos los equipos** | **X** | | | | -| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | | | -| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | | **X** | -| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | -| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | | **X** | -| Ver todos los miembros y equipos de la organización | **X** | **X** | | **X** | -| @mencionar cualquier equipo visible | **X** | **X** | | **X** | -| Poder convertirse en *mantenedor del equipo* | **X** | **X** | | **X** | -| Ver información de la organización (consulta "[Ver información de tu organización](/articles/viewing-insights-for-your-organization)" para obtener más detalles) | **X** | **X** | | **X** | -| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | **X** | | **X** | -| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | | | | -| Editar y eliminar debates de equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" para obtener más detalles) | **X** | | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | | **X** | -| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | | | -| Administrar vistas de la información de las dependencias de la organización (consulta "[Cambiar la visibilidad de la información de las dependencias de tu organización](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para obtener más detalles) | **X** | | | | -| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | | | -| Patrocinar cuentas y administrar los patrocionos de la organización (consulta la sección "[Patrocinar contribuyentes de código abierto](/sponsors/sponsoring-open-source-contributors)" para obener más detalles) | **X** | **X** | | **X** | -| Administrar las actualizaciones de las cuentas patrocinadas (consulta la sección "[Administrar las actualizaciones de los patrocinadores de tu organización](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" para obtener más detalles) | **X** | | | | -| Atribuir tus patrocinios a otra organización (consulta la sección "[Atribuir los patrocionios a tu organización](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" para obtener más detalles) | **X** | | | | -| Administra la publicación de páginas de {% data variables.product.prodname_pages %} desde los repositorios de la organización (consulta "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" para obtener más detalles) | **X** | | | | -| Administrar la configuración de seguridad y de análisis (consulta la sección "[Administrar la configuración de seguridad y de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles) | **X** | | | **X** | -| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** | -| Habilitar y aplicar el [inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | -| [Administrar el acceso de SAML de un usuario a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | -| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | | | | -| Transferir repositorios | **X** | | | | -| Comprar, instalar, administrar la facturación y cancelar aplicaciones {% data variables.product.prodname_marketplace %} | **X** | | | | -| Enumerar aplicaciones en {% data variables.product.prodname_marketplace %} | **X** | | | | -| Recibe [{% data variables.product.prodname_dependabot_alerts %} sobre las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos los repositorios de una organización | **X** | | | **X** | -| Administrar las {% data variables.product.prodname_dependabot_security_updates %} (consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** | -| [Administrar la política de bifurcación](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | | -| [Limitar la actividad en repositorios públicos en una organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | -| Pull (read) *all repositories* in the organization | **X** | | | **X** | -| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | | -| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | | | -| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | -| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | -| Administrar el nombre de la rama predeterminada (consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | -| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | | -| Habilitar la sincronización de equipos (consulta la sección "[Administrar la sincronización de equipos para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" para obtener más detalles) | **X** | | | | +| Organization permission | Owners | Members | Billing managers | Security managers | +|:--------------------|:------:|:-------:|:----------------:|:----------------:| +| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** | | **X** | +| View and edit billing information | **X** | | **X** | | +| Invite people to join the organization | **X** | | | | +| Edit and cancel invitations to join the organization | **X** | | | | +| Remove members from the organization | **X** | | | | +| Reinstate former members to the organization | **X** | | | | +| Add and remove people from **all teams** | **X** | | | | +| Promote organization members to *team maintainer* | **X** | | | | +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | +| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | +| Add collaborators to **all repositories** | **X** | | | | +| Access the organization audit log | **X** | | | | +| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | | | +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | | +| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | | | | +| Delete **all teams** | **X** | | | | +| Delete the organization account, including all repositories | **X** | | | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | | **X** | +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | **X** | +| See all organization members and teams | **X** | **X** | | **X** | +| @mention any visible team | **X** | **X** | | **X** | +| Can be made a *team maintainer* | **X** | **X** | | **X** | +| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | **X** | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | **X** | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | | +| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** | | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | | +| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details) | **X** | | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)" for details) | **X** | | **X** | **X** | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | **X** | +| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** | +| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | +| [Manage a user's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | | +| Transfer repositories | **X** | | | | +| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | | | +| List apps in {% data variables.product.prodname_marketplace %} | **X** | | | | +| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** | | | **X** | +| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** | +| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | +| Pull (read) *all repositories* in the organization | **X** | | | **X** | +| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | +| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | | +| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | | {% elsif ghes > 3.2 or ghae-issue-4999 %} -| Acción de organización | Propietarios | Miembros | Security managers | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------:|:--------:|:---------------------------------:| -| Invitar personas para que se unan a la organización | **X** | | | -| Editar y cancelar invitaciones para unirse a la organización | **X** | | | -| Eliminar miembros de tu organización | **X** | | | | -| Reinstalar antiguos miembros a la organización | **X** | | | | -| Agregar o eliminar personas de **todos los equipos** | **X** | | | -| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | | | -| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | -| Agregar colaboradores a **todos los repositorios** | **X** | | | -| Acceder al registro de auditoría de la organización | **X** | | | -| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para obtener más detalles) | **X** | | |{% ifversion ghes > 3.1 %} -| Verificar los dominios de la organización (consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)" para obtener más detalles) | **X** | | | -| Restringir las notificaciones por correo electrónico para los dominios aprobados o verificados (consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para encontrar más detalles) | **X** | | -{% endif %} -| Eliminar **todos los equipos** | **X** | | | -| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | | -| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | **X** | -| Ver todos los miembros y equipos de la organización | **X** | **X** | **X** | -| @mencionar cualquier equipo visible | **X** | **X** | **X** | -| Poder convertirse en *mantenedor del equipo* | **X** | **X** | **X** | -| Transferir repositorios | **X** | | | -| Administrar la configuración de seguridad y de análisis (consulta la sección "[Administrar la configuración de seguridad y de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles) | **X** | | **X** |{% ifversion ghes > 3.1 %} -| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** -{% endif %} -| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | | | -| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | **X** | -| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | **X** | **X** | -| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | | | -| Editar y eliminar debates de equipo en **todos los equipos** (para obtener más información consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | **X** | -| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | | -| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | |{% ifversion ghes > 3.0 %} -| Administra la publicación de páginas de {% data variables.product.prodname_pages %} desde los repositorios de la organización (consulta "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" para obtener más detalles) | **X** | | -{% endif %} -| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Pull (read) *all repositories* in the organization | **X** | | **X** | -| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | -| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | | -| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Organization action | Owners | Members | Security managers | +|:--------------------|:------:|:-------:|:-------:| +| Invite people to join the organization | **X** | | | +| Edit and cancel invitations to join the organization | **X** | | | +| Remove members from the organization | **X** | | | | +| Reinstate former members to the organization | **X** | | | | +| Add and remove people from **all teams** | **X** | | | +| Promote organization members to *team maintainer* | **X** | | | +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Add collaborators to **all repositories** | **X** | | | +| Access the organization audit log | **X** | | | +| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | |{% ifversion ghes > 3.1 %} +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | +| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | | |{% endif %} +| Delete **all teams** | **X** | | | +| Delete the organization account, including all repositories | **X** | | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | **X** | +| See all organization members and teams | **X** | **X** | **X** | +| @mention any visible team | **X** | **X** | **X** | +| Can be made a *team maintainer* | **X** | **X** | **X** | +| Transfer repositories | **X** | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | **X** |{% ifversion ghes > 3.1 %} +| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %} +| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** |{% endif %} +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | **X** | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | **X** | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% ifversion ghes > 3.0 %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | |{% endif %} +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (read) *all repositories* in the organization | **X** | | **X** | +| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | {% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | | |{% endif %} {% else %} -| Acción de organización | Propietarios | Miembros | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------:|:------------------------------:| -| Invitar personas para que se unan a la organización | **X** | | -| Editar y cancelar invitaciones para unirse a la organización | **X** | | -| Eliminar miembros de tu organización | **X** | | | -| Reinstalar antiguos miembros a la organización | **X** | | | -| Agregar o eliminar personas de **todos los equipos** | **X** | | -| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | | -| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | -| Agregar colaboradores a **todos los repositorios** | **X** | | -| Acceder al registro de auditoría de la organización | **X** | | -| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para obtener más detalles) | **X** | | |{% ifversion ghes > 3.1 %} -| Verificar los dominios de la organización (consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)" para obtener más detalles) | **X** | | -| Restringir las notificaciones por correo electrónico para los dominios aprobados o verificados (consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para encontrar más detalles) | **X** | -{% endif %} -| Eliminar **todos los equipos** | **X** | | -| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | -| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | -| Ver todos los miembros y equipos de la organización | **X** | **X** | -| @mencionar cualquier equipo visible | **X** | **X** | -| Poder convertirse en *mantenedor del equipo* | **X** | **X** | -| Transferir repositorios | **X** | | -| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | | -| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | | -| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | **X** | | -| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | | | -| Editar y eliminar debates de equipo en **todos los equipos** (para obtener más información consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | **X** | -| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | | -| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | |{% ifversion ghes > 3.0 %} -| Administra la publicación de páginas de {% data variables.product.prodname_pages %} desde los repositorios de la organización (consulta "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" para obtener más detalles) | **X** | -{% endif %} -| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Extraer (leer), subir (escribir) y clonar (copiar) *todos los repositorios* en la organización | **X** | | -| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | -| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | -| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | -{% ifversion ghae %}| Administrar listas de IP permitidas (Consulta la sección "[Restringir el tráfico de red hacia tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} +| Organization action | Owners | Members | +|:--------------------|:------:|:-------:| +| Invite people to join the organization | **X** | | +| Edit and cancel invitations to join the organization | **X** | | +| Remove members from the organization | **X** | | | +| Reinstate former members to the organization | **X** | | | +| Add and remove people from **all teams** | **X** | | +| Promote organization members to *team maintainer* | **X** | | +| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** | | +| Add collaborators to **all repositories** | **X** | | +| Access the organization audit log | **X** | | +| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | |{% ifversion ghes > 3.1 %} +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | +| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | |{% endif %} +| Delete **all teams** | **X** | | +| Delete the organization account, including all repositories | **X** | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | +| See all organization members and teams | **X** | **X** | +| @mention any visible team | **X** | **X** | +| Can be made a *team maintainer* | **X** | **X** | +| Transfer repositories | **X** | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% ifversion ghes > 3.0 %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | |{% endif %} +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | +{% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} {% endif %} -## Leer más +## Further reading - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" -- [Permisos de tablero de proyecto para una organización](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)" +- "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/index.md b/translations/es-ES/content/organizations/organizing-members-into-teams/index.md index 5940c736a8..e3c495fc00 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/index.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/index.md @@ -1,6 +1,6 @@ --- -title: Organizar miembros en un equipo -intro: Puedes agrupar miembros de la organización en equipos que reflejen la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. +title: Organizing members into teams +intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions. redirect_from: - /articles/setting-up-teams-improved-organization-permissions/ - /articles/setting-up-teams-for-accessing-organization-repositories/ @@ -26,7 +26,7 @@ children: - /adding-organization-members-to-a-team - /assigning-the-team-maintainer-role-to-a-team-member - /setting-your-teams-profile-picture - - /managing-code-review-assignment-for-your-team + - /managing-code-review-settings-for-your-team - /renaming-a-team - /changing-team-visibility - /synchronizing-a-team-with-an-identity-provider-group @@ -37,6 +37,6 @@ children: - /disabling-team-discussions-for-your-organization - /managing-scheduled-reminders-for-your-team - /deleting-a-team -shortTitle: Organizar a los miembros en equipos +shortTitle: Organize members into teams --- diff --git a/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index 70c8f5fc45..ddd7a0adcc 100644 --- a/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -1,6 +1,6 @@ --- -title: Borrar y restablecer un paquete -intro: Aprende cómo borrar o restablecer un paquete. +title: Deleting and restoring a package +intro: Learn how to delete or restore a package. product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/deleting-a-package @@ -11,84 +11,89 @@ versions: fpt: '*' ghes: '>=3.1' ghec: '*' -shortTitle: Borrar & restablecer un paquete +shortTitle: Delete & restore a package --- {% data reusables.package_registry.packages-ghes-release-stage %} -## Soporte para borrado y restablecimiento de paquetes en {% data variables.product.prodname_dotcom %} +## Package deletion and restoration support on {% data variables.product.prodname_dotcom %} -En {% data variables.product.prodname_dotcom %}, si tienes el acceso necesario, puedes borrar: -- todo un paquete privado -- todo un paquete público, si es que no hay más de 25 descargas de ninguna versión de éste -- una versión específica de un paquete privado -- una versíón específica de un paquete púlico, si dicha versión no tiene más de 25 descargas +On {% data variables.product.prodname_dotcom %} if you have the required access, you can delete: +- an entire private package +- an entire public package, if there's not more than 5000 downloads of any version of the package +- a specific version of a private package +- a specific version of a public package, if the package version doesn't have more than 5000 downloads {% note %} -**Nota:** -- No puedes borrar un paquete público específico si alguna de las versiones de éste tiene más de 25 descargas. En este escenario, contacta a [Soporte de GitHub](https://support.github.com/contact?tags=docs-packages) para que te proporcionen asistencia. -- Cuando borres paquetes públicos, toma en cuenta que podrías dañar proyetos que dependen de ellos. +**Note:** +- You cannot delete a public package if any version of the package has more than 5000 downloads. In this scenario, contact [GitHub support](https://support.github.com/contact?tags=docs-packages) for further assistance. +- When deleting public packages, be aware that you may break projects that depend on your package. {% endnote %} -En {% data variables.product.prodname_dotcom %}, también puedes restablecer un paquete completo o una versión de paquete si: -- Restableces el paquete dentro de los primeros 30 días después de que se borró. -- El espacio de nombre del paquete aún se encuentra disponible y no se ha utilizado en un paquete nuevo. +On {% data variables.product.prodname_dotcom %}, you can also restore an entire package or package version, if: +- You restore the package within 30 days of its deletion. +- The same package namespace is still available and not used for a new package. -## Soporte de la API de paquetes +## Packages API support {% ifversion fpt or ghec %} -Puedes utiliza la API de REST para administrar tus paquetes. Para obtener más información, consulta la sección "[API del {% data variables.product.prodname_registry %}](/rest/reference/packages)". +You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." {% endif %} -En el caso de los paquetes que heredan sus permisos y accesos de los repositorios, puedes utilizar GraphQL para borrar las versiones de los paquetes específicos.{% ifversion fpt or ghec %} La API de GraphQL del {% data variables.product.prodname_registry %} no es compatible con contenedores o imágenes de Docker que utilicen el designador de nombre `https://ghcr.io/OWNER/PACKAGE-NAME`. Para obtener más información sobre la compatibilidad de GraphQL, consulta la sección "[Borrar una versión de un paquete con alcance de repositorio con GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)". +For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% ifversion fpt or ghec %} The {% data variables.product.prodname_registry %} GraphQL API does not support containers or Docker images that use the package namespace `https://ghcr.io/OWNER/PACKAGE-NAME`. For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)." {% endif %} -## Permisos necesarios para borrar o restablecer un paquete +## Required permissions to delete or restore a package -En el caso de los paquetes que heredan sus permisos de acceso de los repositorios, puedes borrar un paquete si tienes permisos administrativos en el repositorio. +For packages that inherit their access permissions from repositories, you can delete a package if you have admin permissions to the repository. -Los paquetes en {% data variables.product.prodname_registry %} con alcance de repositorio incluyen los paquetes: +Repository-scoped packages on {% data variables.product.prodname_registry %} include these packages: - npm - RubyGems - maven - Gradle - NuGet -{% ifversion not fpt or ghec %}- Las imágenes de Docker en `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %} +{% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %} {% ifversion fpt or ghec %} -Para borrar un paquete que tenga permisos granulares separados de un repositorio, tales como imágenes de contenedor que se almacenan en `https://ghcr.io/OWNER/PACKAGE-NAME`, debes tener acceso administrativo en este. +To delete a package that has granular permissions separate from a repository, such as container images stored at `https://ghcr.io/OWNER/PACKAGE-NAME`, you must have admin access to the package. {% endif %} -## Borrar la versión de un paquete +## Deleting a package version -### Borrar la versión de un paquete con alcance de repositorio en {% data variables.product.prodname_dotcom %} +### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %} -Para borrar una versión de un paquete con alcance de repositorio debes tener permisos de administrador en el repositorio al que pertenezca dicho paquete. Para obtener más información, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To delete a version of a repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.package-settings-option %} -5. A la izquierda, da clic en **Administrar versiones**. -5. A la derecha de la versión que quieres borrar, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Borrar versión**. ![Botón de borrar versión del paquete](/assets/images/help/package-registry/delete-container-package-version.png) -6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/package-version-deletion-confirmation.png) +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**. + ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. + ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png) -### Borrar una versión de un paquete con alcance de repositorio con GraphQL +### Deleting a version of a repository-scoped package with GraphQL -En el caso de los paquetes que heredan sus permisos y acceso de los repositorios, puedes utilizar a GraphQL para borrar las versiones específicas de estos. +For packages that inherit their permissions and access from repositories, you can use the GraphQL to delete a specific package version. {% ifversion fpt or ghec %} -GraphQL no es compatible con contenedores o imagenes de Docker en `ghcr.io`. -{% endif %}Usa la mutación `deletePackageVersion` en la API de GraphQL. Debes usar un token con ámbitos `read:packages`, `delete:packages` y `repo`. Para obtener más información acerca de los tokens, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". +GraphQL is not supported for containers or Docker images at `ghcr.io`. +{% endif %} + -El siguiente ejemplo demuestra cómo borrar una versión de paquete utilizando una `packageVersionId` de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`. +Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." + +The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`. ```shell curl -X POST \ @@ -98,121 +103,140 @@ curl -X POST \ HOSTNAME/graphql ``` -Para encontrar todos los paquetes privados que publicaste en {% data variables.product.prodname_registry %}, junto con los ID de versión de los paquetes, puedes usar la conexión `registryPackagesForQuery`. Necesitarás un token con los ámbitos `read:packages` y `repo`. For more information, see the [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) connection or the [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) interface. +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) connection or the [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) interface. -Para obtener más información acerca de la mutación `deletePackageVersion`, consulta "[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)". +For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)." -No puedes borrar directamente todo un paquete utilizando GraphQL, pero si borras cada versión de un paquete, este ya no se mostrará en {% data variables.product.product_name %}. +You cannot directly delete an entire package using GraphQL, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}. {% ifversion fpt or ghec %} -### Borrar una versión de un paquete con alcance de usuario en {% data variables.product.prodname_dotcom %} +### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %} -Para borrar una versión específica de un paquete con alcance de usuario en {% data variables.product.prodname_dotcom %}, tal como para una imagen de Docker en `ghcr.io`, sigue estos pasos. Para borrar un paquete completo, consulta la sección "[Borrar un paquete entero con alcance de usuario en {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)". +To delete a specific version of a user-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps. To delete an entire package, see "[Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)." -Para revisar quién puede borrar una versión de paquete, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.package_registry.package-settings-from-user-level %} {% data reusables.package_registry.package-settings-option %} -5. A la izquierda, da clic en **Administrar versiones**. -5. A la derecha de la versión que quieres borrar, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Borrar versión**. ![Botón de borrar versión del paquete](/assets/images/help/package-registry/delete-container-package-version.png) -6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**. + ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. + ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) -### Borrar una versión de un paquete con alcance de organización en GitHub +### Deleting a version of an organization-scoped package on GitHub -Para borrar una versión específica de un paquete con alcance de organización en {% data variables.product.prodname_dotcom %}, tal como una imagen de Docker en `ghcr.io`, sigue estos pasos. Para borrar un paquete completo, consulta la sección "[Borrar un paquete entero con alcance de organización en {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)". +To delete a specific version of an organization-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps. +To delete an entire package, see "[Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)." -Para revisar quién puede borrar una versión de paquete, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.package-settings-option %} -5. A la izquierda, da clic en **Administrar versiones**. -5. A la derecha de la versión que quieres borrar, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Borrar versión**. ![Botón de borrar versión del paquete](/assets/images/help/package-registry/delete-container-package-version.png) -6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar el borrado de la versión del paquete](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**. + ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. + ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) {% endif %} -## Borrar un paquete completo +## Deleting an entire package -### Borrar un paquete completo con alcance de repositorio en {% data variables.product.prodname_dotcom %} +### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %} -Para borrar un paquete completo con alcance de repositorio, debes tener permisos administrativos en el repositorio al que pertenezca dicho paquete. Para obtener más información, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To delete an entire repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.package-settings-option %} -4. Debajo de "Zona de Peligro", haz clic en **Borrar este paquete**. -5. Para confirmar, revisa el mensaje de confirmación, ingresa el nombre de tu paquete, y haz clic en **Entriendo, borrar este paquete.** ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/package-version-deletion-confirmation.png) +4. Under "Danger Zone", click **Delete this package**. +5. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.** + ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png) {% ifversion fpt or ghec %} -### Borrar un paquete completo con alcance de usuario en {% data variables.product.prodname_dotcom %} +### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %} -Para revisar quién puede borrar un paquete, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.package_registry.package-settings-from-user-level %} {% data reusables.package_registry.package-settings-option %} -5. A la izquierda, da clic en **Opciones**. ![Opción del menú "Opciones"](/assets/images/help/package-registry/options-for-container-settings.png) -6. Debajo de "Zona de peligro", da clic en **Borra este paquete**. ![Botón de borrar versión del paquete](/assets/images/help/package-registry/delete-container-package-button.png) -6. Para confirmar el borrado, teclea el nombre del paquete y da clic en **Entiendo las consecuencias, borrar este paquete**. ![Botón para confirmar el borrado de la versión del paquete](/assets/images/help/package-registry/confirm-container-package-deletion.png) +5. On the left, click **Options**. + !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png) +6. Under "Danger zone", click **Delete this package**. + ![Delete package version button](/assets/images/help/package-registry/delete-container-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**. + ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png) -### Borrar un paquete completo con alcance de organización en {% data variables.product.prodname_dotcom %} +### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %} -Para revisar quién puede borrar un paquete, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.package-settings-option %} -5. A la izquierda, da clic en **Opciones**. ![Opción del menú "Opciones"](/assets/images/help/package-registry/options-for-container-settings.png) -6. Debajo de "Zona de peligro", da clic en **Borra este paquete**. ![Botón para eliminar paquete](/assets/images/help/package-registry/delete-container-package-button.png) -6. Para confirmar el borrado, teclea el nombre del paquete y da clic en **Entiendo las consecuencias, borrar este paquete**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-container-package-deletion.png) +5. On the left, click **Options**. + !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png) +6. Under "Danger zone", click **Delete this package**. + ![Delete package button](/assets/images/help/package-registry/delete-container-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**. + ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png) {% endif %} -## Restablecer paquetes +## Restoring packages -Puedes restablecer un paquete o versión que hayas borrado si: -- Restableces el paquete dentro de los primeros 30 días después de que se borró. -- El mismo designador de nombre del paquete y su versión se encuentran disponibles y no se han reutilizado para un paquete nuevo. +You can restore a deleted package or version if: +- You restore the package within 30 days of its deletion. +- The same package namespace and version is still available and not reused for a new package. -Por ejemplo, si borraste un paquete de rubygem con el nombre `octo-package` que tuviera un alcance para el repositorio `octo-repo-owner/octo-repo`, entonces solo podrías restablecer el paquete si su designador de nombre `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` estuviera disponible todavía, suponiendo que no hayan pasado 30 días. +For example, if you have a deleted rubygem package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed. -También debes de cumplir con estos requisitos de permisos: - - Para los paquetes con alcance de repositorio: Tienes permisos de administrador en el repositorio al que pertenece el paquete que se borró.{% ifversion fpt or ghec %} - - Para los paquetes con alcance de cuenta de usuario: El paquete borrado pertenece a tu cuenta de usuario. - - Para los paquetes con alcance de organización: Tienes permisos de administrador en el paquete que se borró en la organización a la cual este pertenece.{% endif %} +You must also meet one of these permission requirements: + - For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt or ghec %} + - For user-account scoped packages: Your user account owns the deleted package. + - For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %} -Para obtener más información, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." -Una vez que se restablezca el paquete, este utilizará el designador de nombre que ya tenía. Si ya no está disponible el mismo designador de nombre del paquete, no podrás restablecerlo. En este caso, para restablecer el paquete que se borró, primero deberás borrar el paquete nuevo que utiliza el designador de nombre del paquete que se borró. +Once the package is restored, the package will use the same namespace it did before. If the same package namespace is not available, you will not be able to restore your package. In this scenario, to restore the deleted package, you must delete the new package that uses the deleted package's namespace first. -### Restablecer un paquete en una organización +### Restoring a package in an organization -Puedes restablecer un paquete borrado a través de la configuración de cuenta de tu organización siempre y cuando dicho paquete estuviera en uno de tus repositorios{% ifversion fpt or ghec %} o tuviera permisos granulares y tuviera el alcance de tu cuenta de organización{% endif %}. +You can restore a deleted package through your organization account settings, as long as the package was in one of your repositories{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}. -Para revisar quién puede restablecer un paquete en una organización, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} -3. A la izquierda, da clic en **Paquetes**. -4. Debajo de "Paquetes Borrados", junto al paquete que quieres restablecer, haz clic en **Restablecer**. ![Botón de restaurar](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png) -5. Para confirmar, teclea el nombre del paquete y haz clic en **Entiendo las consencuencias, restablecer este paquete**. ![Botón de confirmación para restablecer el paquete](/assets/images/help/package-registry/type-package-name-and-restore-button.png) +3. On the left, click **Packages**. +4. Under "Deleted Packages", next to the package you want to restore, click **Restore**. + ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png) +5. To confirm, type the name of the package and click **I understand the consequences, restore this package**. + ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png) {% ifversion fpt or ghec %} -### Restablecer un paquete con alcance de cuenta de usuario +### Restoring a user-account scoped package -Puedes restablecer un paquete que se haya borrado a través de la configuración de tu cuenta de usuario, siempre y cuando haya estado en uno de tus repositorios o hay tenido el alcance de tu cuenta de usuario. Para obtener más información, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +You can restore a deleted package through your user account settings, if the package was in one of your repositories or scoped to your user account. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." {% data reusables.user_settings.access_settings %} -2. A la izquierda, da clic en **Paquetes**. -4. Debajo de "Paquetes Borrados", junto al paquete que quieres restablecer, haz clic en **Restablecer**. ![Botón de restaurar](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png) -5. Para confirmar, teclea el nombre del paquete y haz clic en **Entiendo las consencuencias, restablecer este paquete**. ![Botón de confirmación para restablecer el paquete](/assets/images/help/package-registry/type-package-name-and-restore-button.png) +2. On the left, click **Packages**. +4. Under "Deleted Packages", next to the package you want to restore, click **Restore**. + ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png) +5. To confirm, type the name of the package and click **I understand the consequences, restore this package**. + ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png) {% endif %} -### Restablecer la versión de un paquete +### Restoring a package version -Puedes restablecer una versión de paquete desde la página de llegada del mismo. Para revisar quién puede restablecer un paquete, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". +You can restore a package version from your package's landing page. To review who can restore a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)." -1. Navega a la página de llegada de tu paquete. -2. A la derecha, haz clic en **Configuración del paquete**. -2. A la izquierda, da clic en **Administrar versiones**. -3. En la parte superior derecha, utiliza el menú desplegable de "Versiones" y selecciona **Borrados**. ![Menú desplegable de versiones que muestra la opción borrada](/assets/images/help/package-registry/versions-drop-down-menu.png) -4. Junto a la versión del paquete que se haya borrado y que quieras restablecer, haz clic en **Restablecer**. ![Opción de restablecer junto a la versión de un paquete borrado](/assets/images/help/package-registry/restore-package-version.png) -5. Para confirmar, haz clic en **Entiendo las consecuencias, restablecer esta versión.** ![Confirmar el restablecimiento de versión de un paquete](/assets/images/help/package-registry/confirm-package-version-restoration.png) +1. Navigate to your package's landing page. +2. On the right, click **Package settings**. +2. On the left, click **Manage versions**. +3. On the top right, use the "Versions" drop-down menu and select **Deleted**. + ![Versions drop-down menu showing the deleted option](/assets/images/help/package-registry/versions-drop-down-menu.png) +4. Next to the deleted package version you want to restore, click **Restore**. + ![Restore option next to a deleted package version](/assets/images/help/package-registry/restore-package-version.png) +5. To confirm, click **I understand the consequences, restore this version.** + ![Confirm package version restoration](/assets/images/help/package-registry/confirm-package-version-restoration.png) diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md index 30ed07e1c5..1326fe9a6b 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -1,6 +1,6 @@ --- -title: Acerca de los dominios personalizados y las Páginas de GitHub -intro: '{% data variables.product.prodname_pages %} respalda el uso de dominios personalizados o el cambio la raíz de la URL del sitio desde el valor predeterminado, como `octocat.github.io`, para cualquier dominio que posea.' +title: About custom domains and GitHub Pages +intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.' redirect_from: - /articles/about-custom-domains-for-github-pages-sites/ - /articles/about-supported-custom-domains/ @@ -13,58 +13,58 @@ versions: ghec: '*' topics: - Pages -shortTitle: Dominios personalizados en GitHub Pages +shortTitle: Custom domains in GitHub Pages --- -## Dominios personalizados compatibles +## Supported custom domains -{% data variables.product.prodname_pages %} trabaja con dos tipos de dominios: subdominios y dominios apex. Para conocer un lista de los dominios personalizados compatibles, consulta "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)". +{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)." -| Tipo de dominio personalizado compatible | Ejemplo | -| ---------------------------------------- | ------------------ | -| Subdominio `www` | `www.example.com` | -| Subdominio personalizado | `blog.example.com` | -| Dominio apex | `example.com` | +| Supported custom domain type | Example | +|---|---| +| `www` subdomain | `www.example.com` | +| Custom subdomain | `blog.example.com` | +| Apex domain | `example.com` | -Puedes configurar cualquiera o ambos de los ajustes de subdominio de apex y de `www` para tu sitio. Para obtener más información sobre los dominios de apex, consulta la sección "[Utilizar un dominio de apex para tu sitio de {% data variables.product.prodname_pages %}](#using-an-apex-domain-for-your-github-pages-site)". +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." -Recomendamos siempre usar un subdominio `www`, incluso si también usas un dominio apex. Cuando creas un sitio nuevo con un dominio de apex, atuomáticamente intentamos asegurar el subdominio de `www` para utilizarlo cuando sirves el contenido de tu sitio. Si configuras un subdominio de `www`, automáticamente intentamos asegurar el dominio asociado de apex. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +We recommend always using a `www` subdomain, even if you also use an apex domain. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." -Después de que configuras un dominio personalizado para un usuario o sitio de organización, el dominio personalizado reemplazará a la porción de `.github.io` o `.github.io` de la URL para cualquier sitio de proyecto que pertenezca a la cuenta que no haya configurado un dominio personalizado. Por ejemplo, si el dominio personalizado para tu sitio de usuario es `www.octocat.com`, y tienes un sitio de proyecto sin un dominio personalizado configurado que se publica desde un repositorio denominado `octo-project`, el sitio {% data variables.product.prodname_pages %} para ese repositorio estará disponible en `www.octocat.com/octo-project`. +After you configure a custom domain for a user or organization site, the custom domain will replace the `.github.io` or `.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`. -## Uso de un subdominio para tu sitio {% data variables.product.prodname_pages %} +## Using a subdomain for your {% data variables.product.prodname_pages %} site -Un subdominio es la parte de una URL antes del dominio raíz. Puedes configurar tu subdominio como `www` o como una sección distinta de tu sitio, como `blog.example.com`. +A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`. -Los subdominios se configuran con un registro `CNAME` a través de su proveedor DNS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)". +Subdomains are configured with a `CNAME` record through your DNS provider. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)." -### Subdominios `www` +### `www` subdomains -Un subdominio `www` es el tipo de subdominio más usado comúnmente. Por ejemplo, `www.example.com` incluue un subdominio `www`. +A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain. -Los subdominios `www` son el tipo de dominio personalizado m ás estable porque los subdominios `www` no están afectados por los cambios en las direcciones IP de los servidores de {% data variables.product.product_name %}. +`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers. -### Subdominios personalizados +### Custom subdomains -Un subdominio personalizado es un tipo de subdominio que no utiliza la variante estándar de `www`. Los subdominios personalizados se utilizan principalmente cuando se necesitan dos secciones distintas de su sitio. Por ejemplo, puedes crear un sitio llamado `blog.example.com` y personalizar esa sección independientemente de `www.example.com`. +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `www.example.com`. -## Uso de un dominio apex para tu sitio {% data variables.product.prodname_pages %} +## Using an apex domain for your {% data variables.product.prodname_pages %} site -Un dominio apex es un dominio personalizado que no contiene un subdominio, como `ejemplo.com`. Los dominios apex también son conocidos como dominios apex base, vacíos, desnudos, o de zona. +An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains. -Un dominio apex está configurado con un registro `A`, `ALIAS` o `ANAME` a través de su proveedor DNS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)". +An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)." -{% data reusables.pages.www-and-apex-domain-recommendation %} Para obtener más información, consulta la sección "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)". +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." -## Actualizar dominios personalizados cuando tu sitio de {% data variables.product.prodname_pages %} está inhabilitado +## Securing the custom domain for your {% data variables.product.prodname_pages %} site -Si tu sitio {% data variables.product.prodname_pages %} no está habilitado pero tiene configurado un dominio personalizado, inmediatamente deberías actualizar o eliminar tus registros de DNS para evitar el riesgo de una adquisición de dominio. La configuración de tu dominio personalizado con tu proveedor DNS mientras tu sitio está inhabilitado, podría hacer que alguien más aloje un sitio en un o de tus subdominios. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." -Existen algunos motivos por los que tu sitio pueda estar inhabilitado automáticamente. +There are a couple of reasons your site might be automatically disabled. -- Si bajaste de categoría de {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, todos los sitios de {% data variables.product.prodname_pages %} que se publicaron actualmente desde repositorios privados en tu cuenta quedarán sin publicar. Para obtener más información, consulta "[Bajar de categoría tu plan de facturación de {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-billing-plan)". -- Si transfieres a un repositorio privado a una cuenta personal que está usando {% data variables.product.prodname_free_user %}, el repositorio perderá acceso a la función de {% data variables.product.prodname_pages %}, y el sitio de {% data variables.product.prodname_pages %} actualmente publicado, quedará sin publicar. Para obtener más información, consulta "[Transferir un repositorio](/articles/transferring-a-repository)". +- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)." +- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)." -## Leer más +## Further reading -- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" +- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md index b7cfe791cd..c51ebbe4fe 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -1,6 +1,6 @@ --- -title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub -intro: 'Puedes personalizar el nombre de dominio de tu sitio de {% data variables.product.prodname_pages %}.' +title: Configuring a custom domain for your GitHub Pages site +intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.' redirect_from: - /articles/tips-for-configuring-an-a-record-with-your-dns-provider/ - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site/ @@ -20,7 +20,8 @@ topics: children: - /about-custom-domains-and-github-pages - /managing-a-custom-domain-for-your-github-pages-site + - /verifying-your-custom-domain-for-github-pages - /troubleshooting-custom-domains-and-github-pages -shortTitle: Configurar un dominio personalizado +shortTitle: Configure a custom domain --- diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md index b6d9287fd5..e656dccca5 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -1,6 +1,6 @@ --- -title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub -intro: 'Puedes configurar o actualizar determinados registros DNS y las configuraciones de tu repositorio para que apunten el dominio predeterminado de tu sitio de {% data variables.product.prodname_pages %} a un dominio personalizado.' +title: Managing a custom domain for your GitHub Pages site +intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.' redirect_from: - /articles/quick-start-setting-up-a-custom-domain/ - /articles/setting-up-an-apex-domain/ @@ -17,40 +17,41 @@ versions: ghec: '*' topics: - Pages -shortTitle: Administra un dominio personalizado +shortTitle: Manage a custom domain --- -Las personas con permisos de administración para un repositorio pueden configurar un dominio personalizado para un sitio de {% data variables.product.prodname_pages %}. +People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site. -## Acerca de la configuración de dominios personalizados +## About custom domain configuration -Asegúrate de agregar tu dominio personalizado al sitio de {% data variables.product.prodname_pages %} antes de configurar el dominio personalizado con tu proveedor DNS. Configurar tu dominio personalizado con tu proveedor DNS sin agregar tu dominio personalizado a {% data variables.product.product_name %} podría dar como resultado que alguien aloje un sitio en uno de tus subdominios. +Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains. {% windows %} -El comando `dig`, que se puede usar para verificar la correcta configuración de los registros DNS, no está incluido en Windows. Antes de poder verificar que tus registros DNS estén configurados correctamente, debes instalar [BIND](https://www.isc.org/bind/). +The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/). {% endwindows %} {% note %} -**Nota:** Los cambios DNS pueden tardar hasta 24 horas en propagarse. +**Note:** DNS changes can take up to 24 hours to propagate. {% endnote %} -## Configurar un subdominio +## Configuring a subdomain -Para configurar un subdominio personalizado o de `www` tal como `www.example.com` o `blog.example.com`, debes agregar tu dominio en la configuración de repositorio, el cual creará un archivo de CNAME en el repositorio de tu sitio. Después de esto, configura un registro de CNAME con tu proveedor de DNS. +To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider. {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -4. Debajo de "Dominio personalizado", teclea tu dominio personalizado y luego da clic en **Guardar**. Esto creará una confirmación que agregará un archivo _CNAME_ en la raíz de tu fuente de publicación. ![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-subdomain.png) -5. Desplázate hasta tu proveedor DNS y crea un registro `CNAME` que apunte tu subdominio al dominio predeterminado de tu sitio. Por ejemplo, si quieres usar el subdominio `www.example.com` para tu sitio de usuario, crea un registro `CNAME` que apunte `www.example.com` a `.github.io`. Si quieres utilizar el subdominio `www.anotherexample.com` para el sitio de tu organización, crea un registro de `CNAME` que apunte a `www.anotherexample.com` hacia `.github.io`. El registro `CNAME` siempre deberá apuntar hacia `.github.io` o `.github.io`, excluyendo el nombre del repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. + ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png) +5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `.github.io`. The `CNAME` record should always point to `.github.io` or `.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} {% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %} -6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _WW.EXAMPLE.COM_ por tu subdominio. +6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain. ```shell $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd > ;WWW.EXAMPLE.COM. IN A @@ -61,26 +62,27 @@ Para configurar un subdominio personalizado o de `www` tal como `www.example.com {% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %} -## Configurar un dominio apex +## Configuring an apex domain -Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un archivo _CNAME_ en tu repositorio de {% data variables.product.prodname_pages %} y por lo menos un registro de `ALIAS`, `ANAME`, o `A` con tu proveedor de DNS. +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. -{% data reusables.pages.www-and-apex-domain-recommendation %} Para obtener más información, consulta la sección "[Configurar un subdominio](#configuring-a-subdomain)". +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -4. Debajo de "Dominio personalizado", teclea tu dominio personalizado y luego da clic en **Guardar**. Esto creará una confirmación que agregará un archivo _CNAME_ en la raíz de tu fuente de publicación. ![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-apex-domain.png) -5. Desplázate hasta tu proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. También puedes crear registros de `AAAA` para compatibilidad con IPv6. {% data reusables.pages.contact-dns-provider %} - - Para crear un registro `ALIAS` o `ANAME`, apunta tu dominio apex al dominio predeterminado de tu sitio. {% data reusables.pages.default-domain-information %} - - Para crear registros `A`, apunta tu dominio apex a las direccioens IP de {% data variables.product.prodname_pages %}. +4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. + ![Save custom domain button](/assets/images/help/pages/save-custom-apex-domain.png) +5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %} + - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %} + - To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}. ```shell 185.199.108.153 185.199.109.153 185.199.110.153 185.199.111.153 ``` - - Para crear registros de `AAAA`, apunta tu dominio de apex a la dirección IP para {% data variables.product.prodname_pages %}. + - To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}. ```shell 2606:50c0:8000::153 2606:50c0:8001::153 @@ -90,8 +92,8 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar {% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %} -6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _EXAMPLE.COM_ por tu dominio apex. Confirma que los resultados coincidan con las direcciones IP de las {% data variables.product.prodname_pages %} que aparecen arriba. - - Para los registros de `A`. +6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above. + - For `A` records. ```shell $ dig EXAMPLE.COM +noall +answer -t A > EXAMPLE.COM 3600 IN A 185.199.108.153 @@ -99,7 +101,7 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar > EXAMPLE.COM 3600 IN A 185.199.110.153 > EXAMPLE.COM 3600 IN A 185.199.111.153 ``` - - Para los registros de `AAAA`. + - For `AAAA` records. ```shell $ dig EXAMPLE.COM +noall +answer -t AAAA > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8000::153 @@ -110,16 +112,16 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar {% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %} -## Configurar un dominio de apex y la variante de subdominio `www` +## Configuring an apex domain and the `www` subdomain variant -Cuando utilizas un dominio apex, te recomendamos configurar tu sitio de {% data variables.product.prodname_pages %} para hospedar contenido tanto en el dominio de apex como en la variante de subdominio `www`. +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. -Para configurar un subdominio `www` junto con el dominio de apex, primero debes configurar un dominio de apex, el cual creará un `ALIAS`, `NOMBRE` o registro `A` con tu proveedor de DNS. Para obtener más información, consulta la sección [Configurar un dominio de apex](#configuring-an-apex-domain)". +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." -Después de configurar el domnio apex, debes configurar un registro de CNAME con tu proveedor de DNS. +After you configure the apex domain, you must configure a CNAME record with your DNS provider. -1. Navega a tu proveedor de DNS y crea un registro de `CNAME` que apunte a `www.example.com` al dominio predeterminado de tu sitio: `.github.io` o `.github.io`. No incluyas el nombre de repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} -2. Para confirmar que tu registro de DNS se configuró correctamente, utiliza el comando `dig`, reemplazando a _WWW.EXAMPLE.COM_ con tu variante de subdominio `www`. +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. ```shell $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd > ;WWW.EXAMPLE.COM. IN A @@ -127,13 +129,18 @@ Después de configurar el domnio apex, debes configurar un registro de CNAME con > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER . > GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1 ``` -## Eliminar un dominio personalizado +## Removing a custom domain {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -4. Debajo de "Dominio personalizado", haz clic en **Eliminar**. ![Botón de guardar dominio personalizado](/assets/images/help/pages/remove-custom-domain.png) +4. Under "Custom domain," click **Remove**. + ![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png) -## Leer más +## Securing your custom domain -- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" +{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." + +## Further reading + +- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md index 3951a3d365..ef31967c41 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -1,6 +1,6 @@ --- -title: Solucionar problemas de dominios personalizados y Páginas de GitHub -intro: 'Puedes buscar errores comunes para resolver los problemas que existan con los dominios personalizados o HTTPS para tu sitio de {% data variables.product.prodname_pages %}.' +title: Troubleshooting custom domains and GitHub Pages +intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.' redirect_from: - /articles/my-custom-domain-isn-t-working/ - /articles/custom-domain-isn-t-working/ @@ -13,58 +13,58 @@ versions: ghec: '*' topics: - Pages -shortTitle: Solucionar problemas de un dominio personalizado +shortTitle: Troubleshoot a custom domain --- -## Errores _CNAME_ +## _CNAME_ errors -Los dominios personalizados se almacenan en un archivo _CNAME_ en la raíz de tu fuente de publicación. Puedes agregar o actualizar este archivo a través de la configuración del repositorio o manualmente. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." -Para que tu sitio se represente en el dominio correcto, asegúrate de que el archivo _CNAME_ aún exista en el repositorio. Por ejemplo, muchos generadores de sitios estáticos realizan empujes forzados a tu repositorio, que pueden sobrescribir el archivo _CNAME_ que se agregó a tu repositorio cuando configuraste tu dominio personalizado. Si compilas tu sitio localmente y subes los archivos generados a {% data variables.product.product_name %}, asegúrate de extraer primero la confirmación que agregó el archivo _CNAME_ a tu repositorio local. De este modo, el archivo se incluirá en la compilación. +For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build. -Luego, asegúrate de que el archivo _CNAME_ tenga el formato correcto. +Then, make sure the _CNAME_ file is formatted correctly. -- El nombre de archivo _CNAME_ debe estar todo en mayúsculas. -- El archivo _CNAME_ puede contener solo un dominio. Para apuntar múltiples dominios a tu sitio, debes configurar un redireccionamiento a través de tu proveedor DNS. -- El archivo _CNAME_ debe contener únicamente el nombre del dominio. Por ejemplo, `www.example.com`, `blog.example.com`, o `example.com`. -- El nombre de dominio debe ser único a lo largo de todos los sitios de {% data variables.product.prodname_pages %}. Por ejemplo, si el archivo _CNAME_ de otro repositorio contiene `example.com`, no puedes usar `example.com` en el archivo _CNAME_ para tu repositorio. +- The _CNAME_ filename must be all uppercase. +- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider. +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository. -## Error de configuración DNS +## DNS misconfiguration -Si tienes problemas para apuntar el dominio predeterminado para tu sitio a tu dominio personalizado, contáctate con tu proveedor DNS. +If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider. -También puedes utilizar uno de los siguientes métodos para probar si los registros de DNS de tus dominios personalizados están configurados correctamente: +You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly: -- Una herramienta de CLI tal como `dig`. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". -- Una herramienta de búsqueda de DNS en línea. +- A CLI tool such as `dig`. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)". +- An online DNS lookup tool. -## Nombres de dominios personalizados que no son compatibles +## Custom domain names that are unsupported -Si tu dominio personalizado no es compatible, puede que debas cambiar tu dominio a un dominio compatible. También te puedes contactar con tu proveedor DNS para ver si ofrece servicios de reenvío para los nombres de dominio. +If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names. -Asegúrate de que en tu sitio no ocurra lo siguiente: -- Uso de más de un dominio apex. Por ejemplo, `example.com` y `anotherexample.com`. -- Uso de más de un subdominio `www`. Por ejemplo, `www.example.com` y `www.anotherexample.com`. -- Uso de un dominio apex y de un subdominio personalizado. Por ejemplo, `example.com` y `docs.example.com`. +Make sure your site does not: +- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`. +- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`. +- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`. - La única exepción es el subdominio `www`. Si se configura correctamente, el subdominio `www` se redirigirá automáticamente al dominio apex. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)". + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)." {% data reusables.pages.wildcard-dns-warning %} -Para obtener una lista de dominios personalizados que son compatibles, consulta "[Acerca de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)". +For a list of supported custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)." -## Errores HTTPS +## HTTPS errors -A los sitios {% data variables.product.prodname_pages %} que utilizan dominios personalizados que no están configurados de manera correcta con _CNAME_, `ALIAS`, `ANAME` o registros DNS `A` se puede acceder por HTTPS. Para obtener más información, consulta "[Asegurar tu sitio de {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)". +{% data variables.product.prodname_pages %} sites using custom domains that are correctly configured with `CNAME`, `ALIAS`, `ANAME`, or `A` DNS records can be accessed over HTTPS. For more information, see "[Securing your {% data variables.product.prodname_pages %} site with HTTPS](/articles/securing-your-github-pages-site-with-https)." -Puede tardar hasta una hora que tu sitio se vuelva disponible a través de HTTPS una vez que configures tu dominio personalizado. Después de actualizar los ajustes DNS existentes, puede que debas eliminar y volver a agregar tu dominio personalizado a tu repositorio del sitio para activar el proceso de habilitación HTTPS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." -Si estás usando registros de Autorización de la Autoridad de Certificación (CAA), debe existir al menos un registro CAA con el valor `letsencrypt.org` para que tu sitio sea accesible a través de HTTPS. Para obtener más información, consulta "[Autorización de la Autoridad de Certificado (CAA)](https://letsencrypt.org/docs/caa/)" en la documentación de Let's Encrypt. +If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value `letsencrypt.org` for your site to be accessible over HTTPS. For more information, see "[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)" in the Let's Encrypt documentation. -## Formato de URL en Linux +## URL formatting on Linux -Si la URL de tu sitio contiene un nombre de usuario o nombre de organización que comienza o termina con un guion, o que contiene guiones consecutivos, las personas que naveguen con Linux recibirán un error del servidor cuando traten de visitar tu sitio. Para corregir esto, cambia tu nombre de usuario de {% data variables.product.product_name %} y elimina cualquier caracter que no sea alfanumérico. Para obtener más información, consulta [Cambiar tu {% data variables.product.prodname_dotcom %} nombre de usuario](/articles/changing-your-github-username/)" +If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.product_name %} username to remove non-alphanumeric characters. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username/)." -## Caché del navegador +## Browser cache -Si has cambiado o eliminado recientemente tu dominio personalizado y no puedes acceder a la URL nueva en tu navegador, puede que debas limpiar el caché de tu navegador para llegar a la URL nueva. Para obtener más información acerca de limpiar tu caché, consulta la documentación de tu navegador. +If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation. diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md index 6d3c2e2532..f91b09f0ad 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -1,5 +1,5 @@ --- -title: Acerca de GitHub Pages +title: About GitHub Pages intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' redirect_from: - /articles/what-are-github-pages/ @@ -20,111 +20,107 @@ topics: - Pages --- -## Acerca de {% data variables.product.prodname_pages %} +## About {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} es un servicio de alojamiento de sitio estático que toma archivos HTML, CSS y JavaScript directamente desde un repositorio en {% data variables.product.product_name %}, opcionalmente ejecuta los archivos a través de un proceso de complilación y publica un sitio web. Puedes ver ejemplos de sitios de {% data variables.product.prodname_pages %} en la recopilación de ejemplos de [{% data variables.product.prodname_pages %}](https://github.com/collections/github-pages-examples). +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). {% ifversion fpt or ghec %} -Puedes alojar tu sitio en el dominio `github.io` de {% data variables.product.prodname_dotcom %} o en tu propio dominio personalizado. Para obtener más información, consulta "[Utilizar un dominio personalizado con {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)". +You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." {% endif %} {% ifversion fpt or ghec %} -{% data reusables.pages.about-private-publishing %} Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." {% endif %} -Para empezar, vea "[Creando un sitio {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)." +To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." {% ifversion fpt or ghes > 3.0 or ghec %} -Los propietarios de la organización pueden inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios de la organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} -## Tipos de sitios {% data variables.product.prodname_pages %} +## Types of {% data variables.product.prodname_pages %} sites -Existen tres tipos básicos de {% data variables.product.prodname_pages %} sitios: de proyecto, de usuario y de la organización. Los sitios de proyecto están conectados coon un proyecto específico alojado en {% data variables.product.product_name %}, como una biblioteca JavaScript o una colección de recetas. User and organization sites are connected to a specific account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. -Para publicar un sitio de usuario, debes crear un repositorio que pertenezca a tu cuenta de usuario que se llame {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. Para publicar un sitio de organización debes crear un repositorio que pertenezca a una organización y que se llame {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}A menos de que estés utilizando un dominio personalizado, los sitios de usuario y de organización se encuentran disponibles en `http(s)://.github.io` o `http(s)://.github.io`.{% elsif ghae %}los sitios de organizaciones y usuarios se encuentran disponibles en `http(s)://pages./` o `http(s)://pages./`.{% endif %} +To publish a user site, you must create a repository owned by your user account that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}Unless you're using a custom domain, user and organization sites are available at `http(s)://.github.io` or `http(s)://.github.io`.{% elsif ghae %}User and organization sites are available at `http(s)://pages./` or `http(s)://pages./`.{% endif %} -Los archivos fuente para un sitio de proyecto se almacenan en el mismo repositorio que su proyecto. {% ifversion fpt or ghec %}A menos de que estés utilizando un dominio personalizado, los sitios de proyecto se encuentran disponibles en `http(s)://.github.io/` o `http(s)://.github.io/`.{% elsif ghae %}Los sitios de proyecto se encuentran disponibles en `http(s)://pages.///` o `http(s)://pages.///`.{% endif %} +The source files for a project site are stored in the same repository as their project. {% ifversion fpt or ghec %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif ghae %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} {% ifversion fpt or ghec %} -Si publicas tu sitio de forma privada, la URL de éste será diferente. Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." {% endif %} {% ifversion fpt or ghec %} -Para obtener más información sobre cómo los dominios personalizados afectan a la URL de tu sitio, consulta "[Acerca de los dominios personalizados y {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". +For more information about how custom domains affect the URL for your site, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)." {% endif %} -Solo puedes crear un sitio de organización o de usuario para cada cuenta en {% data variables.product.product_name %}. Los sitios de proyectos, ya sean propiedad de una cuenta de organización de de usuario, son ilimitados. +You can only create one user or organization site for each account on {% data variables.product.product_name %}. Project sites, whether owned by an organization or a user account, are unlimited. {% ifversion ghes %} -La URL donde tu sitio está disponible depende de si el aislamiento del subdominio está habilitado para {% data variables.product.product_location %}. +The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.product.product_location %}. -| Tipo de sitio | Aislamiento de subdominio habilitado | Aislamiento de subdominio inhabilitado | -| ------------- | ------------------------------------ | -------------------------------------- | -| | | | - Usuario| +| Type of site | Subdomain isolation enabled | Subdomain isolation disabled | +| ------------ | --------------------------- | ---------------------------- | +User | `http(s)://pages./` | `http(s):///pages/` | +Organization | `http(s)://pages./` | `http(s):///pages/` | +Project site owned by user account | `http(s)://pages.///` | `http(s):///pages///` +Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` -`http(s)://pages./` | `http(s):///pages/` | Organización| `http(s)://pages./` | `http(s):///pages/` | Sitio de proyecto que pertenece a una cuenta de usuario | `http(s)://pages.///` | `http(s):///pages///` Sitio de proyecto que pertenece a una cuenta de organización | `http(s)://pages.///` | `http(s):///pages///` - -Para obtener más información, consulta la sección "[Habilitar el aislamiento del subdominio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" o contacta a tu administrador de sitio. +For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} -## Publicar fuentes para sitios {% data variables.product.prodname_pages %} +## Publishing sources for {% data variables.product.prodname_pages %} sites -La fuente de publicación para tu sitio de {% data variables.product.prodname_pages %} es la rama y carpeta en donde se almacenan los archivos fuente de tu sitio. +The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored. {% data reusables.pages.private_pages_are_public_warning %} -Si la fuente de publicación predeterminada existe en tu repositorio, {% data variables.product.prodname_pages %} publicará automáticamente un sitio desde esta fuente. La fuente de publicación predeterminada para los sitios de usuario y de organización es la raíz de la rama predeterminada para el repositorio. La fuente de publicación predeterminada para los sitios de proyecto es la raíz de la rama `gh-pages`. +If the default publishing source exists in your repository, {% data variables.product.prodname_pages %} will automatically publish a site from that source. The default publishing source for user and organization sites is the root of the default branch for the repository. The default publishing source for project sites is the root of the `gh-pages` branch. -Si quieres mantener los archivos fuente para tu sitio en una ubicación distinta, puedes cambiar la fuente de publicación para tu sitio. Puedes publicar tu sitio desde cualquier rama en el repositorio, ya sea desde la raíz del repositorio en esa rama, `/`, o desde la carpeta de `/docs` en ella. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". +If you want to keep the source files for your site in a different location, you can change the publishing source for your site. You can publish your site from any branch in the repository, either from the root of the repository on that branch, `/`, or from the `/docs` folder on that branch. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." -Si eliges la carpeta de `/docs` o cualquier rama como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% ifversion fpt or ghec %}, incluyendo el archivo _CNAME_,{% endif %} desde la carpeta de `/docs`.{% ifversion fpt or ghec %} Por ejemplo, cuando editas tu dominio personalizado a través de la configuración de {% data variables.product.prodname_pages %}, dicho dominio escribirá en `/docs/CNAME`. Para más información sobre los archivos _CNAME_, consulta "[Administrar un dominio personalizado para tu sitio {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} +If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% ifversion fpt or ghec %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% ifversion fpt or ghec %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} -## Generadores de sitios estáticos +## Static site generators -{% data variables.product.prodname_pages %} publica cualquier archivo estático que subas a tu repositorio. Puedes crear tus propios archivos estáticos o usar un generador de sitios estáticos para que desarrolle tu sitio. También puedes personalizar tu propio proceso de compilación de forma local o en otro servidor. Recomendamos Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %} y un proceso de compilación simplificado. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %} y de Jekyll](/articles/about-github-pages-and-jekyll)". +{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." -{% data variables.product.prodname_pages %} usará Jekyll para compilar tu sitio por defecto. Si deseas usar un generador de sitio estático diferente a Jekyll, desactiva el proceso de compilación de Jekyll creando un archivo vacío denominado `en la raíz de tu fuente de publicación, luego seguir las instrucciones del generador de sitio estático para desarrollar tu sitio localmente.

    +{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. -

    {% data variables.product.prodname_pages %} no soporta idiomas del lado del servidor como PHP, Ruby o Python.

    +{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. -

    Guías para usar {% data variables.product.prodname_pages %}

    +## Limits on use of {% data variables.product.prodname_pages %} -

    {% ifversion fpt or ghec %}

    - -
      -
    • los sitios {% data variables.product.prodname_pages %} creados después del 15 de junio de 2016 y utilizando dominios github.io` se brindan a través de HTTPS. Si creaste tu sitio antes del 15 de junio de 2016, puedes habilitar el soporte HTTPS para el tráfico hasta tu sitio. Para obtener más información, consulta "[Asegurar tu {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)".
      • -- {% data reusables.pages.no_sensitive_data_pages %} -- Tu uso de {% data variables.product.prodname_pages %} está sujeto a los [Términos del servicio de GitHub](/free-pro-team@latest/github/site-policy/github-terms-of-service/), incluida la prohibición de reventa.
    - -### Límites de uso -{% endif %} -los sitios {% data variables.product.prodname_pages %} están sujetos a los siguientes límites de uso: - - - Los repositorios de fuente de {% data variables.product.prodname_pages %} tienen un límite recomendado de 1 GB.{% ifversion fpt or ghec %} Para más información, consulta "[¿Cuál es la cuota de mi disco?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} - - Los sitios de {% data variables.product.prodname_pages %} publicados no pueden ser mayores a 1 GB. {% ifversion fpt or ghec %} - - Los sitios de {% data variables.product.prodname_pages %} tienen un ancho de banda *virtual* de 100GB por mes. - - Los sitios de {% data variables.product.prodname_pages %} tienen un límite *virtual* de 10 compilaciones por hora. +{% data variables.product.prodname_pages %} sites created after June 15, 2016 and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)." -Si tu sitio excede estas cuotas de uso, es posible que no podamos prestar servicio a tu sitio, o puedes recibir un correo electrónico formal de {% data variables.contact.contact_support %} sugiriendo estrategias para reducir el impacto de tu sitio en nuestros servidores, lo que incluye poner una red de distribución de contenido de un tercero (CDN) al frente de tu sitio, usar las otras características de {% data variables.product.prodname_dotcom %}, como lanzamientos, o mudar a un servicio de alojamiento diferente que pueda satisfacer mejor tus necesidades. +### Prohibited uses +{% endif %} +{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). {% data reusables.pages.no_sensitive_data_pages %} -### Usos prohibidos +In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/), including the restrictions on get rich quick schemes, sexually obscene content, and violent or threatening content or activity. -{% data variables.product.prodname_pages %} no pretende ser un servicio de alojamiento web gratuito ni permite que se use de ese modo para realizar tus negocios en línea, un sitio de comercio electrónico, o cualquier otro sitio web que esté principalmente dirigido a facilitar las operaciones comerciales o brindar software comercial como un servicio (SaaS). +### Usage limits +{% data variables.product.prodname_pages %} sites are subject to the following usage limits: + + - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% ifversion fpt or ghec %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} + - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. +{% ifversion fpt or ghec %} + - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100GB per month. + - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour. + +If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. -Adicionalmente, {% data variables.product.prodname_dotcom %} no permite que se utilicen las {% data variables.product.prodname_pages %} para algunos propósitos o actividades específicos. Para encontrar una lista de usos prohibidos, consulta la sección "[Condiciones adicionales de producto de {% data variables.product.prodname_dotcom %} para las {% data variables.product.prodname_pages %}](/free-pro-team@latest/github/site-policy/github-terms-for-additional-products-and-features#pages)". {% endif %} -## Tipos MIME en {% data variables.product.prodname_pages %} +## MIME types on {% data variables.product.prodname_pages %} -Un tipo MIME es un encabezado que un servidor envía a un navegador, proporcionando información sobre la naturaleza y el formato de los archivos que solicitó el navegador. {% data variables.product.prodname_pages %} soporta más de 750 tipos MIME entre las miles de extensiones de archivo. La lista de los tipos de MIME compatibles se genera desde el [mime-db project](https://github.com/jshttp/mime-db). +A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). -Si bien no puedes especificar los tipos de MIME personalizados en una base por perfil o por repositorio, puedes agregar o modificar los tipos de MIME para usar en {% data variables.product.prodname_pages %}. Para obtener más información, consulta [los lineamientos de contribución de mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types). +While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). -## Leer más +## Further reading -- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) en {% data variables.product.prodname_learning %} +- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index e517bb92c0..0a8646cfee 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -1,6 +1,6 @@ --- -title: Acerca de los errores de compilación para sitios de Páginas de GitHub -intro: 'Si Jekyll encuentra un error al compilar tu sitio de {% data variables.product.prodname_pages %} localmente o en {% data variables.product.product_name %}, recibirás un mensaje de error con más información.' +title: About Jekyll build errors for GitHub Pages sites +intro: 'If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you''ll receive an error message with more information.' redirect_from: - /articles/viewing-jekyll-build-error-messages/ - /articles/generic-jekyll-build-failures/ @@ -14,51 +14,51 @@ versions: ghec: '*' topics: - Pages -shortTitle: Errores de compilación de Jekyll para las páginas +shortTitle: Jekyll build errors for Pages --- -## Acerca de los errores de compilación de Jekyll +## About Jekyll build errors -Algunas veces, {% data variables.product.prodname_pages %} no intentará compilar tu sitio después de que subas los cambios a la fuente de publicación de tu sitio.{% ifversion fpt or ghec %} -- La persona que subió los cambios no ha verificado su dirección de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".{% endif %} -- Estás subiendo con una llave de despliegue. Si deseas automatizar las subidas al repositorio de tu sitio, puedes configurar un usuario de máquina en su lugar. Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys#machine-users)". -- Estás usando un servicio CI que no está configurado para compilar tu fuente de publicación. Por ejemplo, Travis CI no creará la rama `gh-pages` a menos de que agregues la rama a una lista de seguridad. Para obtener más información, consulta "[Personalizar la compilación](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" en Travis CI o en la documentación del servicio de CI. +Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% ifversion fpt or ghec %} +- The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} +- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." +- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation. {% note %} -**Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}. +**Note:** It can take up to 20 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. {% endnote %} -Si Jekyll intenta compilar tu sitio y encuentra un error, recibirás un mensaje de error de compilación. Hay dos tipos principales de mensajes de error de construcción de Jekyll. -- Un mensaje de "Aviso de compilación de página" significa que la compilación se ha completado correctamente, pero es posible que debas hacer cambios para prevenir problemas futuros. -- Un mensaje "Page build failed" (Falló la construcción de página) significa que no se pudo completar la compilación. Si Jekyll puede detectar el motivo de la falla, verás un mensaje de error descriptivo. +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. +- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. +- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. -Para obtener más información sobre cómo resolver errores de compilación, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)". +For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -## Ver mensajes de error de construcción de Jekyll +## Viewing Jekyll build error messages -Recomendamos probar su sitio localmente, lo que le permite ver mensajes de error de compilación en la línea de comandos, y abordar cualquier fallo de construcción antes de presionar los cambios a {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". +We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." -Cuando creas una solicitud de extracción para actualizar tu fuente de publicación en {% data variables.product.product_name %}, puedes ver los mensajes de error de compilación en la pestaña **Checks** (Comprobaciones) de la solicitud de extracción. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/articles/about-status-checks)". +When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." -Cuando subas los cambios a tu fuente de publicación en {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} intentará compilar tu sitio. Si se produce un error durante la compilación, recibirás un corro electrónico en tu dirección principal de correo electrónico. También recibirás correos electrónicos para advertencias de compilación. {% data reusables.pages.build-failure-email-server %} +When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} -Puedes ver errores de compilación (pero no advertencias de compilación) para tu sitio en {% data variables.product.product_name %} en la pestaña **Settings** (Configuración) del repositorio de tu sitio. +You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. -Puedes configurar un servicio externo como [Travis CI](https://travis-ci.org/) para que muestre mensajes de error después de cada confirmación. +You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit. -1. Si no lo has hecho, agrega un archivo denominado _Gemfile_ en la raíz de tu fuente de publicación, con el siguiente contenido: +1. If you haven't already, add a file called _Gemfile_ in the root of your publishing source, with the following content: ```ruby source `https://rubygems.org` gem `github-pages` ``` -2. Configura el repositorio de tu sitio para el servicio de comprobación que elijas. Por ejemplo, para usar [Travis CI](https://travis-ci.org/), agrega un archivo denominado _.travis.yml_ en la raíz de tu fuente de publicación, con el siguiente contenido: +2. Configure your site's repository for the testing service of your choice. For example, to use [Travis CI](https://travis-ci.org/), add a file named _.travis.yml_ in the root of your publishing source, with the following content: ```yaml language: ruby rvm: - 2.3 script: "bundle exec jekyll build" ``` -3. Es posible que necesites activar tu repositorio con el servicio de comprobación de terceros. Para obtener más información, consulta la documentación del servicio de comprobación. +3. You may need to activate your repository with the third-party testing service. For more information, see your testing service's documentation. diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md index dda139688d..c2529a41aa 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md @@ -35,7 +35,7 @@ If a site administrator disables the merge conflict editor for pull requests bet {% tip %} - **Tip:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line." + **Tip:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)." {% endtip %} {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 6531ae0ad6..04002cc4a8 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -21,7 +21,7 @@ topics: **Note:** When working with pull requests, keep the following in mind: * If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes. -* When pushing commits to a pull request, don't force push. Force pushing can corrupt your pull request. +* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md index 4495c57188..613caee543 100644 --- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md +++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md @@ -84,7 +84,7 @@ $ git fetch upstream recover-B ## Avoid force pushes -Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. +Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests. ## Further reading diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md index 17e213900a..174f9b028d 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Configurar combinación de confirmaciones para las solicitudes de extracción -intro: 'Puedes hacer cumplir, permitir o inhabilitar combinaciones de confirmación para todas las fusiones de las solicitudes de extracción en {% data variables.product.product_location %} en tu repositorio.' +title: Configuring commit squashing for pull requests +intro: 'You can enforce, allow, or disable commit squashing for all pull request merges on {% data variables.product.product_location %} in your repository.' redirect_from: - /articles/configuring-commit-squashing-for-pull-requests - /github/administering-a-repository/configuring-commit-squashing-for-pull-requests @@ -12,19 +12,20 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Configurar la combinación de confirmaciones +shortTitle: Configure commit squashing --- - {% data reusables.pull_requests.configure_pull_request_merges_intro %} {% data reusables.pull_requests.default-commit-message-squash-merge %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. En "Merge button" (Fusionar botón), selecciona **Allow merge commits** (Permitir fusión de confirmaciones). Esto permite que los colaboradores fusionen una solicitud de extracción con un historial completo de confirmaciones. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png) -4. En "Merge button" (Fusionar botón), selecciona **Allow rebase merging** (Permitir fusión de combinación). Esto permite que los colaboradores fusionen una solicitud de extracción al combinar todas las confirmaciones en una confirmación única. Si seleccionas otro método de fusión además de **Allow squash merging** (Permitir combinación de fusiones), los colaboradores podrán elegir el tipo de confirmación de fusiones al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones combinadas de solicitudes de extracción](/assets/images/help/repository/pr-merge-squash.png) +3. Under "Merge button", optionally select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits. +![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png) +4. Under "Merge button", select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. If you select another merge method besides **Allow squash merging**, collaborators will be able to choose the type of merge commit when merging a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} +![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png) -## Leer más +## Further reading -- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" -- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" +- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)" +- "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md index 565b8363b2..371252c242 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -1,6 +1,6 @@ --- -title: Administrar la fusión automática para las solicitudes de cambios en tu repositorio -intro: Puedes permitir o dejar de permitir la fusión automática de solicitudes de cambio en tu repositorio. +title: Managing auto-merge for pull requests in your repository +intro: You can allow or disallow auto-merge for pull requests in your repository. product: '{% data reusables.gated-features.auto-merge %}' versions: fpt: '*' @@ -13,17 +13,17 @@ topics: redirect_from: - /github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository - /github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository -shortTitle: Administrar las fusiones automáticas +shortTitle: Manage auto merge --- +## About auto-merge -## Acerca de la fusión automática +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." -Si permites la fusión automática para las solicitudes de cambio en tu repositorio, las personas con permisos de escritura pueden configurar las solicitudes de extracción individuales en el repositorio para que se fusionen automáticamente cuando se cumplan todos los requisitos de fusión. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". - -## Administrar la fusión automática +## Managing auto-merge {% data reusables.pull_requests.auto-merge-requires-branch-protection %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Debajo de "Botón para fusionar", selecciona o deselecciona **Permitir la fusión automática**. ![Casilla de verificación para permitir o dejar de permitir la fusión automática](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) +1. Under "Merge button", select or deselect **Allow auto-merge**. + ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md index 441800ac8c..3c7a8eee83 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md @@ -1,6 +1,6 @@ --- -title: Administrar la eliminación automática de ramas -intro: Puedes hacer que se eliminen automáticamente ramas centrales después de que se fusionen solicitudes de extracción en tu repositorio. +title: Managing the automatic deletion of branches +intro: You can have head branches automatically deleted after pull requests are merged in your repository. redirect_from: - /articles/managing-the-automatic-deletion-of-branches - /github/administering-a-repository/managing-the-automatic-deletion-of-branches @@ -12,15 +12,15 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Borrado de rama automático +shortTitle: Automatic branch deletion --- - -Cualquier persona con permisos de administrador a un repositorio puede habilitar e inhabilitar la eliminación automática de ramas. +Anyone with admin permissions to a repository can enable or disable the automatic deletion of branches. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Dentro de "Merge button" (Botón fusionar), selecciona o deselecciona **Automatically delete head branches (Eliminar automáticamente ramas centrales)**. ![Casilla de verificación para habilitar o inhabilitar la eliminación automática de ramas](/assets/images/help/repository/automatically-delete-branches.png) +3. Under "Merge button", select or unselect **Automatically delete head branches**. + ![Checkbox to enable or disable automatic deletion of branches](/assets/images/help/repository/automatically-delete-branches.png) -## Leer más -- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" -- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" +## Further reading +- "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" +- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)" diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md index 5d307230c0..9d1c5e6711 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md @@ -24,7 +24,7 @@ Repository administrators can configure merge queues for pull requests targeting For information about how to enable the merge queue protection setting, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)." -## Leer más +## Further reading -- "[Adding a pull request to the merge queue](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)" -- "[Acerca de las ramas protegidas](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)" +- "[Adding a pull request to the merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)" +- "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)" diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index 347a34a707..6353932fb4 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -1,6 +1,6 @@ --- -title: Acerca de las ramas protegidas -intro: 'Puedes proteger las ramas importantes si configuras las reglas de protección de rama, las cuales definen si los colaboradores pueden borrar o hacer subidas forzadas a la rama y configura los requisitos para cualquier subida a la rama, tal como que pasen las verificaciones de estado o un historial de confirmaciones linear.' +title: About protected branches +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches @@ -25,118 +25,113 @@ versions: topics: - Repositories --- +## About branch protection rules -## Acerca de las reglas de protección de rama +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -Puedes requerir ciertos flujos de trabajo o requisitos antes de que un colaborador pueda subir los cambios a una rama en tu repositorio, incluyendo la fusión de una solicitud de cambios en la rama, si creas una regla de protección de rama. +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -Predeterminadamente, cada regla de protección de rama inhabilita las subidas forzadas en las ramas coincidentes y previene que éstas se borren. Opcionalmente, puedes inhabilitar estas restricciones y habilitar la configuración adicional de protección de ramas. +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. -Predeterminadamente, las restricciones de una regla de protección de rama no aplicarán a las personas con permisos administrativos en el repositorio. Opcionalmente, también puedes elegir el incluir administradores. - -{% data reusables.repositories.branch-rules-example %} Para obtener más información sobre los patrones de nombre de rama, consulta la sección "[Administrar una regla de protección de rama](/github/administering-a-repository/managing-a-branch-protection-rule)". +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -## Acerca de la configuración de protección de rama +## About branch protection settings -Para cada regla de protección de rama, puedes elegir habilitar o inhabilitar la siguiente configuración. -- [Requerir revisiones de solicitudes de cambio antes de fusionarlas](#require-pull-request-reviews-before-merging) -- [Requerir verificaciones de estado antes de las fusiones](#require-status-checks-before-merging) +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) {% ifversion fpt or ghes > 3.1 or ghae-issue-4382 or ghec %} -- [Requiere que haya resolución en las conversaciones antes de la fusión](#require-conversation-resolution-before-merging){% endif %} -- [Requerir confirmaciones firmadas](#require-signed-commits) -- [Requerir un historial linear](#require-linear-history) +- [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %} +- [Require signed commits](#require-signed-commits) +- [Require linear history](#require-linear-history) {% ifversion fpt or ghec %} - [Require merge queue](#require-merge-queue) {% endif %} -- [Incluir administradores](#include-administrators) -- [Restringir quiénes pueden subir a las ramas coincidentes](#restrict-who-can-push-to-matching-branches) -- [Permitir las subidas forzadas](#allow-force-pushes) -- [Permitir el borrado](#allow-deletions) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) -Para obtener más información sobre cómo configurar la protección de ramas, consulta la sección "[Administrar la regla de protección de ramas](/github/administering-a-repository/managing-a-branch-protection-rule)". +For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." -### Requerir revisiones de solicitudes de cambio antes de fusionarlas +### Require pull request reviews before merging {% data reusables.pull_requests.required-reviews-for-prs-summary %} -Si habilitas las revisiones requeridas, los colaboradores solo podrán subir los cambios a una rama protegida a través de una solicitud de cambios que se encuentre aprobada por el total de revisores requeridos con permisos de escritura. +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. -Si una persona con permisos administrativos elige la opción **Solicitar cambios** en una revisión, entonces deberá aprobar la solicitud de cambios antes de que se pueda fusionar. Si un revisor que solicita cambios en una solicitud de cambios no está disponible, cualquiera con permisos de escritura para el repositorio podrá descartar la revisión que está haciendo el bloqueo. +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. {% data reusables.repositories.review-policy-overlapping-commits %} -Si un colaborador intenta fusionar una solicitud de cambios con revisiones rechazadas o pendientes en la rama protegida, el colaborador recibirá un mensaje de error. +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. ```shell remote: error: GH006: Protected branch update failed for refs/heads/main. remote: error: Changes have been requested. ``` -Opcionalmente, puedes elegir descartar las aprobaciones de la solicitud de cambios estancada cuando se suban las confirmaciones. Si cualquiera sube una confirmación que modifique el código de una solicitud de cambios aprobada, la aprobación se descartará y la solicitud de cambios no podrá fusionarse. Esto no aplicará si el colaborador sube confirmaciones que no modifiquen el código, como fusionar la rama base en la rama de la solicitud de cambios. Para obtener información acerca de las ramas base, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Opcionalmente, puedes restringir la capacidad para descartar las revisiones de las solicitudes de cambio para que solo puedan hacerlas algunos equipos o personas específicos. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." -Opcionalmente, puedes elegir el requerir revisiones de los propietarios del código. Si lo haces, el propietario de código deberá aprobar cualquier solicitud de cambios que afecte dicho código antes de que la solicitud de cambios pueda fusionarse en la rama protegida. +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. -### Requerir verificaciones de estado antes de las fusiones +### Require status checks before merging -Las verificaciones de estado requeridas garantizan que todas las pruebas de integración continua (CI) requeridas sean aprobadas antes de que los colaboradores puedan realizar cambios en una rama protegida. Para obtener más información, consulta "[Configurar ramas protegidas](/articles/configuring-protected-branches/)" y "[Activar verificaciones de estado requeridas](/articles/enabling-required-status-checks)". Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/github/collaborating-with-issues-and-pull-requests/about-status-checks)". +Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." -Antes de que puedas habilitar las verificaciones de estado requeridas, debes configurar el repositorio para utilizar la API de estado. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#statuses)" en la documentación de REST. +Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. -Después de habilitar las verificaciones de estado requierdas, cualquier verificación de estado deberá pasar antes de que los colaboradores puedan fusionar los cambios en la rama protegida. Una vez que hayan pasado todas las verificaciones de estado requeridas, cualquier confirmación deberá ya sea subirse en otra rama y después fusionarse, o subirse directo a la rama protegida. +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch. -{% note %} +Any person or integration with write permissions to a repository can set the state of any status check in the repository, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates. If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box. -**Nota:** Cualquier persona o integración con permisos de escritura en un repositorio puede establecer el estado de cualquier comprobación de estado en el repositorio. {% data variables.product.company_short %} no verifica que el autor de una comprobación está autorizado para crear un determinado nombre o modificar un estado existente. Antes de fusionar una solicitud de extracción, deberás verificar que se esté esperando al autor de cada estado, los cuales se encuentran listados en la caja de fusión. +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging. -{% endnote %} +| Type of required status check | Setting | Merge requirements | Considerations | +| --- | --- | --- | --- | +| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.| +| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. -Puedes configurar las verificaciones de estado requeridas para que sean "laxas" o "estrictas". El tipo de verificación de estado requerida que elijas determina si se requiere que tu rama esté actualizada con la rama base antes de la fusión. - -| Tipo de verificación de estado requerida | Parámetro | Requisitos de fusión | Consideraciones | -| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Estricta** | La casilla de verificación **Requerir que las ramas estén actualizadas antes de fusionar** está seleccionada. | La rama **debe** estar actualizada con la rama de base antes de la fusión. | Este es el comportamiento predeterminado para las verificaciones de estado requeridas. Se pueden requerir más construcciones, ya que deberás actualizar la rama de encabezado después de que otros colaboradores fusionen las solicitudes de extracción con la rama de base protegida. | -| **Flexible** | La casilla de verificación **Requerir que las ramas estén actualizadas antes de fusionar** **no** está seleccionada. | La rama **no debe** estar actualizada con la rama de base antes de la fusión. | Tendrás menos construcciones requeridas, ya que no necesitarás actualizar la rama de encabezado después de que otros colaboradores fusionen las solicitudes de extracción. Las verificaciones de estado pueden fallar después de que fusiones tu rama si hay cambios incompatibles con la rama de base. | -| **Inhabilitada** | La casilla **Require status checks to pass before merging** (Se deben superar las verificaciones de estado antes de la fusión) **no** está marcada. | La rama no tiene restricciones de fusión. | Si las verificaciones de estado requeridas no están habilitadas, los colaboradores pueden fusionar la rama en cualquier momento, independientemente de si está actualizada con la rama de base. Esto aumenta la posibilidad de cambios incompatibles. | - -Para obtener información sobre la solución de problemas, consulta la sección "[Solucionar probelmas para las verificaciones de estado requeridas](/github/administering-a-repository/troubleshooting-required-status-checks)". +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." {% ifversion fpt or ghes > 3.1 or ghae-issue-4382 or ghec %} -### Requerir la resolución de conversaciones antes de fusionar +### Require conversation resolution before merging -Requiere que se resuelvan todos los comentarios de la solicitud de cambios antes de qeu se pueda fusionar con una rama protegida. Esto garantiza que todos los comentarios se traten o reconozcan antes de fusionar. +Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge. {% endif %} -### Requerir confirmaciones firmadas +### Require signed commits -Cuando habilitas el requerir el firmado de confirmaciones en una rama, los colaboradores {% ifversion fpt or ghec %}y bots{% endif %} solo podrán subir a la rama aquellas confirmaciones que se hayan firmado y verificado. Para obtener más información, consulta "[Acerca de la verificación de firmas en las confirmaciones](/articles/about-commit-signature-verification)." +When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)." {% note %} {% ifversion fpt or ghec %} -**Notas:** +**Notes:** -* Si habilitaste el modo vigilante, el cual indica que tus confirmaciones siempre se firmarán, cualquier confirmación que {% data variables.product.prodname_dotcom %} identifique como "Verificada parcialmente" se permitirá en aquellas ramas que requieran confirmaciones firmadas. Para obtener más información sobre el modo vigilante, consulta la sección "[Mostrar los estados de verificación para todas tus confirmaciones](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)". -* Si un colaborador sube una confirmación sin firmar a una rama que requiere firmas de confirmación, este necesitará rebasar dicha confirmación para incluir una firma verificada y luego subir forzadamente la confirmación reescrita a esta. +* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)." +* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. {% else %} -**Nota:** Si un colaborador sube una confirmación sin firmar a una rama que requiere firmas de confirmación, éste necesitará rebasar la confirmación para incluir una firma verificada y luego subir forzadamente la confirmación re-escrita a la rama. +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. {% endif %} {% endnote %} -Siempre puedes subir confirmaciones locales a la rama si estas se firmaron y verificaron. {% ifversion fpt or ghec %}También puedes fusionar las confirmaciones firmadas y verificadas en la rama utilizando una solicitud de extracción en {% data variables.product.product_name %}. Sin embargo, no puedes combinar y fusionar una solicitud de extracción en la rama en {% data variables.product.product_name %} a menos de que seas el autor de dicha solicitud.{% else %} Sin embargo, no puedes fusionar solicitudes de extracción en la rama en {% data variables.product.product_name %}.{% endif %} Puedes {% ifversion fpt or ghec %}combinar y {% endif %}fusionar las solicitudes de extracción localmente. Para obtener más información, consulta la sección "[Revisar las solicitudes de extracción localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)". +You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)." -{% ifversion fpt or ghec %} Para obtener más información sobre los métodos de fusión consulta la sección "[Acerca de los métodos de fusión en {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)".{% endif %} +{% ifversion fpt or ghec %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} -### Requerir un historial linear +### Require linear history -El requerir un historial de confirmaciones linear previene que los colaboradores suban confirmaciones de fusión a la rama. Esto significa que cualquier solicitud de extracción fusionada con la rama protegida deberá utilizar una fusión combinada o una fusión de rebase. Un historial de confirmaciones estrictamente linear puede ayudar a los equipos a revertir los cambios con mayor facilidad. Para obtener más información acerca de los métodos de fusión, consulta "[Acerca de la fusión de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." -Antes de poder requerir un historial de confirmaciones linear, tu repositorio deberá permitir fusiones combinadas o fusiones de rebase. Para obtener más información, consulta "[Configurar las fusiones de solicitud de extracción](/github/administering-a-repository/configuring-pull-request-merges)." +Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)." {% ifversion fpt or ghec %} ### Require merge queue @@ -146,30 +141,30 @@ Antes de poder requerir un historial de confirmaciones linear, tu repositorio de {% data reusables.pull_requests.merge-queue-references %} {% endif %} -### Incluir administradores +### Include administrators -Predeterminadamente, las reglas de rama protegida no aplican a las personas con permisos administrativos en un repositorio. Puedes habilitar esta configuración para incluir a los administradores en tus reglas de rama protegida. +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. -### Restringir quiénes pueden subir a las ramas coincidentes +### Restrict who can push to matching branches {% ifversion fpt or ghec %} -Puedes habilitar restricciones de rama si tu repositorio le pertenece a una organización que utilice {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}. +You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% endif %} -Cuando habilitas las restricciones de rama, solo los usuarios, equipos o apps a los que se les haya dado permisos pueden subir información a la rama protegida. Puedes ver y editar los usuarios, equipos o apps con acceso de escritura a una rama protegida en la configuración de la misma. +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. -Solo puedes dar acceso de escritura a una rama protegida para usuarios, equipos o {% data variables.product.prodname_github_apps %} instaladas con acceso de tipo write a un repositorio. Las personas y apps con permisos administrativos en un repositorio siempre pueden subir información a una rama protegida. +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. -### Permitir las subidas forzadas +### Allow force pushes -Predeterminadamente, {% data variables.product.product_name %} bloquea las subidas forzadas en todas las ramas protegidas. Cuando habilitas estas subidas forzadas en una rama protegida, cualquiera que tenga privilegios por lo menos de escritura en ese repositorio puede forzar la subida de información a la rama, incluyendo aquellos con permisos de administrador. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests. -Habilitar las subidas forzadas no invalidará ninguna otra regla de protección a la rama. Por ejemplo, si una rama requiere un historial de confirmaciones linear, no puedes forzar la subida de fusión de confirmaciones en esa rama. +Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. -{% ifversion ghes or ghae %}No puedes habilitar las subidas forzadas en una rama protegida si un administrador de sitio las ha bloqueado en todas las ramas de tu repositorio. Para obtener más información, consulta "[Bloquear las subidas de información forzadas en los repositorios que sean propiedad de una organización o cuenta de usuario](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." +{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." -Si un administrador de sitio ha bloqueado las subidas de información forzadas en la rama predeterminada únicamente, entonces aún puedes habilitarlas en cualquier otra rama protegida.{% endif %} +If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} -### Permitir el borrado +### Allow deletions -Por defecto, no puedes eliminar una rama protegida. Cuando habilitas el borrado de una rama protegida, cualquiera que tenga por lo menos permiso de escritura en el repositorio podrá borrar la rama. +By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index d824333b2d..af1d2efaca 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -1,6 +1,6 @@ --- -title: Administrar una regla de protección de rama -intro: 'Puedes crear una regla de protección de rama para requerir ciertos flujos de trabajo en una o más ramas, tal como requerir una revisión de aprobacion o verificaciones de un estado que pase para todas las solicitudes de cambios que se fusionan en la rama protegida.' +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/configuring-protected-branches @@ -26,74 +26,105 @@ versions: permissions: People with admin permissions to a repository can manage branch protection rules. topics: - Repositories -shortTitle: Regla de protección de rama +shortTitle: Branch protection rule --- - -## Acerca de las reglas de protección de rama +## About branch protection rules {% data reusables.repositories.branch-rules-example %} -Puedes crear una regla para todas las ramas actuales y futuras de tu repositorio con la sintaxis de comodín `*`. Ya que {% data variables.product.company_short %} utiliza el indicador `File::FNM_PATHNAME` para la sintaxis `File.fnmatch` el comodín no empata con los separadores de directorio (`/`). Por ejemplo, `qa/*` empatará con todas las ramas que comiencen con `qa/` y contengan una sola diagonal. Puedes incluir varias diagonales con `qa/**/*`, y puedes extender la secuencia de `qa` con `qa**/**/*` para hacer la regla más inclusiva. Para más información sobre las opciones de sintaxis para las reglas de la rama, consulta la [documentación fnmatch](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). -Si un repositorio tiene varias reglas de rama protegida que afectan las mismas ramas, las reglas que incluyen el nombre de una rama específica tienen la mayor prioridad. Si hay más de una regla de rama protegida que hace referencia al mismo nombre de rama específico, entonces la regla de rama creada primera tendrá la prioridad más alta. +If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority. -Las reglas de rama protegida que mencionen un caracter especial, como `*`, `?` o `]`, se aplican en el orden que fueron creadas, así que las reglas más antiguas con estos caracteres tienen la prioridad más alta. +Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority. -Para crear una excepción a una regla de rama existente, puedes crear una nueva regla de protección de rama que sea una prioridad superior, como una regla de rama para un nombre de rama específico. +To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name. -Para obtener más información sobre cada uno de los ajustes de protección de rama disponibles, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." -## Crear una regla de protección de rama +## Creating a branch protection rule -Cuando creas una regla de rama, la rama que especifiques no tendrá que en el repositorio aún. +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} {% data reusables.repositories.add-branch-protection-rules %} -1. Opcionalmente, habilita las revisiones requeridas para las solicitudes de cambios. - - Debajo de "Proteger las ramas coincidentes", selecciona **Requerir revisiones de solicitudes de cambios antes de fusionar**. ![Casilla de verificación Restricción de revisión de solicitud de extracción](/assets/images/help/repository/PR-reviews-required.png) - - Da clic en el menú desplegable de **Revisiones de aprobación requeridas** y luego selecciona la cantidad de revisiones de aprobación que te gustaría requerir para la rama. ![Menú desplegable para seleccionar el número de aprobaciones de revisión requeridas](/assets/images/help/repository/number-of-required-review-approvals.png) - - Opcionalmente, para descartar una revisión de aprobación de la solicitud de cambios cuando una confirmación que modifica el código se sube a la rama, selecciona **Descartar las aprobaciones de solicitudes de cambios estancadas cuando se suban confirmaciones nuevas**. ![Casilla de verificación Descartar aprobaciones de solicitudes de extracción en espera cuando se suben nuevas confirmaciones](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - - Opcionalmente, para requerir una revisión de un propietario del código cuando la solicitud de cambios afecte al código que tenga un propietario designado, selecciona **Requerir la revisión de los propietarios del código**. Para obtener más información, consulta "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Requerir revisión de los propietarios del código](/assets/images/help/repository/PR-review-required-code-owner.png) - - Opcionalmente, si el repositorio es parte de una oranización, selecciona **Restringir quién puede descartar las revisiones de una solicitud de cambios**. Posteriormente, busca y selecciona a las personas o equipos que se les permitirá descartar las revisiones de solicitudes de cambios. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)". ![Restringir quién puede descartar la casilla de verificación de revisiones de solicitudes de extracción](/assets/images/help/repository/PR-review-required-dismissals.png) -1. Opcionalmente, habilita las verificaciones de estado requeridas. - - Selecciona **Requerir verificaciones de estado requeridas antes de la fusión**. ![Opción Verificaciones de estado requeridas](/assets/images/help/repository/required-status-checks.png) - - Opcionalmente, para garantizar que las solicitudes de cambios se prueban con el último código en la rama protegida, selecciona **Requerir que las ramas estén actualizadas antes de fusionarlas**. ![Casilla de verificación de estado estricta o poco estricta](/assets/images/help/repository/protecting-branch-loose-status.png) - - Selecciona las verificaciones que quieres requerir de la lista de verificaciones de estado disponibles. ![Lista de verificaciones de estado disponibles](/assets/images/help/repository/required-statuses-list.png) +{% ifversion fpt or ghec %} +1. Optionally, enable required pull requests. + - Under "Protect matching branches", select **Require a pull request before merging**. + ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png) + - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch. + ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png) +{% else %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. + ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. + ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png) +{% endif %} + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. + ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." + ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) +{% ifversion fpt or ghec %} + - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. + ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) +{% endif %} + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." + ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + - Select **Require status checks to pass before merging**. + ![Required status checks option](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. + ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png) + - Search for status checks, selecting the checks you want to require. + ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png) {%- ifversion fpt or ghes > 3.1 or ghae-issue-4382 %} -1. Opcionalmente, seleccina **Requerir resolución de la conversación antes de fusionar**. ![Opción de requerir la resolución de conversaciones antes de fusionar](/assets/images/help/repository/require-conversation-resolution.png) +1. Optionally, select **Require conversation resolution before merging**. + ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png) {%- endif %} -1. Opcionalmente, selecciona **Requerir confirmaciones firmadas**. ![Opción Requerir confirmaciones firmadas](/assets/images/help/repository/require-signed-commits.png) -1. Opcionalmente, selecciona **Requerir un historial linear**. ![Opción para requerir historial linear](/assets/images/help/repository/required-linear-history.png) +1. Optionally, select **Require signed commits**. + ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. + ![Required linear history option](/assets/images/help/repository/required-linear-history.png) {%- ifversion fpt or ghec %} -1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png) +1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} + ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png) {% tip %} **Tip:** The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup). {% endtip %} {%- endif %} -1. También puedes seleccionar **Incluir administradores**. ![Casilla de verificación Incluir administradores](/assets/images/help/repository/include-admins-protected-branches.png) -1. Opcionalmente,{% ifversion fpt or ghec %} si tu repositorio pertenece a una organización que utilice {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %},{% endif %} habilita las restricciones de rama. - - Selecciona **Restringir quién puede subir a las ramas coincidentes**. ![Casilla de verificación para restricción de rama](/assets/images/help/repository/restrict-branch.png) - - Busca y selecciona las personas, equipos, o apps que tendrán permiso para subir información a la rama protegida. ![Búsqueda de restricciones de rama](/assets/images/help/repository/restrict-branch-search.png) -1. Opcionalmente, debajo de "Reglas que se aplican a todos, incluyendo administradores", selecciona **permitir las subidas forzadas**. ![Permitir la opción de subida de información forzada](/assets/images/help/repository/allow-force-pushes.png) -1. Opcionalmente, selecciona **Permitir los borrados**. ![Opción para habilitar las eliminaciones de ramas](/assets/images/help/repository/allow-branch-deletions.png) -1. Da clic en **Crear**. +1. Optionally, select **Include administrators**. +![Include administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% ifversion fpt or ghec %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. + ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png) + - Search for and select the people, teams, or apps who will have permission to push to the protected branch. + ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png) +2. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)." + ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. + ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png) +1. Click **Create**. -## Editar una regla de protección de rama +## Editing a branch protection rule {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. A la derecha de la regla de protección de rama que quieras editar, da clic en **Editar**. ![Botón editar](/assets/images/help/repository/edit-branch-protection-rule.png) -1. Haz los cambios que desees en la regla de protección de rama. -1. Haz clic en **Guardar cambios**. ![Botón Editar mensaje](/assets/images/help/repository/save-branch-protection-rule.png) +1. To the right of the branch protection rule you want to edit, click **Edit**. + ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. Click **Save changes**. + ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png) -## Borrar una regla de protección de rama +## Deleting a branch protection rule {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. A la derecha de la regla de protección de rama que quieras borrar, da clic en **Borrar**. ![Botón de borrar](/assets/images/help/repository/delete-branch-protection-rule.png) +1. To the right of the branch protection rule you want to delete, click **Delete**. + ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png) diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 4410bcd2da..e5683513b9 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -1,6 +1,6 @@ --- -title: Renombrar una rama -intro: Puedes cambiar el nombre de una rama en un repositorio. +title: Renaming a branch +intro: You can change the name of a branch in a repository. permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. versions: fpt: '*' @@ -13,30 +13,32 @@ redirect_from: - /github/administering-a-repository/renaming-a-branch - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch --- +## About renaming branches -## Acerca de renombrar las ramas +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))." -Puedes renombrar una rama en un repositorio de {% data variables.product.product_location %}. Para obtener más información sobre cómo renombrar ramas, consulta la sección "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches)". +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. -Cuando renombras una rama en {% data variables.product.product_location %}, cualquier URL que contega el nombre de la rama antigua se redireccionará automáticamente a la URL equivalente para la rama que se renombró. También se actualizan las políticas de protección de rama, así como la rama base para las solicitudes de cambios abriertas (incluyendo aquellas para las bifurcaciones) y para los borradores de lanzamientos. Después de que se completa el renombramiento, {% data variables.product.prodname_dotcom %} proporciona instrucciones en la página principal del repositorio y dirige a los colaboradores a actualizar sus ambientes locales de Git. +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. -Aunque las URL de archivo se redirigen automáticamente, las URL de archivo sin procesar no se redirigirán. Además, {% data variables.product.prodname_dotcom %} no realiza ninguna redirección si los usuarios realizan un `git pull` para el nombre de rama anterior. +{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name. -Los flujos de trabajo de las {% data variables.product.prodname_actions %} no siguen a los renombrados, así que, si tu repositorio publica una acción, cualquiera que la utilice con `@{old-branch-name}` fallará. Debes considerar agregar una rama nueva con el contenido original más una confirmación adicional que reporte que el nombre de rama está obsoletizado y que sugiera que los usuarios se migren al nombre de la rama nueva. - -## Renombrar una rama +## Renaming a branch {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} -1. En la lista de ramas, a la derecha de la rama que quieras renombrar, da clic en {% octicon "pencil" aria-label="The edit icon" %}. ![Icono de lápiz a la derecha de la rama que quieras renombrar](/assets/images/help/branch/branch-rename-edit.png) -1. Teclea un nombre nuevo para la rama. ![Campo de texto para teclear un nombre de rama nuevo](/assets/images/help/branch/branch-rename-type.png) -1. Revisa la información sobre los ambientes locales y luego da clic en **Renombrar rama**. ![Información de ambiente local y botón de "Renombrar rama"](/assets/images/help/branch/branch-rename-rename.png) +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. + ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. + ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. + ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) -## Actualizar un clon local después de que cambie el nombre de una rama +## Updating a local clone after a branch name changes -Después de que renombras una rama en un repositorio con {% data variables.product.product_name %}, cualquier colaborador con un clon local del repositorio necesitará actualizar dicho clon. +After you rename a branch in a repository on {% data variables.product.product_name %}, any collaborator with a local clone of the repository will need to update the clone. -Desde el clon local del repositorio en una computadora, ejecuta los siguientes comandos para actualizar el nombre de la rama predeterminada. +From the local clone of the repository on a computer, run the following commands to update the name of the default branch. ```shell $ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME @@ -45,7 +47,7 @@ $ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME $ git remote set-head origin -a ``` -Opcionalmente, ejecuta el siguiente comando para eliminar las referencias de rastreo al nombre de la rama antigua. +Optionally, run the following command to remove tracking references to the old branch name. ``` $ git remote prune origin ``` diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 24a7d8ba0e..280aa369a1 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -1,6 +1,6 @@ --- -title: Crear un repositorio desde una plantilla -intro: Puedes generar un nuevo repositorio con la misma estructura de directorio y los mismos archivos que un repositorio existente. +title: Creating a repository from a template +intro: You can generate a new repository with the same directory structure and files as an existing repository. redirect_from: - /articles/creating-a-repository-from-a-template - /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template @@ -12,39 +12,40 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Crear desde una plantilla +shortTitle: Create from a template --- +## About repository templates -## Acerca de las plantillas de repositorio - -Cualquier usuario con permisos de lectura para un repositorio de plantillas puede crear un repositorio a partir de esa plantilla. Para obtener más información, consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)". +Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)." {% ifversion fpt or ghae or ghes or ghec %} {% tip %} -**Tip**: También puedes crear un repositorio a partir de una plantilla utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}. +**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} {% endif %} {% ifversion fpt or ghae or ghes or ghec %} -Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas. Las ramas que se creen a partir de una plantilla tienen historiales sin relación, lo cual significa que no puedes crear solicitudes de cambio ni hacer fusiones entre las ramas. +You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches. {% endif %} -Crear un repositorio a partir de una plantilla es similar a bifurcar un repositorio, pero existen algunas diferencias importantes: -- Una nueva bifurcación incluye todo el historial de confirmaciones del repositorio padre, mientras que un repositorio creado a partir de una plantilla comienza con una única confirmación. -- Las confirmaciones en una bifurcación no aparecen en tu gráfico de contribuciones, mientras que las confirmaciones en un repositorio creado a partir de una plantilla sí se muestran en tu gráfico de contribuciones. -- Una bifurcación puede ser una forma temporaria de contribuir código a un proyecto existente, mientras que crear un repositorio a partir de una plantilla permite iniciar rápidamente un proyecto nuevo. +Creating a repository from a template is similar to forking a repository, but there are important differences: +- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit. +- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph. +- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly. -Para obtener más información acerca de las bifurcaciones, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". +For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)." -## Crear un repositorio desde una plantilla +## Creating a repository from a template {% data reusables.repositories.navigate-to-repo %} -2. Sobre la lista, haz clic en **Usar esta plantilla**. ![Botón Use this template button (Usar esta plantilla)](/assets/images/help/repository/use-this-template-button.png) +2. Above the file list, click **Use this template**. + ![Use this template button](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} -6. De manera opcional, para incluir la estructura de directorio y los archivos de todas las ramas en la plantilla, y no únicamente aquellos de la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +6. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**. + ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} {% data reusables.repositories.select-marketplace-apps %} -8. Haz clic en **Crear un repositorio a partir de una plantilla**. +8. Click **Create repository from template**. diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index 544d68fb25..fe81a4601c 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -1,6 +1,6 @@ --- -title: Duplicar un repositorio -intro: 'Para mantener una réplica de un repositorio sin bifurcarlo, puedes ejecutar un comando de clonado especial y luego subir la réplica al repositorio nuevo.' +title: Duplicating a repository +intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.' redirect_from: - /articles/duplicating-a-repo/ - /articles/duplicating-a-repository @@ -14,92 +14,91 @@ versions: topics: - Repositories --- - -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec %} {% note %} -**Nota:** Si tienes un proyecto hospedado en otro sistema de control de versiones, puedes importar tu proyecto automáticamente a {% data variables.product.prodname_dotcom %} utilizando la herramienta importadora de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca del importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)". +**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_dotcom %} Importer tool. For more information, see "[About {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)." {% endnote %} {% endif %} -Antes de que puedas subir el repositorio original a tu copia nueva o _réplica_ de este, debes [crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. En estos ejemplos, `exampleuser/new-repository` o `exampleuser/mirrored` son los espejos. +Before you can push the original repository to your new copy, or _mirror_, of the repository, you must [create the new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. In these examples, `exampleuser/new-repository` or `exampleuser/mirrored` are the mirrors. -## Generar un espejo de un repositorio +## Mirroring a repository {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crea un clon desnudo de un repositorio. +2. Create a bare clone of the repository. ```shell $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git ``` -3. Sube en espejo al nuevo repositorio. +3. Mirror-push to the new repository. ```shell $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` -4. Eliminar el repositorio local temporal que creaste previamente. +4. Remove the temporary local repository you created earlier. ```shell $ cd .. $ rm -rf old-repository ``` -## Replicar un repositorio que contiene objetos de {% data variables.large_files.product_name_long %} +## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crea un clon desnudo de un repositorio. Reemplaza el nombre de usuario del ejemplo por el nombre de la persona u organización propietaria del repositorio y reemplaza el nombre del repositorio del ejemplo por el nombre del repositorio que deseas duplicar. +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 %}/exampleuser/old-repository.git ``` -3. Dirígete al repositorio que acabas de clonar. +3. Navigate to the repository you just cloned. ```shell $ cd old-repository ``` -4. Extra los objetos {% data variables.large_files.product_name_long %} del repositorio. +4. Pull in the repository's {% data variables.large_files.product_name_long %} objects. ```shell $ git lfs fetch --all ``` -5. Sube en espejo al nuevo repositorio. +5. Mirror-push to the new repository. ```shell $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` -6. Sube los objetos {% data variables.large_files.product_name_long %} del repositorio a tu espejo. +6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror. ```shell $ git lfs push --all https://github.com/exampleuser/new-repository.git ``` -7. Eliminar el repositorio local temporal que creaste previamente. +7. Remove the temporary local repository you created earlier. ```shell $ cd .. $ rm -rf old-repository ``` -## Replicar un repositorio en otra ubicación +## Mirroring a repository in another location -Si quieres replicar un repositorio en otra ubicación, incluido obtener actualizaciones del original, puedes clonar una réplica y subir periódicamente los cambios. +If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crea un clon desnudo en espejo del repositorio. +2. Create a bare mirrored clone of the repository. ```shell $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git ``` -3. Establece la ubicación para subir en tu espejo. +3. Set the push location to your mirror. ```shell $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` +As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror. -Al igual que sucede con un clon básico, un clon replicado incluye todas las ramas y etiquetas remotas, pero todas las referencias locales se sobrescribirán cada vez que extraigas elementos, por eso siempre será igual al repositorio original. El proceso para subir elementos a tu espejo se simplifica si estableces la URL para los elementos que subes. Para actualizar tu espejo, extrae las actualizaciones y súbelas. +4. To update your mirror, fetch updates and push. + ```shell + $ git fetch -p origin + $ git push --mirror + ``` +{% ifversion fpt or ghec %} +## Further reading -```shell -$ git fetch -p origin -$ git push --mirror -``` -{% ifversion fpt or ghec %} -## Leer más - -* "[Subir cambios a GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" -* "[Acerca del Almacenamiento de Archivos Grandes de Git y de GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" -* "[Acerca del Importador GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" +* "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" +* "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" +* "[About GitHub Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" {% endif %} diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md index a0f3c435c3..9d3e3467d3 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md @@ -1,6 +1,6 @@ --- -title: Restaurando un repositorio eliminado -intro: Puede restaurar algunos de los repositorios eliminados para recuperar su contenido. +title: Restoring a deleted repository +intro: You can restore some deleted repositories to recover their contents. redirect_from: - /articles/restoring-a-deleted-repository - /github/administering-a-repository/restoring-a-deleted-repository @@ -12,23 +12,22 @@ versions: ghae: '*' topics: - Repositories -shortTitle: Restablecer el repositorio borrado +shortTitle: Restore deleted repository --- - {% ifversion fpt or ghec %} -Cualquier usuario puede restaurar repositorios eliminados que le pertenecieron a su propia cuenta de usuario. Los propietarios de la organización pueden restaurar repositorios eliminados que le pertenecieron a la organización. +Anyone can restore deleted repositories that were owned by their own user account. Organization owners can restore deleted repositories that were owned by the organization. -## Acerca de la restauración de repositorios +## About repository restoration -Un repositorio eliminado se puede restaurar en un plazo de 90 días, a menos que el repositorio haya sido parte de una red de bifurcaciones que actualmente no está vacía. Una red de bifurcaciones consiste en un repositorio padre, las bifurcaciones del repositorio y las bifurcaciones de las bifurcaciones del repositorio. Si tu repositorio forma parte de una red de bifurcaciones, no se puede restaurar a menos que se elimine cualquier otro repositorio de la red o que se haya separado de la red. Para obtener más información acerca de las bifurcaciones, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". +A deleted repository can be restored within 90 days, unless the repository was part of a fork network that is not currently empty. A fork network consists of a parent repository, the repository's forks, and forks of the repository's forks. If your repository was part of a fork network, it cannot be restored unless every other repository in the network is deleted or has been detached from the network. For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)." -Si quieres restaurar un repositorio que era parte de una red de bifurcaciones que actualmente no está vacía, te puedes contactar con {% data variables.contact.contact_support %}. +If you want to restore a repository that was part of a fork network that is not currently empty, you can contact {% data variables.contact.contact_support %}. -Puede tardar hasta una hora después de que se elimine un repositorio antes de que ese repositorio esté disponible para la restauración. +It can take up to an hour after a repository is deleted before that repository is available for restoration. -Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o los permisos de equipo. Las propuestas que se restablezcan no se etiquetarán. +Restoring a repository will not restore release attachments or team permissions. Issues that are restored will not be labeled. -## Restaurar un repositorio eliminado que le pertenecía a una cuenta de usuario +## Restoring a deleted repository that was owned by a user account {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.repo-tab %} @@ -36,7 +35,7 @@ Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o l {% data reusables.user_settings.restore-repo %} {% data reusables.user_settings.restore-confirmation %} -## Restaurar un repositorio eliminado que le pertenecía a una organización +## Restoring a deleted repository that was owned by an organization {% data reusables.profile.access_org %} @@ -45,10 +44,10 @@ Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o l {% data reusables.user_settings.restore-repo %} {% data reusables.user_settings.restore-confirmation %} -## Leer más +## Further reading -- "[Borrar un repositorio](/articles/deleting-a-repository)" +- "[Deleting a repository](/articles/deleting-a-repository)" {% else %} -Usually, deleted repositories can be restored within 90 days by a {% data variables.product.prodname_enterprise %} site administrator. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". +Usually, deleted repositories can be restored within 90 days by a {% data variables.product.prodname_enterprise %} site administrator. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% endif %} diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 1d4408adca..461bb3da0c 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -1,6 +1,6 @@ --- -title: Acerca de los archivos de CITATION -intro: Puedes agregar un archivo de CITATION a tu repositorio para ayudar a que los usuarios citen tu software correctamente. +title: About CITATION files +intro: You can add a CITATION file to your repository to help users correctly cite your software. redirect_from: - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files versions: @@ -11,12 +11,11 @@ versions: topics: - Repositories --- +## About CITATION files -## Acerca de los archivos de CITATION +You can add a `CITATION.cff` file to the root of a repository to let others know how you would like them to cite your work. The citation file format is plain text with human- and machine-readable citation information. -Puedes agregar un archivo de `CITATION.cff` a la raíz de un repositorio para que otros sepan cómo te gustaría que citaran tu trabajo. El formato de archivo de cita es texto simple con información de cita legible para humanos y máquinas. - -Ejemplo de archivo de `CITATION.cff`: +Example `CITATION.cff` file: ``` cff-version: 1.2.0 @@ -35,7 +34,7 @@ date-released: 2017-12-18 url: "https://github.com/github/linguist" ``` -El mensaje de cita de GitHub en tu repositorio te mostrará el contenido de ejemplo de un `CITATION.cff` en estos formatos: +The GitHub citation prompt on your repository will show the example `CITATION.cff` content in these formats: **APA** @@ -59,25 +58,35 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw ``` {% endraw %} -Toma en cuenta que el ejemplo anterior producirá una cita de _software_ (es decir, un tipo de `@software` en BibTeX en vez de un `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). -Para obtener más información, consulta el sitio web de [Formatos de Archivos de Citas](https://citation-file-format.github.io/). +For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. -Cuando agregas un archivo de `CITATION.cff` a la rama predeterminada de tu repositorio, este se enlaza automáticamente desde la página de llegada del repositorio. Esto hace fácil que otros usuarios citen tu proyecto de software, utilizando la información que proporcionaste. +When you add a `CITATION.cff` file to the default branch of your repository, it is automatically linked from the repository landing page. This makes it easy for other users to cite your software project, using the information you've provided. -![Enlaze de cita en la página de inicio de un repositorio](/assets/images/help/repository/citation-link.png) +![Citation link on repository landing page](/assets/images/help/repository/citation-link.png) -## Citar algo que no sea software +## Citing something other than software -Si prefieres que la información de cita de {% data variables.product.prodname_dotcom %} enlace a otro recurso tal como un artículo de investigación, entonces puedes utilizar la anulación de `preferred-citation` en CFF con los siguientes tipos. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -| Recurso | Type | -| ------------------------- | ------------------ | -| Artículo de investigación | `article` | -| Escrito de conferencia | `conference-paper` | -| Libro | `book` | +| Resource | CFF type | BibTeX type | APA annotation | +|----------|----------|-------------|----------------| +| Journal article/paper | `article` | `@article` | | +| Book | `book` | `@book` | | +| Booklet (bound but not published) | `pamphlet` | `@booklet` | | +| Conference article/paper | `conference-paper` | `@inproceedings` | [Conference paper] | +| Conference proceedings | `conference`, `proceedings` | `@proceedings` | | +| Data set | `data`, `database` | `@misc` | [Data set] | +| Magazine article | `magazine-article` | `@article` | | +| Manual | `manual` | `@manual` | | +| Misc/generic/other | `generic`, any other CFF type | `@misc` | | +| Newspaper article | `newspaper-article` | `@article` | | +| Software | `software`, `software-code`, `software-container`, `software-executable`, `software-virtual-machine` | `@software` | [Computer software] | +| Report/technical report | `report` | `@techreport` | | +| Unpublished | `unpublished` | `@unpublished` | | -Archivo de CITATION.cff extendido que describe el software, pero vincula a un artículo de investigación como la cita preferida: +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -114,7 +123,7 @@ preferred-citation: year: 2021 ``` -El archivo `CITATION.cff` anterior producirá los siguientes resultados en el mensaje de cita de GitHub: +The example `CITATION.cff` file above will produce the following outputs in the GitHub citation prompt: **APA** @@ -140,15 +149,15 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} -## Citar un conjunto de datos +## Citing a dataset -Si tu repositorio contiene un conjunto de datos, puedes configurar `type: dataset` en tu archivo `CITATION.cff` para producir una salida de secuencia de cita de datos en el mensaje de cita de {% data variables.product.prodname_dotcom %}. +If your repository contains a dataset, you can set `type: dataset` at the top level of your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. -## Otros archivos de cita +## Other citation files -La característica de cita de GitHub también detectará una cantidad pequeña de archivos adicionales que a menudo se utilizan en las comunidades y proyectos para describir cómo quieren que se cite su trabajo. +The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. -GitHub enlazará estos archivos en el mensaje de _Citar este repositorio_, pero no intentará analizarlos en otros formatos de cita. +GitHub will link to these files in the _Cite this repository_ prompt, but will not attempt to parse them into other citation formats. ``` # Note these are case-insensitive and must be in the root of the repository @@ -159,12 +168,12 @@ CITATIONS.bib CITATION.md CITATIONS.md -# CITATION files for R packages are typically found at inst/CITATION +# CITATION files for R packages are typically found at inst/CITATION inst/CITATION ``` -## Formatos de cita +## Citation formats -Actualmente tenemos compatibilidad con formatos de archivo en APA y BibTex. +We currently support APA and BibTex file formats. -¡Estás buscando formatos de cita adicionales? GitHub utiliza una librería de Ruby para analizar los archivos de `CITATION.cff`. Puedes solicitar formatos adicionales en el repositorio [ruby-cff](https://github.com/citation-file-format/ruby-cff) o proporcionarlos tú mismo como contribución. +Are you looking for additional citation formats? GitHub uses a Ruby library, to parse the `CITATION.cff` files. You can request additional formats in the [ruby-cff](https://github.com/citation-file-format/ruby-cff) repository, or contribute them yourself. diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 583f2bba7f..be05049a7c 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -1,6 +1,6 @@ --- -title: Acerca de los propietarios del código -intro: Puedes usar un archivo CODEOWNERS para definir individuos o equipos que sean responsables del código en un repositorio. +title: About code owners +intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository. redirect_from: - /articles/about-codeowners/ - /articles/about-code-owners @@ -15,60 +15,61 @@ versions: topics: - Repositories --- +People with admin or owner permissions can set up a CODEOWNERS file in a repository. -Las personas con permisos administrativos o de propietario pueden configurar un archivo CODEOWNERS en un repositorio. +The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. -Las personas que elijas como propietarios del código deben tener permisos de escritura para el repositorio. Cuando el propietario del código es un equipo, ese equipo debe ser visible y tener permisos de escritura, incluso si todos los miembros individuales del equipo ya tienen permisos de escritura, a través de la membresía de la organización o a través de la membresía de otro equipo. +## About code owners -## Acerca de los propietarios del código +Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)." -Cuando alguien abre una solicitud de extracción que modifica el código que pertenece a alguien, automáticamente se les solicita una revisión a los propietarios del mismo. Lo que no se solicita automáticamente a estos propietarios es la revisión de los borradores de solicitudes de extracción. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Se notificará automáticamente a los dueños del código cuando marques un borrador de solicitud de extracción como listo para revisión. Si conviertes una solicitud de extracción en borrador, las personas que ya estén suscritas a las notificaciones no se darán de baja automáticamente. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)". +When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -Cuando alguien con permisos administrativos o de propietario ha activado las revisiones requeridas, opcionalmente, también pueden solicitar aprobación de un propietario del código antes de que el autor pueda fusionar una solicitud de extracción en el repositorio. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". +If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}. -{% ifversion fpt or ghae or ghes or ghec %}Si un equipo habilitó las tareas de revisión de código, las aprobaciones individuales no satisfarán el requisito de aprobación del propietario del código en una rama protegida. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)".{% endif %} +![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png) -Si un archivo tiene un propietario del código, puedes ver quién es éste antes de que abras una solicitud de extracción. Puedes buscar el archivo en el repositorio y pasar el puntero sobre {% octicon "shield-lock" aria-label="The edit icon" %}. +## CODEOWNERS file location -![Dueño del código de un archivo en un repositorio](/assets/images/help/repository/code-owner-for-a-file.png) +To use a CODEOWNERS file, create a new file called `CODEOWNERS` in the root, `docs/`, or `.github/` directory of the repository, in the branch where you'd like to add the code owners. -## Ubicación del archivo CODEOWNERS +Each CODEOWNERS file assigns the code owners for a single branch in the repository. Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch. -Para usar un archivo CODEOWNERS, crea un archivo nuevo llamado `CODEOWNERS` en la raíz, `docs/`, o en el directorio `.github/` del repositorio, en la rama en la que quieras agregar los propietarios del código. - -Cada archivo CODEOWNERS asigna los propietarios del código para una única rama en el repositorio. Por lo tanto, puedes asignar propietarios diferentes para el código en ramas diferentes, tal como `@octo-org/codeowners-team` para una base de código en la rama predeterminada y `@octocat` para un sitio de {% data variables.product.prodname_pages %} en la rama de `gh-pages`. - -Para que los propietarios del código reciban las solicitudes de revisión, el archivo CODEOWNERS debe estar en la rama base de la solicitud de extracción. Por ejemplo, si asignas `@octocat` como el propietario del código para los archivos *.js* en la rama `gh-pages` de tu repositorio, `@octocat` recibirá las solicitudes de revisión cuando una solicitud de extracción con cambios en los archivos *.js* se abra entre la rama de encabezado y `gh-pages`. +For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`. {% ifversion fpt or ghae or ghes > 3.2 or ghec %} -## Tamaño de archivo de CODEOWNERS +## CODEOWNERS file size -Los archivos de CODEOWNERS deben ser de menos de 3 MB. Un archivo de CODEOWNERS que sobrepase este límite no se cargará, lo cual significa que la información de los propietarios de código no se mostrará y que no se solicitará que los propietarios de código adecuados revisen los cambios en una solicitud de cambios. +CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. -Para reducir el tamaño de tu archivo de CODEOWNERS, considera utilizar patrones de comodín para consolidar varias entradas en una. +To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. {% endif %} -## Sintáxis de CODEOWNERS +## CODEOWNERS syntax -Un archivo de CODEOWNERS utiliza un patrón que sigue la mayoría de las mismas reglas que utilizan los archivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), con [algunas excepciones](#syntax-exceptions). El patrón es seguido por uno o más nombres de usuarios o nombres de equipos de {% data variables.product.prodname_dotcom %} usando el formato estándar `@username` o `@org/team-name`. Los usuarios deben tener acceso de `read` en el repositorio y los equipos deben tener acceso explícito de `write`, incluso si los miembros de dichos equipos ya tienen acceso. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. +A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. -Si cualquier línea de tu archivo de CODEOWNERS contiene una sintaxi inválida, el archivo no se detectará y no se utilizará para solicitar revisiones. -### Ejemplo de un archivo CODEOWNERS +If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. +### Example of a CODEOWNERS file ``` -# Este es un comentario. -# Cada línea es el patrón de un archivo seguido por uno o más propietarios. +# This is a comment. +# Each line is a file pattern followed by one or more owners. -# Estos propietarios serán los propietarios predeterminados para todo en # el repositorio. A menos que una coincidencia posterior tenga prioridad, se le solicitará # revisión a # @global-owner1 y @global-owner2 cuando alguien abra una solicitud de extracción. +# These owners will be the default owners for everything in +# the repo. Unless a later match takes precedence, +# @global-owner1 and @global-owner2 will be requested for +# review when someone opens a pull request. * @global-owner1 @global-owner2 -# El orden es importante; el último patrón en coincidir tiene la mayor -# prioridad. Cuando alguien abre una solicitud de extracción que solo -# modifica archivos JS, solo se le solicitará una revisión a @js-owner y no al/los # propietario(s) general(es). +# Order is important; the last matching pattern takes the most +# precedence. When someone opens a pull request that only +# modifies JS files, only @js-owner and not the global +# owner(s) will be requested for a review. *.js @js-owner -# Si prefieres, también puedes usar direcciones de correo electrónico. Serán -# usadas para buscar usuarios como hacemos para los -# correos electrónicos del autor de la confirmación. +# You can also use email addresses if you prefer. They'll be +# used to look up users just like we do for commit author +# emails. *.go docs@example.com # Teams can be specified as code owners as well. Teams should @@ -82,13 +83,13 @@ Si cualquier línea de tu archivo de CODEOWNERS contiene una sintaxi inválida, # subdirectories. /build/logs/ @doctocat -# El patrón `docs/*` coincidirá con archivos como -# `docs/getting-started.md` pero no con otros archivos anidados como +# The `docs/*` pattern will match files like +# `docs/getting-started.md` but not further nested files like # `docs/build-app/troubleshooting.md`. docs/* docs@example.com -# En este ejemplo, @octocat posee cualquier archivo en el directorio de las apps -# en cualquier lugar en tu repositorio. +# In this example, @octocat owns any file in an apps directory +# anywhere in your repository. apps/ @octocat # In this example, @doctocat owns any file in the `/docs` @@ -102,16 +103,16 @@ apps/ @octocat /apps/ @octocat /apps/github ``` -### Excepciones de sintaxis -Hay algunas reglas de sintaxis para los archivos de gitignore que no funcionan con los archivos de CODEOWNERS: -- Escapar un patrón comenzando con `#` utilizando `\` para que se trate como un patrón y no como un comentario -- Utilizar `!` para negar un patrón -- Utilizar `[ ]` para definir un rango de carácter +### Syntax exceptions +There are some syntax rules for gitignore files that do not work in CODEOWNERS files: +- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment +- Using `!` to negate a pattern +- Using `[ ]` to define a character range -## Protección de rama y de CODEOWNERS -Los propietarios de los repositorios pueden agregar reglas de protección de rama para asegurarse de que los propietarios de los archivos que se modificaron revisen el código que cambió. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)". +## CODEOWNERS and branch protection +Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." -### Ejemplo de un archivo CODEOWNERS +### Example of a CODEOWNERS file ``` # In this example, any change inside the `/apps` directory # will require approval from @doctocat. @@ -123,18 +124,14 @@ Los propietarios de los repositorios pueden agregar reglas de protección de ram # In this example, any change inside the `/apps` directory # will require approval from a member of the @example-org/content team. -# If a member of @example-org/content opens a pull request -# with a change inside the `/apps` directory, their approval is implicit. -# The team is still added as a reviewer but not a required reviewer. -# Anyone can approve the changes. /apps/ @example-org/content-team ``` -## Leer más +## Further reading -- "[Crear archivos nuevos](/articles/creating-new-files)" -- "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)" -- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" -- "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" -- "[Ver la revisión de una solicitud de extracción](/articles/viewing-a-pull-request-review)" +- "[Creating new files](/articles/creating-new-files)" +- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)" +- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)" +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)" diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md index f81138c31d..b027483903 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Administrar la configuración de seguridad y análisis para tu repositorio -intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tu proyecto dentro de {% data variables.product.prodname_dotcom %}.' +title: Managing security and analysis settings for your repository +intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.' permissions: People with admin permissions to a repository can manage security and analysis settings for the repository. redirect_from: - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/ @@ -22,21 +22,21 @@ topics: - Dependency graph - Secret scanning - Repositories -shortTitle: Seguridad & análisis +shortTitle: Security & analysis --- - {% ifversion fpt or ghec %} -## Habilitar o inhabilitar las características de análisis y seguridad para los repositorios públicos +## Enabling or disabling security and analysis features for public repositories -Puedes administrar un subconjunto de características de análisis y seguridad para los repositorios públicos. Otras características se encuentran habilitadas permanentemente, incluyendo la gráfica de dependencias y el escaneo de secretos. +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y análisis" en un repositorio público.](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. + !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) {% endif %} -## Habilitar o inhabilitar las características de seguridad y análisis{% ifversion fpt or ghec %} para los repositorios privados{% endif %} +## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %} You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion fpt or ghes or ghec %} If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %}{% endif %} @@ -46,69 +46,77 @@ You can manage the security and analysis features for your {% ifversion fpt or g {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} {% ifversion fpt or ghes > 3.0 or ghec %} -4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %} -!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% elsif ghes > 3.2 %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% else %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} {% note %} - **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion fpt or ghec %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Cualquier flujo de trabajo, cargas de SARIF o llamados de la API para el {% data variables.product.prodname_code_scanning %} fallarán. + **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion fpt or ghec %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. {% endnote %} {% endif %} {% ifversion ghes = 3.0 %} -4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} {% ifversion ghae %} -4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. Antes de que puedas habilitar el "{% data variables.product.prodname_secret_scanning %}" para tu repositorio, puede que necesites habilitar la {% data variables.product.prodname_GH_advanced_security %}. ![Habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} o el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. Before you can enable "{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}. + ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png) {% endif %} -## Otorgar acceso a las alertas de seguridad +## Granting access to security alerts -Después de que habilitas al {% ifversion not ghae %}{% data variables.product.prodname_dependabot %} o {% endif %}las alertas del {% data variables.product.prodname_secret_scanning %} para un repositorio en una organización, los propietarios de esta y los administradores de repositorio pueden ver las alertas predeterminadamente. Puedes dar acceso a equipos y personas adicionales para las alertas de un repositorio. +After you enable {% ifversion not ghae %}{% data variables.product.prodname_dependabot %} or {% endif %}{% data variables.product.prodname_secret_scanning %} alerts for a repository in an organization, organization owners and repository administrators can view the alerts by default. You can give additional teams and people access to the alerts for a repository. {% note %} -Los propietarios de las organizaciones y administradores de repositorio solo pueden otorgar acceso para visualizar alertas de seguridad, tales como alertas del {% data variables.product.prodname_secret_scanning %}, para las personas o equipos que tienen acceso de escritura en el repositorio. +Organization owners and repository administrators can only grant access to view security alerts, such as {% data variables.product.prodname_secret_scanning %} alerts, to people or teams who have write access to the repo. {% endnote %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Acceso a las alertas", en el campo de búsqueda, comienza a teclear el nombre de la persona o equipo que quieres encontrar y luego da clic en su nombre dentro de la lista de coincidencias. - {% ifversion fpt or ghec %} - ![Campo de búsqueda para otorgar acceso a las alertas de seguridad a personas y equipos](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. + {% ifversion fpt or ghec or ghes > 3.2 %} + ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) {% endif %} - {% ifversion ghes %} - ![Campo de búsqueda para otorgar acceso a las alertas de seguridad a personas y equipos](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% ifversion ghes < 3.3 %} + ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png) {% endif %} {% ifversion ghae %} - ![Campo de búsqueda para otorgar acceso a las alertas de seguridad a personas y equipos](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png) + ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png) + {% endif %} + +5. Click **Save changes**. + {% ifversion fpt or ghes > 3.2 or ghec %} + !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) + {% endif %} + {% ifversion ghes < 3.3 %} + !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png) + {% endif %} + {% ifversion ghae %} + !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png) {% endif %} -5. Haz clic en **Guardar cambios**. - {% ifversion fpt or ghes or ghec %} - ![Botón de "Guardar cambios" para los cambios realizados a la configuración de alertas de seguridad](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) - {% endif %} - {% ifversion ghae %} - ![Botón de "Guardar cambios" para los cambios realizados a la configuración de alertas de seguridad](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png) - {% endif %} - -## Eliminar el acceso a las alertas de seguridad +## Removing access to security alerts {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Acceso a las alertas", a la derecha de la persona o equipo para el cual quieres eliminar el acceso, haz clic en {% octicon "x" aria-label="X symbol" %}. - {% ifversion fpt or ghec %} - ![Botón "x" para eliminar el acceso de alguien a las alertas de seguridad para tu repositorio](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. + {% ifversion fpt or ghec or ghes > 3.2 %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) {% endif %} - {% ifversion ghes %} - ![Botón "x" para eliminar el acceso de alguien a las alertas de seguridad para tu repositorio](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% ifversion ghes < 3.3 %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png) {% endif %} {% ifversion ghae %} - ![Botón "x" para eliminar el acceso de alguien a las alertas de seguridad para tu repositorio](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png) + !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png) {% endif %} + 5. Click **Save changes**. -## Leer más +## Further reading -- "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)" -- "[Administrar la seguridad y la configuración de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" +- "[Securing your repository](/code-security/getting-started/securing-your-repository)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md index 4337f7f3b6..cc124d180d 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Administrar la política de ramificación para tu repositorio -intro: 'Puedes permitir o prevenir la ramificación de un repositorio privado {% ifversion fpt or ghae or ghes or ghec %} o interno {% endif %} en específico que sea propiedad de una organización.' +title: Managing the forking policy for your repository +intro: 'You can allow or prevent the forking of a specific private{% ifversion fpt or ghae or ghes or ghec %} or internal{% endif %} repository owned by an organization.' redirect_from: - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization @@ -14,18 +14,18 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Administrar la política de bifurcación +shortTitle: Manage the forking policy --- - -El propietario de la organización debe permitir que las ramificaciones de repositorios privados {% ifversion fpt or ghae or ghes or ghec %} e internos {% endif %} a nivel organizacional antes de que puedas permitir o impedir las ramificaciones de un repositorio específico. Para obtener más información, consulta "[Administrar la política de ramificación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." +An organization owner must allow forks of private{% ifversion fpt or ghae or ghes or ghec %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." {% data reusables.organizations.internal-repos-enterprise %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. En "Features" (Características), selecciona **Allow forking** (Permitir bifurcación). ![Casilla de verificación para permitir o prohibir la bifurcación de un repositorio privado](/assets/images/help/repository/allow-forking-specific-org-repo.png) +3. Under "Features", select **Allow forking**. + ![Checkbox to allow or disallow forking of a private repository](/assets/images/help/repository/allow-forking-specific-org-repo.png) -## Leer más +## Further reading -- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index f93beac0df..d9b908a097 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -1,6 +1,6 @@ --- -title: Configurar la visibilidad de un repositorio -intro: Puedes elegir quién puede ver tu repositorio. +title: Setting repository visibility +intro: You can choose who can view your repository. redirect_from: - /articles/making-a-private-repository-public/ - /articles/making-a-public-repository-private/ @@ -15,86 +15,85 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Visibilidad del repositorio +shortTitle: Repository visibility --- +## About repository visibility changes -## Acerca de los cambios a la visibilidad de un repositorio - -Los propietarios de las organizaciones pueden restringir la capacidad de cambiar la visibilidad de un repositorio únicamente para otros propietarios de organizaciones. Para obtener más información, consulta la sección "[Restringir los cambios a la visibilidad del repositorio en tu organización](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)". +Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." {% ifversion fpt or ghec %} -Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, los repositorios que pertenezcan a tu cuenta de usuario solo podrán ser privados, y aquellos en las organizaciones de tu empresa solo podrán ser privados o internos. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. {% endif %} -Te recomendamos revisar las siguientes consideraciones antes de que cambies la visibilidad de un repositorio. +We recommend reviewing the following caveats before you change the visibility of a repository. {% ifversion ghes or ghae %} {% warning %} -**Advertencia:** Los cambios en la visbilidad de un repositorio grande o en una red de repositorio podrían afectar a la integridad de los datos. Los cambios en la visibilidad también pueden tener efectos accidentales en las bifurcaciones. {% data variables.product.company_short %} recomienda lo siguiente antes de que cambies la visibilidad de una red de un repositorio. +**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network. -- Espera a un periodo de actividad reducida en {% data variables.product.product_location %}. +- Wait for a period of reduced activity on {% data variables.product.product_location %}. -- Contacta a tu {% ifversion ghes %}administrador de sitio{% elsif ghae %}propietario de empresa{% endif %} antes de proceder. Tu {% ifversion ghes %}administrador de sitio{% elsif ghae %}propietario de empresa{% endif %} puede contactar al {% data variables.contact.contact_ent_support %} para obtener más instrucciones. +- Contact your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} before proceeding. Your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance. {% endwarning %} {% endif %} -### Convertir un repositorio en privado +### Making a repository private {% ifversion fpt or ghes or ghec %} -* {% data variables.product.product_name %} separará las bifurcaciones públicas del repositorio público y las pondrá en una red nueva. Las bifurcaciones públicas no se hacen privadas.{% endif %} -* Si cambias la visibilidad de un repositorio de interna a privada, {% data variables.product.prodname_dotcom %} eliminará las bifurcaciones que pertenezcan a cualquiera de los usuarios sin acceso al repositorio que recientemente se hizo privado. {% ifversion fpt or ghes or ghec %}La visibilidad de cualquier bifurcación también cambiará a privada.{% elsif ghae %}Si el repositorio interno tiene cualquier bifurcación, la visibilidad de éstas ya será privada.{% endif %} Para obtener más información, consulta la sección "[¿Qué pasa con las bifurcaciones cuando un repositorio se borra o cambia su visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% ifversion fpt or ghec %} -* Si utilizas {% data variables.product.prodname_free_user %} para cuentas de usuario o de organización, algunas características no estarán disponibles en el repositorio después de que cambies la visibilidad a privada. {% data reusables.gated-features.more-info %}{% endif %} -* Cualquier sitio de {% data variables.product.prodname_pages %} publicado se dejará de publicar automáticamente.{% ifversion fpt or ghec %} Si agregaste un dominio personalizado al sitio de {% data variables.product.prodname_pages %}, deberás eliminar o actualizar tus registros de DNS antes de que hagas al repositorio privado para evitar el riesgo de que alguien más tome el dominio. Para obtener más información, consulta la sección "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %}{% ifversion fpt or ghec %} -* {% data variables.product.prodname_dotcom %} ya no incluirá el repositorio en el {% data variables.product.prodname_archive %}. Para obtener más información, consulta la sección "[Acerca de archivar el contenido y los datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)".{% endif %}{% ifversion fpt or ghec %} -* Las características de la {% data variables.product.prodname_GH_advanced_security %}, tales como el {% data variables.product.prodname_code_scanning %}, dejarán de funcionar a menos de que el repositorio pertenezca a una organización que sea parte de una empresa con una licencia para {% data variables.product.prodname_advanced_security %} y suficientes plazas disponibles. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion ghes %} -* El acceso anónimo de Git ya no está disponible. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".{% endif %} +* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %} +* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% ifversion fpt %} +* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% ifversion fpt or ghec %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion ghes %} +* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} {% ifversion fpt or ghae or ghes or ghec %} -### Convertir un repositorio en interno +### Making a repository internal {% note %} -**Nota:** {% data reusables.gated-features.internal-repos %} +**Note:** {% data reusables.gated-features.internal-repos %} {% endnote %} -* Cualquier bifurcación del repositorio se mantendrá en la red del mismo y {% data variables.product.product_name %} mantendrá la relación entre el repositorio raíz y la bifurcación. Para obtener más información, consulta la sección "[¿Qué le sucede a las bifurcaciones cuando se elimina un repositorio o cuando cambia la visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" +* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" {% endif %} {% ifversion fpt or ghes or ghec %} -### Convertir un repositorio en público +### Making a repository public -* {% data variables.product.product_name %} se deslindará de las bifurcaciones privadas y lasconvertirá en repositorios privados independientes. Para obtener más información, consulta la sección "[¿Qué sucede con las bifurcaciones cuando se borra un repositorio o cuando cambia su visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %} -* Si vas a convertir tu repositorio privado en uno público como parte de un movimiento hacia la creación de un proyecto de código abierto, consulta las [Guías de Código Abierto](http://opensource.guide) para encontrar tips ylineamientos útiles. También puedes tomar un curso gratuito sobre cómo administrar un proyecto de código abierto con [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Una vez que tu repositorio es público, también puedes ver el perfil de la comunidad de tu repositorio para ver si tu proyecto cumple con las mejoras prácticas para los colaboradores de apoyo. Para obtener más información, consulta "[Ver el perfil de tu comunidad](/articles/viewing-your-community-profile)" -* El repositorio obtendrá acceso automático a las características de la {% data variables.product.prodname_GH_advanced_security %}. +* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. -Para obtener más información sobre cómo mejorar la seguridad del repositorio, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)".{% endif %} +For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %} {% endif %} -## Cambiar la visibilidad de un repositorio +## Changing a repository's visibility {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Debajo de "Zona de Peligro", a la derecha de "Cambiar la visibilidad del repositorio", da clic en **Cambiar la visibilidad**. ![Botón de cambiar la visibilidad](/assets/images/help/repository/repo-change-vis.png) -4. Selecciona una visibilidad. +3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**. + ![Change visibility button](/assets/images/help/repository/repo-change-vis.png) +4. Select a visibility. {% ifversion fpt or ghec %} - ![Diálogo de opciones para la visbilidad del repositorio](/assets/images/help/repository/repo-change-select.png){% else %} -![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %} -5. Para verificar que estás cambiando la visibilidad del repositorio correcto, teclea el nombre del repositorio para el cual quieres cambiar la visibilidad. -6. Da clic en **Entiendo, cambiar la visibilidad del repositorio**. + ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %} + ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %} +5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of. +6. Click **I understand, change repository visibility**. {% ifversion fpt or ghec %} - ![Botón de confirmar cambio para la visibilidad de un repositorio](/assets/images/help/repository/repo-change-confirm.png){% else %} -![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} + ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %} + ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} -## Leer más -- "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" +## Further reading +- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md b/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md index 0a7cdc8471..883c2fc595 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md @@ -1,6 +1,6 @@ --- -title: Acerca de los lanzamientos -intro: 'Puedes crear un lanzamiento para empaquetar software, junto con notas de lanzamiento y enlaces a archivos binarios, para que los usen otras personas.' +title: About releases +intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.' redirect_from: - /articles/downloading-files-from-the-command-line/ - /articles/downloading-files-with-curl/ @@ -17,43 +17,42 @@ versions: topics: - Repositories --- - -## Acerca de los lanzamientos +## About releases {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} -![Un resumen de los lanzamientos](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) -{% elsif ghes > 3.2 or ghae-issue-4972 %} -![Un resumen de los lanzamientos](/assets/images/help/releases/releases-overview-with-contributors.png) +![An overview of releases](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) +{% elsif ghes > 3.3 or ghae-issue-4972 %} +![An overview of releases](/assets/images/help/releases/releases-overview-with-contributors.png) {% else %} -![Un resumen de los lanzamientos](/assets/images/help/releases/releases-overview.png) +![An overview of releases](/assets/images/help/releases/releases-overview.png) {% endif %} -Los lanzamientos son iteraciones de software desplegable que puedes empaquetar y poner a disposición de una audiencia más amplia para su descarga y uso. +Releases are deployable software iterations you can package and make available for a wider audience to download and use. -Los lanzamientos se basan en las [etiquetas Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcan un punto específico en el historial de tu repositorio. Una fecha de etiqueta puede ser diferente a una fecha de lanzamiento ya que ambas pueden crearse en momentos diferentes. Para obtener más información sobre cómo visualizar tus etiquetas existentes, consulta "[Ver las etiquetas y lanzamientos de tu repositorio](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." +Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." -Puedes recibir notificaciones cuando se publican nuevos lanzamientos en un repositorio sin recibir notificaciones sobre otras actualizaciones del repositorio. Para obtener más información, consulta la sección {% ifversion fpt or ghae or ghes or ghec %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Observar y dejar de observar los lanzamientos de un repositorio](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}". +You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching releases for a repository](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." -Cualquiera que tenga acceso de lectura a un repositorio podrá ver y comparar los lanzamientos, pero únicamente aquellos con permisos de escritura en éste podrán administrarlos. Para obtener más información, consulta "[Administrar lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)." +Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)." {% ifversion fpt or ghec %} -Puedes crear notas de lanzamiento manualmente mientras administras un lanzamiento. Como alternativa, puedes generar notas de lanzamiento automáticamente desde una plantilla predeterminada o personalizar tu propia plantilla de notas de lanzamiento. Para obtener más información, consulta la sección "[Notas de lanzamiento generadas automáticamente](/repositories/releasing-projects-on-github/automatically-generated-release-notes)". +You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)." -Las personas con permisos administrativos sobre un repositorio pueden elegir si los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluirán en los archivos ZIP y en los archivos .tar que {% data variables.product.product_name %} crea para cada lanzamiento. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". +People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} {% ifversion fpt or ghec %} -Si un lanzamiento arregla una vulnerabilidad de seguridad, deberás publicar una asesoría de seguridad en tu repositorio. {% data variables.product.prodname_dotcom %} revisa cada asesoría de seguridad que se publica y podría utilizarla para enviar {% data variables.product.prodname_dependabot_alerts %} a los repositorios afectados. Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)". +If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -Puedes ver la pestaña de **Dependientes** de la gráfica de dependientes para ver qué repositorios y paquetes dependen del código en tu repositorio, y podrían entonces verse afectados con un nuevo lanzamiento. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -También puedes usar la API de releases para recopilar información, como la cantidad de veces que las personas descargan un recurso de lanzamiento. Para obtener más información, consulta la sección "[Lanzamientos](/rest/reference/repos#releases)." +You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)." {% ifversion fpt or ghec %} -## Cuotas de ancho de banda y de almacenamiento +## Storage and bandwidth quotas - Cada archivo incluido en un lanzamiento debe ser de menos de {% data variables.large_files.max_file_size %}. No hay un límite para el tamaño total de un lanzamiento, ni para el uso de ancho de banda. + Each file included in a release must be under {% data variables.large_files.max_file_size %}. There is no limit on the total size of a release, nor bandwidth usage. {% endif %} diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index f173f77d75..f03d82caf8 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -1,6 +1,6 @@ --- -title: Administrar lanzamientos en un repositorio -intro: Puedes crear lanzamientos que desees poner en conjunto y entregar iteraciones de un proyecto a los usuarios. +title: Managing releases in a repository +intro: You can create releases to bundle and deliver iterations of a project to users. redirect_from: - /articles/creating-releases - /articles/listing-and-editing-releases/ @@ -18,23 +18,22 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Administrar los lanzamientos +shortTitle: Manage releases --- - {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -## Acerca de la administración de lanzamientos +## About release management -Puedes crear lanzamientos nuevos con notas de lanzamiento, @menciones de contribuyentes y enlaces a archivos binarios, así como editar o borrar los lanzamientos existentes. +You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases. {% ifversion fpt or ghec %} -También puedes publicar una acción desde un lanzamiento específico en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "Publicar una acción en {% data variables.product.prodname_marketplace %}". +You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "Publishing an action in the {% data variables.product.prodname_marketplace %}." -Puedes elegir si los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluirán en los archivos ZIP y .tar que cree {% data variables.product.product_name %} para cada lanzamiento. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". +You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} {% endif %} -## Crear un lanzamiento +## Creating a release {% include tool-switcher %} @@ -42,40 +41,47 @@ Puedes elegir si los objetos de {% data variables.large_files.product_name_long {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} -3. Haz clic en **Borrador de un nuevo lanzamiento**. +3. Click **Draft a new release**. + {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %} -4. {% ifversion fpt or ghec %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec %}, and press **Enter**{% endif %}. Como alternativa, selecciona una etiqueta existente. - {% ifversion fpt or ghec %} - ![Ingresa una etiqueta](/assets/images/help/releases/releases-tag-create.png) -5. Si estás creando una etiqueta nueva, haz clic en **Crear etiqueta nueva**. ![Confirma si quieres crear una etiqueta nueva](/assets/images/help/releases/releases-tag-create-confirm.png) +4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}, and press **Enter**{% endif %}. Alternatively, select an existing tag. + + {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. + + ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} - ![Versión de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-version.png) + ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. Si creaste una etiqueta nueva, utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar. - {% ifversion fpt or ghec %}![Elige una rama](/assets/images/help/releases/releases-choose-branch.png) - {% else %}![Rama de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-branch.png) - {% endif %} -6. Escribe un título y una descripción para tu lanzamiento. - {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 %} - Si @mencionas a cualquier usuario de {% data variables.product.product_name %} en la descripción, el lanzamiento publicado incluirá una sección de **Contribuyentes** con una lista de avatares de los usuarios mencionados. +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + + {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %} +6. Type a title and description for your release. + {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} + If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - {% ifversion fpt or ghec %} Como alternativa, puedes generar tus notas de lanzamiento automáticamente dando clic en **Generar notas de lanzamiento automáticamente**. + {% ifversion fpt or ghec %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. {% endif %} - ![Descripción de lanzamientos](/assets/images/help/releases/releases_description_auto.png) -7. Opcionalmente, para incluir los archivos binarios tales como programas compilados en tu lanzamiento, arrastra y suelta o selecciona manualmente los archivos en la caja de binarios. ![Proporcionar un DMG con el lanzamiento](/assets/images/help/releases/releases_adding_binary.gif) -8. Para notificar a los usuarios que el lanzamiento no está listo para producción y puede ser inestable, selecciona **Esto es un pre-lanzamiento**. ![Casilla de verificación para marcar un lanzamiento como prelanzamiento](/assets/images/help/releases/prerelease_checkbox.png) + ![Releases description](/assets/images/help/releases/releases_description_auto.png) +7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. + ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) +8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. + ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt or ghec %} -1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Casilla de verificación para crear un debate de lanzamiento y menú desplegable para elegir una categoría](/assets/images/help/releases/create-release-discussion.png) +1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. + ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) {%- endif %} -9. Si estás listo para publicitar tu lanzamiento, haz clic en **Publicar lanzamiento**. Para seguir trabajando luego en el lanzamiento, haz clic en **Guardar borrador**. ![Botones Publicar lanzamiento y Borrador de lanzamiento](/assets/images/help/releases/release_buttons.png) +9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. + ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 or ghae-issue-4974 %} - Entonces podrás ver tus lanzamientos publicados o en borrador dentro de las noticias de lanzamientos de tu repositorio. Para obtener más información, consulta la sección "[Ver las etiquetas y lanzamientos de tu repositorio](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)". + You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)." {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} - ![Lanzamiento publicado con contribuyentes @mencionados](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) - {% else %} - ![Lanzamiento publicado con contribuyentes @mencionados](/assets/images/help/releases/releases-overview-with-contributors.png) + ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) + {% else %} + ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png) {% endif %} {%- endif %} @@ -85,24 +91,24 @@ Puedes elegir si los objetos de {% data variables.large_files.product_name_long {% data reusables.cli.cli-learn-more %} -1. Para crear un lanzamiento, utiliza el subcomando `gh release create`. Reemplaza `tag` con la etiqueta deseada para el lanzamiento. +1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release. ```shell gh release create tag ``` -2. Sigue los mensajes interactivos. Como alternativa, puedes especificar los argumentos para omitir estos mensajes. Para obtener más información sobre los argumentos posibles, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_release_create). Por ejemplo, este comando crea un pre-lanzamiento con el título y notas especificados. +2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes. ```shell gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease ``` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4972 or ghec %} -Si @mencionas a cualquier usuario de {% data variables.product.product_name %} en las notas, el lanzamiento publicado en el {% data variables.product.prodname_dotcom_the_website %} incluirá una sección de **Contribuyentes** con una lista de avatares de todos los usuarios mencionados. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4972 or ghec %} +If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users. {% endif %} {% endcli %} -## Editar un lanzamiento +## Editing a release {% include tool-switcher %} @@ -111,21 +117,24 @@ Si @mencionas a cualquier usuario de {% data variables.product.product_name %} e {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} -3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. ![Editar un lanzamiento](/assets/images/help/releases/edit-release-pencil.png) +3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. + ![Edit a release](/assets/images/help/releases/edit-release-pencil.png) {% else %} -3. En la parte derecha de la página, junto al lanzamiento que quieres editar, da clic en **Editar lanzamiento**. ![Editar un lanzamiento](/assets/images/help/releases/edit-release.png) +3. On the right side of the page, next to the release you want to edit, click **Edit release**. + ![Edit a release](/assets/images/help/releases/edit-release.png) {% endif %} -4. Edita los detalles del lanzamiento en el formato, luego haz clic en **Actualizar lanzamiento**.{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 %} Si agregas o eliminas cualquier @mención de los usuarios de GitHub en la descripción, estos se agregarán o eliminarán de la lista de avatares en la sección de **Contribuyentes** del lanzamiento.{% endif %} ![Actualizar un lanzamiento](/assets/images/help/releases/update-release.png) +4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %} + ![Update a release](/assets/images/help/releases/update-release.png) {% endwebui %} {% cli %} -Los lanzamientos no pueden editarse con {% data variables.product.prodname_cli %} actualmente. +Releases cannot currently be edited with {% data variables.product.prodname_cli %}. {% endcli %} -## Eliminar un lanzamiento +## Deleting a release {% include tool-switcher %} @@ -134,18 +143,22 @@ Los lanzamientos no pueden editarse con {% data variables.product.prodname_cli % {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} -3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. ![Borrar un lanzamiento](/assets/images/help/releases/delete-release-trash.png) +3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. + ![Delete a release](/assets/images/help/releases/delete-release-trash.png) {% else %} -3. Da clic en el nombre del lanzamiento que quieres eliminar. ![Enlace para ver el lanzamiento](/assets/images/help/releases/release-name-link.png) -4. En la esquina superior derecha de la página, haz clic en **Eliminar**. ![Botón para eliminar lanzamiento](/assets/images/help/releases/delete-release.png) +3. Click the name of the release you wish to delete. + ![Link to view release](/assets/images/help/releases/release-name-link.png) +4. In the upper-right corner of the page, click **Delete**. + ![Delete release button](/assets/images/help/releases/delete-release.png) {% endif %} -5. Da clic en **Eliminar este lanzamiento**. ![Confirmar la eliminación del lanzamiento](/assets/images/help/releases/confirm-delete-release.png) +5. Click **Delete this release**. + ![Confirm delete release](/assets/images/help/releases/confirm-delete-release.png) {% endwebui %} {% cli %} -1. Para borrar un lanzamiento, utiliza el subcomando `gh release delete`. Reemplaza `tag` con la etiqueta del lanzamiento que se debe borrar. Utiliza el marcador `-y` para omitir la confirmación. +1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation. ```shell gh release delete tag -y diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md index 27b618cbf5..0035e6e331 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md @@ -1,6 +1,6 @@ --- -title: Ver los colaboradores de un proyecto -intro: 'Puedes ver quién aportó confirmaciones a un repositorio{% ifversion fpt or ghec %} y sus dependencias{% endif %}.' +title: Viewing a project's contributors +intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.' redirect_from: - /articles/i-don-t-see-myself-in-the-contributions-graph/ - /articles/viewing-contribution-activity-in-a-repository/ @@ -15,37 +15,38 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Visualizar a los contribuyentes del proyecto +shortTitle: View project contributors --- +## About contributors -## Acerca de los colaboradores - -Puedes ver hasta 100 colaboradores de un repositorio{% ifversion ghes or ghae %}, incluidos los coautores de confirmaciones,{% endif %} en el gráfico de colaboradores. Las confirmaciones de fusión y las confirmaciones vacías no se cuentan en las contribuciones para este gráfico. +You can view the top 100 contributors to a repository{% ifversion ghes or ghae %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph. {% ifversion fpt or ghec %} -También puedes ver una lista de personas que han contribuido con las dependencias de Python del proyecto. Para acceder a esta lista de colaboradores de la comunidad, visita `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. +You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. {% endif %} -## Acceder al gráfico de colaboradores +## Accessing the contributors graph {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} -3. En la barra lateral izquierda, haz clic en **Contributors (Colaboradores)**. ![Pestaña de colaboradores](/assets/images/help/graphs/contributors_tab.png) -4. Como alternativa, para ver colaboradores durante un período de tiempo específico, haz clic, después arrastra hasta que se selecciona el período de tiempo. La gráfica de contribuyentes suma las cantidades de confirmaciones semanales cada domingo, así que tu periodo de tiempo debe incluir un domingo. ![Rango de tiempo seleccionado en el gráfico de colaboradores](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) +3. In the left sidebar, click **Contributors**. + ![Contributors tab](/assets/images/help/graphs/contributors_tab.png) +4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday. + ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) -## Resolución de problemas con colaboradores +## Troubleshooting contributors -Si no apareces en el gráfico de colaboradores de un repositorio, puede deberse a que: -- No eres uno de los 100 colaboradores principales. -- Tus confirmaciones no se han fusionado en la rama por defecto. -- La dirección de correo electrónico que utilizaste para crear las confirmaciones no está conectada a tu cuenta en {% data variables.product.product_name %}. +If you don't appear in a repository's contributors graph, it may be because: +- You aren't one of the top 100 contributors. +- Your commits haven't been merged into the default branch. +- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}. {% tip %} -**Tip:** Para listar todos los colaboradores de una confirmación en un repositorio, consulta la sección "[Repositorios](/rest/reference/repos#list-contributors)". +**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)." {% endtip %} -Si todas tus confirmaciones en el repositorio están en ramas que no son por defecto, no estarás en el gráfico de colaboradores. Por ejemplo, las confirmaciones en la rama `gh-pages` no están incluidas en el gráfico excepto que `gh-pages` sea la rama por defecto del repositorio. Para que tus confirmaciones se fusionen en la rama por defecto, puedes crear una solicitud de extracción. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." +If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Si la dirección de correo electrónico que utilizaste para crear las confirmaciones no está conectada a tu cuenta en {% data variables.product.product_name %}, tus confirmaciones no se enlazarán a ésta, y no aparecerás en la gráfica de colaboradores. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address){% ifversion not ghae %}" y "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/adding-an-email-address-to-your-github-account){% endif %}". +If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address){% ifversion not ghae %}" and "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}." diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md index 295056557e..2ded74c394 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Ver la actividad de implementación de tu repositorio -intro: Puedes ver la información acerca de las implementaciones de tu repositorio completo o de una solicitud de extracción específica. +title: Viewing deployment activity for your repository +intro: You can view information about deployments for your entire repository or a specific pull request. redirect_from: - /articles/viewing-deployment-activity-for-your-repository - /github/administering-a-repository/viewing-deployment-activity-for-your-repository @@ -12,23 +12,23 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Visualizar la actividad de despliegue +shortTitle: View deployment activity --- - {% note %} -**Nota:** el tablero de implementaciones está actualmente en beta y es susceptible a cambios. +**Note:** The deployments dashboard is currently in beta and subject to change. {% endnote %} -Las personas con acceso de lectura a un repositorio pueden ver un resumen de todas las implementaciones actuales y un registro de la actividad de implementación pasada, si el flujo de trabajo de implementación del repositorio está integrado con {% data variables.product.product_name %} a través de las implementaciones API o una app de [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment). Para obtener más información, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". +People with read access to a repository can see an overview of all current deployments and a log of past deployment activity, if the repository's deployment workflow is integrated with {% data variables.product.product_name %} through the Deployments API or an app from [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment). For more information, see "[Deployments](/rest/reference/repos#deployments)." -También puedes ver información de implementación en la pestaña "Conversation" (Conversación) de una solicitud de extracción. +You can also see deployment information on the "Conversation" tab of a pull request. -## Ver el tablero de implementaciones +## Viewing the deployments dashboard {% data reusables.repositories.navigate-to-repo %} -2. A la derecha de la lista de archivos, haz clic en **Ambientes**. ![Ambientes a la derecha de la página del repositorio](/assets/images/help/repository/environments.png) +2. To the right of the list of files, click **Environments**. +![Environments on the right of the repository page](/assets/images/help/repository/environments.png) -## Leer más - - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" +## Further reading + - "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md b/translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md index b68c6e01d9..ab6df4bca0 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md @@ -1,6 +1,6 @@ --- -title: Crear nuevos archivos -intro: 'Puedes crear nuevos archivos directamente en {% data variables.product.product_name %} en cualquier repositorio al que tengas acceso de escritura.' +title: Creating new files +intro: 'You can create new files directly on {% data variables.product.product_name %} in any repository you have write access to.' redirect_from: - /articles/creating-new-files - /github/managing-files-in-a-repository/creating-new-files @@ -13,20 +13,22 @@ versions: topics: - Repositories --- +When creating a file on {% data variables.product.product_name %}, consider the following: -Cuando crees un archivo en {% data variables.product.product_name %}, ten en cuenta lo siguiente: - -- Si intentas crear un nuevo archivo en un repositorio al que no tienes acceso, bifurcaremos el proyecto para tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original una vez que confirmes tu cambio. -- Los nombres de los archivos creados a través de la interfaz web solo pueden contener caracteres alfanuméricos y guiones (`-`). Para usar otros caracteres, [crea y confirma los archivos de manera local, y luego súbelos al repositorio en {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository-using-the-command-line). +- If you try to create a new file in a repository that you don’t have access to, we will fork the project to your user account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. +- File names created via the web interface can only contain alphanumeric characters and hyphens (`-`). To use other characters, [create and commit the files locally, then push them to the repository on {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository-using-the-command-line). {% data reusables.repositories.sensitive-info-warning %} {% data reusables.repositories.navigate-to-repo %} -2. En tu repositorio, dirígete a la carpeta en la que deseas crear un archivo. +2. In your repository, browse to the folder where you want to create a file. {% data reusables.files.add-file %} -4. En el campo para el nombre del archivo, escribe el nombre y la extensión del archivo. Para crear subdirectorios, escribe el separador de directorio `/`. ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png) -5. En la pestaña **Editar nuevo archivo**, agrega contenido al archivo. ![Contenido del nuevo archivo](/assets/images/help/repository/new-file-content.png) -6. Para revisar el nuevo contenido, haz clic en **Vista previa**. ![Botón New file preview (Vista previa del archivo nuevo)](/assets/images/help/repository/new-file-preview.png) +4. In the file name field, type the name and extension for the file. To create subdirectories, type the `/` directory separator. +![New file name](/assets/images/help/repository/new-file-name.png) +5. On the **Edit new file** tab, add content to the file. +![Content in new file](/assets/images/help/repository/new-file-content.png) +6. To review the new content, click **Preview**. +![New file preview button](/assets/images/help/repository/new-file-preview.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md b/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md index f9b92eddf4..04611a377b 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md @@ -1,6 +1,6 @@ --- -title: Mover un archivo a una nueva ubicación -intro: 'Puedes mover un archivo a un directorio diferente desde {% data variables.product.product_name %} o utilizando la línea de comandos.' +title: Moving a file to a new location +intro: 'You can move a file to a different directory on {% data variables.product.product_name %} or by using the command line.' redirect_from: - /articles/moving-a-file-to-a-new-location - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location @@ -15,43 +15,44 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Mover un archivo +shortTitle: Move a file --- +In addition to changing the file location, you can also [update the contents of your file](/articles/editing-files-in-your-repository), or [give it a new name](/articles/renaming-a-file) in the same commit. -Además de cambiar la ubicación del archivo, también puedes [actualizar los contenidos de tu archivo](/articles/editing-files-in-your-repository), o [darle un nuevo nombre](/articles/renaming-a-file) en la misma confirmación. - -## Migrar un archivo a una ubicación nueva en {% data variables.product.product_name %} +## Moving a file to a new location on {% data variables.product.product_name %} {% tip %} **Tips**: -- Si tratas de mover un archivo en un repositorio al cual no tienes acceso, bifurcaremos el proyecto a tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de confirmar tu cambio. -- Algunos archivos, como imágenes, necesitan que los muevas desde la línea de comando. Para obtener más información, consulta "[Mover un archivo a una nueva ubicación utilizando la línea de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)". +- If you try to move a file in a repository that you don’t have access to, we'll fork the project to your user account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. +- Some files, such as images, require that you move them from the command line. For more information, see "[Moving a file to a new location using the command line](/articles/moving-a-file-to-a-new-location-using-the-command-line)". - {% data reusables.repositories.protected-branches-block-web-edits-uploads %} {% endtip %} -1. En tu repositorio, navega hasta el archivo que deseas mover. -2. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Icono Edit file (Editar archivo)](/assets/images/help/repository/move-file-edit-file-icon.png) -3. En el campo de nombre de archivo, cambia el nombre del archivo utilizando estos lineamientos: ![Editar el nombre del archivo](/assets/images/help/repository/moving_files.gif) - - Para mover el archivo **dentro de una subcarpeta**, escribe el nombre de la carpeta que deseas, seguido de `/`. El nombre de tu nueva carpeta se convierte en el nuevo elemento en la ruta de navegación. - - Para mover el archivo dentro de un directorio **encima de la ubicación actual del archivo**, coloca tu cursor al comienzo del campo de nombre de archivo, después escribe `../` para subir un nivel completo de directorio, o presiona la tecla de `retroceso` para editar el nombre de la carpeta padre. +1. In your repository, browse to the file you want to move. +2. In the upper right corner of the file view, click {% octicon "pencil" aria-label="The edit icon" %} to open the file editor. +![Edit file icon](/assets/images/help/repository/move-file-edit-file-icon.png) +3. In the filename field, change the name of the file using these guidelines: + ![Editing a file name](/assets/images/help/repository/moving_files.gif) + - To move the file **into a subfolder**, type the name of the folder you want, followed by `/`. Your new folder name becomes a new item in the navigation breadcrumbs. + - To move the file into a directory **above the file's current location**, place your cursor at the beginning of the filename field, then either type `../` to jump up one full directory level, or type the `backspace` key to edit the parent folder's name. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -## Mover un archivo a una nueva ubicación utilizando la línea de comando +## Moving a file to a new location using the command line -Puedes utilizar la línea de comando para mover archivos dentro de un repositorio al eliminar el archivo de la ubicación anterior y después agregarlo en la nueva ubicación. +You can use the command line to move files within a repository by removing the file from the old location and then adding it in the new location. -Muchos archivos pueden [moverse directamente en {% data variables.product.product_name %}](/articles/moving-a-file-to-a-new-location), pero algunos archivos, como imágenes, necesitan que los muevas desde la línea de comando. +Many files can be [moved directly on {% data variables.product.product_name %}](/articles/moving-a-file-to-a-new-location), but some files, such as images, require that you move them from the command line. {% data reusables.command_line.manipulating_file_prereqs %} -1. En la computadora, mueve el archivo a una nueva ubicación dentro del directorio que fue creado localmente en tu computadora cuando clonaste el repositorio. +1. On your computer, move the file to a new location within the directory that was created locally on your computer when you cloned the repository. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Utiliza `git status` para verificar la nueva ubicación y la ubicación anterior del archivo. +3. Use `git status` to check the old and new file locations. ```shell $ git status > # On branch your-branch @@ -68,13 +69,13 @@ Muchos archivos pueden [moverse directamente en {% data variables.product.produc > # > # no changes added to commit (use "git add" and/or "git commit -a") ``` -{% data reusables.git.stage_for_commit %} Esto eliminará, o `git rm`, el archivo de la ubicación antigua y agregará, o `git add`, el archivo en la nueva ubicación. +{% data reusables.git.stage_for_commit %} This will delete, or `git rm`, the file from the old location and add, or `git add`, the file to the new location. ```shell $ git add . - # Agrega el archivo a tu repositorio local y lo presenta para la confirmación. + # Adds the file to your local repository and stages it for commit. # {% data reusables.git.unstage-codeblock %} ``` -5. Utiliza `git status` para verificar los cambios preparados para confirmar. +5. Use `git status` to check the changes staged for commit. ```shell $ git status > # On branch your-branch diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md b/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md index c2bb6b9c15..3eed3e628b 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md @@ -1,6 +1,6 @@ --- -title: Renombrar un archivo -intro: 'Puedes renombrar cualquier archivo en tu repositorio directamente en {% data variables.product.product_name %} o utilizando la línea de comandos.' +title: Renaming a file +intro: 'You can rename any file in your repository directly in {% data variables.product.product_name %} or by using the command line.' redirect_from: - /articles/renaming-a-file - /github/managing-files-in-a-repository/renaming-a-file @@ -17,42 +17,44 @@ topics: - Repositories --- -## Renombrar un archivo en {% data variables.product.product_name %} +## Renaming a file on {% data variables.product.product_name %} -El renombrar un archivo también te da la oportunidad de [mover el archivo a una ubicación nueva](/articles/moving-a-file-to-a-new-location) +Renaming a file also gives you the opportunity to [move the file to a new location](/articles/moving-a-file-to-a-new-location) {% tip %} **Tips**: -- Si intentas renombrar un archivo de un repositorio al que no tienes acceso, bifurcaremos el proyecto para tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de que confirmes tu cambio. -- Los nombres de los archivos creados a través de la interfaz web solo pueden contener caracteres alfanuméricos y guiones (`-`). Para utilizar otros caracteres, crea y confirma los archivos de forma local y luego súbelos al repositorio. -- Algunos archivos, como las imágenes, requieren que los renombres desde la línea de comando. Para obtener más información, consulta "[Renombrar un archivo usando la línea de comando](/articles/renaming-a-file-using-the-command-line)". +- If you try to rename a file in a repository that you don’t have access to, we will fork the project to your user account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. +- File names created via the web interface can only contain alphanumeric characters and hyphens (`-`). To use other characters, create and commit the files locally and then push them to the repository. +- Some files, such as images, require that you rename them from the command line. For more information, see "[Renaming a file using the command line](/articles/renaming-a-file-using-the-command-line)." {% endtip %} -1. En tu repositorio, busca el archivo que quieres renombrar. -2. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Icono Edit file (Editar archivo)](/assets/images/help/repository/edit-file-icon.png) -3. En el campo de nombre del archivo, cambia el nombre del archivo con el nombre de archivo nuevo que quieras. También puedes actualizar los contenidos de tu archivo en el mismo momento. ![Editar el nombre del archivo](/assets/images/help/repository/changing-file-name.png) +1. In your repository, browse to the file you want to rename. +2. In the upper right corner of the file view, click {% octicon "pencil" aria-label="The edit icon" %} to open the file editor. +![Edit file icon](/assets/images/help/repository/edit-file-icon.png) +3. In the filename field, change the name of the file to the new filename you want. You can also update the contents of your file at the same time. +![Editing a file name](/assets/images/help/repository/changing-file-name.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -## Renombrar un archivo usando la línea de comando +## Renaming a file using the command line -Puedes usar la línea de comando para renombrar cualquier archivo de tu repositorio. +You can use the command line to rename any file in your repository. -Muchos archivos se pueden [renombrar directamente en {% data variables.product.product_name %}](/articles/renaming-a-file), pero algunos, como las imágenes, requieren que los renombres desde la línea de comando. +Many files can be [renamed directly on {% data variables.product.product_name %}](/articles/renaming-a-file), but some files, such as images, require that you rename them from the command line. {% data reusables.command_line.manipulating_file_prereqs %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} -3. Renombra el archivo, especificando el nombre de archivo antiguo y el nombre de archivo nuevo que le quieres asignar. Esto preparará tu cambio para la confirmación. +3. Rename the file, specifying the old file name and the new name you'd like to give the file. This will stage your change for commit. ```shell $ git mv old_filename new_filename ``` -4. Utiliza `git status` para comprobar los nombres de archivo antiguo y nuevo. +4. Use `git status` to check the old and new file names. ```shell $ git status > # On branch your-branch diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md index 5864dbd75d..773630514c 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md @@ -1,6 +1,6 @@ --- -title: Colaboración con el almacenamiento de archivos de gran tamaño de Git -intro: 'Con {% data variables.large_files.product_name_short %} habilitado, podrás extraer, modificar y subir archivos de gran tamaño del mismo modo que lo harías con cualquier archivo que administre Git. Sin embargo, un usuario que no tiene {% data variables.large_files.product_name_short %} experimentará un flujo de trabajo diferente.' +title: Collaboration with Git Large File Storage +intro: 'With {% data variables.large_files.product_name_short %} enabled, you''ll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn''t have {% data variables.large_files.product_name_short %} will experience a different workflow.' redirect_from: - /articles/collaboration-with-large-file-storage/ - /articles/collaboration-with-git-large-file-storage @@ -11,37 +11,36 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Colaboración +shortTitle: Collaboration --- - -Si los colaboradores en tu repositorio no tienen {% data variables.large_files.product_name_short %} instalado, no tendrán acceso al archivo de gran tamaño original. Si intentan clonar tu repositorio, solo extraerán los archivos punteros, y no tendrán acceso a los datos trues. +If collaborators on your repository don't have {% data variables.large_files.product_name_short %} installed, they won't have access to the original large file. If they attempt to clone your repository, they will only fetch the pointer files, and won't have access to any of the actual data. {% tip %} -**Tip:** Te recomendamos configurar lineamientos para los contribuyentes del repositorio, los cuales describan la forma de trabajar con archivos grandes, para todo usuario que no tenga {% data variables.large_files.product_name_short %} habilitado. Por ejemplo, puedes pedirles a los colaboradores que no modifiquen archivos de gran tamaño o que carguen los cambios a un servicio de intercambio de archivos como [Dropbox](http://www.dropbox.com/) o Google Drive. Para obtener más información, consulta "[Establecer pautas para los colaboradores del repositorio](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". +**Tip:** To help users without {% data variables.large_files.product_name_short %} enabled, we recommend you set guidelines for repository contributors that describe how to work with large files. For example, you may ask contributors not to modify large files, or to upload changes to a file sharing service like [Dropbox](http://www.dropbox.com/) or Google Drive. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." {% endtip %} -## Ver archivos de gran tamaño en solicitudes de extracción +## Viewing large files in pull requests -{% data variables.product.product_name %} no representa {% data variables.large_files.product_name_short %} objectos en solicitudes de extracción. Únicamente se muestra el archivo de puntero: +{% data variables.product.product_name %} does not render {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown: -![Ejemplo de PR para archivos de gran tamaño](/assets/images/help/large_files/large_files_pr.png) +![Sample PR for large files](/assets/images/help/large_files/large_files_pr.png) -Para obtener más información acerca de los archivos puntero, consulta la sección "[Acerca de{% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". +For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)." -Para ver los cambios que se realizaron en los archivos grandes, verifica localmente la solicitud de extracción para revisar la diferencia. Para obtener más información, consulta la sección "[Revisar las solicitudes de extracción localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)". +To view changes made to large files, check out the pull request locally to review the diff. For more information, see "[Checking out pull requests locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)." {% ifversion fpt or ghec %} -## Subir archivos de gran tamaño a bifurcaciones +## Pushing large files to forks -La subida de archivos de gran tamaño cuenta para el ancho de banda de un repositorio padre y las cuotas de almacenamiento, en lugar de hacerlo para las cuotas del propietario de la bifurcación. +Pushing large files to forks of a repository count against the parent repository's bandwidth and storage quotas, rather than the quotas of the fork owner. -Puedes subir {% data variables.large_files.product_name_short %} objetos a las bifurcaciones públicas si la red del repositorio ya tiene {% data variables.large_files.product_name_short %} objetos o si tienes acceso de escritura a la raíz de la red del repositorio. +You can push {% data variables.large_files.product_name_short %} objects to public forks if the repository network already has {% data variables.large_files.product_name_short %} objects or you have write access to the root of the repository network. {% endif %} -## Leer más +## Further reading -- "[Duplicar un repositorio con objetos de almacenamiento de gran tamaño de Git](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)" +- "[Duplicating a repository with Git Large File Storage objects](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)" diff --git a/translations/es-ES/content/rest/overview/other-authentication-methods.md b/translations/es-ES/content/rest/overview/other-authentication-methods.md index af8f2bffdb..b75ab98525 100644 --- a/translations/es-ES/content/rest/overview/other-authentication-methods.md +++ b/translations/es-ES/content/rest/overview/other-authentication-methods.md @@ -1,6 +1,6 @@ --- -title: Otros métodos de autenticación -intro: Puedes utilizar la autenticación básica para hacer pruebas en un ambiente diferente al productivo. +title: Other authentication methods +intro: You can use basic authentication for testing in a non-production environment. redirect_from: - /v3/auth versions: @@ -10,73 +10,83 @@ versions: ghec: '*' topics: - API -shortTitle: Otros métodos de autenticación +shortTitle: Other authentication methods --- {% ifversion fpt or ghes or ghec %} -Cuando la API proporciona varios métodos de autenticación, te recomendamos fuertemente utilizar [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) para las aplicaciones productivas. Los otros métodos que se proporcionan tienen la intención de que se utilicen para scripts o para pruebas (por ejemplo, en los casos en donde utilizar todo el OAuth sería exagerado). Las aplicaciones de terceros que dependen de -{% data variables.product.product_name %} para la autenticación no deben pedir o recolectar credenciales de {% data variables.product.product_name %}. -En vez de esto, deben utilizar el [flujo web de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). +While the API provides multiple methods for authentication, we strongly +recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) for production applications. The other +methods provided are intended to be used for scripts or testing (i.e., cases +where full OAuth would be overkill). Third party applications that rely on +{% data variables.product.product_name %} for authentication should not ask for or collect {% data variables.product.product_name %} credentials. +Instead, they should use the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). {% endif %} {% ifversion ghae %} -Para autenticarte, te recomendamos utilizar los tokens de [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/), tales como un token de acceso personal a través del [flujo web de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). +To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a personal access token through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). {% endif %} -## Autenticación Básica +## Basic Authentication -La API es compatible con la autenticación básica de acuerdo a lo que se define en el [RFC2617](http://www.ietf.org/rfc/rfc2617.txt) con algunas diferencias menores. La diferencia principal es que el RFC requiere de solicitudes sin autenticar para que se le den respuestas `401 Unauthorized`. En muchos lugares, esto divulgaría la existencia de los datos de los usuarios. Instead, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API responds with `404 Not Found`. Esto puede causar problemas para las bibliotecas de HTTP que asumen una respuesta de `401 Unauthorized`. La solución es construir manualmente el encabezado de `Authorization`. +The API supports Basic Authentication as defined in +[RFC2617](http://www.ietf.org/rfc/rfc2617.txt) with a few slight differences. +The main difference is that the RFC requires unauthenticated requests to be +answered with `401 Unauthorized` responses. In many places, this would disclose +the existence of user data. Instead, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API responds with `404 Not Found`. +This may cause problems for HTTP libraries that assume a `401 Unauthorized` +response. The solution is to manually craft the `Authorization` header. -### A través de OAuth y los tokens de acceso personal +### Via OAuth and personal access tokens -Te recomendamos utilizar tokens de OAuth para autenticarte en la API de GitHub. Los tokens de OAuth incluyen a los [tokens de acceso personal][personal-access-tokens] y habilitan al usuario para revocar el acceso en cualquier momento. +We recommend you use OAuth tokens to authenticate to the GitHub API. OAuth tokens include [personal access tokens][personal-access-tokens] and enable the user to revoke access at any time. ```shell $ curl -u username:token {% data variables.product.api_url_pre %}/user ``` -Este acercamiento es útil si tus herramientas solo son compatibles con la Autenticación Básica pero quieres sacar ventaja de las características de seguridad de los tokens de acceso de OAuth. +This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. -### A través de nombre de usuario y contraseña +### Via username and password {% ifversion fpt or ghec %} {% note %} -**Nota:** {% data variables.product.prodname_dotcom %} descontinuó la autenticación por contraseña hacia la API desde el 13 de noviembre de 2020 para todas las cuentas de {% data variables.product.prodname_dotcom_the_website %}, incluyendo aquellas en planes {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}. {% data variables.product.prodname_team %}, o {% data variables.product.prodname_ghe_cloud %}. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. Para obtener más información, consulta la sección "[Solución de problemas](/rest/overview/troubleshooting#basic-authentication-errors)". - +**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." + {% endnote %} {% endif %} {% ifversion ghes %} -Para utilizar la autenticación básica con la -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, simply send the username and -contraseña asociados con la cuenta. +To use Basic Authentication with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, simply send the username and +password associated with the account. -Por ejemplo, si estás accediendo a la API a través de [cURL][curl], el siguiente comando te autenticaría si lo reemplazas al `` con tu nombre de usuario de {% data variables.product.product_name %}. (cURL te pedirá ingresar la contraseña.) +For example, if you're accessing the API via [cURL][curl], the following command +would authenticate you if you replace `` with your {% data variables.product.product_name %} username. +(cURL will prompt you to enter the password.) ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -Si habilitaste la autenticación de dos factores, asegúrate de que entiendes como [trabajar con ella](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). +If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). {% endif %} {% ifversion fpt or ghec %} -### Autenticarse con el SSO de SAML +### Authenticating for SAML SSO {% note %} -**Nota:** Las integraciones y las aplicaciones de OAuth que generan tokens en nombre de otros se autorizan automáticamente. +**Note:** Integrations and OAuth applications that generate tokens on behalf of others are automatically authorized. {% endnote %} -Si estás usando la API para acceder a una organización que requiere el [SSO de SAML][saml-sso] para la autenticación, necesitarás crear un token de acceso personal (PAT) y [autorizarlo][allowlist] para esa organización. Visita la URL especificada en `X-GitHub-SSO` para autorizar el token para la organización. +If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a personal access token (PAT) and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. ```shell $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test @@ -88,7 +98,7 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api } ``` -Cuando solicites datos que pudieran venir de organizaciones múltiples (por ejemplo, [solicitar la lista de informes de problemas que creó el usuario][user-issues]), el encabezado `X-GitHub-SSO` indica qué organizaciones te solicitarán autorizar tu token de acceso personal: +When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your personal access token: ```shell $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/user/issues @@ -96,26 +106,26 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api > X-GitHub-SSO: partial-results; organizations=21955855,20582480 ``` -El valor `organizations` es una lista separada por comas de las ID de organización para aquellas que requieren autorización de tu token de acceso personal. +The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your personal access token. {% endif %} {% ifversion fpt or ghes or ghec %} -## Trabajar con la autenticación de dos factores +## Working with two-factor authentication -Cuando tienes la autenticación bifactorial habilitada, la [Autenticación Básica](#basic-authentication) para la _mayoría_ de las terminales en la API de REST requiere que utilices un token de acceso personal{% ifversion ghes %} o un token de OAuth en vez de tu nombre de usuario y contraseña{% endif %}. +When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token{% ifversion ghes %} or OAuth token instead of your username and password{% endif %}. -Puedes generar un token de acceso personal {% ifversion fpt or ghec %}utilizando la [configuración de desarrollador de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} o con la terminal de "\[Crear una autorización nueva\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" en la API de autorizciones de OAuth para generar un token de OAuth nuevo{% endif %}. Para obtener más información, consulta la sección"[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} +You can generate a new personal access token {% ifversion fpt or ghec %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} {% endif %} {% ifversion ghes %} -### Utilizar la API de Autorizaciones de OAuth con autenticación de dos factores +### Using the OAuth Authorizations API with two-factor authentication -Cuando haces llamadas a la API de Autorizaciones de OAuth, la Autenticación Básica requiere que utilces una contraseña de única vez (OTP) así como tu nombre de usuario y contraseña en vez de utilizar tokens. Cuando intentas autenticarte con la API de Autorizaciones de OAuth, el servidor te responderá con un `401 Unauthorized` y con uno de estos encabezados para decirte que necesitas un código de autenticación de dos factores: +When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code: -`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`. +`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`. -Este encabezado te dice cómo tu cuenta recibe sus códigos de autenticación de dos factores. Dependiendo de cómo configures tu cuenta, podrías recibir tus códigos de OTP por SMS o utilizarías una aplicación tal como Google Autenticator o como 1Password. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". Passa la OTP en el encabezado: +This header tells you how your account receives its two-factor authentication codes. Depending how you set up your account, you will either receive your OTP codes via SMS or you will use an application like Google Authenticator or 1Password. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." Pass the OTP in the header: ```shell $ curl --request POST \ @@ -128,8 +138,9 @@ $ curl --request POST \ {% endif %} [curl]: http://curl.haxx.se/ -[oauth-auth]: /rest#authentication +[oauth-auth]: /rest/overview/resources-in-the-rest-api#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on +[saml-sso-tokens]: https://github.com/settings/tokens [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on [user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/es-ES/content/rest/reference/actions.md b/translations/es-ES/content/rest/reference/actions.md index cfdf1cad27..d18e1d43d1 100644 --- a/translations/es-ES/content/rest/reference/actions.md +++ b/translations/es-ES/content/rest/reference/actions.md @@ -1,5 +1,6 @@ --- -title: Acciones +title: Actions +intro: 'With the Actions API, you can manage and control {% data variables.product.prodname_actions %} for an organization or repository.' redirect_from: - /v3/actions versions: @@ -14,15 +15,15 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.ae-beta %} -La API de {% data variables.product.prodname_actions %} te permite administrar las {% data variables.product.prodname_actions %} utilizando la API de REST. La {% data reusables.actions.actions-authentication %} de las {% data variables.product.prodname_github_apps %} requieren los permisos que se mencionan en cada terminal. Para obtener más información, consulta la sección "[Documentación de {% data variables.product.prodname_actions %}](/actions)". +The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)." {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Artefactos +## Artifacts -La API de Artefactos te permite descargar, borrar y recuperar información acerca de los artefactos de los flujos de trabajo. {% data reusables.actions.about-artifacts %} Para obtener más información, consulta la sección "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -31,58 +32,58 @@ La API de Artefactos te permite descargar, borrar y recuperar información acerc {% endfor %} {% ifversion fpt or ghes > 2.22 or ghae or ghec %} -## Permisos +## Permissions -La API de permisos te permite configurar permisos para indicar qué organizaciones y repositorios pueden ejecutar las {% data variables.product.prodname_actions %}, y qué acciones se pueden ejecutar. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)". +The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)." -También puedes configurar permisos para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#github-actions)". +You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. {% for operation in currentRestOperations %} {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %} {% endfor %} {% endif %} -## Secretos +## Secrets -La API de Secretos te permite crear, actualizar, borrar y recuperar información acerca de los secretos cifrados. {% data reusables.actions.about-secrets %} Para obtener más información, consulta la sección "[Crear y utilizar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." -La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `secrets` para utilizar esta API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos. +{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets. {% for operation in currentRestOperations %} {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %} {% endfor %} -## Ejecutores autoalojados +## Self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} -La API de Ejecutores auto-hospedados te permite registrar, ver, y borrar estos ejecutores. {% data reusables.actions.about-self-hosted-runners %} Para obtener más información, consulta "[Alojar tus propios ejecutores](/actions/hosting-your-own-runners)". +The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)." -La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben tener acceso administrativo al repositorio o a la organización para utilizar esta API. +{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API. -Puedes administrar los ejecutores auto-programados para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#github-actions)". +You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. {% for operation in currentRestOperations %} {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %} {% endfor %} -## Grupos de ejecutores auto-hospedados +## Self-hosted runner groups {% data reusables.actions.ae-self-hosted-runners-notice %} -La API de Grupos de Ejecutores Auto-Hospedados te permite administrar grupos para los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". +The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)." -La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben tener acceso administrativo al repositorio o a la organización para utilizar esta API. +{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API. -Puedes administrar los grupos de ejecutores auto-hospedados para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin##github-actions)". +You can manage self-hosted runner groups for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin##github-actions)" REST API. {% for operation in currentRestOperations %} {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %} {% endfor %} -## Flujos de trabajo +## Workflows -La API de flujos de trabajo te permite ver los flujos de trabajo de un repositorio. {% data reusables.actions.about-workflows %} Para obtener más información, consulta la sección "[Automatizar tu flujo de trabajo con GitHub Actions](/actions/automating-your-workflow-with-github-actions)". +The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -90,9 +91,9 @@ La API de flujos de trabajo te permite ver los flujos de trabajo de un repositor {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %} {% endfor %} -## Jobs de los flujos de trabajo +## Workflow jobs -La API de Jobs de Flujos de Trabajo te permite ver las bitácoras y los jobs de un flujo de trabajo. {% data reusables.actions.about-workflow-jobs %} Para obtener más información, consulta la sección "[Sintaxis de flujode trabajo para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". +The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -100,9 +101,9 @@ La API de Jobs de Flujos de Trabajo te permite ver las bitácoras y los jobs de {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %} {% endfor %} -## Ejecuciones de flujo de trabajo +## Workflow runs -La API de Ejecuciones de Flujo de Trabajo te permite ver, re-ejecutar, cancelar y ver las bitácoras de las ejecuciones de los flujos de trabajo. {% data reusables.actions.about-workflow-runs %} Para obtener más información, consulta la sección "[Administrar una ejecución de flujo de trabajo](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". +The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/es-ES/content/rest/reference/activity.md b/translations/es-ES/content/rest/reference/activity.md index 0b26edd73f..804b4094d2 100644 --- a/translations/es-ES/content/rest/reference/activity.md +++ b/translations/es-ES/content/rest/reference/activity.md @@ -1,5 +1,6 @@ --- -title: Actividad +title: Activity +intro: 'The Activity API allows you to list events and feeds and manage notifications, starring, and watching for the authenticated user.' redirect_from: - /v3/activity versions: @@ -16,13 +17,13 @@ miniTocMaxHeadingLevel: 3 {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Eventos +## Events -La API de eventos es una API de solo lectura para los eventos de {% data variables.product.prodname_dotcom %}. Estos eventos alimentan a los diversos flujos de actividad en el sitio. +The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site. -La API de eventos puede devolver tipos diferentes de eventos que se activan por actividad en {% data variables.product.product_name %}. La API de eventos puede devolver tipos diferentes de eventos que se activan por actividad en {% data variables.product.product_name %}. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos, consulta la sección "[Tipos de evento en {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". Para obtener más información, consulta la "[API de Eventos de Informes de Problemas](/rest/reference/issues#events)". +The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)." -Los eventos se optimizan para el sondeo con el encabezado "ETag". Si no se han desencadenado eventos nuevos, verás la respuesta "304 Sin Modificar", y tu límite de tasa actual permanecerá intacto. También hay un encabezado de "X-Poll-Interval" que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado. +Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header. ``` shell $ curl -I {% data variables.product.api_url_pre %}/users/tater/events @@ -37,25 +38,25 @@ $ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"' > X-Poll-Interval: 60 ``` -Solo los eventos creados en los últimos 90 días se incluirán en las líneas de tiempo. Los eventos de más de 90 días de antigüedad no se incluirán (aún si la cantidad total de eventos en la línea de tiempo es de 300). +Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300). {% for operation in currentRestOperations %} {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %} {% endfor %} -## Fuentes +## Feeds {% for operation in currentRestOperations %} {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %} {% endfor %} -### Ejemplo de obtención de un canal de Atom +### Example of getting an Atom feed -Para obtener un canal en formato de Atom, debes especificar el tipo `application/atom+xml` en el encabezado `Accept`. Por ejemplo, para obtener un canal de Atom para las asesorías de seguridad de GitHub: +To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories: curl -H "Accept: application/atom+xml" https://github.com/security-advisories -#### Respuesta +#### Response ```shell HTTP/2 200 @@ -100,26 +101,26 @@ HTTP/2 200 ``` -## Notificaciones +## Notifications -Los usuarios reciben notificaciones para las conversaciones en los repositorios que observan, incluyendo: +Users receive notifications for conversations in repositories they watch including: -* Las de los informes de problemas y sus comentarios -* Las de las solicitudes de extracción en sus comentarios -* Las de los comentarios en cualquier confirmación +* Issues and their comments +* Pull Requests and their comments +* Comments on any commits -También se envían notificaciones para las conversaciones en los repositorios sin observar cuando el usuario está involucrado, incluyendo: +Notifications are also sent for conversations in unwatched repositories when the user is involved including: -* **@menciones** -* Asignaciones de informes de problemas -* Confirmaciones que confirme o cree el usuario -* Cualquier debate en el que el usuario participe activamente +* **@mentions** +* Issue assignments +* Commits the user authors or commits +* Any discussion in which the user actively participates -Todas las llamadas de la API para notificaciones necesitan los alcances de la API para `notifications` o `repo`. El hacerlo te dará acceso de solo lectura a algunos contenidos de informes de problemas y de confirmaciones. Aún necesitarás el alcance de `repo` para acceder a los informes de problemas y a las confirmaciones desde sus respectivas terminales. +All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints. -Las notificaciones se devuelven como "hilos". Un hilo contiene información acerca del debate actual sobre un informe de problemas, solicitud de extracción o confirmación. +Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit. -Las notificaciones se optimizan para el sondeo con el encabezado `Last-Modified`. Si no hay notificaciones nuevas, verás una respuesta `304 Not Modified`, la cual dejará tu límite de tasa intacto. Hay un encabezado de `X-Poll-Interval` que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado. +Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header. ``` shell # Add authentication to your requests @@ -135,58 +136,62 @@ $ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" > X-Poll-Interval: 60 ``` -### Razones para obtener las notificaciones +### Notification reasons -Cuando recuperas respuestas de la API de Notificaciones, cada carga útil tiene una clave que se titula `reason`. Estas corresponden a los eventos que activan una notificación. +When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification. -Hay una lista potencial de `reason` para recibir una notificación: +Here's a list of potential `reason`s for receiving a notification: -| Nombre de la razón | Descripción | -| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `assign` | Se te asignó al informe de problemas. | -| `autor` | Creaste el hilo. | -| `comentario` | Comentaste en el hilo. | -| `ci_activity` | Se completó una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %}. | -| `invitación` | Aceptaste una invitación para colaborar en el repositorio. | -| `manual` | Te suscribiste al hilo (a través de un informe de problemas o solicitud de extracción). | -| `mención` | Se te **@mencionó** específicamente en el contenido. | -| `review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %} -| `security_alert` | {% data variables.product.prodname_dotcom %} descubrió una [vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en tu repositorio.{% endif %} -| `state_change` | Cambiaste el estado del hilo (por ejemplo, cerraste un informe de problemas o fusionaste una solicitud de extracción). | -| `subscribed` | Estás observando el repositorio. | -| `team_mention` | Estuviste en un equipo al que se mencionó. | +Reason Name | Description +------------|------------ +`assign` | You were assigned to the issue. +`author` | You created the thread. +`comment` | You commented on the thread. +`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. +`invitation` | You accepted an invitation to contribute to the repository. +`manual` | You subscribed to the thread (via an issue or pull request). +`mention` | You were specifically **@mentioned** in the content. +`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %} +`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %} +`state_change` | You changed the thread state (for example, closing an issue or merging a pull request). +`subscribed` | You're watching the repository. +`team_mention` | You were on a team that was mentioned. -Toma en cuenta que la `reason` se modificará conforme al hilo, y puede cambiar si esta `reason` es diferente en una notificación posterior. +Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different. -Por ejemplo, si eres el autor de un informe de problemas, las notificaciones subsecuentes de dicho informe tendrán una `reason` o un `author`. Si entonces se te **@menciona** en el mismo informe de problemas, las notificaciones que obtengas de ahí en adelante tendrán una `reason` o una `mention`. La `reason` se queda como una `mention`, sin importar si nunca se te menciona. +For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again. {% for operation in currentRestOperations %} {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %} {% endfor %} -## Marcar con una estrella +## Starring -El marcar a los repositorios con una estrella es una característica que permite a los usuarios marcar a los repositorios como favoritos. Las estrellas se muestran junto a los repositorios para denotar un nivel aproximado de interés. Las estrellas no tienen efecto alguno en las notificaciones o en los canales de actividad. +Repository starring is a feature that lets users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect on notifications or the activity feed. -### Marcar con estrella vs. Observar +### Starring vs. Watching -En agosto de 2012, [cambiamos la forma en la que funciona el observar repositorios](https://github.com/blog/1204-notifications-stars) en {% data variables.product.prodname_dotcom %}. Muchas aplicaciones de cliente de la API podrían estar utilizando las terminales de "observación" originales para acceder a estos datos. Ahora puedes comenzar a utilizar las terminales de "estrella" como sustitución (como se describe más adelante). Para obtener más información, consulta la [publicación de Cambio de la API de observaciones](https://developer.github.com/changes/2012-09-05-watcher-api/) y la "[API para Observar Repositorios](/rest/reference/activity#watching)". +In August 2012, we [changed the way watching +works](https://github.com/blog/1204-notifications-stars) on {% data variables.product.prodname_dotcom %}. Many API +client applications may be using the original "watcher" endpoints for accessing +this data. You can now start using the "star" endpoints instead (described +below). For more information, see the [Watcher API Change post](https://developer.github.com/changes/2012-09-05-watcher-api/) and the "[Repository Watching API](/rest/reference/activity#watching)." -### Tipos de medio personalizados para marcar con estrella +### Custom media types for starring -Hay un tipo de medios personalizado compatible para la API de REST para Marcar con estrella. Cuando utilizas este tipo de medios personalizado, recibirás una respuesta con la marca de tiempo `starred_at` que indica la hora en el que se creó la estrella. La respuesta también tiene una segunda propiedad que incluye el recurso que se devuelve cuando no se incluye el tipo de medios personalizado. La propiedad que contiene el recurso puede ser `user` o `repo`. +There is one supported custom media type for the Starring REST API. When you use this custom media type, you will receive a response with the `starred_at` timestamp property that indicates the time the star was created. The response also has a second property that includes the resource that is returned when the custom media type is not included. The property that contains the resource will be either `user` or `repo`. application/vnd.github.v3.star+json -Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". +For more information about media types, see "[Custom media types](/rest/overview/media-types)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %} {% endfor %} -## Observar +## Watching -Observar un repositorio registra al usuario para recibir notificaciones en debates nuevos, así como en los eventos de los canales de actividad del mismo. Para marcar a un repositorio como favorito de forma sencilla, consulta la sección "[Marcar repositorios con una estrella](/rest/reference/activity#starring)". +Watching a repository registers the user to receive notifications on new discussions, as well as events in the user's activity feed. For simple repository bookmarks, see "[Repository starring](/rest/reference/activity#starring)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/apps.md b/translations/es-ES/content/rest/reference/apps.md index 8284233132..fe8a5dc5ff 100644 --- a/translations/es-ES/content/rest/reference/apps.md +++ b/translations/es-ES/content/rest/reference/apps.md @@ -1,5 +1,6 @@ --- -title: Aplicaciones +title: Apps +intro: 'The GitHub Apps API enables you to retrieve the information about the installation as well as specific information about GitHub Apps.' redirect_from: - /v3/apps versions: @@ -12,23 +13,21 @@ topics: miniTocMaxHeadingLevel: 3 --- -La API de GitHub Apps te permite obtener información de alto nivel acerca de una GitHub App así como la información específica acerca de las instalaciones de la misma. Para conocer más sobre las GitHub Apps, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)". - {% data reusables.apps.general-apps-restrictions %} -Esta página lista las terminales a las que puedes acceder mientras te autenticas como una GitHub App. Consulta la sección "[Autenticarse como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" para conocer más. +This page lists endpoints that you can access while authenticated as a GitHub App. See "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" to learn more. -Cuando estás autenticado como una GitHub App, la API de GitHub Apps te habilita para obtener información de alto nivel sobre una GitHub App así como para obtener información específica sobre las instalaciones de éstas. +When authenticated as a GitHub App, the GitHub Apps API enables you to get high-level information about a GitHub App as well as specific information about installations of an app. -Puedes acceder a las terminales de la API v3 de REST mientras estás autenticado como una GitHub App. Estas terminales tienen una sección de "Notas" que contiene una viñeta que dice "Funciona con las GitHub Apps". También puedes acceder a estas terminales mientras estás autenticado como un usuario. +You can access REST API v3 endpoints while authenticated as a GitHub App. These endpoints have a "Notes" section that contains a bullet point that says "Works with GitHub Apps." You can also access these endpoints while authenticated as a user. -Un subconjunto de terminales de la API v3 de REST requiere que te autentiques como una instalación de una GitHub App. Consulta las [Instalaciones](/rest/reference/apps#installations) para obtener una lista de estas terminales. +A subset of REST API v3 endpoints requires authenticating as a GitHub App installation. See [Installations](/rest/reference/apps#installations) for a list of these endpoints. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## API de las Aplicaciones de OAuth +## OAuth Applications API You can use this API to manage the OAuth tokens an OAuth application uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. @@ -36,11 +35,11 @@ You can use this API to manage the OAuth tokens an OAuth application uses to acc {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %} {% endfor %} -## Instalaciones +## Installations -La API de instalaciones te habilita para obtener información acerca de las instalaciones de tu GitHub App y para realizar acciones dentro de esas instalaciones. Una _instalación_ se refiere a cualquier cuenta de usuario o de organización que tenga la app instalada. Para obtener más información sobre cómo autenticarte como una instalación y limitar el acceso a repositorios específicos, consulta la sección "[Autenticarte como una instalación](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". +The Installations API enables you to get information about installations of your GitHub App and perform actions within those installations. An _installation_ refers to any user or organization account that has installed the app. For information on how to authenticate as an installation and limit access to specific repositories, see "[Authenticating as an installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)." -Para listar las instalaciones de una GitHub App para una organización, consulta la sección "[Listar instalaciones de la app para una organización](/rest/reference/orgs#list-app-installations-for-an-organization)". +To list all GitHub App installations for an organization, see "[List app installations for an organization](/rest/reference/orgs#list-app-installations-for-an-organization)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %} @@ -49,17 +48,17 @@ Para listar las instalaciones de una GitHub App para una organización, consulta {% ifversion fpt or ghec %} ## Marketplace -Para obtener más información acerca de {% data variables.product.prodname_marketplace %}, consulta "[GitHub Marketplace](/marketplace/)". +For more information about {% data variables.product.prodname_marketplace %}, see "[GitHub Marketplace](/marketplace/)." -La API de {% data variables.product.prodname_marketplace %} te permite ver qué clientes están utilizando un plan de precios, ver sus compras y también ver si una cuenta tiene una suscripción activa. +The {% data variables.product.prodname_marketplace %} API allows you to see which customers are using a pricing plan, see a customer's purchases, and see if an account has an active subscription. -### Hacer pruebas con terminales de muestra +### Testing with stubbed endpoints -Esta API incluye terminales que te permiten [probar tu {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) con **datos de muestra**. Los datos de muestra son datos falsos y preprogramados que no cambiarán con base en las suscripciones reales. +This API includes endpoints that allow you to [test your {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) with **stubbed data**. Stubbed data is hard-coded, fake data that will not change based on actual subscriptions. -Para hacer pruebas con estos datos, utiliza una terminal de muestra en vez de su contraparte productiva. Esto te permite probar si la lógica de la API tendrá éxito antes de listar tus {% data variables.product.prodname_github_apps %} en {% data variables.product.prodname_marketplace %}. +To test with stubbed data, use a stubbed endpoint in place of its production counterpart. This allows you to test whether API logic succeeds before listing {% data variables.product.prodname_github_apps %} on {% data variables.product.prodname_marketplace %}. -Asegúrate de reemplazar tus terminales de muestra con aquellas productivas antes de desplegar tu {% data variables.product.prodname_github_app %}. +Be sure to replace stubbed endpoints with production endpoints before deploying your {% data variables.product.prodname_github_app %}. {% for operation in currentRestOperations %} {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %} @@ -70,7 +69,7 @@ Asegúrate de reemplazar tus terminales de muestra con aquellas productivas ante {% ifversion fpt or ghes > 2.22 or ghae or ghec %} ## Webhooks -Un webhook de {% data variables.product.prodname_github_app %} te permite recibir cargas útiles de `POST` por HTTP cada que sucedan ciertos eventos para una app. {% data reusables.webhooks.webhooks-rest-api-links %} +A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/billing.md b/translations/es-ES/content/rest/reference/billing.md index cfdab7466e..8876b25d3f 100644 --- a/translations/es-ES/content/rest/reference/billing.md +++ b/translations/es-ES/content/rest/reference/billing.md @@ -1,5 +1,6 @@ --- -title: Facturación +title: Billing +intro: 'With the Billing API, you can monitor the charges and usage {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} for a user or organization.' versions: fpt: '*' ghec: '*' @@ -8,9 +9,7 @@ topics: miniTocMaxHeadingLevel: 3 --- -Puedes monitorear tus cargos y uso de {% data variables.product.prodname_actions %} y de {% data variables.product.prodname_registry %} para un usuario y organización a través de la API de Facturación. - -Puedes obtener información de facturación para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#billing)". +You can get billing information for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#billing)" REST API. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/es-ES/content/rest/reference/checks.md b/translations/es-ES/content/rest/reference/checks.md index dda4698da3..723346a74c 100644 --- a/translations/es-ES/content/rest/reference/checks.md +++ b/translations/es-ES/content/rest/reference/checks.md @@ -1,5 +1,6 @@ --- -title: Verificaciones +title: Checks +intro: 'With the Checks API, you can build {% data variables.product.prodname_github_apps %} that run powerful checks against the code changes in a repository.' redirect_from: - /v3/checks versions: @@ -11,24 +12,23 @@ topics: - API miniTocMaxHeadingLevel: 3 --- - -La API de Verificaciones te permite crear GitHub Apps que ejecuten verificaciones poderosas contra los cámbios de código en un repositorio. Puedes crear apps que lleven a cabo integración contínua, limpieza de código, o servicios de escaneo de código y que proporcionen retroalimentación detallada en las confirmaciones. Para obtener más información, consulta la sección "[Empezar con la API de verificaciones](/rest/guides/getting-started-with-the-checks-api)" y "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)". +You can create apps that perform continuous integration, code linting, or code scanning services and provide detailed feedback on commits. For more information, see "[Getting started with the checks API](/rest/guides/getting-started-with-the-checks-api)" and "[Creating CI tests with the Checks API](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)." {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Ejecuciones de Verificación +## Check Runs {% for operation in currentRestOperations %} {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %} {% endfor %} -## Conjuntos de Verificaciones +## Check Suites {% note %} - **Nota:** Una GitHub App solo recibe un evento de [`check_suite`](/webhooks/event-payloads/#check_suite) por SHA de confirmación, aún si cargas este SHA en más de una rama. Para saber cuándo se carga un SHA de confirmación a una rama, puedes suscribirte a los eventos de [`create`](/webhooks/event-payloads/#create) de la misma. + **Note:** A GitHub App only receives one [`check_suite`](/webhooks/event-payloads/#check_suite) event per commit SHA, even if you push the commit SHA to more than one branch. To find out when a commit SHA is pushed to a branch, you can subscribe to branch [`create`](/webhooks/event-payloads/#create) events. {% endnote %} diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md index eed5e1ae3a..d8512c1e8d 100644 --- a/translations/es-ES/content/rest/reference/enterprise-admin.md +++ b/translations/es-ES/content/rest/reference/enterprise-admin.md @@ -1,6 +1,6 @@ --- -title: Administración de GitHub Enterprise -intro: 'You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. Entre las tareas que puedes realizar con esta API hay muchas que se relacionan con las GitHub Actions.' +title: GitHub Enterprise administration +intro: You can use these endpoints to administer your enterprise. Among the tasks you can perform with this API are many relating to GitHub Actions. allowTitleToDifferFromFilename: true redirect_from: - /v3/enterprise-admin @@ -13,47 +13,50 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -shortTitle: Administración empresarial +shortTitle: Enterprise administration --- {% ifversion fpt or ghec %} {% note %} -**Nota:** Este artículo aplica a {% data variables.product.prodname_ghe_cloud %}. Para ver la versión de {% data variables.product.prodname_ghe_managed %} o de {% data variables.product.prodname_ghe_server %}, utiliza el menú desplegable de **{% data ui.pages.article_version %}**. +**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu. {% endnote %} {% endif %} -### URL de las Terminales +### Endpoint URLs -Las terminales de la API de REST{% ifversion ghes %}—excepto las terminales de la API de [Consola de Administración](#management-console)—{% endif %} se prefijan con la siguiente URL: +REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: ```shell {% data variables.product.api_url_pre %} ``` {% ifversion ghes %} -Las terminales de la API de [Consola de Administración](#management-console) solo llevan un prefijo con un nombre de host: +[Management Console](#management-console) API endpoints are only prefixed with a hostname: ```shell http(s)://hostname/ ``` {% endif %} {% ifversion ghae or ghes %} -### Autenticación +### Authentication -Las terminales de la API para tu instalación de {% data variables.product.product_name %} acceptan [los mismos métodos de autenticación](/rest/overview/resources-in-the-rest-api#authentication) que los de la API de GitHub.com. Puedes autenticarte con **[Tokens de OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(los cuales se pueden crear utilizando la [API de autorizciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}o con la **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} Los tokens de OAuth deben tener el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) de `site_admin` cuando se utilicen con las terminales específicas de la empresa. {% endif %} +Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} +OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %} -Solo los administradores de sitio autenticados en {% data variables.product.product_name %} pueden acceder a las terminales de la API de administración empresarial{% ifversion ghes %}, con exepción de la API de [Consola de Administración](#management-console), la cual requiere la [contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. +Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. {% endif %} {% ifversion ghae or ghes %} -### Información de la versión +### Version information -La versión actual de tu empresa se devuelve en el encabezado de respuesta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` También puedes leer la versión actual si llamas a la [terminal de meta](/rest/reference/meta/). +The current version of your enterprise is returned in the response header of every API: +`X-GitHub-Enterprise-Version: {{currentVersion}}.0` +You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -61,9 +64,9 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.2 %} -## Registro de auditoría +## Audit log {% for operation in currentRestOperations %} {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} @@ -72,7 +75,7 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% endif %} {% ifversion fpt or ghec %} -## Facturación +## Billing {% for operation in currentRestOperations %} {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %} @@ -90,9 +93,9 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% ifversion ghae or ghes %} -## Estadísticas de los Administradores +## Admin stats -La API de estadísticas de los administradores proporciona diversas métricas sobre tu instalación. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. +The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. {% for operation in currentRestOperations %} {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %} @@ -102,9 +105,9 @@ La API de estadísticas de los administradores proporciona diversas métricas so {% ifversion ghae or ghes > 2.22 %} -## Anuncios +## Announcements -La API de anuncios te permite administrar el letrero de anuncios globales en tu empresa. Para obtener más información, consulta la sección "[Personalizar los mensajes de usuario para tu empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)". +The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %} @@ -114,11 +117,11 @@ La API de anuncios te permite administrar el letrero de anuncios globales en tu {% ifversion ghae or ghes %} -## Webhooks globales +## Global webhooks -Los webhooks globales se instalan en tu empresa. Puedes utilizar los webhooks globales para monitorear, responder a, o requerir las reglas para los usuarios, organizaciones, equipos y repositorios en tu empresa. Los webhooks globales se pueden suscribir a los tipos de evento para [organizaciones](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuarios](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositorios](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipos](/developers/webhooks-and-events/webhook-events-and-payloads#team), [miembros](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membrecías](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifuraciones](/developers/webhooks-and-events/webhook-events-and-payloads#fork), y [pings](/developers/webhooks-and-events/about-webhooks#ping-event). +Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types. -*Esta API solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. Para aprender cómo configurar los webhooks globales, consulta la sección [Acerca de los webhooks globales](/enterprise/admin/user-management/about-global-webhooks). +*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks). {% for operation in currentRestOperations %} {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %} @@ -130,9 +133,9 @@ Los webhooks globales se instalan en tu empresa. Puedes utilizar los webhooks gl ## LDAP -Puedes utilizar la API de LDAP para actualizar las relaciones de cuenta entre un usuario de {% data variables.product.product_name %} o un equipo y su entrada enlazada de LDAP o poner en cola una sincronización nueva. +You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization. -Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, por sus siglas en inglés) al cual mapea un usuario o equipo. Toma en cuenta que las terminales de LDAP generalmente solo son efectivas si tu aplicativo de {% data variables.product.product_name %} [habilitó la sincronización con LDAP](/enterprise/admin/authentication/using-ldap). La terminal de [mapeo de LDAP para actualización para un usuario](#update-ldap-mapping-for-a-user) puede utilizarse cuando se habilita LDAP, aún si la sincronización con LDAP está inhabilitada. +With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled. {% for operation in currentRestOperations %} {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %} @@ -141,9 +144,9 @@ Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, {% endif %} {% ifversion ghae or ghes %} -## Licencia +## License -La API de licencias proporciona información sobre tu licencia empresarial. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. +The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. {% for operation in currentRestOperations %} {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %} @@ -153,31 +156,31 @@ La API de licencias proporciona información sobre tu licencia empresarial. *Sol {% ifversion ghes %} -## Consola de administración +## Management console -La API de la Consola de Administración te ayuda a administrar tu instalación de {% data variables.product.product_name %}. +The Management Console API helps you manage your {% data variables.product.product_name %} installation. {% tip %} -Debes configurar el número de puerto explícitamente cuando haces llamadas de la API hacia la Consola de Administración. Si habilitaste TLS en tu empresa, el número de puerto es `8443`; de lo contrario, el número de puerto es `8080`. +You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. -Si no quieres proporcionar un número de puerto, necesitarás configurar tu herramienta para seguir automáticamente las redirecciones. +If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects. -Podría que también necesites agregar el [marcador `-k`](http://curl.haxx.se/docs/manpage.html#-k) cuando utilices `curl`, ya que {% data variables.product.product_name %} utiliza un certificado auto-firmado antes de que [agregues tu propio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/). +You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/). {% endtip %} -### Autenticación +### Authentication -Necesitas pasar tu [Contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/) como un token de autenticación para cada terminal de la API de ésta, con excepción de [`/setup/api/start`](#create-a-github-enterprise-server-license). +You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license). -Utiliza el parámetro de `api_key` para enviar este token con cada solicitud. Por ejemplo: +Use the `api_key` parameter to send this token with each request. For example: ```shell $ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password' ``` -También puedes utilizar la autenticación HTTP estándar para enviar este token. Por ejemplo: +You can also use standard HTTP authentication to send this token. For example: ```shell $ curl -L 'https://api_key:your-amazing-password@hostname:admin_port/setup/api' @@ -190,9 +193,9 @@ $ curl -L 'https://api_key:your-amazing-password@hostname: {% endif %} {% ifversion ghae or ghes %} -## Organizaciones +## Organizations -La API de Administración Organizacional te permite crear organizaciones en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. +The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. {% for operation in currentRestOperations %} {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} @@ -201,22 +204,25 @@ La API de Administración Organizacional te permite crear organizaciones en tu e {% endif %} {% ifversion ghes %} -## Ganchos de Pre-recepción de la Organización +## Organization pre-receive hooks -La API de Ganchos de Pre-recepción de la Organización te permite ver y modificar la aplicación de dichos ganchos que están disponibles para una organización. +The Organization Pre-receive Hooks API allows you to view and modify +enforcement of the pre-receive hooks that are available to an organization. -### Atributos de objeto +### Object attributes -| Nombre | Type | Descripción | -| -------------------------------- | ----------- | --------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del gancho. | -| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. | -| `allow_downstream_configuration` | `boolean` | Si los repositorios pueden ignorar la imposición o no. | -| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. | +| Name | Type | Description | +|----------------------------------|-----------|-----------------------------------------------------------| +| `name` | `string` | The name of the hook. | +| `enforcement` | `string` | The state of enforcement for the hook on this repository. | +| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. | +| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | -Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject +any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` podría ser un enlace a esta terminal o ser la configuración global de este gancho. Solo los administradores de sistema pueden acceder a la configuración global. +`configuration_url` may be a link to this endpoint or this hook's global +configuration. Only site admins are able to access the global configuration. {% for operation in currentRestOperations %} {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %} @@ -226,31 +232,31 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% ifversion ghes %} -## Ambientes de pre-recepción +## Pre-receive environments -La API de Ambientes de Pre-recepción te permite crear, listar, actualizar y borrar ambientes para los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. +The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. -### Atributos de objeto +### Object attributes -#### Ambiente de pre-recepción +#### Pre-receive Environment -| Nombre | Type | Descripción | -| --------------------- | ----------- | --------------------------------------------------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del ambiente como se muestra en la IU. | -| `image_url` | `secuencia` | La URL del tarball que se descargará y extraerá. | -| `default_environment` | `boolean` | Si este es el ambiente predeterminado que viene con {% data variables.product.product_name %} o no. | -| `download` | `objeto` | El estado de descarga de este ambiente. | -| `hooks_count` | `número` | La cantidad de ganchos de pre-recepción que utilizan este ambiente. | +| Name | Type | Description | +|-----------------------|-----------|----------------------------------------------------------------------------| +| `name` | `string` | The name of the environment as displayed in the UI. | +| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. | +| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. | +| `download` | `object` | This environment's download status. | +| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. | -#### Descarga del Ambiente de Pre-recepción +#### Pre-receive Environment Download -| Nombre | Type | Descripción | -| --------------- | ----------- | -------------------------------------------------------------------------------- | -| `state` | `secuencia` | El estado de la mayoría de las descargas recientes. | -| `downloaded_at` | `secuencia` | La hora en la cual iniciaron la mayoría de las descrgas recientes. | -| `message` | `secuencia` | Cuando algo falla, este tendrá cualquier mensaje de error que se haya producido. | +| Name | Type | Description | +|-----------------|----------|---------------------------------------------------------| +| `state` | `string` | The state of the most recent download. | +| `downloaded_at` | `string` | The time when the most recent download started. | +| `message` | `string` | On failure, this will have any error messages produced. | -Los valores posibles para `state` son `not_started`, `in_progress`, `success`, `failed`. +Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`. {% for operation in currentRestOperations %} {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %} @@ -259,24 +265,26 @@ Los valores posibles para `state` son `not_started`, `in_progress`, `success`, ` {% endif %} {% ifversion ghes %} -## Ganchos de pre-recepción +## Pre-receive hooks -La API de Ganchos Pre-recepción te permite crear, listar, actualizar y borrar los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. +The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to +[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. -### Atributos de objeto +### Object attributes -#### Ganchos de pre-recepción +#### Pre-receive Hook -| Nombre | Type | Descripción | -| -------------------------------- | ----------- | ----------------------------------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del gancho. | -| `script` | `secuencia` | El script que ejecuta el gancho. | -| `script_repository` | `objeto` | El repositorio de GitHub en donde se mantiene el script. | -| `environment` | `objeto` | El ambiente de pre-recepción en donde se ejecuta el script. | -| `enforcement` | `secuencia` | El estado de las imposiciones para este gancho. | -| `allow_downstream_configuration` | `boolean` | Si las imposiciones pueden o no ignorarse a nivel de organización o de repositorio. | +| Name | Type | Description | +|----------------------------------|-----------|-----------------------------------------------------------------| +| `name` | `string` | The name of the hook. | +| `script` | `string` | The script that the hook runs. | +| `script_repository` | `object` | The GitHub repository where the script is kept. | +| `environment` | `object` | The pre-receive environment where the script is executed. | +| `enforcement` | `string` | The state of enforcement for this hook. | +| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. | -Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject +any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. {% for operation in currentRestOperations %} {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %} @@ -286,21 +294,22 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% ifversion ghes %} -## Ganchos de pre-recepción del repositorio +## Repository pre-receive hooks -La API de Ganchos de Pre-recepción para Repositorios te permite ver y modificar la imposición de los ganchos de pre-recepción que están disponibles para un repositorio. +The Repository Pre-receive Hooks API allows you to view and modify +enforcement of the pre-receive hooks that are available to a repository. -### Atributos de objeto +### Object attributes -| Nombre | Type | Descripción | -| ------------------- | ----------- | --------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del gancho. | -| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. | -| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. | +| Name | Type | Description | +|---------------------|----------|-----------------------------------------------------------| +| `name` | `string` | The name of the hook. | +| `enforcement` | `string` | The state of enforcement for the hook on this repository. | +| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | -Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` podría ser un enlace a este repositorio, al propietario de su organización o a su configuración global. La autorización para acceder a esta terminal en `configuration_url` se determina a nivel de administrador de sitio o de propietario. +`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. {% for operation in currentRestOperations %} {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %} @@ -309,9 +318,9 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% endif %} {% ifversion ghae or ghes %} -## Usuarios +## Users -La API de Administración de Usuarios te permite suspender{% ifversion ghes %}, dejar de suspender, promover, y degradar{% endif %}{% ifversion ghae %} y dejar de suspender{% endif %} a los usuarios en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `403` si intentan acceder a ella. +The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it. {% for operation in currentRestOperations %} {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/pulls.md b/translations/es-ES/content/rest/reference/pulls.md index d295b1f066..9d0005a41b 100644 --- a/translations/es-ES/content/rest/reference/pulls.md +++ b/translations/es-ES/content/rest/reference/pulls.md @@ -1,6 +1,6 @@ --- -title: Extracciones -intro: 'La API de extracciones te permite listar, ver editar, crear e incluso fusionar las solicitudes de cambios.' +title: Pulls +intro: 'The Pulls API allows you to list, view, edit, create, and even merge pull requests.' redirect_from: - /v3/pulls versions: @@ -13,13 +13,13 @@ topics: miniTocMaxHeadingLevel: 3 --- -La API de Solicitudes de Extracción te permite listar, ver, editar, crear e incluso fusionar solicitudes de extracción. Los comentarios en las solicitudes de extracción se pueden administrar a través de la [API de Comentarios de los Informes de Problemas](/rest/reference/issues#comments). +The Pull Request API allows you to list, view, edit, create, and even merge pull requests. Comments on pull requests can be managed via the [Issue Comments API](/rest/reference/issues#comments). -Cada solicitud de extracción es un informe de problemas, pero no todos los informes de problemas son una solicitud de extracción. Es por esto que las acciones "compartidas" para ambas características, como el manipular a los asignados, etiquetas e hitos, se proporcionan dentro de la [API de Informes de Problemas](/rest/reference/issues). +Every pull request is an issue, but not every issue is a pull request. For this reason, "shared" actions for both features, like manipulating assignees, labels and milestones, are provided within [the Issues API](/rest/reference/issues). -### Tipos de medios personalizados para las solicitudes de extracción +### Custom media types for pull requests -Estos son los tipos de medios compatibles para las solicitudes de extracción. +These are the supported media types for pull requests. application/vnd.github.VERSION.raw+json application/vnd.github.VERSION.text+json @@ -28,59 +28,60 @@ Estos son los tipos de medios compatibles para las solicitudes de extracción. application/vnd.github.VERSION.diff application/vnd.github.VERSION.patch -Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". +For more information, see "[Custom media types](/rest/overview/media-types)." -Si existe alguna diff que se haya dañado, contacta a {% data variables.contact.contact_support %}. Incluye el nombre del repositorio y la ID de la solicitud de extracción en tu mensaje. +If a diff is corrupt, contact {% data variables.contact.contact_support %}. Include the repository name and pull request ID in your message. -### Relaciones de los enlaces +### Link Relations -Las solicitudes de extracción tienen estas posibles relaciones de enlaces: +Pull Requests have these possible link relations: -| Nombre | Descripción | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `self` | La ubicación de la API para esta Solicitud de Extracción. | -| `html` | La ubicación de HTML para esta Solicitud de Extracción. | -| `propuesta` | La ubicación de la API para el [informe de problemas](/rest/reference/issues) de esta Solicitud de Extracción. | -| `comments` | La ubicación de la API para los [Comentarios del informe de problemas](/rest/reference/issues#comments) de esta Solicitud de Extracción. | -| `review_comments` | La ubicación de la API para los [Comentarios de revisión](/rest/reference/pulls#comments) de esta Solicitud de Extracción. | -| `review_comment` | La [plantilla de URL](/rest#hypermedia) para construir la ubicación de la API para un [Comentario de revisión](/rest/reference/pulls#comments) en el repositorio de esta Solicitud de Extracción. | -| `commits` | La ubicación de la API para las [confirmaciones](#list-commits-on-a-pull-request) de esta solicitud de extracción. | -| `estados` | La ubicación de la API para los [estados de las confirmaciones](/rest/reference/repos#statuses) de esta Solicitud de Extracción, los cuales son los estados de su rama `head`. | +Name | Description +-----|-----------| +`self`| The API location of this Pull Request. +`html`| The HTML location of this Pull Request. +`issue`| The API location of this Pull Request's [Issue](/rest/reference/issues). +`comments`| The API location of this Pull Request's [Issue comments](/rest/reference/issues#comments). +`review_comments`| The API location of this Pull Request's [Review comments](/rest/reference/pulls#comments). +`review_comment`| The [URL template](/rest#hypermedia) to construct the API location for a [Review comment](/rest/reference/pulls#comments) in this Pull Request's repository. +`commits`|The API location of this Pull Request's [commits](#list-commits-on-a-pull-request). +`statuses`| The API location of this Pull Request's [commit statuses](/rest/reference/repos#statuses), which are the statuses of its `head` branch. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Revisiones +## Reviews -Las revisiones de las solicitudes de extracción son grupos de Comentarios de Revisión de las Solicitudes de Extracción en las mismas, los cuales se agrupan con un estado y, opcionalmente, con un comentario en el cuerpo. +Pull Request Reviews are groups of Pull Request Review Comments on the Pull +Request, grouped together with a state and optional body comment. {% for operation in currentRestOperations %} {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %} {% endfor %} -## Comentarios de revisión +## Review comments -Los comentarios de revisión de las solicitudes de extracción son comentarios de una porción de la diff unificada durante la revisión de esta solicitud. Los comentarios de confirmación y comentarios de la solicitud de extracción son diferentes de aquellos sobre la revisión de estas solicitudes. Se aplican comentarios de confirmación directamente a un confirmación, así como se aplican comentarios del informe de problemas sin referenciar una porción de la diff unificada. Para obtener más información, consulta las secciones "[Crear un comentario sobre una confirmación](/rest/reference/git#create-a-commit)" y "[Crear un comentario sobre un informe de problemas](/rest/reference/issues#create-an-issue-comment)". +Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/repos#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)." -### Tipos de medios personalizados para los comentarios sobre las revisiones de las solicitudes de extracción +### Custom media types for pull request review comments -Estos son los tipos de medios compatibles para los comentarios sobre las revisiones de las solicitudes de exstracción. +These are the supported media types for pull request review comments. application/vnd.github.VERSION.raw+json application/vnd.github.VERSION.text+json application/vnd.github.VERSION.html+json application/vnd.github.VERSION.full+json -Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". +For more information, see "[Custom media types](/rest/overview/media-types)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} {% endfor %} -## Solicitudes de revisión +## Review requests -Los autores de las solicitudes de extracción y los propietarios y colaboradores de los repositorios pueden solicitar una revisión de una solicitud de extracción a cualquiera con acceso de escritura en el repositorio. Cada revisor solicitado recibirá una notificación solicitándoles revisar la solicitud de extracción. +Pull request authors and repository owners and collaborators can request a pull request review from anyone with write access to the repository. Each requested reviewer will receive a notification asking them to review the pull request. {% for operation in currentRestOperations %} {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md index f15061dca4..2c1c4fa314 100644 --- a/translations/es-ES/content/rest/reference/repos.md +++ b/translations/es-ES/content/rest/reference/repos.md @@ -1,6 +1,6 @@ --- -title: Repositorios -intro: 'La API de Repos te permite crear, administrar y controlar el flujo de trabajo de los repositorios públicos y privados de {% data variables.product.product_name %}.' +title: Repositories +intro: 'The Repos API allows to create, manage and control the workflow of public and private {% data variables.product.product_name %} repositories.' allowTitleToDifferFromFilename: true redirect_from: - /v3/repos @@ -18,63 +18,64 @@ miniTocMaxHeadingLevel: 3 {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -{% ifversion fpt or ghec %} -## Autoenlaces +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %} +## Autolinks {% tip %} -**Nota:** La API de autoenlaces se encuentra en beta y podría cambiar. +**Note:** The Autolinks API is in beta and may change. {% endtip %} -Para ayudar a optimizar tu flujo de trabajo, puedes utilizar la API para agregar autoenlaces a los recursos externos como propuestas de JIRA y tickets de Zendesk. Para obtener más información, consulta la sección "[Configurar los autoenlaces para referenciar recursos externos](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)". +To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)." -Las {% data variables.product.prodname_github_apps %} requieren permisos de administración de repositorios con acceso de lectura o escritura para utilizar la API de Autoenlaces. +{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API. {% for operation in currentRestOperations %} {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %} {% endfor %} {% endif %} -## Ramas +## Branches {% for operation in currentRestOperations %} {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %} {% endfor %} -## Colaboradores +## Collaborators {% for operation in currentRestOperations %} {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} {% endfor %} -## Comentarios +## Comments -### Tipos de medios personalizados para los comentarios de las confirmaciones +### Custom media types for commit comments -Estos son los tipos de medios compatibles para los comentarios de las confirmaciones. Puedes leer más sobre el uso de tipos de medios en la API [aquí](/rest/overview/media-types). +These are the supported media types for commit comments. You can read more +about the use of media types in the API [here](/rest/overview/media-types). application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json application/vnd.github-commitcomment.html+json application/vnd.github-commitcomment.full+json -Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". +For more information, see "[Custom media types](/rest/overview/media-types)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} {% endfor %} -## Confirmaciones +## Commits -La API de Confirmaciones del Repositorio puede listar, ver y comparar las confirmaciones de un repositorio. +The Repo Commits API supports listing, viewing, and comparing commits in a repository. {% for operation in currentRestOperations %} {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} {% endfor %} {% ifversion fpt or ghec %} -## Comunidad +## Community {% for operation in currentRestOperations %} {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %} @@ -82,54 +83,56 @@ La API de Confirmaciones del Repositorio puede listar, ver y comparar las confir {% endif %} -## Contenido +## Contents -Las terminales de esta API te permiten crear, modificar y borrar contenido cifrado en Base64 en un repositorio. Para solicitar el formato sin procesar y interpretado en HTML (cuando sea posible), utiliza los tipos de medios personalizados para el contenido de un repositorio. +These API endpoints let you create, modify, and delete Base64 encoded content in a repository. To request the raw format or rendered HTML (when supported), use custom media types for repository contents. -### Tipos de medios personalizados para el contenido de un repositorio +### Custom media types for repository contents -Los [README](/rest/reference/repos#get-a-repository-readme), [archivos](/rest/reference/repos#get-repository-content) y [symlinks](/rest/reference/repos#get-repository-content) son compatibles con los siguientes tipos de medios personalizados: +[READMEs](/rest/reference/repos#get-a-repository-readme), [files](/rest/reference/repos#get-repository-content), and [symlinks](/rest/reference/repos#get-repository-content) support the following custom media types: application/vnd.github.VERSION.raw application/vnd.github.VERSION.html -Utiliza el tipo de medios `.raw` para recuperar el contenido del archivo. +Use the `.raw` media type to retrieve the contents of the file. -Para archivos de markup tales como Markdown o AsciiDoc, puedes recuperar la interpretación en HTML si utilizas el tipo de medios `.html`. Los lenguajes de Markup se interpretan en HTML utilizando nuestra [biblioteca de Markup](https://github.com/github/markup) de código abierto. +For markup files such as Markdown or AsciiDoc, you can retrieve the rendered HTML using the `.html` media type. Markup languages are rendered to HTML using our open-source [Markup library](https://github.com/github/markup). -[Todos los objetos](/rest/reference/repos#get-repository-content) son compatibles con el siguiente tipo de medios personalizados: +[All objects](/rest/reference/repos#get-repository-content) support the following custom media type: application/vnd.github.VERSION.object -Utiliza el parámetro de tipo de medios `object` para recuperar el contenido en un formato de objeto consistente sin importar el tipo de contenido. Por ejemplo, en vez de ser una matriz de objetos para un directorio, la respuesta será un objeto con un atributo de `entries` que contenga la matriz de objetos. +Use the `object` media type parameter to retrieve the contents in a consistent object format regardless of the content type. For example, instead of an array of objects +for a directory, the response will be an object with an `entries` attribute containing the array of objects. -Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types). +You can read more about the use of media types in the API [here](/rest/overview/media-types). {% for operation in currentRestOperations %} {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %} {% endfor %} -## Llaves de implementación +## Deploy keys {% data reusables.repositories.deploy-keys %} -Las llaves de despliegue pueden ya sea configurarse utilizando las siguientes terminales de la API, o mediante GitHub. Para aprender cómo configurar las llaves de despliegue en GitHub, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys)". +Deploy keys can either be setup using the following API endpoints, or by using GitHub. To learn how to set deploy keys up in GitHub, see "[Managing deploy keys](/developers/overview/managing-deploy-keys)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %} {% endfor %} -## Implementaciones +## Deployments -Los despliegues son slicitudes para desplegar una ref específica (rma, SHA, etiqueta). GitHub despliega un [evento de `deployment`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) al que puedan escuchar los servicios externos y al con el cual puedan actuar cuando se creen los despliegues nuevos. Los despliegues habilitan a los desarrolladores y a las organizaciones para crear herramientas sin conexión directa en torno a los despliegues, sin tener que preocuparse acerca de los detalles de implementación de entregar tipos de aplicaciones diferentes (por ejemplo, web o nativas). +Deployments are requests to deploy a specific ref (branch, SHA, tag). GitHub dispatches a [`deployment` event](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) that external services can listen for and act on when new deployments are created. Deployments enable developers and organizations to build loosely coupled tooling around deployments, without having to worry about the implementation details of delivering different types of applications (e.g., web, native). -Los estados de despliegue permiten que los servicios externos marquen estos despliegues con un estado de `error`, `failure`, `pending`, `in_progress`, `queued`, o `success` que pueden consumir los sistemas que escuchan a los [eventos de `deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status). +Deployment statuses allow external services to mark deployments with an `error`, `failure`, `pending`, `in_progress`, `queued`, or `success` state that systems listening to [`deployment_status` events](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) can consume. -Los estados de despliegue también incluyen una `description` y una `log_url` opcionales, las cuales se recomiendan ampliamente, ya que hacen que los estados de despliegue sean más útiles. La `log_url` es la URL completa para la salida del despliegue, y la `description` es el resumen de alto nivel de lo que pasó con este despliegue. +Deployment statuses can also include an optional `description` and `log_url`, which are highly recommended because they make deployment statuses more useful. The `log_url` is the full URL to the deployment output, and +the `description` is a high-level summary of what happened with the deployment. -GitHub envía eventos de `deployment` y `deployment_status` cuando se crean despliegues y estados de despliegue nuevos. Estos eventos permiten que las integraciones de terceros reciban respuesta de las solicitudes de despliegue y actualizan el estado de un despliegue conforme éste progrese. +GitHub dispatches `deployment` and `deployment_status` events when new deployments and deployment statuses are created. These events allows third-party integrations to receive respond to deployment requests and update the status of a deployment as progress is made. -Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionarían estas interacciones. +Below is a simple sequence diagram for how these interactions would work. ``` +---------+ +--------+ +-----------+ +-------------+ @@ -158,46 +161,50 @@ Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionar | | | | ``` -Ten en cuenta que GitHub jamás accede a tus servidores realmente. La interacción con los eventos de despliegue dependerá de tu integración de terceros. Varios sistemas pueden escuchar a los eventos de despliegue, y depende de cada uno de ellos decidir si son responsables de cargar el código a tus servidores, si crean código nativo, etc. +Keep in mind that GitHub is never actually accessing your servers. It's up to your third-party integration to interact with deployment events. Multiple systems can listen for deployment events, and it's up to each of those systems to decide whether they're responsible for pushing the code out to your servers, building native code, etc. -Toma en cuenta que el [Alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo_deployment` otorga acceso dirigido para los despliegues y estados de despliegue **sin** otorgar acceso al código del repositorio, mientras que {% ifversion not ghae %} los alcances de `public_repo` y{% endif %}`repo` también otorgan permisos para el código. +Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% ifversion not ghae %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well. -### Despliegues inactivos +### Inactive deployments -Cuando configuras el estado de un despliegue como `success`, entonces todos los despliegues anteriores que no sean transitorios ni de producción y que se encuentren en el mismo repositorio con el mismo ambiente se convertirán en `inactive`. Para evitar esto, puedes configurar a `auto_inactive` como `false` cuando creas el estado del servidor. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. -Puedes comunicar que un ambiente transitorio ya no existe si configuras el `state` como `inactive`. El configurar al `state` como `inactive`muestra el despliegue como `destroyed` en {% data variables.product.prodname_dotcom %} y elimina el acceso al mismo. +You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it. {% for operation in currentRestOperations %} {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %} {% endfor %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Ambientes +## Environments -La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener más información sobre los ambientes, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". Para administrar los secretos de ambiente, consulta la sección "[Secretos](/rest/reference/actions#secrets)". +The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." + +{% data reusables.gated-features.environments %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} {% endfor %} {% endif %} -## Bifurcaciones +## Forks {% for operation in currentRestOperations %} {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %} {% endfor %} -## Invitaciones +## Invitations -La API de Invitaciones al Repositorio permite a los usuarios o a los servicios externos invitar a otros usuarios para colaborar en un repositorio. Los usuarios invitados (o los servicios externos en nombre de estos) pueden elegir aceptar o rechazar la invitación. +The Repository Invitations API allows users or external services to invite other users to collaborate on a repo. The invited users (or external services on behalf of invited users) can choose to accept or decline the invitations. -Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` otorga un acceso dirigido a las invitaciones **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código así como para las invitaciones. +Note that the `repo:invite` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted +access to invitations **without** also granting access to repository code, while the +`repo` scope grants permission to code as well as invitations. -### Invitar a un usuario a un repositorio +### Invite a user to a repository -Utiliza la terminal de la API para agregar un colaborador. Para obtener más información, consulta la sección "[Agregar un colaborador del repositorio](/rest/reference/repos#add-a-repository-collaborator)". +Use the API endpoint for adding a collaborator. For more information, see "[Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %} @@ -213,11 +220,13 @@ Utiliza la terminal de la API para agregar un colaborador. Para obtener más inf {% endif %} -## Fusionar +## Merging -La API de Fusión de Repositorios puede fusionar ramas en un repositorio. Esto logra esencialmente lo mismo que el fusionar una rama con otra en un repositorio local para después cargarlo a {% data variables.product.product_name %}. El beneficio es que esta fusión se lleva a cabo del lado del servidor y no se requiere un repositorio local. Esto lo hace más adecuado para la automatización y para otras herramientas mientras que el mantener repositorios locales sería incómodo e ineficiente. +The Repo Merging API supports merging branches in a repository. This accomplishes +essentially the same thing as merging one branch into another in a local repository +and then pushing to {% data variables.product.product_name %}. The benefit is that the merge is done on the server side and a local repository is not needed. This makes it more appropriate for automation and other tools where maintaining local repositories would be cumbersome and inefficient. -El usuario autenticado será el autor de cualquier fusión que se realice a través de esta terminal. +The authenticated user will be the author of any merges done through this endpoint. {% for operation in currentRestOperations %} {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %} @@ -225,30 +234,30 @@ El usuario autenticado será el autor de cualquier fusión que se realice a trav ## Pages -La API de {% data variables.product.prodname_pages %} recupera información sobre tu configuración de {% data variables.product.prodname_pages %} y sobre los estados de tus compilaciones. Solo los propietarios autenticados pueden acceder a la información sobre el sitio y sobre las compilaciones{% ifversion not ghae %}, incluso si los sitios web son públicos{% endif %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% ifversion not ghae %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." -En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes: -* `null`: El sitio aún tiene que crearse. -* `queued`: Se solicitó la compilación, pero no ha iniciado. -* `building`: La compilación está en curso. -* `built`: Se creó el sitio. -* `errored`: Indica que ocurrió un error durante la compilación. +In {% data variables.product.prodname_pages %} API endpoints with a `status` key in their response, the value can be one of: +* `null`: The site has yet to be built. +* `queued`: The build has been requested but not yet begun. +* `building`:The build is in progress. +* `built`: The site has been built. +* `errored`: Indicates an error occurred during the build. -En las terminales de la API de {% data variables.product.prodname_pages %} que devulenven información del sitio de GitHub Pages, las respuestas de JSON incluyen estos campos: -* `html_url`: La URL absoluta (incluyendo el modelo) del sitio de Páginas que se interpretó. Por ejemplo, `https://username.github.io`. -* `source`: Un objeto que contiene la rama origen y el directorio del sitio de Páginas que se interpretó. Esto incluye: - - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _main_ o _gh-pages_. - - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`. +In {% data variables.product.prodname_pages %} API endpoints that return GitHub Pages site information, the JSON responses include these fields: +* `html_url`: The absolute URL (including scheme) of the rendered Pages site. For example, `https://username.github.io`. +* `source`: An object that contains the source branch and directory for the rendered Pages site. This includes: + - `branch`: The repository branch used to publish your [site's source files](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. + - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`. {% for operation in currentRestOperations %} {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %} {% endfor %} -## Lanzamientos +## Releases {% note %} -**Nota:** La API de Lanzamientos reemplaza a la API de Descargas. Puedes recuperar el conteo de descargas y la URL de descarga del buscador desde las terminales en esta API, las cuales devuelven los lanzamientos y los activos de éstos. +**Note:** The Releases API replaces the Downloads API. You can retrieve the download count and browser download URL from the endpoints in this API that return releases and release assets. {% endnote %} @@ -256,50 +265,68 @@ En las terminales de la API de {% data variables.product.prodname_pages %} que d {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %} {% endfor %} -## Estadísticas +## Statistics -La API de Estadísticas del Repositorio te permite recuperar los datos que {% data variables.product.product_name %} utiliza para visualizar los diferentes tipos de actividad del repositorio. +The Repository Statistics API allows you to fetch the data that {% data variables.product.product_name %} uses for visualizing different +types of repository activity. -### Unas palabras sobre el almacenamiento en caché +### A word about caching -El calcular las estadísitcas del repositorio es una operación costosa, así que intentamos devolver los datos almacenados en caché cuando nos es posible. Si los datos no se han almacenado en caché cuando consultas la estadística de un repositorio, recibirás una respuesta `202`; también se dispara un job en segundo plano para comenzar a compilar estas estadísticas. Permite que el job se complete, y luego emite la solicitud nuevamente. Si el job ya terminó, esa solicitud recibirá una respuesta `200` con la estadística en el cuerpo de la respuesta. +Computing repository statistics is an expensive operation, so we try to return cached +data whenever possible. If the data hasn't been cached when you query a repository's +statistics, you'll receive a `202` response; a background job is also fired to +start compiling these statistics. Give the job a few moments to complete, and +then submit the request again. If the job has completed, that request will receive a +`200` response with the statistics in the response body. -El SHA de la rama predeterminada del repositorio guarda en caché las estadísticas del repositorio; el subir información a la rama predeterminada restablece el caché de de las estadísticas. +Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache. -### Las estadísticas excluyen algunos tipos de confirmaciones +### Statistics exclude some types of commits -Las estadísticas que expone la API empatan con aquellas que muestran [diversas gráficas del repositorio](/github/visualizing-repository-data-with-graphs/about-repository-graphs). +The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs). -Para resumir: -- Todas las estadísticas excluyen las confirmaciones de fusión. -- Las estadísticas del colaborador también excluyen a las confirmaciones vacías. +To summarize: +- All statistics exclude merge commits. +- Contributor statistics also exclude empty commits. {% for operation in currentRestOperations %} {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %} {% endfor %} -## Estados +## Statuses -La API de estados permite que los servicios externos marquen las confirmaciones con un estado de `error`, `failure`, `pending`, o `success`, el cual se refleja después en las solicitudes de extracción que involucran a esas confirmaciones. +The status API allows external services to mark commits with an `error`, +`failure`, `pending`, or `success` state, which is then reflected in pull requests +involving those commits. -Los estados también incluyen una `description` y una `target_url` opcionales, y recomendamos ampliamente proporcionarlas, ya que hacen mucho más útiles a los estados en la IU de GitHub. +Statuses can also include an optional `description` and `target_url`, and +we highly recommend providing them as they make statuses much more +useful in the GitHub UI. -Como ejemplo, un uso común es que los servicios de integración contínua marquen a las confirmaciones como compilaciones que pasan o fallan utilizando los estados. La `target_url` sería la URL completa de la salida de la compilación, y la `description` sería el resumen de alto nivel de lo que pasó con la compilación. +As an example, one common use is for continuous integration +services to mark commits as passing or failing builds using status. The +`target_url` would be the full URL to the build output, and the +`description` would be the high level summary of what happened with the +build. -Los estados pueden incluir un `context` para indicar qué servicio está proporcionando ese estado. Por ejemplo, puedes hacer que tu servicio de integración continua cargue estados con un contexto de `ci`, y que una herramienta de auditoria de seguridad cargue estados con un contexto de `security`. Puedes utilizar entonces el [Obtener el estado combinado para una referencia específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) para recuperar todo el estado de una confirmación. +Statuses can include a `context` to indicate what service is providing that status. +For example, you may have your continuous integration service push statuses with a context of `ci`, and a security audit tool push statuses with a context of `security`. You can +then use the [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) to retrieve the whole status for a commit. -Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo:status` otorga acceso dirigido a los estados **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código y también para los estados. +Note that the `repo:status` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to statuses **without** also granting access to repository code, while the +`repo` scope grants permission to code as well as statuses. -Si estás desarrollando una GitHub App y quieres proporcionar información más detallada sobre un servicio externo, tal vez quieras utilizar la [API de Verificaciones](/rest/reference/checks). +If you are developing a GitHub App and want to provide more detailed information about an external service, you may want to use the [Checks API](/rest/reference/checks). {% for operation in currentRestOperations %} {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %} {% endfor %} {% ifversion fpt or ghec %} -## Tráfico +## Traffic -Para los repositorios en los que tienes acceso de carga, la API de tráfico proporciona acceso a la información proporcionada en tu gráfica de repositorio. Para obtener más información, consulta la sección "Ver el tráfico hacia un repositorio". +For repositories that you have push access to, the traffic API provides access +to the information provided in your repository graph. For more information, see "Viewing traffic to a repository." {% for operation in currentRestOperations %} {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %} @@ -308,49 +335,50 @@ Para los repositorios en los que tienes acceso de carga, la API de tráfico prop ## Webhooks -Los webhooks de repositorio te permiten recibir cargas útiles de `POST` por HTTP cuando ciertos eventos suceden en un repositorio. {% data reusables.webhooks.webhooks-rest-api-links %} +Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %} -Si te gustaría configurar un solo webhook para recibir eventos de todos los repositorios de tu organización, consulta nuestra documentación de la API para los [Webhooks de una Organización](/rest/reference/orgs#webhooks). +If you would like to set up a single webhook to receive events from all of your organization's repositories, see our API documentation for [Organization Webhooks](/rest/reference/orgs#webhooks). -Adicionalmente a la API de REST, {% data variables.product.prodname_dotcom %} también puede servir como un punto de [PubSubHubbub](#pubsubhubbub) para los repositorios. +In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories. {% for operation in currentRestOperations %} {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -### Recibir Webhooks +### Receiving Webhooks -Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS. +In order for {% data variables.product.product_name %} to send webhook payloads, your server needs to be accessible from the Internet. We also highly suggest using SSL so that we can send encrypted payloads over HTTPS. -#### Encabezados de Webhook +#### Webhook headers -{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para encontrar más detalles. +{% data variables.product.product_name %} will send along several HTTP headers to differentiate between event types and payload identifiers. See [webhook headers](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) for details. ### PubSubHubbub -GitHub también puede fungir como un centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos los repositorios. PSHB es un proptocolo simple de publicación/suscripción que permite a los servidores registrarse para recibir actualizaciones de cuándo se actualiza un tema. Las actualizaciones se mandan con una solicitud HTTP de tipo POST a una URL de rellamado. Las URL de tema para las cargas a un repositorio de GitHub están en este formato: +GitHub can also serve as a [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) hub for all repositories. PSHB is a simple publish/subscribe protocol that lets servers register to receive updates when a topic is updated. The updates are sent with an HTTP POST request to a callback URL. +Topic URLs for a GitHub repository's pushes are in this format: `https://github.com/{owner}/{repo}/events/{event}` -El veneto puede ser cualquier evento de webhook disponible. Para obtener más información, consulta la sección "[eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhook-events-and-payloads)". +The event can be any available webhook event. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." -#### Formato de respuesta +#### Response format -El formato predeterminado es lo que [deberían esperar los ganchos de post-recepción](/post-receive-hooks/): Un cuerpo de JSON que se envía como un parámetro de `payload` en un POST. También puedes especificar si quieres recibir el cuerpo en JSON sin procesar, ya sea un encabezado de `Accept` o una extensión `.json`. +The default format is what [existing post-receive hooks should expect](/post-receive-hooks/): A JSON body sent as the `payload` parameter in a POST. You can also specify to receive the raw JSON body with either an `Accept` header, or a `.json` extension. Accept: application/json https://github.com/{owner}/{repo}/events/push.json -#### URL de Rellamado +#### Callback URLs -Las URL de rellamado puede utilizar el protocolo `http://`. +Callback URLs can use the `http://` protocol. # Send updates to postbin.org http://postbin.org/123 -#### Suscribirse +#### Subscribing -La terminal de PubSubHubbub de GitHub es: `{% data variables.product.api_url_code %}/hub`. Una solicitud exitosa con curl se vería así: +The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like: ``` shell curl -u "user" -i \ @@ -360,13 +388,13 @@ curl -u "user" -i \ -F "hub.callback=http://postbin.org/123" ``` -Las solicitudes de PubSubHubbub pueden enviarse varias veces. Si el gancho ya existe, se modificará de acuerdo con la solicitud. +PubSubHubbub requests can be sent multiple times. If the hook already exists, it will be modified according to the request. -##### Parámetros +##### Parameters -| Nombre | Type | Descripción | -| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `hub.mode` | `secuencia` | **Requerido**. Ya sea `subscribe` o `unsubscribe`. | -| `hub.topic` | `secuencia` | **Requerido**. La URI del repositorio de GitHub al cual suscribirse. La ruta debe estar en el formato `/{owner}/{repo}/events/{event}`. | -| `hub.callback` | `secuencia` | La URI para recibir las actualizaciones del tema. | -| `hub.secret` | `secuencia` | Una llave de secreto compartido que genera una firma de hash del contenido saliente del cuerpo. You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghes < 3.0 %}`X-Hub-Signature` header{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. Puedes ver [la documentación de PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obtener más detalles. | +Name | Type | Description +-----|------|-------------- +``hub.mode``|`string` | **Required**. Either `subscribe` or `unsubscribe`. +``hub.topic``|`string` |**Required**. The URI of the GitHub repository to subscribe to. The path must be in the format of `/{owner}/{repo}/events/{event}`. +``hub.callback``|`string` | The URI to receive the updates to the topic. +``hub.secret``|`string` | A shared secret key that generates a hash signature of the outgoing body content. You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghes < 3.0 %}`X-Hub-Signature` header{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details. diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-code.md b/translations/es-ES/content/search-github/searching-on-github/searching-code.md index e9b60633dd..199bf291e3 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-code.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-code.md @@ -1,6 +1,6 @@ --- -title: Buscar código -intro: 'Puedes buscar código en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de código en cualquier combinación.' +title: Searching code +intro: 'You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination.' redirect_from: - /articles/searching-code - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches @@ -15,99 +15,98 @@ versions: topics: - GitHub search --- +{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." -{% data reusables.search.you-can-search-globally %} Para obtener más información, consulta la sección "[Acerca de buscar en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". - -Únicamente puedes buscar código utilizando estos calificadores de búsqueda de código. Los calificadores de búsqueda especialmente para repositorios, usuarios o confirmaciones de cambios, no funcionarán cuando busques código. +You can only search code using these code search qualifiers. Search qualifiers specifically for repositories, users, or commits, will not work when searching for code. {% data reusables.search.syntax_tips %} -## Consideraciones sobre la búsqueda de código +## Considerations for code search -Debido a la complejidad de la búsqueda de código, hay algunas restricciones sobre cómo se realizan las búsquedas: +Due to the complexity of searching code, there are some restrictions on how searches are performed: {% ifversion fpt or ghes or ghec %} - {% data reusables.search.required_login %}{% endif %} -- El código en [bifurcaciones](/articles/about-forks) es únicamente indexado si la bifurcación tiene más estrellas que el repositorio padre. Las bifurcaciones con menos estrellas que el repositorio padre **no** son indexadas para la búsqueda de código. Para incluir bifurcaciones con más estrellas que sus padres en los resultados de las búsquedas, deberás agregar `fork:true` o `fork:only` en tu consulta. Para obtener más información, consulta "[Buscar en bifurcaciones](/search-github/searching-on-github/searching-in-forks)". -- Solo la _rama predeterminada_ se indiza para la búsqueda de código.{% ifversion fpt or ghec %} -- Solo los archivos menores de 384 KB son indexados.{% else %}* Solo los archivos menores de 5 MB son indexados. -- Solo los primeros 500 KB de cada archivo son indexados.{% endif %} -- Solo se pueden hacer búsquedas en los repositorios con menos de 500,000 archivos.{% ifversion fpt or ghec %} -- Solo se pueden hacer búsquedas en los repositorios que han tenido actividad o que se han devuelto en los resultados de búsqueda dentro del último año.{% endif %} -- Excepto con las búsquedas por [`nombre de archivo`](#search-by-filename), siempre debes incluir por lo menos un término de búsqueda cuando buscas el código fuente. Por ejemplo, no es válido buscar por [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults), mientras que sí los es por [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults). -- A lo sumo, los resultados de búsqueda pueden mostrar dos fragmentos del mismo archivo, pero puede haber más resultados dentro del archivo. -- No puedes utilizar los siguientes caracteres comodines como parte de la consulta de búsqueda: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. La búsqueda simplemente ignorará estos símbolos. +- Code in [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are **not** indexed for code search. To include forks with more stars than their parent in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." +- Only the _default branch_ is indexed for code search.{% ifversion fpt or ghec %} +- Only files smaller than 384 KB are searchable.{% else %}* Only files smaller than 5 MB are searchable. +- Only the first 500 KB of each file is searchable.{% endif %} +- Only repositories with fewer than 500,000 files are searchable.{% ifversion fpt or ghec %} +- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %} +- Except with [`filename`](#search-by-filename) searches, you must always include at least one search term when searching source code. For example, searching for [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) is not valid, while [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) is. +- At most, search results can show two fragments from the same file, but there may be more results within the file. +- You can't use the following wildcard characters as part of your search query: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. The search will simply ignore these symbols. -## Buscar según los contenidos del archivo o la ruta de archivo +## Search by the file contents or file path -Con el calificador `in` puedes restringir tu búsqueda a los contenidos del archivo del código fuente, de la ruta del archivo, o de ambos. Cuando omites este calificador, únicamente se busca el contenido del archivo. +With the `in` qualifier you can restrict your search to the contents of the source code file, the file path, or both. When you omit this qualifier, only the file contents are searched. -| Qualifier | Ejemplo | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) encuentra el código donde aparece "octocat" en el contenido del archivo. | -| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) encuentra el código donde aparece "octocat" en la ruta del archivo. | -| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) encuentra el código donde aparece "octocat" en el contenido del archivo o la ruta del archivo. | +| Qualifier | Example +| ------------- | ------------- +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) matches code where "octocat" appears in the file contents. +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) matches code where "octocat" appears in the file path. +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) matches code where "octocat" appears in the file contents or the file path. -## Buscar dentro de los repositorios de un usuario u organización +## Search within a user's or organization's repositories -Para buscar el código en todos los repositorios que son propiedad de una determinada organización o usuario, puedes utilizar el calificador `user` u `org`. Para buscar el código en un repositorio específico, puedes utilizar el calificador `repo`. +To search the code in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search the code in a specific repository, you can use the `repo` qualifier. -| Qualifier | Ejemplo | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) encuentra el código de @defunkt que termina en .rb. | -| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) encuentra el código de GitHub que termina en .js. | -| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) encuentra el código del proyecto shumway de @mozilla que termina en .as. | +| Qualifier | Example +| ------------- | ------------- +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) matches code from @defunkt that ends in .rb. +| org:ORGNAME |[**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) matches code from GitHub that ends in .js. +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) matches code from @mozilla's shumway project that ends in .as. -## Buscar por ubicación del archivo +## Search by file location -Puedes utilizar el calificador `path` (ruta) para buscar el código fuente que aparece en una ubicación específica en un repositorio. Utiliza `path:/` para buscar archivos que estén ubicados a nivel de la raíz de un repositorio. O especifica un nombre de directorio o ruta a un directorio para buscar archivos que estén ubicados dentro de ese directorio o alguno de sus subdirectorios. +You can use the `path` qualifier to search for source code that appears at a specific location in a repository. Use `path:/` to search for files that are located at the root level of a repository. Or specify a directory name or the path to a directory to search for files that are located within that directory or any of its subdirectories. -| Qualifier | Ejemplo | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) encuentra los archivos _readme_ con la palabra "octocat" que se encuentran al nivel de raíz de un repositorio. | -| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) encuentra los archivos Perl con la palabra "form" en el directorio cgi-bin o en cualquiera de sus subdirectorios. | -| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) encuentra los archivos JavaScript con la palabra "console" en el directorio app/public o en cualquiera de sus subdirectorios (incluso si se encuentran en app/public/js/form-validators). | +| Qualifier | Example +| ------------- | ------------- +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) matches _readme_ files with the word "octocat" that are located at the root level of a repository. +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). -## Buscar por lenguaje +## Search by language -Puedes buscar el código basado en el lenguaje en que está escrito. El calificador `language` puede ser el nombre o el alias del idioma. Para obtener una lista completa de lenguajes compatibles con sus nombres y alias, consulta el [repositorio github/linguist](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). +You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). -| Qualifier | Ejemplo | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) encuentra código con la palabra "element" que está marcada como XML y tiene exactamente 100 bytes. | -| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) encuentra código con la palabra "display," que está marcada como SCSS. | -| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) encuentra código de todos los repositorios de @mozilla que están marcados como Markdown. | +| Qualifier | Example +| ------------- | ------------- +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) matches code with the word "element" that's marked as being XML and has exactly 100 bytes. +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) matches code with the word "display," that's marked as being SCSS. +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) matches code from all @mozilla's repositories that's marked as Markdown. -## Buscar por tamaño de archivo +## Search by file size -Puedes utilizar el calificador `size` (tamaño) para buscar código fuente en base al tamaño del archivo donde existe el código. El calificador `size` utiliza [calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para filtrar resultados en base al tamaño de bytes del archivo en donde se encuentra el código. +You can use the `size` qualifier to search for source code based on the size of the file where the code exists. The `size` qualifier uses [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to filter results based on the byte size of the file in which the code is found. -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) encuentra código con la palabra "function," escrita en Python, en archivos que son mayores a 10 KB. | +| Qualifier | Example +| ------------- | ------------- +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) matches code with the word "function," written in Python, in files that are larger than 10 KB. -## Buscar por nombre de archivo +## Search by filename -El calificador `filename` (nombre de archivo) encuentra archivos de código con un determinado nombre de archivo. También puedes encontrar un archivo en un repositorio utilizando el buscador de archivo. Para obtener más información, consulta "[Encontrar archivos en GitHub](/search-github/searching-on-github/finding-files-on-github)." +The `filename` qualifier matches code files with a certain filename. You can also find a file in a repository using the file finder. For more information, see "[Finding files on GitHub](/search-github/searching-on-github/finding-files-on-github)." -| Qualifier | Ejemplo | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) encuentra archivos con el nombre de "linguist." | -| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) encuentra los archivos *.vimrc* con la palabra "commands". | -| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) encuentra archivos Ruby con el nombre *test_helper* dentro del directorio *test*. | +| Qualifier | Example +| ------------- | ------------- +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) matches files named "linguist." +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) matches *.vimrc* files with the word "commands." +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) matches Ruby files named *test_helper* within the *test* directory. -## Buscar por extensión de archivo +## Search by file extension -El calificador `extension` (extensión) encuentra archivos de código con una determinada extensión de archivo. +The `extension` qualifier matches code files with a certain file extension. -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) encuentra el código con la palabra "form", debajo de cgi-bin, con la extensión de archivo .pm. | -| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) busca archivos más grandes de 200 KB que terminan en .css y tienen la palabra "icon". | +| Qualifier | Example +| ------------- | ------------- +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) matches code with the word "form," under cgi-bin, with the .pm file extension. +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) matches files larger than 200 KB that end in .css and have the word "icon." -## Leer más +## Further reading -- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" -- "[Buscar en ramificaciones](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt or ghec %} -- "[Navegar en el código de {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt or ghec %} +- "[Navigating code on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-commits.md b/translations/es-ES/content/search-github/searching-on-github/searching-commits.md index 0392e94f49..784d1b9e9d 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-commits.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-commits.md @@ -1,6 +1,6 @@ --- -title: Buscar confirmaciones de cambios -intro: 'Puedes buscar confirmaciones de cambios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de confirmaciones con cualquier combinación.' +title: Searching commits +intro: 'You can search for commits on {% data variables.product.product_name %} and narrow the results using these commit search qualifiers in any combination.' redirect_from: - /articles/searching-commits - /github/searching-for-information-on-github/searching-commits @@ -13,100 +13,103 @@ versions: topics: - GitHub search --- +You can search for commits globally across all of {% data variables.product.product_name %}, or search for commits within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." -Puedes buscar confirmaciones de cambios globalmente a través de todos los {% data variables.product.product_name %}, o buscar confirmaciones de cambios dentro de un repositorio particular u organización. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". - -Cuando buscas confirmaciones de cambios, se busca únicamente la [rama predeterminada](/articles/about-branches) de un repositorio. +When you search for commits, only the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) of a repository is searched. {% data reusables.search.syntax_tips %} -## Buscar dentro de los mensajes de confirmación +## Search within commit messages -Puedes encontrar confirmaciones que contengan determinadas palabras en el mensaje. Por ejemplo, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) encuentra las confirmaciones que contienen las palabras "fix" y "typo." +You can find commits that contain particular words in the message. For example, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) matches commits containing the words "fix" and "typo." -## Buscar por el autor o la persona que confirma el cambio +## Search by author or committer -Puedes encontrar confirmaciones de cambios por un usuario particular con los calificadores `author` (autor) o `committer` (persona que confirma el cambio). +You can find commits by a particular user with the `author` or `committer` qualifiers. -| Qualifier | Ejemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) encuentra confirmaciones cuya autoría corresponde a @defunkt. | -| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) encuentra confirmaciones de @defunkt. | +| Qualifier | Example +| ------------- | ------------- +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) matches commits authored by @defunkt. +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) matches commits committed by @defunkt. -Los calificadores `author-name` y `committer-name` encuentran confirmaciones por el nombre de su autor o de la persona que confirma el cambio. +The `author-name` and `committer-name` qualifiers match commits by the name of the author or committer. -| Qualifier | Ejemplo | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) encuentra confirmaciones con "wanstrath" en el nombre de autor. | -| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) encuentra confirmaciones con "wanstrath" en el nombre de la persona que confirma el cambio. | +| Qualifier | Example +| ------------- | ------------- +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the author name. +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the committer name. -Los calificadores `author-email` y `committer-email` encuentran confirmaciones por la dirección completa de correo electrónico del autor o de la persona que confirma el cambio. +The `author-email` and `committer-email` qualifiers match commits by the author's or committer's full email address. -| Qualifier | Ejemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) encuentra confirmaciones cuyo autor es chris@github.com. | -| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) encuentra confirmaciones de chris@github.com. | +| Qualifier | Example +| ------------- | ------------- +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) matches commits authored by chris@github.com. +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) matches commits committed by chris@github.com. -## Buscar por fecha de autoría o de confirmación +## Search by authored or committed date -Utiliza los calificadores `author-date` y `committer-date` para encontrar confirmaciones que fueron creadas o confirmadas dentro de un rango de fechas especificado. +Use the `author-date` and `committer-date` qualifiers to match commits authored or committed within the specified date range. {% data reusables.search.date_gt_lt %} -| Qualifier | Ejemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) encuentra confirmaciones creadas antes del 2016-01-01. | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) encuentra las confirmaciones que se crearon después del 2016-01-01. | +| Qualifier | Example +| ------------- | ------------- +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01. +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. -## Filtrar confirmaciones de fusión +## Filter merge commits -Los filtros del calificador `merge` de confirmación de fusión. +The `merge` qualifier filters merge commits. -| Qualifier | Ejemplo | -| ------------- | ---------------------------------------------------------------------------------------------------------------- | -| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) encuentra confirmaciones de fusión. | -| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) encuentra confirmaciones de no fusión. | +| Qualifier | Example +| ------------- | ------------- +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) matches merge commits. +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) matches non-merge commits. -## Filtrar por hash +## Search by hash -El calificador `hash` encuentra confirmaciones con el hash SHA-1 especificado. +The `hash` qualifier matches commits with the specified SHA-1 hash. -| Qualifier | Ejemplo | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) encuentra confirmaciones con el hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | +| Qualifier | Example +| ------------- | ------------- +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) matches commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. -## Filtrar por padre +## Search by parent -El calificador `parent` (padre) encuentra confirmaciones cuyo padre tiene el hash SHA-1 especificado. +The `parent` qualifier matches commits whose parent has the specified SHA-1 hash. -| Qualifier | Ejemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) encuentra el hijo de las confirmaciones con el hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | +| Qualifier | Example +| ------------- | ------------- +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) matches children of commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. -## Filtrar por árbol +## Search by tree -El calificador `tree` (árbol) encuentra confirmaciones con el hash de árbol de git SHA-1 especificado. +The `tree` qualifier matches commits with the specified SHA-1 git tree hash. -| Qualifier | Ejemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) encuentra confirmaciones que se refieren al hash del árbol `99ca967`. | +| Qualifier | Example +| ------------- | ------------- +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) matches commits that refer to the tree hash `99ca967`. -## Buscar dentro de los repositorios de un usuario u organización +## Search within a user's or organization's repositories -Para buscar confirmaciones en todos los repositorios que son propiedad de una determinada organización o usuario, utiliza el calificador `user` (usuario) u `org` (organización). Para buscar confirmaciones en un repositorio específico, utiliza el calificador `repo`. +To search commits in all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To search commits in a specific repository, use the `repo` qualifier. -| Qualifier | Ejemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) encuentra mensajes de confirmación con la palabra "gibberish" en repositorios propiedad de @defunkt. | -| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) encuentra mensajes de confirmación con la palabra "test" en repositorios propiedad de @github. | -| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) encuentra mensajes de confirmación con la palabra "language" en un repositorio "gibberish" de @defunkt. | +| Qualifier | Example +| ------------- | ------------- +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) matches commit messages with the word "gibberish" in repositories owned by @defunkt. +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) matches commit messages with the word "test" in repositories owned by @github. +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) matches commit messages with the word "language" in @defunkt's "gibberish" repository. -## Filtrar por visibilidad de repositorio +## Filter by repository visibility -El calificador `is` coincide con las confirmaciones de los repositorios con la visibilidad especificada. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". +The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -| Calificador| Ejemplo | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) coincide con las confirmaciones de los repositorios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) coincide con las confirmaciones de los repositorios internos. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) coincide con las confirmaciones de los repositorios privados. +| Qualifier | Example +| ------------- | ------------- |{% ifversion fpt or ghes or ghec %} +| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.{% endif %} +| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. +| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories. -## Leer más +## Further reading -- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md b/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md index a578ae9f8f..ff099cedaf 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md @@ -1,6 +1,6 @@ --- -title: Buscar en bifurcaciones -intro: 'Por defecto, las bifurcaciones [forks](/articles/about-forks) no se muestran en los resultados de la búsqueda. Puedes elegir incluirlas en las búsquedas de repositorios y en las búsquedas de código si cumplen con determinados criterios.' +title: Searching in forks +intro: 'By default, [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) are not shown in search results. You can choose to include them in repository searches, and in code searches if they meet certain criteria.' redirect_from: - /articles/searching-in-forks - /github/searching-for-information-on-github/searching-in-forks @@ -13,21 +13,20 @@ versions: topics: - GitHub search --- +To show forks in [repository search](/search-github/searching-on-github/searching-for-repositories) results, add `fork:true` or `fork:only` to your query. -Para mostrar bifurcaciones en los resultados de la [búsqueda de repositorios](/search-github/searching-on-github/searching-for-repositories), agrega `fork:true` o `fork:only` en tu consulta. +Forks are only indexed for [code search](/search-github/searching-on-github/searching-code) when they have more stars than the parent repository. You will not be able to search the code in a fork that has less stars than its parent. To show forks with more stars than the parent repository in code search results, add `fork:true` or `fork:only` to your query. -Las fiburcaciones solo se indexan por [búsqueda de código](/search-github/searching-on-github/searching-code) cuando tienen más estrellas que el repositorio padre. No podrás buscar el código en una bifurcación que tenga menos estrellas que su padre. Para mostrar bifurcaciones con más estrellas que el repositorio padre en los resultados de una búsqueda de código, agrega `fork:true` o `fork:only` en tu consulta. +The `fork:true` qualifier finds all results that match your search query, including forks. The `fork:only` qualifier finds _only_ forks that match your search query. -El calificador `fork:true` encuentra todos los resultados que coinciden con tu consulta de búsqueda, incluidas las bifurcaciones. El calificador `fork:only` encuentra _únicamente_ bifurcaciones que coinciden con tu consulta de búsqueda. +| Qualifier | Example +| ------------- | ------------- +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) matches all repositories containing the word "github," including forks. +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) matches code with the word "android" that's written in Java, in both forks and regular repositories. +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) matches all fork repositories containing the word "github." +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) matches repositories with more than 500 forks, and only returns those that are forks. -| Qualifier | Ejemplo | -| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) encuentra todos los repositorios que contienen la palabra "github," incluidas las bifurcaciones. | -| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) encuentra código con la palabra "android" que está escrito en Java, tanto en bifurcaciones como en repositorios normales. | -| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) encuentra todos los repositorios de bifurcaciones que contienen la palabra "github." | -| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) coincidirá con repositorios de más de 500 ramificaciones, y regresará únicamente aquellos que son ramificaciones. | +## Further reading -## Leer más - -- "[Acerca de las bifurcaciones](/articles/about-forks)" -- "[Acerca de buscar en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" \ No newline at end of file diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 30bc5d8c5c..2e726d5f01 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Buscar propuestas y solicitudes de extracción -intro: 'Puedes buscar propuestas y solicitudes de extracción en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda en cualquier combinación.' +title: Searching issues and pull requests +intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.' redirect_from: - /articles/searching-issues/ - /articles/searching-issues-and-pull-requests @@ -13,332 +13,338 @@ versions: ghec: '*' topics: - GitHub search -shortTitle: Buscar propuestas & solicitudes de cambio +shortTitle: Search issues & PRs --- - -Puedes buscar propuestas y solicitudes de extracción globalmente a través de todos los {% data variables.product.product_name %}, o buscar propuestas y solicitudes de extracción dentro de una organización particular. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". +You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." {% tip %} **Tips:**{% ifversion ghes or ghae %} - - Este artículo contiene búsquedas de ejemplo en el sitio web {% data variables.product.prodname_dotcom %}.com, pero puedes utilizar los mismos filtros de búsqueda en {% data variables.product.product_location %}.{% endif %} - - Para obtener una lista de sintaxis de búsqueda que puedas agregar a cualquier calificador para mejorar aún más tus resultados, consulta "[Comprender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". - - Utiliza comillas alrededor de los términos de búsqueda que contengan varias palabras. Por ejemplo, si deseas buscar propuestas con la etiqueta "In progress" (En curso), buscarías por la etiqueta `label:"in progress"`. Buscar no distingue entre mayúsculas y minúsculas. + - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %} + - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". + - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. - {% data reusables.search.search_issues_and_pull_requests_shortcut %} {% endtip %} -## Buscar únicamente propuestas o solicitudes de extracción +## Search only issues or pull requests -Por defecto, la búsqueda de {% data variables.product.product_name %} devolverá tanto propuestas como solicitudes de extracción. Sin embargo, puedes restringir los resultados de la búsqueda a solo propuestas y solicitudes de extracción utilizando el calificador `type` o `is`. +By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier. -| Qualifier | Ejemplo | -| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) encuentra solicitudes de extracción con la palabra "cat." | -| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) encuentra propuestas que contienen la palabra "github," y tienen un comentario de @defunkt. | -| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) encuentra solicitudes de extracción con la palabra "event." | -| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) encuentra propuestas cerradas con la etiqueta "bug." | +| Qualifier | Example +| ------------- | ------------- +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat." +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt. +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event." +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug." -## Buscar por título, cuerpo o comentarios +## Search by the title, body, or comments -Con el calificador `in` puedes restringir tu búsqueda por título, cuerpo, comentarios o cualquier combinación de estos. Cuando omites este calificador, se buscan el título, el cuerpo y los comentarios, todos ellos. +With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched. -| Qualifier | Ejemplo | -| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) encuentra propuestas con "warning" en su título. | -| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) encuentra propuestas con "error" en su título o cuerpo. | -| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) encuentra propuestas que mencionan "shipit" en sus comentarios. | +| Qualifier | Example +| ------------- | ------------- +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title. +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body. +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments. -## Buscar dentro de los repositorios de un usuario u organización +## Search within a user's or organization's repositories -Para buscar propuestas y solicitudes de extracción en todos los repositorios que son propiedad de un determinado usuario u organización, puedes utilizar el calificador `user` o `org`. Para buscar propuestas y solicitudes de extracción en un repositorio específico, puedes utilizar el calificador `repo`. +To search issues and pull requests in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier. {% data reusables.pull_requests.large-search-workaround %} -| Qualifier | Ejemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) encuentra propuestas con la palabra "ubuntu" de repositorios que son propiedad de @defunkt. | -| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) encuentra propuestas en repositorios que son propiedad de la organización de GitHub. | -| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) coincidirá con informes de problemas del proyecto de shumway de @mozilla que fueron creados antes de marzo de 2012. | +| Qualifier | Example +| ------------- | ------------- +| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt. +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization. +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012. -## Buscar por estado abierto o cerrado +## Search by open or closed state -Puedes filtrar propuestas y solicitudes de extracción en base a si están abiertas o cerradas utilizando el calificador `state` o `is`. +You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier. -| Qualifier | Ejemplo | -| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) encuentra propuestas abiertas que mencionan a @vmg con la palabra "libraries." | -| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) encuentra propuestas cerradas con la palabra "design" en el cuerpo. | -| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) encuentra propuestas abiertas con la palabra "performance." | -| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) encuentra propuestas y solicitudes de extracción cerradas con la palabra "android." | +| Qualifier | Example +| ------------- | ------------- +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries." +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body. +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance." +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android." -## Filtrar por visibilidad de repositorio +## Filter by repository visibility -Puedes filtrar por la visibilidad del repositorio que contenga las propuestas y solicitudes de cambios utilizando el calificador `is`. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". +You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion fpt or ghes or ghae or ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. +| Qualifier | Example +| ------------- | ------------- |{% ifversion fpt or ghes or ghec %} +| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion fpt or ghes or ghae or ghec %} +| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} +| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. -## Buscar por autor +## Search by author -El calificador `author` (autor) encuentra propuestas y solicitudes de extracción creadas por un determinado usuario o cuenta de integración. +The `author` qualifier finds issues and pull requests created by a certain user or integration account. -| Qualifier | Ejemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) coincide con las propeustas y solicitudes de cambios que contienen la palabra "cool" y que creó @gjtorikian. | -| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) coincide con las propuestas que escribió @mdo y que contienen la palabra "bootstrap" en el cuerpo. | -| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) coincide con las propuestas que creó la cuenta de integración llamada "robot". | +| Qualifier | Example +| ------------- | ------------- +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." -## Buscar por asignatario +## Search by assignee -El calificador `assignee` (asignatario) encuentra propuestas y solicitudes de extracción que están asignadas a un determinado usuario. No puedes buscar propuestas y solicitudes que tengan _algún_ asignado cualquiera, sin embargo, puedes buscar por [propuestas y solicitudes de cambios que no tengan asignados](#search-by-missing-metadata). +The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata). -| Qualifier | Ejemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) coincide con las propuestas y solicitudes de cambio en el proyecto de libgit2 que se hayan asignado a @vmg. | +| Qualifier | Example +| ------------- | ------------- +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. -## Buscar por mención +## Search by mention -El calificador `mentions` (menciones) encuentra propuestas que mencionan a un determinado usuario. Para obtener más información, consulta [Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." +The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." -| Qualifier | Ejemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) coincide con las propuestas que tengan la palabra "resque" y que mencionen a @defunkt. | +| Qualifier | Example +| ------------- | ------------- +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. -## Buscar por mención de equipo +## Search by team mention -Para las organizaciones y los equipos a los que perteneces, puedes utilizar el calificador `team` (equipo) para encontrar propuestas y solicitudes de extracción que mencionan a un determinado equipo dentro de esa organización. Reemplaza estos nombres de ejemplo con el nombre de tu organización y equipo para realizar una búsqueda. +For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search. -| Qualifier | Ejemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------- | -| team:ORGNAME/TEAMNAME | **team:jekyll/owners** coincide con las propeustas en donde se menciona al equipo `@jekyll/owners`. | -| | **team:myorg/ops is:open is:pr** coincide con las solicitudes de cambios en donde se menciona al equipo `@myorg/ops`. | +| Qualifier | Example +| ------------- | ------------- +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned. +| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. -## Buscar por comentarista +## Search by commenter -El calificador `commenter` (comentarista) encuentra propuestas que contienen un comentario de un determinado usuario. +The `commenter` qualifier finds issues that contain a comment from a certain user. -| Qualifier | Ejemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) coincide con las propuestas en los repositorios que le pertenecen a GitHub y que contienen la palabra "github" y un comentario de @defunkt. | +| Qualifier | Example +| ------------- | ------------- +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. -## Buscar por usuario que participa en una propuesta o solicitud de extracción +## Search by a user that's involved in an issue or pull request -Puedes utilizar el calificador `involves` para encontrar propuestas que de algún modo involucran a un determinado usuario. El calificador `involves` es un operador lógico OR (o) entre los calificadores `author`, `assignee`, `mentions` y `commenter` para un usuario único. En otras palabras, este calificador encuentra propuestas y solicitudes de extracción que fueron creadas por un determinado usuario, asignadas a ese usuario, que lo mencionan o que fueron comentadas por ese usuario. +You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user. -| Qualifier | Ejemplo | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** coincide con las propeustas en donde estén involucrados ya sea @defunkt o @jlord. | -| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) coincide con las propuestas en donde se involucra a @mdo y que no contienen la palabra "bootstrap" en el cuerpo. | +| Qualifier | Example +| ------------- | ------------- +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in. +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. {% ifversion fpt or ghes or ghae or ghec %} -## Buscar reportes de problemas y solicitudes de extracción enlazados -Puedes acotar tus resultados para que solo incluyan informes de problemas que se enlazaron con solicitudes de extracción con una referencia cerrada, o solicitudes de extracción que se enlazaron a un informe de problemas que se pueden cerrar con otra solicitud de extracción. +## Search for linked issues and pull requests +You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close. -| Qualifier | Ejemplo | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) coincidirá con informes de problemas abiertos en el repositorio `desktop/desktop` que se enlazan a una solicitud de extracción con una referencia cerrada. | -| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) coincidirá con las solicitudes de extracción cerradas en el repositorio `desktop/desktop` que se enlazaron a un informe de problemas que se pudo haber cerrado con una solicitud de extracción. | -| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) coincidirá con informes de problemas abiertos en el repositorio `desktop/desktop` que no estén enlazados a una solicitud de extracción por una referencia cerrada. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) Coincidirá con las solicitudes de extracción abiertas en el repositorio `desktop/desktop` que no se hayan enlazado con un informe de problemas que la solicitud de extracción haya creado. -{% endif %} +| Qualifier | Example | +| ------------- | ------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. |{% endif %} -## Buscar por etiqueta +## Search by label -Puedes acotar tus resultados por etiquetas, utilizando el calificador `label` (etiqueta). Ya que las propuestas pueden tener múltiples etiquetas, puedes enumerar un calificador separado para cada propuesta. +You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue. -| Qualifier | Ejemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) encuentra propuestas con la etiqueta "help wanted" (se necesita ayuda) que están en los repositorios Ruby. | -| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) encuentra propuestas con la palabra "broken" en el cuerpo, que no tienen la etiqueta "bug" (error), pero *que tienen* la etiqueta "priority" (prioridad). | -| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} -| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) encuentra propuestas con la etiqueta "bug" o "resolved".{% endif %} +| Qualifier | Example +| ------------- | ------------- +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} -## Buscar por hito +## Search by milestone -El calificador `milestone` (hito) encuentra propuestas o solicitudes de extracción que son parte de un [hito](/articles/about-milestones) dentro de un repositorio. +The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository. -| Qualifier | Ejemplo | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) encuentra propuestas que son un hito con el nombre de "overhaul." | -| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) encuentra propuestas que están en un hito con el nombre de "bug fix." | +| Qualifier | Example +| ------------- | ------------- +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." -## Buscar por tablero de proyecto +## Search by project board -Puedes utilizar el calificador `project` (proyecto) para encontrar propuestas que están asociadas con un [tablero de proyecto](/articles/about-project-boards/) específico en un repositorio u organización. Debes buscar tableros de proyecto por el número del tablero de proyecto. Puedes encontrar el número del tablero de proyecto al final de la URL de cada tablero de proyecto. +You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL. -| Qualifier | Ejemplo | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| project:PROJECT_BOARD | **project:github/57** encuentra propuestas propiedad de GitHub que están asociadas con el tablero de proyecto de la organización número 57. | -| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** encuentra propuestas que están asociadas con el tablero de proyecto 1 en el repositorio lingüístico de @github. | +| Qualifier | Example +| ------------- | ------------- +| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. -## Buscar por estado de confirmación +## Search by commit status -Puedes filtrar solicitudes de extracción en base al estado de las confirmaciones. Esto es particularmente útil si estás utilizando [el estado API](/rest/reference/repos#statuses) o un servicio CI. +You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service. -| Qualifier | Ejemplo | -| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) encuentra solicitudes de extracción abiertas en repositorios Go donde el estado es pendiente. | -| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) encuentra solicitudes de extracción abiertas con la palabra "finally" en el cuerpo con un estado exitoso. | -| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) encuentra solicitudes de extracción abiertas en mayo de 2015 con un estado falló. | +| Qualifier | Example +| ------------- | ------------- +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. -## Buscar por SHA de confirmación +## Search by commit SHA -Si sabes el hash SHA específico de una confirmación, puedes utilizarlo para buscar solicitudes de extracción que contienen ese SHA. La sintaxis SHA debe ser por lo menos de siete caracteres. +If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters. -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) encuentra solicitudes de extracción con una confirmación SHA que comience con `e1109ab`. | -| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) encuentra solicitudes de extracción fusionadas con una confirmación SHA que comience con `0eff326d6213c`. | +| Qualifier | Example +| ------------- | ------------- +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. -## Buscar por nombre de la rama +## Search by branch name -Puedes filtrar solicitudes de extracción en base a la rama de la que provienen (la rama "head" [de encabezado]) o la rama en la que están fusionadas (en la rama "base" [base]). +You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch). -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) encuentra solicitudes de extracción abiertas desde los nombres de las ramas que comienzan con la palabra "change" que están cerradas. | -| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) encuentra solicitudes de extracción que se están fusionando dentro de la rama `gh-pages`. | +| Qualifier | Example +| ------------- | ------------- +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. -## Buscar por lenguaje +## Search by language -Con el calificador `language` (lenguaje) puedes buscar propuestas y solicitudes de extracción dentro de repositorios que están escritos en un determinado lenguaje. +With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language. -| Qualifier | Ejemplo | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) encuentra propuestas abiertas que están en los repositorios Ruby. | +| Qualifier | Example +| ------------- | ------------- +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. -## Buscar por cantidad de comentarios +## Search by number of comments -Puedes utilizar el calificador `comments` (comentarios) junto con los calificadores [mayor que, menor que y rango ](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para buscar por cantidad de comentarios. +You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments. -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) encuentra propuestas cerradas con más de 100 comentarios. | -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) encuentra propuestas con comentarios que van desde 500 a 1000. | +| Qualifier | Example +| ------------- | ------------- +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. -## Buscar por cantidad de interacciones +## Search by number of interactions -Puedes filtrar propuestas y solicitudes de extracción en base a la cantidad de interacciones, utilizando el calificador `interactions` (interacciones) y junto con [los calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). El conteo de interacciones es la cantidad de reacciones y comentarios sobre una propuesta o solicitud de extracción. +You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). The interactions count is the number of reactions and comments on an issue or pull request. -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) encuentra solicitudes de extracción o propuestas con más de 2000 interacciones. | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) encuentra solicitudes de extracción o propuestas con un rango de interacciones entre 500 a 1000. | +| Qualifier | Example +| ------------- | ------------- +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions. +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. -## Buscar por cantidad de reacciones +## Search by number of reactions -Puedes filtrar propuestas y solicitudes de extracción en base a la cantidad de reacciones, utilizando el calificador `reactions` (reacciones) y junto con [los calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). +You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). -| Qualifier | Ejemplo | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) encuentra propuestas con más de 1000 reacciones. | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) encuentra propuestas con reacciones con un rango de entre 500 a 1000. | +| Qualifier | Example +| ------------- | ------------- +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions. +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. -## Buscar solicitudes de extracción en borrador -Puedes filtrar por solicitudes de extracción en borrador. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)." +## Search for draft pull requests +You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." -| Qualifier | Example | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) coincidirá con las solicitudes de extracción listas para revisión.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) coincidirá con las solicitudes de extracción en estado de borrador.{% endif %} +| Qualifier | Example +| ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} +| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review.{% else %} +| `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) matches draft pull requests.{% endif %} -## Buscar por estado de revisión de solicitud de extracción y revisor +## Search by pull request review status and reviewer -Puedes filtrar las solicitudes de extracción en función de su [estado de revisión](/articles/about-pull-request-reviews) (_ninguno_, _requerido_, _aprobado_ o _cambios solicitados_), por revisor y por revisor solicitado. +You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. -| Qualifier | Ejemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) encuentra solicitudes de extracción que no han sido revisadas. | -| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) encuentra solicitudes de extracción que requieren una revisión antes de poder ser fusionadas. | -| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) encuentra solicitudes de extracción que un revisor ha aprobado. | -| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) encuentra solicitudes de extracción en las cuales un revisor ha solicitado cambios. | -| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) encuentra revisión de solicitudes de extracción por una persona particular. | -| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) encuentra solicitudes de extracción donde una persona específica solicitó una revisión. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -| user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) coincide con las solicitudes de cambio que se te solicitaron revisar directamente.{% endif %} -| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) encuentra solicitudes de extracción que tienen solicitudes de revisión de un equipo `atom/design`. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. | +| Qualifier | Example +| ------------- | ------------- +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed. +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged. +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved. +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes. +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person. +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +| user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %} +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request. -## Buscar por cuándo una propuesta o solicitud de extracción fue creada o actualizada por última vez +## Search by when an issue or pull request was created or last updated -Puedes filtrar propuestas en base al momento de creación o al momento de su última actualización. Para la creación de una propuesta, puedes usar el calificador `created` (creado); para encontrar cuándo se actualizó por última vez un repositorio, querrás utilizar el calificador `pushed` (subido). +You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier. -Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Ejemplo | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) encuentra las propuestas que se crearon antes de 2011 en los repositorios que están escritos en C#. | -| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) encuentra las propuestas con la palabra "weird" en el cuerpo, las cuales se actualizaron después de febrero del 2013. | +| Qualifier | Example +| ------------- | ------------- +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#. +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013. -## Buscar por cuándo una propuesta o solicitud de extracción fue cerrada +## Search by when an issue or pull request was closed -Puedes filtrar propuestas y solicitudes de extracción en base a su momento de cierre, utilizando el calificador `closed` (cerrada). +You can filter issues and pull requests based on when they were closed, using the `closed` qualifier. -Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Ejemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) encuentra las propuestas y solicitudes de cambios en Swift que se cerraron después del 11 de junio de 2014. | -| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) encuentra las propuestas y solicitudes de cambio con la palabra "data" en el cuerpo, las cuales se cerrron antes de octubre de 2012. | +| Qualifier | Example +| ------------- | ------------- +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014. +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012. -## Buscar por cuándo una solicitud de extracción fue fusionada +## Search by when a pull request was merged -Puedes filtrar solicitudes de extracción en base a cuándo fueron fusionadas, utilizando el calificador `merged` (fusionada). +You can filter pull requests based on when they were merged, using the `merged` qualifier. -Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Ejemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) encuntra las solicitudes de cambio en los repositorios de JavaScript que se fusionaron antes de 2011. | -| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) encuentra las solicitudes de cambiosen Ruby con la palabra "fast" en el título, los cuales se hayan fusionado después de mayo de 2014. | +| Qualifier | Example +| ------------- | ------------- +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011. +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014. -## Buscar en base a si una solicitud de extracción se fusionó o se desagrupó +## Search based on whether a pull request is merged or unmerged -Puedes filtrar solicitudes de extracción en base a cuándo fueron fusionadas o desagrupadas, utilizando el calificador `is`. +You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier. -| Qualifier | Ejemplo | -| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) encuentra solicitudes de extracción fusionadas con la palabra "bugfix." | -| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) encuentra propuestas y solicitudes de extracción cerradas con la palabra "error." | +| Qualifier | Example +| ------------- | ------------- +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bugfix." +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error." -## Buscar en base a si un repositorio está archivado +## Search based on whether a repository is archived -El calificador `archived` (archivado) filtra tus resultados en base a si una propuesta o una solicitud de extracción está en un repositorio archivado. +The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository. -| Qualifier | Ejemplo | -| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) encuentra propuestas y solicitudes de extracción que contienen la palabra "GNOME" en repositorios archivados a los que tienes acceso. | -| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) encuentra propuestas y solicitudes de extracción que contienen la palabra "GNOME" en repositorios no archivados a los que tienes acceso. | +| Qualifier | Example +| ------------- | ------------- +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to. +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to. -## Buscar en base a si una conversación está bloqueada +## Search based on whether a conversation is locked -Puedes buscar por una propuesta o solicitud de extracción que tiene una conversación utilizando el calificador `is`. Para obtener más información, consulta "[Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations)." +You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." -| Qualifier | Ejemplo | -| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) encuentra propuestas o solicitudes de extracción con las palabras "code of conduct" que tienen una conversación bloqueada en un repositorio que no se ha archivado. | -| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) encuentra propuestas o solicitudes de extracción con las palabras "code of conduct" que tienen una conversación desbloqueada en un repositorio que no se ha archivado. | +| Qualifier | Example +| ------------- | ------------- +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived. +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived. -## Buscar por metadatos faltantes +## Search by missing metadata -Puedes acotar tu búsqueda a propuestas y solicitudes de extracción que tienen determinados metadatos faltantes, utilizando el calificador `no`. Esos metadatos incluyen: +You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes: -* Etiquetas -* Hitos -* Asignatarios -* Proyectos +* Labels +* Milestones +* Assignees +* Projects -| Qualifier | Ejemplo | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) encuentra propuestas y solicitudes de extracción con la palabra "priority" que tampoco tienen ninguna etiqueta. | -| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) encuentra propuestas no asociadas con un hito que contienen la palabra "sprint." | -| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) encuentra propuestas no asociadas con un asignatario, que contienen la palabra "important," y en repositorios Java. | -| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) encuentra propuestas no asociadas con un tablero de proyecto, que contienen la palabra "build." | +| Qualifier | Example +| ------------- | ------------- +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels. +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint." +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories. +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build." -## Leer más +## Further reading -- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index a48eb3d5e4..518e7b5e0f 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- title: プライベートコントリビューションをプロフィールで公開または非公開にする -intro: '{% data variables.product.product_name %} プロフィールには、過去 1 年間のリポジトリコントリビューションのグラフが表示されます。 パブリックリポジトリ{% endif %}からのアクティビティに加えて、{% ifversion fpt or ghes or ghec %}プライベートおよび内部{% else %}プライベート{% endif %}リポジトリ{% ifversion fpt or ghes or ghec %}からの匿名化されたアクティビティを表示するように選択できます。' +intro: 'Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.' redirect_from: - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile - /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index 28f6aa7d4e..6ba64d8d33 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -1,6 +1,6 @@ --- -title: ユーザ アカウント設定の管理 -intro: ユーザ名を変更する、アカウントを削除するなど、個人アカウントの設定を変更できます。 +title: Managing user account settings +intro: 'You can change several settings for your personal account, including changing your username and deleting your account.' redirect_from: - /categories/29/articles/ - /categories/user-accounts/ @@ -23,6 +23,7 @@ children: - /deleting-your-user-account - /permission-levels-for-a-user-account-repository - /permission-levels-for-user-owned-project-boards + - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - /managing-security-and-analysis-settings-for-your-user-account - /managing-access-to-your-user-accounts-project-boards diff --git a/translations/ja-JP/content/actions/guides.md b/translations/ja-JP/content/actions/guides.md index a894d4fd48..7ac00d9b29 100644 --- a/translations/ja-JP/content/actions/guides.md +++ b/translations/ja-JP/content/actions/guides.md @@ -1,6 +1,6 @@ --- title: Guides for GitHub Actions -intro: '{% data variables.product.prodname_actions %} のこれらのガイドには、ワークフローの設定に役立つ特定の使用例とサンプルが含まれています。' +intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -13,6 +13,7 @@ learningTracks: - continuous_integration - continuous_deployment - deploy_to_the_cloud + - '{% ifversion ghec or ghes or ghae %}adopting_github_actions_for_your_enterprise{% endif %}' - hosting_your_own_runners - create_actions includeGuides: diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md index 0d03432463..d92f270477 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Enterprise を設定する -intro: '{% data variables.product.product_name %} が稼働したら、Organization のニーズに合わせて Enterprise を設定できます。' +title: Configuring your enterprise +intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.' redirect_from: - /enterprise/admin/guides/installation/basic-configuration/ - /enterprise/admin/guides/installation/administrative-tools/ @@ -34,6 +34,7 @@ children: - /restricting-network-traffic-to-your-enterprise - /configuring-github-pages-for-your-enterprise - /configuring-the-referrer-policy-for-your-enterprise + - /configuring-custom-footers shortTitle: Configure your enterprise --- diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md deleted file mode 100644 index 93d88357bd..0000000000 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: GitHub Enterprise Server の GitHub Actions を使い始める -shortTitle: GitHub Actionsを使ってみる -intro: '{% data variables.product.prodname_ghe_server %} での {% data variables.product.prodname_actions %} の有効化と設定について初めて学びます。' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -redirect_from: - - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server -versions: - ghes: '*' -type: how_to -topics: - - Actions - - Enterprise ---- - -{% data reusables.actions.enterprise-beta %} - -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% ifversion ghes %} - -この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_server %} を設定する方法について説明しています。 ハードウェアとソフトウェアの要件、ストレージオプション、セキュリティ管理ポリシーについて説明します。 - -{% endif %} - -## ハードウェアについての留意点を確認する - -{% ifversion ghes = 3.0 %} - -{% note %} - -**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)」を参照してください。 - -{% endnote %} - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -{% data variables.product.product_location %} で使用可能な CPU およびメモリリソースによって、{% data variables.product.prodname_actions %} の最大ジョブスループットが決まります。 - -{% data variables.product.company_short %} での内部テストでは、さまざまな CPU およびメモリ設定の {% data variables.product.prodname_ghe_server %} インスタンスで次の最大スループットが実証されました。 インスタンスのアクティビティの全体的なレベルに応じて、スループットが異なる場合があります。 - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. - -The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -| vCPUs | メモリ | 最大ジョブスループット数 | -|:----- |:------ |:------------ | -| 4 | 32 GB | デモまたは軽いテスト | -| 8 | 64 GB | 25ジョブ | -| 16 | 160 GB | 35ジョブ | -| 32 | 256 GB | 100ジョブ | - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -| vCPUs | メモリ | Maximum Concurrency* | -|:----- |:------ |:-------------------- | -| 32 | 128 GB | 1500ジョブ | -| 64 | 256 GB | 1900ジョブ | -| 96 | 384 GB | 2200ジョブ | - -*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. - -{%- endif %} - -If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. {% data variables.product.prodname_ghe_server %}のキャパシティとパフォーマンスのモニタリングに関する詳しい情報については「[アプラインアンスのモニタリング](/admin/enterprise-management/monitoring-your-appliance)」を参照してください。 - -{% data variables.product.product_location %} の最小ハードウェア要件の詳細については、インスタンスのプラットフォームのハードウェアに関する考慮事項を参照してください。 - -- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) -- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) -- [Google Cloud Plafform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) -- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) -- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) -- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %} -- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %} - -{% data reusables.enterprise_installation.about-adjusting-resources %} - -## 外部ストレージの要件 - -{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にするには、外部 Blob ストレージにアクセスできる必要があります。 - -{% data variables.product.prodname_actions %} は、blob ストレージを使用して、ワークフローログやユーザがアップロードしたビルドアーティファクトなど、ワークフロー実行によって生成されたアーティファクトを保存します。 必要なストレージ容量は、{% data variables.product.prodname_actions %} の使用状況によって異なります。 単一の外部ストレージ設定のみがサポートされており、複数のストレージプロバイダを同時に使用することはできません。 - -{% data variables.product.prodname_actions %} は、次のストレージプロバイダをサポートしています。 - -* Azure Blob ストレージ -* Amazon S3 -* NAS ストレージ用の S3 対応 MinIO ゲートウェイ - -{% note %} - -**注釈:** これらは、{% data variables.product.company_short %} がサポートし、支援を提供できる唯一のストレージプロバイダです。 他の S3 API 互換のストレージプロバイダは、S3 API との違いにより、機能しない可能性があります。 追加のストレージプロバイダのサポートをリクエストするには、[お問い合わせ](https://support.github.com/contact)ください。 - -{% endnote %} - -## Networking considerations - -{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)." - -{% ifversion ghes %} - -## ストレージプロバイダで {% data variables.product.prodname_actions %} を有効化する - -以下の手順のいずれかに従って、選択したストレージプロバイダで {% data variables.product.prodname_actions %} を有効にします。 - -* [Azure Blob ストレージで GitHub Actions を有効化する](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) -* [Amazon S3 ストレージで GitHub Actions を有効化する](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) -* [NAS ストレージ用の MinIO ゲートウェイで GitHub Actions を有効化する](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) - -## Enterprise 内の {% data variables.product.prodname_actions %} のアクセス権限を管理する - -ポリシーを使用して、{% data variables.product.prodname_actions %} へのアクセスを管理できます。 詳しい情報については、「[Enterprise に GitHub Actions のポリシーを施行する](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。 - -## セルフホストランナーの追加 - -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% data variables.product.prodname_actions %} ワークフローを実行するには、セルフホストランナーを追加する必要があります。 Enterprise、Organization、リポジトリレベルでセルフホストランナーを追加できます。 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 - -## Enterprise で使用できるアクションを管理する - -ユーザーが Enterprise で使用できるアクションを制御できます。 これには、{% data variables.product.prodname_dotcom_the_website %} からのアクションへの自動アクセス用の {% data variables.product.prodname_github_connect %} の設定、または {% data variables.product.prodname_dotcom_the_website %} からのアクションの手動同期が含まれます。 - -詳しい情報については、「[Enterprise でのアクションの使用について](/admin/github-actions/about-using-actions-in-your-enterprise)」を参照してください。 - -## {% data variables.product.prodname_actions %} の一般的なセキュリティ強化 - -{% data variables.product.prodname_actions %} のセキュリティプラクティスについて詳しく学ぶには、「[{% data variables.product.prodname_actions %} のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions)」を参照してください。 - -{% endif %} - -## Reserved Names - -When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore. diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 27afa76b94..ee0f477635 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -1,12 +1,11 @@ --- -title: GitHub Enterprise Server の GitHub Actions を有効化する -intro: 'ストレージを設定し、{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効化する方法を学びます。' +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' versions: ghes: '*' topics: - Enterprise children: - - /getting-started-with-github-actions-for-github-enterprise-server - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage diff --git a/translations/ja-JP/content/admin/github-actions/index.md b/translations/ja-JP/content/admin/github-actions/index.md index f61a904a0a..808fdae5b0 100644 --- a/translations/ja-JP/content/admin/github-actions/index.md +++ b/translations/ja-JP/content/admin/github-actions/index.md @@ -1,14 +1,16 @@ --- -title: Enterprise 向けの GitHub Actions を管理する -intro: '{% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} で {% data variables.product.prodname_actions %} を有効にし、{% data variables.product.prodname_actions %} のポリシーと設定を管理します。' +title: Managing GitHub Actions for your enterprise +intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, and manage {% data variables.product.prodname_actions %} policies and settings.' redirect_from: - /enterprise/admin/github-actions versions: + ghec: '*' ghes: '*' ghae: '*' topics: - Enterprise children: + - /getting-started-with-github-actions-for-your-enterprise - /using-github-actions-in-github-ae - /enabling-github-actions-for-github-enterprise-server - /managing-access-to-actions-from-githubcom diff --git a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md deleted file mode 100644 index b2f7efd25e..0000000000 --- a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: GitHub AE の GitHub Actions を使い始める -shortTitle: GitHub Actionsを使ってみる -intro: '{% data variables.product.prodname_ghe_managed %} で {% data variables.product.prodname_actions %} を設定する方法を学びます。' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -versions: - ghae: '*' -type: how_to -topics: - - Actions - - Enterprise -redirect_from: - - /admin/github-actions/getting-started-with-github-actions-for-github-ae ---- - -{% data reusables.actions.ae-beta %} - -この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_managed %} を設定する方法について説明しています。 - -## Enterprise 内の {% data variables.product.prodname_actions %} のアクセス権限を管理する - -ポリシーを使用して、{% data variables.product.prodname_actions %} へのアクセスを管理できます。 詳しい情報については、「[Enterprise に GitHub Actions のポリシーを施行する](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。 - -## ランナーを追加する - -{% note %} - -**Note:** To add {% data variables.actions.hosted_runner %}s to {% data variables.product.prodname_ghe_managed %}, you will need to contact {% data variables.product.prodname_dotcom %} support. - -{% endnote %} - -{% data variables.product.prodname_actions %} ワークフローを実行するには、ランナーを追加する必要があります。 Enterprise、Organization、またはリポジトリレベルでランナーを追加できます。 詳しい情報については、「[{% data variables.actions.hosted_runner %} について](/actions/using-github-hosted-runners/about-ae-hosted-runners)」を参照してください。 - - -## {% data variables.product.prodname_actions %} の一般的なセキュリティ強化 - -{% data variables.product.prodname_actions %} のセキュリティプラクティスについて詳しく学ぶには、「[{% data variables.product.prodname_actions %} のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions)」を参照してください。 diff --git a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md index 07d50b7626..ed67e364c7 100644 --- a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md +++ b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md @@ -1,10 +1,9 @@ --- -title: GitHub AE で GitHub Actions を使用する -intro: '{% data variables.product.prodname_ghe_managed %} で {% data variables.product.prodname_actions %} を設定する方法を学びます。' +title: Using GitHub Actions in GitHub AE +intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' versions: ghae: '*' children: - - /getting-started-with-github-actions-for-github-ae - /using-actions-in-github-ae shortTitle: Use Actions in GitHub AE --- diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md index 0205aaa45e..6eee293a97 100644 --- a/translations/ja-JP/content/admin/guides.md +++ b/translations/ja-JP/content/admin/guides.md @@ -1,6 +1,6 @@ --- title: GitHub Enterprise guides -shortTitle: ガイド +shortTitle: Guides intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.' allowTitleToDifferFromFilename: true layout: product-sublanding @@ -9,14 +9,15 @@ versions: ghes: '*' ghae: '*' learningTracks: + - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' - '{% ifversion ghae %}get_started_with_github_ae{% endif %}' - '{% ifversion ghes %}deploy_an_instance{% endif %}' - '{% ifversion ghes %}upgrade_your_instance{% endif %}' + - adopting_github_actions_for_your_enterprise - '{% ifversion ghes %}increase_fault_tolerance{% endif %}' - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}' - - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' includeGuides: - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - /admin/authentication/changing-authentication-methods diff --git a/translations/ja-JP/content/billing/index.md b/translations/ja-JP/content/billing/index.md index 732d1ae8ac..067b356ef5 100644 --- a/translations/ja-JP/content/billing/index.md +++ b/translations/ja-JP/content/billing/index.md @@ -1,15 +1,46 @@ --- -title: Billing and payments for GitHub -shortTitle: 請求と支払い -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}.{% endif %}' +title: Billing and payments on GitHub +shortTitle: Billing and payments +intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github +introLinks: + overview: '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/about-billing-on-github{% elsif ghes%}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' +featuredLinks: + guides: + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method{% endif %}' + - '{% ifversion fpt %}/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription{% endif %}' + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/setting-your-billing-email{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/about-per-user-pricing{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + popular: + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + guideCards: + - /billing/managing-your-github-billing-settings/removing-a-payment-method + - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process + - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud{% endif %}' +layout: product-landing versions: fpt: '*' - ghec: '*' ghes: '*' ghae: '*' + ghec: '*' +topics: + - Billing children: - /managing-your-github-billing-settings - /managing-billing-for-your-github-account @@ -23,5 +54,4 @@ children: - /managing-billing-for-github-marketplace-apps - /managing-billing-for-git-large-file-storage - /setting-up-paid-organizations-for-procurement-companies ---- - +--- \ No newline at end of file diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index bbe6c925b7..14ea4e4b20 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -59,7 +59,7 @@ You can use the dependency graph to: - Explore the repositories your code depends on{% ifversion fpt or ghec %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% ifversion fpt or ghec %} - View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} - View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes > 3.1 or ghec %} -- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."{% endif %} +- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %} ## Enabling the dependency graph diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md index d39a344f5b..48cb432198 100644 --- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md @@ -1,6 +1,6 @@ --- -title: 高度なフォーマットを使用して作業する -intro: テーブルのようなフォーマット、構文の強調表示、および自動リンキングを使用すると、プルリクエスト、Issue、およびコメントに複雑な情報を明確に配置できます。 +title: Working with advanced formatting +intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.' redirect_from: - /articles/working-with-advanced-formatting versions: @@ -10,6 +10,7 @@ versions: ghec: '*' children: - /organizing-information-with-tables + - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /autolinked-references-and-urls - /attaching-files diff --git a/translations/ja-JP/content/graphql/guides/index.md b/translations/ja-JP/content/graphql/guides/index.md index c2a6b87c46..7311e5cf39 100644 --- a/translations/ja-JP/content/graphql/guides/index.md +++ b/translations/ja-JP/content/graphql/guides/index.md @@ -1,6 +1,6 @@ --- -title: ガイド -intro: GraphQLの始め方、RESTからGraphQLへの移行、様々なタスクでのGitHub GraphQL APIの利用方法について学んでください。 +title: Guides +intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.' redirect_from: - /v4/guides versions: @@ -18,5 +18,6 @@ children: - /using-the-explorer - /managing-enterprise-accounts - /using-the-graphql-api-for-discussions + - /migrating-graphql-global-node-ids --- diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md deleted file mode 100644 index 6dd5a346c1..0000000000 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ /dev/null @@ -1,256 +0,0 @@ ---- -title: Configurar notificações -intro: 'Escolha o tipo de atividade no {% data variables.product.prodname_dotcom %} do qual você deseja receber notificações e a forma como deseja que essas atualizações sejam entregues.' -redirect_from: - - /articles/about-web-notifications - - /format-of-notification-emails/ - - /articles/configuring-notification-emails/ - - /articles/about-notification-emails/ - - /articles/about-email-notifications - - /articles/accessing-your-notifications - - /articles/configuring-notification-delivery-methods/ - - /articles/managing-notification-delivery-methods/ - - /articles/managing-notification-emails-for-organizations/ - - /articles/choosing-the-delivery-method-for-your-notifications - - /articles/choosing-the-types-of-notifications-you-receive/ - - /github/managing-subscriptions-and-notifications-on-github/configuring-notifications - - /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Notifications ---- - -{% ifversion ghes %} -{% data reusables.mobile.ghes-release-phase %} -{% endif %} - -## Opções de entrega de notificação - -Você pode receber notificações de atividades em {% data variables.product.product_location %} nos locais a seguir. - - - Caixa de entrada de notificações na interface web de {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} - - A caixa de entrada no {% data variables.product.prodname_mobile %}, que sincroniza com a caixa de entrada em {% data variables.product.product_location %}{% endif %} - - Um cliente de e-mail que usa um endereço de e-mail verificado, que também pode sincronizar com a caixa de entrada de {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} e {% data variables.product.prodname_mobile %}{% endif %} - -{% ifversion fpt or ghes or ghec %} -{% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obter mais informações, consulte "[Escolhendo suas configurações de notificação](#choosing-your-notification-settings)". -{% endif %} - -{% data reusables.notifications.shared_state %} - -### Benefícios da caixa de entrada de notificações - -A caixa de entrada de notificações em {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} e {% data variables.product.prodname_mobile %}{% endif %} inclui opções de triagem desenhadas especificamente para o seu fluxo de notificações de {% data variables.product.prodname_dotcom %}, incluindo opções para: - - Fazer triagem de várias notificações ao mesmo tempo. - - Marcar as notificações concluídas como **Concluído** e removê-las da sua caixa de entrada. Para ver todas as suas notificações marcadas como **Concluído**, use a consulta `is:done`. - - Salvar uma notificação para revisar mais tarde. As notificações salvas são sinalizadas na sua caixa de entrada e mantidas indefinidamente. Para visualizar todas as suas notificações salvas, use a consulta `is:saved`. - - Cancelar inscrição e remover uma notificação da sua caixa de entrada. - - Visualizar o problema, a pull request ou uma discussão em equipe onde a notificação se origina no {% data variables.product.product_location %} de dentro da caixa de entrada de notificações. - - Ver uma das últimas razões pelas quais você está recebendo uma notificação de sua caixa de entrada com uma etiqueta `razões`. - - Criar filtros personalizados para focar em notificações diferentes quando quiser. - - Notificações em grupo em sua caixa de entrada por repositório ou data para obter uma visão geral rápida com menos comutação de contexto - -{% ifversion fpt or ghes or ghec %} -Além disso, você pode receber e testar notificações no seu dispositivo móvel com {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte "[Gerenciar as suas configurações de notificação com o GitHub para celular](#managing-your-notification-settings-with-github-for-mobile)" ou "[GitHub para celular](/github/getting-started-with-github/github-for-mobile)". -{% endif %} - -### Benefícios da utilização de um cliente de e-mail para notificações - -Um benefício de usar um cliente de e-mail é que todas as suas notificações podem ser mantidas indefinidamente, dependendo da capacidade de armazenamento do seu cliente de e-mail. As suas notificações na caixa de entrada só são mantidas por 5 meses em {% data variables.product.prodname_dotcom %} a menos que você as tenha marcado como **Salvas**. As notificações **Saved** (Salvas) são mantidas indefinidamente. Para obter mais informações sobre a política de retenção da sua caixa de entrada, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)". - -O envio de notificações para o cliente de e-mail também permite que você personalize sua caixa de entrada de acordo com as configurações do cliente de e-mail que pode incluir etiquetas personalizadas ou codificadas por cores. - -As notificações de e-mail também permitem flexibilidade com os tipos de notificações que você recebe e permitem que você escolha diferentes endereços de e-mail para atualizações. Por exemplo, você pode enviar determinadas notificações para um repositório para um endereço de e-mail pessoal verificado. Para obter mais informações, sobre suas opções de personalização de e-mail, consulte "[Personalizando suas notificações de e-mail](#customizing-your-email-notifications)." - -## Sobre notificações de participação e inspeção - -Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)". - -Para ver repositórios que você está inspecionando, acesse a sua [página de inspeção](https://github.com/watching). Para obter mais informações, consulte "[Gerenciando assinaturas e notificações do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". - -{% ifversion ghae or ghes < 3.1 %} -### Configurar notificações -{% endif %} -É possível configurar as notificações para um repositório na página do repositório ou na página de inspeção.{% ifversion ghes < 3.1 %} Você pode optar por receber apenas notificações de versões em um repositório ou ignorar todas as notificações de um repositório.{% endif %} - -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} - -### Sobre as notificações personalizadas -É possível personalizar notificações para um repositório. Por exemplo, você pode optar por receber notificação apenas quando atualizações de um ou mais tipos de eventos ({% data reusables.notifications-v2.custom-notification-types %}) ocorrerem em um repositório, ou ignorar todas as notificações de um repositório. -{% endif %} Para obter mais informações, consulte "[Definir as suas configurações de inspeção para um repositório individual](#configuring-your-watch-settings-for-an-individual-repository)" abaixo. - -### Participar de conversas -A qualquer momento que você comentar em uma conversa ou quando alguém @mencionar seu nome de usuário, você estará _participando_ de uma conversa. Por padrão, você é inscrito automaticamente em uma conversa ao participar dela. Você pode cancelar manualmente a inscrição de uma conversa que você participou, clicando em **Cancelar inscrição** no problema ou na pull request ou através da opção **Cancelar inscrição** na caixa de entrada de notificações. - -Para conversas que você está inspecionando ou participando, você pode escolher se deseja receber notificações por e-mail ou através da caixa de entrada de notificações em {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} e {% data variables.product.prodname_mobile %}{% endif %}. - -![Opções de notificações de participação e inspeção](/assets/images/help/notifications-v2/participating-and-watching-options.png) - -Por exemplo: - - Se você não quiser que as notificações sejam enviadas para o seu e-mail, desmarque **e-mail** para participar e inspecionar as notificações. - - Se quiser receber notificações por e-mail quando você participou de uma conversa, então selecione **e-mail** abaixo de "Participar". - -Se você não habilitar a notificação de inspeção ou participação para web{% ifversion fpt or ghes or ghec %} e mobile{% endif %}, então sua caixa de entrada de notificações não terá nenhuma atualização. - -## Personalizando suas notificações por e-mail - -Após habilitar as notificações de e-mail, o {% data variables.product.product_location %} enviará notificações a você como e-mails em diversas partes que contêm cópias do conteúdo em HTML e texto sem formatação. O conteúdo da notificação de e-mail inclui markdown, @menção, emojis, links por hash e muito mais, que aparecem no conteúdo original do {% data variables.product.product_location %}. Se você quiser ver apenas o texto do e-mail, configure o cliente de e-mail para exibir apenas a cópia do texto sem formatação. - -{% data reusables.notifications.outbound_email_tip %} - -{% data reusables.notifications.shared_state %} - -{% ifversion fpt or ghec %} - -Se estiver usando o Gmail, você poderá clicar em um botão junto ao e-mail de notificação para acessar o problema ou a pull request original que gerou a notificação. - -![Botões no Gmail](/assets/images/help/notifications/gmail-buttons.png) - -{% endif %} - -Escolha um endereço de e-mail padrão para enviar atualizações de conversas que você está participando ou inspecionando. Você também pode especificar qual atividade no {% data variables.product.product_location %} você deseja receber atualizações usando seu endereço de e-mail padrão. Por exemplo, escolha se você quer atualizações do seu e-mail padrão de: - - Comentários em problemas ou pull requests. - - Revisões de pull request. - - Pushes de pull request. - - Suas próprias atualizações, como quando você abre, comenta ou encerra um problema ou uma pull request. - -Dependendo da organização proprietária do repositório, você também pode enviar notificações para diferentes endereços de e-mail. Sua organização pode exigir que o endereço de e-mail seja verificado para um domínio específico. Para obter mais informações, consulte "[Escolher onde as notificações de e-mail da sua organização são enviadas](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)". - -Você também pode enviar notificações de um repositório específico para um endereço de e-mail. Para obter mais informações, consulte "[Sobre notificações de email para push no seu repositório](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)". - -{% data reusables.notifications-v2.email-notification-caveats %} - -## Filtrar notificações de e-mail - -Cada notificação de e-mail que o {% data variables.product.product_location %} envia contém informações de header. As informações de header em cada e-mail são consistentes, de modo que é possível usá-las no cliente de e-mail para filtrar ou encaminhar todas as notificações do {% data variables.product.prodname_dotcom %} ou determinados tipos de notificação do {% data variables.product.prodname_dotcom %}. - -Se você acredita que está recebendo notificações que não pertencem a você, examine os headers `X-GitHub-Recipient` e `X-GitHub-Recipient-Address`. Estes headers mostram quem é o destinatário pretendido. Dependendo de sua configuração de e-mail, você pode receber notificações destinadas a outro usuário. - -As notificações de e-mail do {% data variables.product.product_location %} contêm as seguintes informações de header: - -| Header | Informações | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Endereço do `remetente` | Esse endereço sempre será {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'o endereço de e-mail no-reply configurado pelo administrador do seu site'{% endif %}. | -| Campo `To` | Este campo conecta-se diretamente à corrente.{% ifversion not ghae %} Se você responder ao e-mail, você adicionará um novo comentário na conversa.{% endif %} -| Endereço de `Cc` | O {% data variables.product.product_name %} colocará você em cópia (`Cc`) se você estiver inscrito para uma conversa. O segundo endereço de e-mail de `Cc` corresponde ao motivo da notificação. O sufixo para esses motivos de notificação é {% data variables.notifications.cc_address %}. Os possíveis motivos de notificação são:
    • 'assign': você foi atribuído a um problema ou uma pull request.
    • 'author': você criou um problema ou uma pull request.
    • `ci_activity`: Uma execução de fluxo de trabalho de {% data variables.product.prodname_actions %} que você acionou foi concluída.
    • 'comment': você comentou um problema ou uma pull request.
    • 'manual': houve uma atualização em um problema ou uma pull request para o(a) qual você assinou manualmente.
    • 'mention': você foi mencionado em um problema ou uma pull request.
    • 'push': alguém fez commit em uma pull request que você assinou.
    • 'review_requested': você ou uma equipe da qual faz você faz parte foi solicitado para revisar uma pull request.
      • {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
    • 'security_alert': o {% data variables.product.prodname_dotcom %} detectou uma vulnerabilidade em um repositório para o qual você recebe alertas de segurança.
      • {% endif %}
    • 'state_change': um problema ou uma pull request que você assinou foi fechado(a) ou aberto(a).
    • 'subscribed': houve uma atualização em um repositório que você está inspecionando.
    • 'team_mention': uma equipe a qual você pertence foi mencionada em um problema ou uma pull request.
    • 'your_activity': você abriu, comentou ou fechou um problema ou uma pull request.
    | -| campo `mailing list` | Esse campo identifica o nome do repositório e seu proprietário. O formato desse endereço é sempre `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Os níveis possíveis de gravidade são:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -{% endif %} - -## Escolhendo suas configurações de notificação - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications-v2.manage-notifications %} -3. Na página de configurações de notificações, escolha como receber notificações quando: - - Há atualizações em repositórios ou discussões de equipe que você está inspecionando ou em uma conversa na qual você está participando. Para obter mais informações, consulte "[Sobre notificações de participação e inspeção](#about-participating-and-watching-notifications)". - - Você obtém acesso a um novo repositório ou se juntou a uma nova equipe. Para obter mais informações, consulte "[Inspeção automática](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} - - Há novos {% if page.version == 'dotcom' %} {% data variables.product.prodname_dependabot_alerts %} {% else %} alertas de segurança {% endif %} em seu repositório. Para obter mais informações, consulte "[{% data variables.product.prodname_dependabot_alerts %} opções de notificação](#dependabot-alerts-notification-options)". {% endif %} {% ifversion fpt or ghec %} - - Há atualizações de fluxo de trabalho nos repositórios configurados com o {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %} opções de notificação](#github-actions-notification-options)".{% endif %} - -## Inspeção automática - -Por padrão, sempre que você obtiver acesso a um novo repositório, você começará a inspecionar aquele repositório automaticamente. Sempre que você entrar em uma nova equipe, você será automaticamente inscrito em atualizações e receberá notificações quando essa equipe for @mencionada. Se você não quiser ser automaticamente inscrito, você pode desmarcar as opções de inspeção automática. - - ![Opções de inspeção automática](/assets/images/help/notifications-v2/automatic-watching-options.png) - -Se "Inspecionar repositórios automaticamente" estiver desativado, então você não inspecionará automaticamente seus próprios repositórios. É necessário navegar na página do seu repositório e escolher a opção de inspeção. - -## Configurando as configurações de inspeção para um repositório individual - -É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. Você também pode optar por ser notificado apenas de {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}certos tipos de eventos como {% data reusables.notifications-v2.custom-notification-types %} (se habilitado para o repositório) {% else %}novas versões{% endif %}, ou ignorar completamente um repositório individual. - -{% data reusables.repositories.navigate-to-repo %} -2. No canto superior direito, selecione o menu suspenso "Inspecionar" para clicar em uma opção de inspecionar. -{% ifversion fpt or ghes > 3.0 or ghae-issue-4910 or ghec %} - ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options-custom.png) - - A opção **Personalizar** permite que você personalize ainda mais as notificações para que você seja notificado apenas quando eventos específicos ocorrerem no repositório, além de participar e @mentions. -{% else %} - ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-issue-4910 or ghec %} - ![Opções de inspeção personalizadas em um menu suspenso para um repositório](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) Se você selecionar "Problemas", você será notificado e irá inscrever-se para receber atualizações sobre cada problema (incluindo aqueles que existiam antes de você selecionar esta opção) no repositório. Se você for @mentioned em um pull request neste repositório, você receberá notificações sobre isso também e será inscrito em atualizações desse pull request específico, além de ser notificado sobre problemas. -{% endif %} - -## Escolhendo para onde as notificações de e-mail da sua organização são enviadas - -Se pertencer a uma organização, você poderá escolher a conta de e-mail em que deseja receber as notificações da atividade da organização. Por exemplo, se pertencer a uma organização para fins de trabalho, talvez você queira receber as notificações no seu endereço de e-mail profissional, e não no endereço pessoal. - -{% data reusables.notifications-v2.email-notification-caveats %} - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications-v2.manage-notifications %} -3. Em "Default notification email" (E-mail padrão de notificação), selecione o endereço de e-mail em que você quer receber as notificações. - ![Menu suspenso de endereço de e-mail padrão de notificação](/assets/images/help/notifications/notifications_primary_email_for_orgs.png) -4. Clique em **Salvar**. - -### Personalizar rotas de e-mail por organização - -Se você for integrante de mais de uma organização, você poderá configurar cada uma para enviar notificações para qualquer um dos{% ifversion fpt or ghec %} seus endereços de e-mail verificados{% else %} os endereços de e-mail para a sua conta{% endif %}. {% ifversion fpt or ghec %} Para obter mais informações, consulte "[Verificando seu endereço de e-mail](/articles/verifying-your-email-address)."{% endif %} - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications-v2.manage-notifications %} -3. Na lista em "Custom routing" (Encaminhamento personalizado), localize o nome da sua organização. - ![Lista de organizações e endereços de e-mail](/assets/images/help/notifications/notifications_org_emails.png) -4. Clique em **Edit** (Editar) ao lado do endereço de e-mail que você pretende alterar. ![Editar endereços de e-mail da organização](/assets/images/help/notifications/notifications_edit_org_emails.png) -5. Selecione um dos seus endereços de e-mail verificados e clique em **Save** (Salvar). - ![Alterar o endereço de e-mail por organização](/assets/images/help/notifications/notifications_switching_org_email.gif) - -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -## Opções de notificação {% data variables.product.prodname_dependabot_alerts %} - -{% data reusables.notifications.vulnerable-dependency-notification-enable %} -{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} -{% data reusables.notifications.vulnerable-dependency-notification-options %} - -Para mais informações sobre os métodos de entrega de notificação disponíveis para você e aconselhamento sobre como otimizar as notificações para {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". -{% endif %} - -{% ifversion fpt or ghes or ghec %} -## Opções de notificação {% data variables.product.prodname_actions %} - -Escolha como você deseja receber atualizações de execução de fluxo de trabalho para repositórios que você está inspecionando que estão configurados com o {% data variables.product.prodname_actions %}. Você também pode optar por receber apenas notificações de execução de fluxo de trabalho falha. - - ![Opções de notificação para {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png) - -{% endif %} - -{% ifversion fpt or ghes or ghec %} -## Gerenciar as suas configurações de notificação com {% data variables.product.prodname_mobile %} - -Quando você instalar {% data variables.product.prodname_mobile %}, você será automaticamente incluído em notificações da web. No aplicativo, você pode habilitar notificações push para os seguintes eventos. -- Menções diretas -- Atribuições para problemas ou pull requests -- Solicitações para revisar um pull request -- Solicitações para aprovação de implantação - -Você também pode agendar quando {% data variables.product.prodname_mobile %} enviará notificações por push para o seu dispositivo móvel. - -{% data reusables.mobile.push-notifications-on-ghes %} - -### Gerenciar as suas configurações de notificação com {% data variables.product.prodname_ios %} - -1. No menu inferior, toque em **Perfil**. -2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. -3. Para atualizar as suas configurações de notificação, toque em **Notificações** e, em seguida, use os atalhos para habilitar ou desabilitar os seus tipos preferidos de notificações de push. -4. Opcionalmente, para agendar quando {% data variables.product.prodname_mobile %} enviará notificações de push para seu dispositivo móvel, toque em **Horas de Trabalho**, use o **horário de trabalho personalizado** e, em seguida, escolha quando você gostaria de receber notificações de push. - -### Gerenciar as suas configurações de notificação com {% data variables.product.prodname_android %} - -1. No menu inferior, toque em **Perfil**. -2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. -3. Para atualizar suas configurações de notificação, toque em **Configurar notificações** e, em seguida, use os atalhos para habilitar ou desabilitar seus tipos preferidos de notificações push. -4. Opcionalmente, para agendar quando {% data variables.product.prodname_mobile %} enviará notificações de push para seu dispositivo móvel, toque em **Horas de Trabalho**, use o **horário de trabalho personalizado** e, em seguida, escolha quando você gostaria de receber notificações de push. - -## Configurar as configurações de inspeção para um repositório individual com {% data variables.product.prodname_mobile %} - -É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. Você também pode optar por receber notificações apenas sobre {% ifversion fpt or ghec %}certos tipos de eventos como problemas, pull requests, discussões (se habilitado para o repositório) e {% endif %}novas versões, ou ignorar completamente um repositório individual. - -1. No {% data variables.product.prodname_mobile %}, navegue até a página principal do repositório. -2. Toque em **Inspecionar**. ![O botão de inspecionar em {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png) -3. Para escolher para quais atividades você recebe notificações, toque nas suas configurações de inspeção preferenciais. ![Manu suspenso de configurações de inspeção em {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png) - -{% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index 23650fb09e..6ba64d8d33 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -1,6 +1,6 @@ --- -title: Gerenciar configurações de conta de usuário -intro: 'Você pode alterar várias configurações de sua conta pessoal, inclusive alterar seu nome de usuário e excluir sua conta.' +title: Managing user account settings +intro: 'You can change several settings for your personal account, including changing your username and deleting your account.' redirect_from: - /categories/29/articles/ - /categories/user-accounts/ @@ -23,12 +23,13 @@ children: - /deleting-your-user-account - /permission-levels-for-a-user-account-repository - /permission-levels-for-user-owned-project-boards + - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - /managing-security-and-analysis-settings-for-your-user-account - /managing-access-to-your-user-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do -shortTitle: Configurações de conta de usuário +shortTitle: User account settings --- diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index c00dfed926..ff77342e3d 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -1,6 +1,6 @@ --- -title: Gerenciar as configurações de temas -intro: 'Você pode gerenciar como {% data variables.product.product_name %} se parece com você definindo uma preferência de tema que segue as configurações do seu sistema ou sempre usa um modo claro ou escuro.' +title: Managing your theme settings +intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.' versions: fpt: '*' ghae: next @@ -11,51 +11,51 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings -shortTitle: Gerenciar configurações de tema +shortTitle: Manage theme settings --- -Por escolha e flexibilidade sobre como e quando você usa {% data variables.product.product_name %}, você pode configurar configurações de tema para mudar como {% data variables.product.product_name %} fica para você. Você pode escolher entre temas claros e escuros ou você pode configurar {% data variables.product.product_name %} para seguir as configurações do seu sistema. +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. -Você pode querer usar um tema escuro para reduzir o consumo de energia em certos dispositivos, reduzir o cansaço da vista em condições com pouca luz, ou porque você prefere o tema. +You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}Se você tiver baixa visão, você poderá aproveitar um tema de alto contraste, com maior contraste entre o primeiro plano e os elementos de segundo plano.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} se você for daltônico, você poderá beneficiar-se dos nossos temas de cor clara e escura. +{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. {% note %} -**Observação:** Os temas coloridos estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)". +**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} {% endif %} {% data reusables.user_settings.access_settings %} -1. Na barra lateral de configurações do usuário, clique em **Aparência**. +1. In the user settings sidebar, click **Appearance**. - ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png) + !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) -1. Em "Modo do tema", selecione o menu suspenso e clique em uma preferência de tema. +1. Under "Theme mode", select the drop-down menu, then click a theme preference. - ![Menu suspenso em "Modo tema" para seleção de preferência de tema](/assets/images/help/settings/theme-mode-drop-down-menu.png) -1. Clique no tema que deseja usar. - - Se você escolheu um único tema, clique em um tema. + ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png) +1. Click the theme you'd like to use. + - If you chose a single theme, click a theme. {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - - Se você escolheu seguir as configurações do sistema, clique em um tema diurno e um tema noturno. + - If you chose to follow your system settings, click a day theme and a night theme. {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghae-issue-4619 or ghec %} - - Se você quiser escolher um tema que esteja atualmente em beta público, primeiro você deverá habilitá-lo com pré-visualização de recursos. Para obter mais informações, consulte "[Explorar versões de acesso antecipado com visualização de recursos em](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".{% endif %} + - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %} {% if command-palette %} {% note %} -**Observação:** Você também pode alterar as configurações do seu tema com a paleta de comandos. Para obter mais informações, consulte "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)". +**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)". {% endnote %} {% endif %} -## Leia mais +## Further reading -- "[Configurar tema para o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" +- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index c7b0e88faa..603f7c540d 100644 --- a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -1,7 +1,7 @@ --- -title: Memorizar dependências para acelerar os fluxos de trabalho -shortTitle: Memorizar dependências -intro: 'Para agilizar os seus fluxos de trabalho e torná-los mais eficientes, você pode criar e usar caches para dependências e outros arquivos reutilizados geralmente.' +title: Caching dependencies to speed up workflows +shortTitle: Caching dependencies +intro: 'To make your workflows faster and more efficient, you can create and use caches for dependencies and other commonly reused files.' redirect_from: - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows @@ -15,59 +15,82 @@ topics: - Workflows --- -## Sobre a memorização das dependências do fluxo de trabalho +## About caching workflow dependencies -As execuções do fluxo de trabalho geralmente reutilizam as mesmas saídas ou dependências baixadas de uma execução para outra. Por exemplo, as ferramentas de gerenciamento de pacotes e de dependência, como, por exemplo, Maven, Gradle, npm e Yarn mantêm uma cache local de dependências baixadas. +Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies. -Os trabalhos nos executores hospedados em {% data variables.product.prodname_dotcom %} começam em um ambiente virtual limpo e devem baixar as dependências todas as vezes, o que gera uma maior utilização da rede, maior tempo de execução e aumento dos custos. Para ajudar a acelerar o tempo que leva para recrear esses arquivos, {% data variables.product.prodname_dotcom %} pode memorizar as dependências que você usa frequentemente nos fluxos de trabalho. +Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. To help speed up the time it takes to recreate these files, {% data variables.product.prodname_dotcom %} can cache dependencies you frequently use in workflows. -Para memorizar as dependências para um trabalho, você precisará usar a ação `cache` do {% data variables.product.prodname_dotcom %}. A ação recupera uma cache identificada por uma chave única. Para obter mais informações, consulte [`ações/cache`](https://github.com/actions/cache). +To cache dependencies for a job, you'll need to use {% data variables.product.prodname_dotcom %}'s `cache` action. The action retrieves a cache identified by a unique key. For more information, see [`actions/cache`](https://github.com/actions/cache). -Se você estiver armazenando gems do Ruby, disso considere usar a ação mantida pelo Ruby, que pode armazenar em cache as instalações do pacote na iniciação. Para obter mais informações, consulte [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically). +If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use. -Para armazenar em cache e restaurar as dependências do npm, Yarn ou pnpm, você pode usar a ação [`actions/setup-node`](https://github.com/actions/setup-node). - -O cache do Gradle e Maven está disponível com a ação [`actions/setup-java`](https://github.com/actions/setup-java). + + + + + + + + + + + + + + + + + + + + + + + + + +
    Package managerssetup-* action for caching
    npm, yarn, pnpmsetup-node
    pip, pipenvsetup-python
    gradle, mavensetup-java
    ruby gemssetup-ruby
    {% warning %} -**Alerta**: Recomendamos que você não armazene nenhuma informação confidencial na cache dos repositórios públicos. Por exemplo, as informações confidenciais podem incluir tokens de acesso ou credenciais de login armazenadas em um arquivo no caminho da cache. Além disso, os programas de interface da linha de comando (CLI) como o `login do Docker` pode salvar as credenciais de acesso em um arquivo de configuração. Qualquer pessoa com acesso de leitura pode criar um pull request em um repositório e acessar o conteúdo da cache. As bifurcações de um repositório também podem criar pull requests no branch-base e acessar as caches no branch-base. +**Warning**: We recommend that you don't store any sensitive information in the cache of public repositories. For example, sensitive information can include access tokens or login credentials stored in a file in the cache path. Also, command line interface (CLI) programs like `docker login` can save access credentials in a configuration file. Anyone with read access can create a pull request on a repository and access the contents of the cache. Forks of a repository can also create pull requests on the base branch and access caches on the base branch. {% endwarning %} -## Comparando artefatos e memorização de dependência +## Comparing artifacts and dependency caching -Os artefatos são similares, pois fornecem a habilidade de armazenar arquivos em {% data variables.product.prodname_dotcom %}, mas cada recurso oferece usos diferentes e não podem ser usados de forma intercambiável. +Artifacts and caching are similar because they provide the ability to store files on {% data variables.product.prodname_dotcom %}, but each feature offers different use cases and cannot be used interchangeably. -- Use a memorização quando desejar reutilizar os arquivos que não mudam com frequência entre trabalhos ou execuções de fluxos de trabalho. -- Use artefatos quando desejar salvar arquivos produzidos por um trabalho a ser visualizado após a conclusão de um fluxo de trabalho. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +- Use caching when you want to reuse files that don't change often between jobs or workflow runs. +- Use artifacts when you want to save files produced by a job to view after a workflow has ended. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." -## Restrições para acessar uma cache +## Restrictions for accessing a cache -Com `v2` da ação da `cache`, você pode acessar a cache nos fluxos de trabalho ativados por qualquer evento que tem um `GITHUB_REF`. Se você estiver usando `v1` da ação da `cache`, você só poderá acessar a cache em fluxos de trabalho ativados por eventos de `push` e `pull_request`, exceto para o evento `fechado` de `pull_request`. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". +With `v2` of the `cache` action, you can access the cache in workflows triggered by any event that has a `GITHUB_REF`. If you are using `v1` of the `cache` action, you can only access the cache in workflows triggered by `push` and `pull_request` events, except for the `pull_request` `closed` event. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." -Um fluxo de trabalho pode acessar e restaurar um cache criado no branch atual, no branch de base (incluindo branches base de repositórios bifurcados) ou no branch-padrão (geralmente `principal`). Por exemplo, um cache criado no branch-padrão pode ser acessado a partir de qualquer pull request. Além disso, se o branch `feature-b` tiver o branch de base `feature-a`, um fluxo de trabalho acionado em `feature-b` teria acesso a caches criados no branch-padrão (`principal`), `feature-a` e `feature-b`. +A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`. -As restrições de acesso fornecem o isolamento da cache e a segurança ao criar um limite lógico entre os diferentes branches. Por exemplo, um cache criado para o branch `feature-a` (com a base no `principal`) não seria acessível para um pull request para o branch `feature-b` (com a base no `principal`). +Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-b` (with the base `main`). -Vários fluxos de trabalho dentro de um repositório compartilham entradas de cache. Uma cache criada para um branch de um fluxo de trabalho pode ser acessada e restaurada a partir de outro fluxo de trabalho para o mesmo repositório e branch. +Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch. -## Usar a ação `cache` +## Using the `cache` action -A ação `cache` tentará restaurar uma cache com base na `chave` que você fornecer. Quando a ação encontrar uma cache, ela irá restaurar os arquivos memorizados no `caminho` que você configurar. +The `cache` action will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure. -Se não houver uma correspondência perfeita, a ação criará uma nova entrada da cache se o trabalho for concluído com sucesso. A nova cache usará a `chave` que você forneceu e conterá os arquivos no diretório do `caminho`. +If there is no exact match, the action creates a new cache entry if the job completes successfully. The new cache will use the `key` you provided and contains the files in the `path` directory. -Como alternativa, você pode fornecer uma lista de `chaves de restauração` a serem usadas quando a `chave` não corresponder à cache existente. Uma lista de `chaves de restauração` é importante quando você está tentando restaurar uma cache de outro branch, pois `as chaves de restauração` math-homework.txt - - name: Upload math result for job 1 - uses: actions/upload-artifact@v2 - with: - name: homework - path: math-homework.txt - - job_2: - name: Multiply by 9 - needs: job_1 - runs-on: windows-latest - steps: - - name: Download math result for job 1 - uses: actions/download-artifact@v2 - with: - name: homework - - shell: bash - run: | - value=`cat math-homework.txt` - expr $value \* 9 > math-homework.txt - - name: Upload math result for job 2 - uses: actions/upload-artifact@v2 - with: - name: homework - path: math-homework.txt - - job_3: - name: Display results - needs: job_2 - runs-on: macOS-latest - steps: - - name: Download math result for job 2 - uses: actions/download-artifact@v2 - with: - name: homework - - name: Print the final result - shell: bash - run: | - value=`cat math-homework.txt` - echo The result is $value -``` - -A execução do fluxo de trabalho arquivará quaisquer artefatos gerados por ele. Para obter mais informações sobre o download de artefatos arquivados, consulte "[Fazer download dos artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)". -{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -![Fluxo de trabalho que transmite dados entre trabalhos para executar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) -{% else %} -![Fluxo de trabalho que transmite dados entre trabalhos para executar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) -{% endif %} - -{% ifversion fpt or ghec %} - -## Leia mais - -- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". - -{% endif %} diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index f5b8c32011..0715e07423 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -1,6 +1,6 @@ --- -title: Criar e testar Node.js -intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto Node.js. +title: Building and testing Node.js +intro: You can create a continuous integration (CI) workflow to build and test your Node.js project. redirect_from: - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions - /actions/language-and-framework-guides/using-nodejs-with-github-actions @@ -16,7 +16,7 @@ topics: - CI - Node - JavaScript -shortTitle: Criar & testar Node.js +shortTitle: Build & test Node.js hasExperimentalAlternative: true --- @@ -24,24 +24,24 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Introdução +## Introduction -Este guia mostra como criar um fluxo de trabalho de integração contínua (CI) que cria e testa o código Node.js. Se o seu teste de CI for aprovado, é possível que você deseje publicar seu código ou um pacote. +This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package. -## Pré-requisitos +## Prerequisites -Recomendamos que você tenha um entendimento básico do Node.js, YAML, das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte: +We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see: -- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" -- "[Começar com Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)" +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" +- "[Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)" {% data reusables.actions.enterprise-setup-prereq %} -## Introdução com o modelo de workflow do Node.js +## Starting with the Node.js workflow template -O {% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do Node.js que funcionará para a maioria dos projetos Node.js. Esse guia inclui exemplos de npm e Yarn que você pode usar para personalizar o modelo. Para obter mais informações, consulte o [modelo do fluxo de trabalho do Node.js](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml). +{% data variables.product.prodname_dotcom %} provides a Node.js workflow template that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the template. For more information, see the [Node.js workflow template](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml). -Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. O fluxo de trabalho mostrado abaixo pressupõe que o branch padrão para o seu repositório é `principal`. +To get started quickly, add the template to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`. {% raw %} ```yaml{:copy} @@ -76,15 +76,15 @@ jobs: {% data reusables.github-actions.example-github-runner %} -## Especificar a versão do Node.js +## Specifying the Node.js version -A maneira mais fácil de especificar uma versão do Node.js é usar a ação `setup-node` fornecida pelo {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte [`setup-node`](https://github.com/actions/setup-node/). +The easiest way to specify a Node.js version is by using the `setup-node` action provided by {% data variables.product.prodname_dotcom %}. For more information see, [`setup-node`](https://github.com/actions/setup-node/). -A ação `setup-node` considera uma versão do Node.js como uma entrada e configura essa versão no executor. A ação `setup-node` localiza uma versão específica do Node.js da cache das ferramentas em casa executor e adiciona os binários necessários ao `PATH`, que persiste no resto do trabalho. Usar a ação `setup-node` é a forma recomendada de usar o Node.js com {% data variables.product.prodname_actions %}, pois garante um comportamento consistente nos diferentes executores e nas diferentes versões do Node.js. Se você estiver usando um executor auto-hospedado, você deverá instalar o Node.js e adicioná-lo ao `PATH`. +The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`. -O modelo inclui uma estratégia matriz que cria e testa seu código com quatro versões de Node.js: 10.x, 12.x, 14.x e 15.x. O "x" é um caractere curinga que corresponde à última versão menor e à versão do patch disponível para uma versão. Cada versão do Node.js especificada na matriz `node-version` cria uma tarefa que executa as mesmas etapas. +The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps. -Cada trabalho pode acessar o valor definido na matriz `node-version` usando o contexto `matriz`. A ação `setup-node` usa o contexto como entrada de `node-version`. A ação `setup-node` configura cada tarefa com uma versão diferente de Node.js antes de criar e testar o código. Para obter mais informações sobre estratégias e contextos de matriz, consulte "[Sintaxe do Fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" e "[Contextos](/actions/learn-github-actions/contexts)". +Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)." {% raw %} ```yaml{:copy} @@ -101,15 +101,15 @@ steps: ``` {% endraw %} -Como alternativa, você pode criar e fazes testes com versões exatas do Node.js. +Alternatively, you can build and test with exact Node.js versions. ```yaml{:copy} -estratégia: - matriz: +strategy: + matrix: node-version: [8.16.2, 10.17.0] ``` -Você também pode criar e testar usando uma versão única do Node.js. +Or, you can build and test using a single version of Node.js too. {% raw %} ```yaml{:copy} @@ -134,20 +134,20 @@ jobs: ``` {% endraw %} -Se você não especificar uma versão do Node.js, o {% data variables.product.prodname_dotcom %} usará a versão-padrão do Node.js do ambiente. -{% ifversion ghae %} Para obter instruções sobre como ter certeza de que o {% data variables.actions.hosted_runner %} possui o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". -{% else %} Para obter mais informações, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +If you don't specify a Node.js version, {% data variables.product.prodname_dotcom %} uses the environment's default Node.js version. +{% ifversion ghae %} For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." +{% else %} For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} -## Instalar dependências +## Installing dependencies -Executores hospedados em {% data variables.product.prodname_dotcom %} têm gerenciadores de dependências npm e Yarn instalados. Você pode usar o npm e o Yarn para instalar dependências no seu fluxo de trabalho antes de criar e testar seu código. Os executores do Windows e Linux hospedados em {% data variables.product.prodname_dotcom %} também têm o Grunt, Gulp, e Bower instalado. +{% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed. -Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." -### Exemplo de uso do npm +### Example using npm -Este exemplo instala as dependências definidas no arquivo *package.json*. Para obter mais informações, consulte [`instalação do npm`](https://docs.npmjs.com/cli/install). +This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install). ```yaml{:copy} steps: @@ -160,7 +160,7 @@ steps: run: npm install ``` -O uso do `npm ci` instala as versões no arquivo *package-lock.json* ou *npm-shrinkwrap.json* e impede as atualizações do arquivo de bloqueio. Usar `npm ci` geralmente é mais rápido que executar a `instalação do npm`. Para obter mais informações, consulte [`npm ci`](https://docs.npmjs.com/cli/ci.html) e "[Introduzindo `npm` para criações mais rápidas e confiáveis](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)". +Using `npm ci` installs the versions in the *package-lock.json* or *npm-shrinkwrap.json* file and prevents updates to the lock file. Using `npm ci` is generally faster than running `npm install`. For more information, see [`npm ci`](https://docs.npmjs.com/cli/ci.html) and "[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)." {% raw %} ```yaml{:copy} @@ -175,9 +175,9 @@ steps: ``` {% endraw %} -### Exemplo de uso do Yarn +### Example using Yarn -Este exemplo instala as dependências definidas no arquivo *package.json*. Para obter mais informações, consulte [`instalação do yarn`](https://yarnpkg.com/en/docs/cli/install). +This example installs the dependencies defined in the *package.json* file. For more information, see [`yarn install`](https://yarnpkg.com/en/docs/cli/install). ```yaml{:copy} steps: @@ -190,7 +190,7 @@ steps: run: yarn ``` -Como alternativa, você pode aprovar o `--frozen-lockfile` para instalar as versões no arquivo *yarn.lock* e impedir atualizações no arquivo *yarn.lock*. +Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file. ```yaml{:copy} steps: @@ -203,15 +203,15 @@ steps: run: yarn --frozen-lockfile ``` -### Exemplo do uso de um registro privado e de criação o arquivo .npmrc +### Example using a private registry and creating the .npmrc file {% data reusables.github-actions.setup-node-intro %} -Para efetuar a autenticação com seu registro privado, você precisará armazenar seu token de autenticação npm como um segredo. Por exemplo, crie um repositório secreto denominado `NPM_TOKEN`. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." -No exemplo abaixo, o segredo `NPM_TOKEN` armazena o token de autenticação npm. A ação `setup-node` configura o arquivo *.npmrc* para ler o token de autenticação npm a partir da variável de ambiente `NODE_AUTH_TOKEN`. Ao usar a ação `setup-node` para criar um arquivo *.npmrc*, você deverá definir a variável de ambiente `NODE_AUTH_TOKEN` com o segredo que contém seu token de autenticação npm. +In the example below, the secret `NPM_TOKEN` stores the npm authentication token. The `setup-node` action configures the *.npmrc* file to read the npm authentication token from the `NODE_AUTH_TOKEN` environment variable. When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token. -Antes de instalar as dependências, use a ação `setup-node` para criar o arquivo *.npmrc* file. A ação tem dois parâmetros de entrada. O parâmetro `node-version` define a versão do Node.js e o parâmetro `registry-url` define o registro-padrão. Se o registro do seu pacote usar escopos, você deverá usar o parâmetro `escopo`. Para obter mais informações, consulte [`npm-scope`](https://docs.npmjs.com/misc/scope). +Before installing dependencies, use the `setup-node` action to create the *.npmrc* file. The action has two input parameters. The `node-version` parameter sets the Node.js version, and the `registry-url` parameter sets the default registry. If your package registry uses scopes, you must use the `scope` parameter. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope). {% raw %} ```yaml{:copy} @@ -231,7 +231,7 @@ steps: ``` {% endraw %} -O exemplo acima cria um arquivo *.npmrc* com o conteúdo a seguir: +The example above creates an *.npmrc* file with the following contents: ```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @@ -239,11 +239,11 @@ O exemplo acima cria um arquivo *.npmrc* com o conteúdo a seguir: always-auth=true ``` -### Exemplo de memorização de dependências +### Example caching dependencies -Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você pode armazenar em cache e restaurar as dependências usando a ação [`setup-node`](https://github.com/actions/setup-node). +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node). -O exemplo a seguir armazena dependências do npm. +The following example caches dependencies for npm. ```yaml{:copy} steps: - uses: actions/checkout@v2 @@ -255,7 +255,7 @@ steps: - run: npm test ``` -O exemplo a seguir armazena dependências para o Yarn. +The following example caches dependencies for Yarn. ```yaml{:copy} steps: @@ -268,7 +268,7 @@ steps: - run: yarn test ``` -O exemplo a seguir armazena dependências para pnpm (v6.10+). +The following example caches dependencies for pnpm (v6.10+). ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -288,11 +288,11 @@ steps: - run: pnpm test ``` -Para armazenar dependências de cache, você deve ter um `pacote-lock.json`, `yarn.lock` ou um arquivo `pnpm-lock.yaml` na raiz do repositório. Se você precisar de uma personalização mais flexível, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "Dependências de cache para acelerar fluxos de trabalho". +If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "Caching dependencies to speed up workflows". -## Criar e testar seu código +## Building and testing your code -Você pode usar os mesmos comandos usados localmente para criar e testar seu código. Por exemplo, se você executar `criação da execução do npm` para executar os passos de compilação definidos no seu arquivo *package.json* e o `teste do npm` para executar seu conjunto de testes, você adicionaria esses comandos no seu arquivo de fluxo de trabalho. +You can use the same commands that you use locally to build and test your code. For example, if you run `npm run build` to run build steps defined in your *package.json* file and `npm test` to run your test suite, you would add those commands in your workflow file. ```yaml{:copy} steps: @@ -306,10 +306,10 @@ steps: - run: npm test ``` -## Empacotar dados do fluxo de trabalho como artefatos +## Packaging workflow data as artifacts -Você pode salvar artefatos das suas etapas de criação e teste para serem visualizados após a conclusão de um trabalho. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +You can save artifacts from your build and test steps to view after a job completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." -## Publicar nos registros do pacote +## Publishing to package registries -Você pode configurar o seu fluxo de trabalho para publicar o seu pacote Node.js em um pacote de registro após os seus testes de CI serem aprovados. Para obter mais informações sobre a publicação no npm e em {% data variables.product.prodname_registry %}, consulte "[Publicando pacotes do Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)". +You can configure your workflow to publish your Node.js package to a package registry after your CI tests pass. For more information about publishing to npm and {% data variables.product.prodname_registry %}, see "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)." diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md index 46b8315b9f..9b0b916538 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -1,6 +1,6 @@ --- -title: Criar e testar o Python -intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto Python. +title: Building and testing Python +intro: You can create a continuous integration (CI) workflow to build and test your Python project. redirect_from: - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions - /actions/language-and-framework-guides/using-python-with-github-actions @@ -15,7 +15,7 @@ hidden: true topics: - CI - Python -shortTitle: Criar & testar o Python +shortTitle: Build & test Python hasExperimentalAlternative: true --- @@ -23,30 +23,30 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Introdução +## Introduction -Este guia mostra como criar, testar e publicar um pacote no Python. +This guide shows you how to build, test, and publish a Python package. -{% ifversion ghae %} Para obter instruções sobre como ter certeza de que o {% data variables.actions.hosted_runner %} possui o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". -Os executores hospedados em {% else %} {% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado, que inclui Python e PyPy. Você não precisa instalar nada! Para obter uma lista completa do software atualizado e das versões pré-instaladas do Python e PyPy, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +{% ifversion ghae %} For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." +{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anything! For a full list of up-to-date software and the pre-installed versions of Python and PyPy, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} -## Pré-requisitos +## Prerequisites -Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -Recomendamos que você tenha um entendimento básico do Python, PyPy e pip. Para obter mais informações, consulte: -- [Primeiros passos com o Python](https://www.python.org/about/gettingstarted/) +We recommend that you have a basic understanding of Python, PyPy, and pip. For more information, see: +- [Getting started with Python](https://www.python.org/about/gettingstarted/) - [PyPy](https://pypy.org/) -- [Gerenciador de pacotes do Pip](https://pypi.org/project/pip/) +- [Pip package manager](https://pypi.org/project/pip/) {% data reusables.actions.enterprise-setup-prereq %} -## Introdução com o modelo do fluxo de trabalho do Python +## Starting with the Python workflow template -O {% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do Python que deve funcionar na maioria dos projetos Python. Este guia inclui exemplos que você pode usar para personalizar o modelo. Para obter mais informações, consulte o [modelo de fluxo de trabalho do Python](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml). +{% data variables.product.prodname_dotcom %} provides a Python workflow template that should work for most Python projects. This guide includes examples that you can use to customize the template. For more information, see the [Python workflow template](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml). -Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. +To get started quickly, add the template to the `.github/workflows` directory of your repository. {% raw %} ```yaml{:copy} @@ -85,38 +85,38 @@ jobs: ``` {% endraw %} -## Especificar uma versão do Python +## Specifying a Python version -Para usar uma versão pré-instalada do Python ou do PyPy em um executor hospedado em {% data variables.product.prodname_dotcom %}, use a ação `setup-python`. Esta ação encontra uma versão específica do Python ou do PyPy na cache das ferramenatas em cada executor e adiciona os binários necessários ao `PATH`, que persiste para o restante do trabalho. Se uma versão específica do Python não for pré-instalada na cache de ferramentas, a `setup-python` ação fará o download e irá configurar a versão apropriada do repositório [`python-versions`](https://github.com/actions/python-versions). +To use a pre-installed version of Python or PyPy on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-python` action. This action finds a specific version of Python or PyPy from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. If a specific version of Python is not pre-installed in the tools cache, the `setup-python` action will download and set up the appropriate version from the [`python-versions`](https://github.com/actions/python-versions) repository. -Using the `setup-action` is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. Se você estiver usando um executor auto-hospedado, você deverá instalar Python e adicioná-lo ao `PATH`. Para obter mais informações, consulte a ação [`setup-python`](https://github.com/marketplace/actions/setup-python). +Using the `setup-python` action is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. If you are using a self-hosted runner, you must install Python and add it to `PATH`. For more information, see the [`setup-python` action](https://github.com/marketplace/actions/setup-python). -A tabela abaixo descreve os locais para o armazenamento de ferramentas em cada executor hospedado em {% data variables.product.prodname_dotcom %}. +The table below describes the locations for the tools cache in each {% data variables.product.prodname_dotcom %}-hosted runner. -| | Ubuntu | Mac | Windows | -| ------------------------------------ | ------------------------------- | ---------------------------------------- | ------------------------------------------ | -| **Diretório da cache da ferramenta** | `/opt/hostedtoolcache/*` | `/Users/runner/hostedtoolcache/*` | `C:\hostedtoolcache\windows\*` | -| **Cache da ferramenta do Python** | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\*` | -| **Cache da ferramenta do PyPy** | `/opt/hostedtoolcache/PyPy/*` | `/Users/runner/hostedtoolcache/PyPy/*` | `C:\hostedtoolcache\windows\PyPy\*` | +|| Ubuntu | Mac | Windows | +|------|-------|------|----------| +|**Tool Cache Directory** |`/opt/hostedtoolcache/*`|`/Users/runner/hostedtoolcache/*`|`C:\hostedtoolcache\windows\*`| +|**Python Tool Cache**|`/opt/hostedtoolcache/Python/*`|`/Users/runner/hostedtoolcache/Python/*`|`C:\hostedtoolcache\windows\Python\*`| +|**PyPy Tool Cache**|`/opt/hostedtoolcache/PyPy/*`|`/Users/runner/hostedtoolcache/PyPy/*`|`C:\hostedtoolcache\windows\PyPy\*`| -Se você estiver usando um executor auto-hospedado, você poderá configurá-lo para usar a ação `setup-python` para gerenciar suas dependências. Para obter mais informações, consulte [usando o setup-python com um executor auto-hospedado](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) na README do `setup-python`. +If you are using a self-hosted runner, you can configure the runner to use the `setup-python` action to manage your dependencies. For more information, see [using setup-python with a self-hosted runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in the `setup-python` README. -O {% data variables.product.prodname_dotcom %} é compatível com a sintaxe semântica de versionamento. Para obter mais informações, consulte "[Usar o versionamento semântico](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" e "[Especificação do versionamento semântico](https://semver.org/)". +{% data variables.product.prodname_dotcom %} supports semantic versioning syntax. For more information, see "[Using semantic versioning](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" and the "[Semantic versioning specification](https://semver.org/)." -### Usar várias versões do Python +### Using multiple Python versions {% raw %} ```yaml{:copy} -nome: Pacote Python +name: Python package -em: [push] +on: [push] -trabalhos: - criar: +jobs: + build: runs-on: ubuntu-latest - estratégia: - # Você pode usar as versões do PyPy em python-version. + strategy: + # You can use PyPy versions in python-version. # For example, pypy2 and pypy3 matrix: python-version: ["2.7", "3.6", "3.7", "3.8", "3.9"] @@ -133,9 +133,9 @@ trabalhos: ``` {% endraw %} -### Usar uma versão específica do Python +### Using a specific Python version -Você pode configurar uma versão específica do python. Por exemplo, 3,8. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. Este exemplo usa a última versão secundária do Python 3. +You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. {% raw %} ```yaml{:copy} @@ -163,11 +163,11 @@ jobs: ``` {% endraw %} -### Excluir uma versão +### Excluding a version -Se especificar uma versão do Python que estiver indisponível, `setup-python` ocorrerá uma falha com um erro como: `##[error]Version 3.4 with arch x64 not found`. A mensagem de erro inclui as versões disponíveis. +If you specify a version of Python that is not available, `setup-python` fails with an error such as: `##[error]Version 3.4 with arch x64 not found`. The error message includes the available versions. -Também é possível usar a palavra-chave `excluir` no seu fluxo de trabalho se houver uma configuração do Python que você não deseja executar. Para obter mais informações, consulte a sintaxe "[ para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)." +You can also use the `exclude` keyword in your workflow if there is a configuration of Python that you do not wish to run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)." {% raw %} ```yaml{:copy} @@ -191,134 +191,120 @@ jobs: ``` {% endraw %} -### Usar a versão padrão do Python +### Using the default Python version -Recomendamos usar `setup-python` para configurar a versão do Python usada nos seus fluxos de trabalho, porque isso ajuda a deixar as suas dependências explícitas. Se você não usar `setup-python`, a versão padrão do Python definida em `PATH` será usada em qualquer shell quando você chamar `python`. A versão-padrão do Python varia entre executores hospedados no {% data variables.product.prodname_dotcom %}, o que pode causar mudanças inesperadas ou usar uma versão mais antiga do que o esperado. +We recommend using `setup-python` to configure the version of Python used in your workflows because it helps make your dependencies explicit. If you don't use `setup-python`, the default version of Python set in `PATH` is used in any shell when you call `python`. The default version of Python varies between {% data variables.product.prodname_dotcom %}-hosted runners, which may cause unexpected changes or use an older version than expected. -| Executor hospedado em{% data variables.product.prodname_dotcom %} | Descrição | -| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Ubuntu | Os executores do Ubuntu têm várias versões do sistema do Python instaladas em `/usr/bin/python` e `/usr/bin/python3`. As versões do Python que vêm empacotadas com o Ubuntu são adicionais às versões que o {% data variables.product.prodname_dotcom %} instala na cache das ferramentas. | -| Windows | Excluindo as versões do Python que estão na cache de ferramentas, o Windows não é compatível com uma versão equivalente do sistema do Python. Para manter um comportamento consistente com outros executores e permitir que o Python seja usado de forma inovadora sem a ação `setup-python` , {% data variables.product.prodname_dotcom %} adiciona algumas versões da cache das ferramentas ao `PATH`. | -| macOS | Os executores do macOS têm mais de uma versão do sistema do Python instalada, além das versões que fazem parte da cache de ferramentas. As versões do sistema do Python estão localizadas no diretório `/usr/local/Cellar/python/*`. | +| {% data variables.product.prodname_dotcom %}-hosted runner | Description | +|----|----| +| Ubuntu | Ubuntu runners have multiple versions of system Python installed under `/usr/bin/python` and `/usr/bin/python3`. The Python versions that come packaged with Ubuntu are in addition to the versions that {% data variables.product.prodname_dotcom %} installs in the tools cache. | +| Windows | Excluding the versions of Python that are in the tools cache, Windows does not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the `setup-python` action, {% data variables.product.prodname_dotcom %} adds a few versions from the tools cache to `PATH`.| +| macOS | The macOS runners have more than one version of system Python installed, in addition to the versions that are part of the tools cache. The system Python versions are located in the `/usr/local/Cellar/python/*` directory. | -## Instalar dependências +## Installing dependencies -Os executores hospedados em {% data variables.product.prodname_dotcom %} têm instalado o gerenciador do pacote pip. Você pode usar o pip para instalar dependências do registro de pacotes do PyPI antes de criar e testar o seu código. Por exemplo, o YAML abaixo instala ou atualiza o instalador de pacotes `pip` e as os pacotes `setuptools` e `wheel`. +{% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages. -Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "Caching dependencies to speed up workflows." {% raw %} ```yaml{:copy} -etapas: -- usa: actions/checkout@v2 -- nome: Configurar Python - usa: actions/setup-python@v2 - com: +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: python-version: '3.x' -- Nome: Instalar dependências - executar: python -m pip install --upgrade pip setuptools wheel +- name: Install dependencies + run: python -m pip install --upgrade pip setuptools wheel ``` {% endraw %} -### Arquivo de requisitos +### Requirements file -Depois de atualizar o `pip`, um o próximo passo típico é instalar as dependências de *requirements.txt*. Para obter mais informações, consulte [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file). +After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file). {% raw %} ```yaml{:copy} -etapas: -- usa: actions/checkout@v2 -- nome: Configurar Python - usa: actions/setup-python@v2 - com: +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: python-version: '3.x' -- nome: Instalar dependências - executar: | +- name: Install dependencies + run: | python -m pip install --upgrade pip pip install -r requirements.txt ``` {% endraw %} -### Memorizar dependências +### Caching Dependencies -Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache dependências usando uma chave única e restaurar as dependências quando você executar fluxos de trabalho futuros usando a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python). -O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu abaixo, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip). +The following example caches dependencies for pip. -{% raw %} ```yaml{:copy} -etapas: -- usa: actions/checkout@v2 -- nome: Setup Python - usa: actions/setup-python@v2 - com: - python-version: '3.x' -- nome: Cache pip - usa: actions/cache@v2 - com: - # Este caminho é específico para o Ubuntu - caminho: ~/.cache/pip - # Observe se há uma correspondência da cache para o arquivo de requisitos correspondente - chave: ${{ runner.os }}-pip-${{ hashFiles('requirements.txt') }} - restore-keys: | - ${{ runner.os }}-pip- - ${{ runner.os }}- -- nome: Instalar dependências - executar: pip install -r requirements.txt +steps: +- uses: actions/checkout@v2 +- uses: actions/setup-python@v2 + with: + python-version: '3.9' + cache: 'pip' +- run: pip install -r requirements.txt +- run: pip test ``` -{% endraw %} -{% note %} +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "Caching packages dependencies" in the `setup-python` actions README. -**Observação:** Dependendo do número de dependências, pode ser mais rápido para usar o armazenamento de dependências. Os projetos com muitas dependências grandes devem ver um aumento no desempenho conforme reduz o tempo necessário para fazer o download. Os projetos com menos dependências podem não ver um aumento significativo no desempenho e até mesmo ver um ligeiro diminuir devido à forma como o pip instala dependências armazenadas em cache. O desempenho varia de projeto para projeto. +If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository. -{% endnote %} +## Testing your code -## Testar seu código +You can use the same commands that you use locally to build and test your code. -Você pode usar os mesmos comandos usados localmente para criar e testar seu código. +### Testing with pytest and pytest-cov -### Testar com pytest e pytest-cov - -Este exemplo instala ou atualiza `pytest` e `pytest-cov`. Em seguida, os testes são executados e retornados no formato JUnit enquanto os resultados da cobertura do código são emitidos em Cobertura. Para obter mais informações, consulte [JUnit](https://junit.org/junit5/) e [Cobertura](https://cobertura.github.io/cobertura/). +This example installs or upgrades `pytest` and `pytest-cov`. Tests are then run and output in JUnit format while code coverage results are output in Cobertura. For more information, see [JUnit](https://junit.org/junit5/) and [Cobertura](https://cobertura.github.io/cobertura/). {% raw %} ```yaml{:copy} -etapas: -- usa: actions/checkout@v2 -- nome: Set up Python - usa: actions/setup-python@v2 - com: +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: python-version: '3.x' -- nome: Instalar dependências - executar: | +- name: Install dependencies + run: | python -m pip install --upgrade pip pip install -r requirements.txt -- Nome: Testar com pytest - executar: | +- name: Test with pytest + run: | pip install pytest pip install pytest-cov pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html ``` {% endraw %} -### UsarFlake8 para código lint +### Using Flake8 to lint code -O exemplo a seguir instala ou atualiza o `flake8` e o usa para limpar todos os arquivos. Para obter mais informações, consulte [Flake8](http://flake8.pycqa.org/en/latest/). +The following example installs or upgrades `flake8` and uses it to lint all files. For more information, see [Flake8](http://flake8.pycqa.org/en/latest/). {% raw %} ```yaml{:copy} -etapas: -- usa: actions/checkout@v2 -- nome: Configurar Python - usa: actions/setup-python@v2 - com: +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: python-version: '3.x' -- nome: Instalar dependências - executar: | +- name: Install dependencies + run: | python -m pip install --upgrade pip pip install -r requirements.txt -- nome: Lint with flake8 +- name: Lint with flake8 run: | pip install flake8 flake8 . @@ -326,11 +312,11 @@ etapas: ``` {% endraw %} -O passo de limpeza de código foi configurado com `continue-on-error: true`. Isto impedirá que o fluxo de trabalho falhe se a etapa de limpeza de código não for bem-sucedida. Após corrigir todos os erros de limpeza de código, você poderá remover essa opção para que o fluxo de trabalho capture novos problemas. +The linting step has `continue-on-error: true` set. This will keep the workflow from failing if the linting step doesn't succeed. Once you've addressed all of the linting errors, you can remove this option so the workflow will catch new issues. -### Executar testes com tox +### Running tests with tox -Com {% data variables.product.prodname_actions %}, você pode executar testes com tox e distribuir o trabalho para vários trabalhos. Você precisará invocar tox usando a opção `-e py` para escolher a versão do Python no seu `PATH`, em vez de especificar uma versão específica. Para obter mais informações, consulte [tox](https://tox.readthedocs.io/en/latest/). +With {% data variables.product.prodname_actions %}, you can run tests with tox and spread the work across multiple jobs. You'll need to invoke tox using the `-e py` option to choose the version of Python in your `PATH`, rather than specifying a specific version. For more information, see [tox](https://tox.readthedocs.io/en/latest/). {% raw %} ```yaml{:copy} @@ -360,11 +346,11 @@ jobs: ``` {% endraw %} -## Empacotar dados do fluxo de trabalho como artefatos +## Packaging workflow data as artifacts -Você pode fazer o upload de artefatos para visualização após a conclusão de um fluxo de trabalho. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". +You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." -O exemplo a seguir demonstra como você pode usar a ação `upload-artefact` para arquivar os resultados de teste da execução do `pytest`. Para obter mais informações, consulte a ação <[`upload-artifact`](https://github.com/actions/upload-artifact). +The following example demonstrates how you can use the `upload-artifact` action to archive test results from running `pytest`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact). {% raw %} ```yaml{:copy} @@ -403,11 +389,11 @@ jobs: ``` {% endraw %} -## Publicar nos registros do pacote +## Publishing to package registries -Você pode configurar seu fluxo de trabalho para publicar seu pacote do Python em um pacote de registro assim que seu CI teste passar. Esta seção demonstra como você pode usar {% data variables.product.prodname_actions %} para fazer o upload do seu pacote para o PyPI toda vez que [publicar uma versão](/github/administering-a-repository/managing-releases-in-a-repository). +You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository). -Para este exemplo, você deverá criar dois [tokens da API do PyPI](https://pypi.org/help/#apitoken). Você pode usar segredos para armazenar os tokens de acesso ou credenciais necessárias para publicar o seu pacote. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -440,4 +426,4 @@ jobs: password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %} ``` -Para obter mais informações sobre o fluxo de trabalho do modelo, consulte [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml). +For more information about the template workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml). diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md index 189d575fa5..660ebfdd95 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md @@ -1,6 +1,6 @@ --- -title: Criar uma ação JavaScript -intro: 'Neste guia, você aprenderá como criar uma ação JavaScript usando o conjunto de ferramentas de ações.' +title: Creating a JavaScript action +intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.' redirect_from: - /articles/creating-a-javascript-action - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action @@ -15,100 +15,100 @@ type: tutorial topics: - Action development - JavaScript -shortTitle: Ação do JavaScript +shortTitle: JavaScript action --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Introdução +## Introduction -Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação JavaScript empacotada. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Olá, mundo" nos registros ou "Olá, [who-to-greet]", se você fornecer um nome personalizado. +In this guide, you'll learn about the basic components needed to create and use a packaged JavaScript action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name. -Este guia usa o módulo Node.js do kit de ferramentas {% data variables.product.prodname_actions %} para acelerar o desenvolvimento. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit). +This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.js module to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository. -Ao terminar esse projeto, você entenderá como criar sua própria ação JavaScript e poderá testá-la em um fluxo de trabalho. +Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow. {% data reusables.github-actions.pure-javascript %} {% data reusables.github-actions.context-injection-warning %} -## Pré-requisitos +## Prerequisites -Antes de começar, você deverá fazer o download do Node.js e criar um repositório público em {% data variables.product.prodname_dotcom %}. +Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository. -1. Baixe e instale o Node.js, que inclui npm. +1. Download and install Node.js 12.x, which includes npm. https://nodejs.org/en/download/current/ -1. Crie um novo repositório público em {% data variables.product.product_location %} e chame-o de "hello-world-javascript-action". Para obter mais informações, consulte "[Criar um repositório novo](/articles/creating-a-new-repository)". +1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)." -1. Clone o repositório para seu computador. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)". +1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -1. No seu terminal, mude os diretórios para seu novo repositório. +1. From your terminal, change directories into your new repository. - ```shell + ```shell{:copy} cd hello-world-javascript-action ``` -1. No terminal, inicialize o diretório com npm para gerar um arquivo `package.json`. +1. From your terminal, initialize the directory with npm to generate a `package.json` file. - ```shell + ```shell{:copy} npm init -y ``` -## Criar um arquivo de metadados de ação +## Creating an action metadata file -Crie um novo arquivo denominado `action.yml` no diretório `hello-world-javascript-action` com o código de exemplo a seguir. Para obter mais informações, consulte "[Sintaxe dos metadados para {% data variables.product.prodname_actions %}}](/actions/creating-actions/metadata-syntax-for-github-actions)." +Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)." -```yaml +```yaml{:copy} name: 'Hello World' description: 'Greet someone and record the time' inputs: - who-to-greet: # id da entrada + who-to-greet: # id of input description: 'Who to greet' required: true default: 'World' outputs: - time: # id da saída + time: # id of output description: 'The time we greeted you' runs: using: 'node12' main: 'index.js' ``` -Esse arquivo define a entrada `who-to-greet` e a saída `time`. O arquivo também diz ao executor da ação como começar a executar essa ação JavaScript. +This file defines the `who-to-greet` input and `time` output. It also tells the action runner how to start running this JavaScript action. -## Adicionar pacotes do kit de ferramenta de ações +## Adding actions toolkit packages -O conjunto de ferramentas de ações é uma coleção de pacotes Node.js que permite a rápida criação de ações JavaScript com mais consistência. +The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency. -O pacote do kit de ferramentas [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) fornece uma interface com os comandos do fluxo de trabalho, variáveis de entrada e saída, status de saída e mensagens de depuração. +The toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package provides an interface to the workflow commands, input and output variables, exit statuses, and debug messages. -O conjunto de ferramentas também oferece um pacote [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) que retorna um cliente REST Octokit autenticado e acesso aos contexto do GitHub Actions. +The toolkit also offers a [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) package that returns an authenticated Octokit REST client and access to GitHub Actions contexts. -O conjunto de ferramentas oferece mais do que pacotes `core` and `github`. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit). +The toolkit offers more than the `core` and `github` packages. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository. -No seu terminal, instale os pacotes de conjunto de ferramentas de ações `core` e `github`. +At your terminal, install the actions toolkit `core` and `github` packages. -```shell +```shell{:copy} npm install @actions/core npm install @actions/github ``` -Você pode ver agora um diretório `node_modules` com três módulos recém-instalados e um arquivo `package-lock.json` com as dependências do módulo instalado e as versões de cada módulo instalado. +Now you should see a `node_modules` directory with the modules you just installed and a `package-lock.json` file with the installed module dependencies and the versions of each installed module. -## Gravar um código de ação +## Writing the action code -Esta ação usa o conjunto de ferramentas para obter a variável de entrada obrigatória `who-to-greet` no arquivo de metadados da ação e imprime "Hello [who-to-greet]" em uma mensagem de depuração no log. Na sequência, o script obtém a hora atual e a configura como uma variável de saída que pode ser usada pelas ações executadas posteriormente em um trabalho. +This action uses the toolkit to get the `who-to-greet` input variable required in the action's metadata file and prints "Hello [who-to-greet]" in a debug message in the log. Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. -O GitHub Actions fornece informações de contexto sobre o evento webhook, Git refs, fluxo de trabalho, ação e a pessoa que acionou o fluxo de trabalho. Para acessar as informações de contexto, você pode usar o pacote `github`. A ação que você vai escrever imprimirá a carga do evento webhook no log. +GitHub Actions provide context information about the webhook event, Git refs, workflow, action, and the person who triggered the workflow. To access the context information, you can use the `github` package. The action you'll write will print the webhook event payload to the log. -Adicione um arquivo novo denominado `index.js`, com o seguinte código: +Add a new file called `index.js`, with the following code. {% raw %} -```javascript +```javascript{:copy} const core = require('@actions/core'); const github = require('@actions/github'); @@ -127,31 +127,31 @@ try { ``` {% endraw %} -Se um erro for lançado no exemplo `index.js` acima, `core.setFailed(error.message);` usará o pacote do conjunto de ferramentas de ações [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) para registrar uma mensagem em log e definir um código de saída de falha. Para obter mais informações, consulte "[Definindo os códigos de saída para as ações](/actions/creating-actions/setting-exit-codes-for-actions)". +If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)." -## Criar README +## Creating a README -Para que as pessoas saibam como usar sua ação, você pode criar um arquivo README. Um arquivo README é útil quando você planeja compartilhar publicamente sua ação, mas também é uma ótima maneira de lembrá-lo ou sua equipe sobre como usar a ação. +To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action. -No diretório `hello-world-javascript-action`, crie um arquivo `README.md` que especifica as seguintes informações: +In your `hello-world-javascript-action` directory, create a `README.md` file that specifies the following information: -- Descrição detalhada do que a ação faz; -- Argumentos obrigatórios de entrada e saída; -- Argumentos opcionais de entrada e saída; -- Segredos usados pela ação; -- Variáveis de ambiente usadas pela ação; -- Um exemplo de uso da ação no fluxo de trabalho. +- A detailed description of what the action does. +- Required input and output arguments. +- Optional input and output arguments. +- Secrets the action uses. +- Environment variables the action uses. +- An example of how to use your action in a workflow. ```markdown # Hello world javascript action -Esta ação imprime "Hello World" ou "Hello" + o nome de uma pessoa a ser cumprimentada no log. +This action prints "Hello World" or "Hello" + the name of a person to greet to the log. ## Inputs ## `who-to-greet` -**Required** The name of the person to greet. Padrão `"World"`. +**Required** The name of the person to greet. Default `"World"`. ## Outputs @@ -159,41 +159,46 @@ Esta ação imprime "Hello World" ou "Hello" + o nome de uma pessoa a ser cumpri The time we greeted you. -## Exemplo de uso +## Example usage -usa: ações/hello-world-javascript-action@v1.1 -com: - quem cumprimentar: 'Mona, a Octocat' +uses: actions/hello-world-javascript-action@v1.1 +with: + who-to-greet: 'Mona the Octocat' ``` -## Fazer commit, tag e push da sua ação para o GitHub +## Commit, tag, and push your action to GitHub -O {% data variables.product.product_name %} faz o download de cada ação executada em um fluxo de trabalho durante o tempo de execução e executa-a como um pacote completo do código antes de você poder usar os comandos do fluxo de trabalho como, por exemplo, `executar` para interagir com a máquina executora. Isso significa que você deve incluir quaisquer dependências de pacotes necessárias para executar o código JavaScript. Você precisará verificar os pacotes de conjuntos de ferramentas `core` e `github` no repositório de ação. +{% data variables.product.product_name %} downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like `run` to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit `core` and `github` packages to your action's repository. -No seu terminal, faça commit dos arquivos `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json` e `README.md`. Se você adicionar um arquivo `.gitignore` que lista `node_modules`, será necessário remover essa linha para fazer commit do diretório `node_modules`. +From your terminal, commit your `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json`, and `README.md` files. If you added a `.gitignore` file that lists `node_modules`, you'll need to remove that line to commit the `node_modules` directory. -Adicionar uma tag da versão para versões da sua ação é considerada uma prática recomendada. Para obter mais informações sobre versões da sua ação, consulte "[Sobre ações](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". +It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)." -```shell +```shell{:copy} git add action.yml index.js node_modules/* package.json package-lock.json README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1.1 git push --follow-tags ``` -Verificar seu diretório `node_modules` pode causar problemas. Como alternativa, você pode usar uma ferramenta denominada [`@vercel/ncc`](https://github.com/vercel/ncc) para compilar o seu código e módulos em um arquivo usado para distribuição. +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. -1. Instale o `vercel/ncc` executando este comando no seu terminal. `npm i -g @vercel/ncc` +1. Install `vercel/ncc` by running this command in your terminal. + `npm i -g @vercel/ncc` -1. Compile seu arquivo `index.js`. `ncc build index.js --license licenses.txt` +1. Compile your `index.js` file. + `ncc build index.js --license licenses.txt` - Você verá um novo arquivo `dist/index.js` com seu código e os módulos compilados. Você também verá um arquivo que acompanha `dist/licenses.txt` e contém todas as licenças dos `node_modules` que você está usando. + You'll see a new `dist/index.js` file with your code and the compiled modules. + You will also see an accompanying `dist/licenses.txt` file containing all the licenses of the `node_modules` you are using. -1. Altere a palavra-chave `main` (principal) no arquivo `action.yml` para usar o novo arquivo `dist/index.js`. `main: 'dist/index.js'` +1. Change the `main` keyword in your `action.yml` file to use the new `dist/index.js` file. + `main: 'dist/index.js'` -1. Se você já verificou o diretório `node_modules`, remova-o. `rm -rf node_modules/*` +1. If you already checked in your `node_modules` directory, remove it. + `rm -rf node_modules/*` -1. No seu terminal, faça commit das atualizações para os arquivos `action.yml`, `dist/index.js` e `node_modules`. +1. From your terminal, commit the updates to your `action.yml`, `dist/index.js`, and `node_modules` files. ```shell git add action.yml dist/index.js node_modules/* git commit -m "Use vercel/ncc" @@ -201,20 +206,20 @@ git tag -a -m "My first action release" v1.1 git push --follow-tags ``` -## Testar sua ação em um fluxo de trabalho +## Testing out your action in a workflow -Agora você está pronto para testar sua ação em um fluxo de trabalho. Quando uma ação está em um repositório privado, a ação somente pode ser usada em fluxos de trabalho no mesmo repositório. Ações públicas podem ser usadas por fluxos de trabalho em qualquer repositório. +Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository. {% data reusables.actions.enterprise-marketplace-actions %} -### Exemplo usando uma ação pública +### Example using a public action -Este exemplo demonstra como sua nova ação pública pode ser executada dentro de um repositório externo. +This example demonstrates how your new public action can be run from within an external repository. -Copie o seguinte YAML em um novo arquivo em `.github/workflows/main.yml` e atualize a linha `uses: octocat/hello-world-javascript-action@v1.1` com seu nome de usuário e o nome do repositório público que você criou acima. Você também pode substituir a entrada `who-to-greet` pelo seu nome. +Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name. {% raw %} -```yaml +```yaml{:copy} on: [push] jobs: @@ -233,43 +238,43 @@ jobs: ``` {% endraw %} -Quando este fluxo de trabalho é acionado, o executor fará o download da ação `hello-world-javascript-action` do repositório público e, em seguida, irá executá-la. +When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it. -### Exemplo usando uma ação privada +### Example using a private action -Copie o código do fluxo de trabalho em um arquivo `.github/workflows/main.yml` no repositório da ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. +Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% raw %} **.github/workflows/main.yml** -```yaml -em: [push] +```yaml{:copy} +on: [push] -trabalhos: +jobs: hello_world_job: runs-on: ubuntu-latest - nome: Um trabalho para dizer "Olá" - etapas: - # Para usar a ação privada desse repositório, - # você deve verificar o repositório - - nome: Checkout - usa: actions/checkout@v2 - - nome: Etapa da ação "Olá, mundo" - usa: ./ # Usa uma ação no diretório-raiz - id: olá - com: + name: A job to say hello + steps: + # To use this repository's private action, + # you must check out the repository + - name: Checkout + uses: actions/checkout@v2 + - name: Hello world action step + uses: ./ # Uses an action in the root directory + id: hello + with: who-to-greet: 'Mona the Octocat' - # Usa a saída da etapa `hello` - - nome: Obtém o tempo de saída - executar: echo "O tempo foi ${{ steps.hello.outputs.time }}" + # Use the output from the `hello` step + - name: Get the output time + run: echo "The time was ${{ steps.hello.outputs.time }}" ``` {% endraw %} -No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Em **Trabalhos** ou no gráfico de visualização, clique em **A job to say hello**. {% endif %}Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log. +From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) {% elsif ghes %} -![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run-updated.png) +![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} -![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run.png) +![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png) {% endif %} diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index 5487615b38..af36775458 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -1,11 +1,11 @@ --- -title: Configurando o OpenID Connect no Amazon Web Services -shortTitle: Configurando o OpenID Connect no Amazon Web Services -intro: Use o OpenID Connect dentro de seus fluxos de trabalho para efetuar a autenticação com Amazon Web Services. +title: Configuring OpenID Connect in Amazon Web Services +shortTitle: Configuring OpenID Connect in Amazon Web Services +intro: 'Use OpenID Connect within your workflows to authenticate with Amazon Web Services.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' - ghae: issue-4856 + ghae: 'issue-4856' ghec: '*' type: tutorial topics: @@ -15,30 +15,30 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Visão Geral +## Overview -O OpenID Connect (OIDC) permite que seus fluxos de trabalho de {% data variables.product.prodname_actions %} acessem os recursos na Amazon Web Services (AWS), sem precisar armazenar as credenciais AWS como segredos de {% data variables.product.prodname_dotcom %} de longa duração. +OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. -Este guia explica como configurar o AWS para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada e inclui um exemplo de fluxo de trabalho para o [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) que usa tokens para efetuar a autenticação no AWS e acessar os recursos. +This guide explains how to configure AWS to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) that uses tokens to authenticate to AWS and access resources. -## Pré-requisitos +## Prerequisites {% data reusables.actions.oidc-link-to-intro %} {% data reusables.actions.oidc-security-notice %} -## Adicionando o provedor de identidade ao AWS +## Adding the identity provider to AWS -Para adicionar o provedor OIDC de {% data variables.product.prodname_dotcom %} ao IAM, consulte a [documentação AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). +To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, see the [AWS documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). -- Para a URL do provedor: Use `https://token.actions.githubusercontent.com` -- Para o "público": Use `sts.amazonaws.com` se você estiver usando a [ação oficial](https://github.com/aws-actions/configure-aws-credentials). +- For the provider URL: Use `https://token.actions.githubusercontent.com` +- For the "Audience": Use `sts.amazonaws.com` if you are using the [official action](https://github.com/aws-actions/configure-aws-credentials). -### Configurando a função e a política de confiança +### Configuring the role and trust policy -Para configurar a função e confiar no IAM, consulte a documentação do AWS para ["Assumindo uma função"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) e ["Criando uma função para a identidade web ou federação de conexão do OpenID"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html). +To configure the role and trust in IAM, see the AWS documentation for ["Assuming a Role"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) and ["Creating a role for web identity or OpenID connect federation"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html). -Por padrão, a validação inclui apenas a condição de público (`aud`). Portanto, você deve adicionar manualmente a condição de assunto (`sub`). Edite o relacionamento de confiança para adicionar o campo `sub` às condições de validação. Por exemplo: +By default, the validation only includes the audience (`aud`) condition, so you must manually add a subject (`sub`) condition. Edit the trust relationship to add the `sub` field to the validation conditions. For example: ```json{:copy} "Condition": { @@ -49,29 +49,29 @@ Por padrão, a validação inclui apenas a condição de público (`aud`). Porta } ``` -## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} +## Updating your {% data variables.product.prodname_actions %} workflow -Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alterações no seu YAML: -1. Adicionar configurações de permissões para o token. -2. Use a ação [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) para trocar o token do OIDC (JWT) por um token de acesso na nuvem. +To update your workflows for OIDC, you will need to make two changes to your YAML: +1. Add permissions settings for the token. +2. Use the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) action to exchange the OIDC token (JWT) for a cloud access token. -### Adicionando configurações de permissões +### Adding permissions settings -O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo: +The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example: ```yaml{:copy} permissions: id-token: write ``` -Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho. +You may need to specify additional permissions here, depending on your workflow's requirements. -### Solicitando o token de acesso +### Requesting the access token -A ação `aws-actions/configure-aws-credentials` recebe um JWT do provedor do OIDC {% data variables.product.prodname_dotcom %} e, em seguida, solicita um token de acesso do AWS. Para obter mais informações, consulte a documentação do AWS [](https://github.com/aws-actions/configure-aws-credentials). +The `aws-actions/configure-aws-credentials` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from AWS. For more information, see the AWS [documentation](https://github.com/aws-actions/configure-aws-credentials). -- ``: Adicione o nome do seu bucket S3 aqui. -- ``: Substitua o exemplo pela sua função do AWS. +- ``: Add the name of your S3 bucket here. +- ``: Replace the example with your AWS role. - ``: Add the name of your AWS region here. ```yaml{:copy} diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md index 4254aeb755..80231b121a 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md @@ -1,11 +1,11 @@ --- -title: Configurando o OpenID Connect no Azure -shortTitle: Configurando o OpenID Connect no Azure -intro: Use OpenID Connect dentro dos seus fluxos de trabalho para efetuar a autenticação com o Azure. +title: Configuring OpenID Connect in Azure +shortTitle: Configuring OpenID Connect in Azure +intro: 'Use OpenID Connect within your workflows to authenticate with Azure.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' - ghae: issue-4856 + ghae: 'issue-4856' ghec: '*' type: tutorial topics: @@ -15,86 +15,78 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Visão Geral +## Overview -O OpenID Connect (OIDC) permite aos seus fluxos de trabalho de {% data variables.product.prodname_actions %} acessar recursos no Azure, sem precisar armazenar as credenciais do Azure como segredos de {% data variables.product.prodname_dotcom %} de longa duração. +OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. -Este guia fornece uma visão geral de como configurar o Azure para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada, e inclui um exemplo de fluxo de trabalho para o [`azure/login`](https://github.com/Azure/login) ação que usa tokens para efetuar a autenticação ao Azure e acessar recursos. +This guide gives an overview of how to configure Azure to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`azure/login`](https://github.com/Azure/login) action that uses tokens to authenticate to Azure and access resources. -## Pré-requisitos +## Prerequisites {% data reusables.actions.oidc-link-to-intro %} {% data reusables.actions.oidc-security-notice %} -## Adicionando as credenciais federadas ao Azure +## Adding the Federated Credentials to Azure -Provedor OIDC de {% data variables.product.prodname_dotcom %} funciona com a federação de identidade do Azure. Para uma visão geral, consulte a documentação da Microsoft em "[Federação de identidade da carga](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation)". +{% data variables.product.prodname_dotcom %}'s OIDC provider works with Azure's workload identity federation. For an overview, see Microsoft's documentation at "[Workload identity federation](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation)." -Para configurar o provedor de identidade OIDC no Azure, você deverá definir a configuração a seguir. Para obter instruções sobre como fazer essas alterações, consulte [a documentação do Azure](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure). +To configure the OIDC identity provider in Azure, you will need to perform the following configuration. For instructions on making these changes, refer to [the Azure documentation](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure). -1. Cria um aplicativo Azure Active Directory e um diretor de serviço. -2. Adicione ascredenciais federadas ao aplicativo Azure Active Directory. -3. Crie segredos de {% data variables.product.prodname_dotcom %} para armazenar a configuração do Azure. +1. Create an Azure Active Directory application and a service principal. +2. Add federated credentials for the Azure Active Directory application. +3. Create {% data variables.product.prodname_dotcom %} secrets for storing Azure configuration. -Orientação adicional para a configuração do provedor de identidade: +Additional guidance for configuring the identity provider: -- Para aumentar a segurança, verifique se você revisou ["Configurando a confiança do OIDC com a nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). Por exemplo, consulte ["Configurar o assunto no seu provedor de nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). -- Para a configuração `audiência`, `api://AzureADTokenExchange` é o valor recomendado, mas você também pode especificar outros valores aqui. +- For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). +- For the `audience` setting, `api://AzureADTokenExchange` is the recommended value, but you can also specify other values here. -## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} +## Updating your {% data variables.product.prodname_actions %} workflow -Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alterações no seu YAML: -1. Adicionar configurações de permissões para o token. -2. Use a ação [`azure/login`](https://github.com/Azure/login) para trocar o token OIDC (JWT) para um token de acesso da nuvem. +To update your workflows for OIDC, you will need to make two changes to your YAML: +1. Add permissions settings for the token. +2. Use the [`azure/login`](https://github.com/Azure/login) action to exchange the OIDC token (JWT) for a cloud access token. -### Adicionando configurações de permissões +### Adding permissions settings -O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo: +The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example: ```yaml{:copy} permissions: id-token: write ``` -Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho. +You may need to specify additional permissions here, depending on your workflow's requirements. -### Solicitando o token de acesso +### Requesting the access token -A ação [`azure/login`](https://github.com/Azure/login) recebe um JWT do provedor OIDC {% data variables.product.prodname_dotcom %} e, em seguida, solicita um token de acesso do Azure. Para obter mais informações, consulte a documentação [`azure/login`](https://github.com/Azure/login). +The [`azure/login`](https://github.com/Azure/login) action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from Azure. For more information, see the [`azure/login`](https://github.com/Azure/login) documentation. -O exemplo a seguir troca um token de ID do OIDC com o Azure para receber um token de acesso, que pode, em seguida, ser usado para acessar os recursos da nuvem. +The following example exchanges an OIDC ID token with Azure to receive an access token, which can then be used to access cloud resources. +{% raw %} ```yaml{:copy} -name: Run Azure Login with OpenID Connect +name: Run Azure Login with OIDC on: [push] permissions: id-token: write - + contents: read jobs: build-and-deploy: runs-on: ubuntu-latest steps: - - - name: Installing CLI-beta for OpenID Connect - run: | - cd ../.. - CWD="$(pwd)" - python3 -m venv oidc-venv - . oidc-venv/bin/activate - echo "activated environment" - python3 -m pip install -q --upgrade pip - echo "started installing cli beta" - pip install -q --extra-index-url https://azcliprod.blob.core.windows.net/beta/simple/ azure-cli - echo "***************installed cli beta*******************" - echo "$CWD/oidc-venv/bin" >> $GITHUB_PATH - - - name: 'Az CLI login' - uses: azure/login@v1.4.0 - with: - client-id: {% raw %}${{ secrets.AZURE_CLIENTID }}{% endraw %} - tenant-id: {% raw %}${{ secrets.AZURE_TENANTID }}{% endraw %} - subscription-id: {% raw %}${{ secrets.AZURE_SUBSCRIPTIONID }}{% endraw %} + - name: 'Az CLI login' + uses: azure/login@v1 + with: + client-id: ${{ secrets.AZURE_CLIENT_ID }} + tenant-id: ${{ secrets.AZURE_TENANT_ID }} + subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }} + + - name: 'Run az commands' + run: | + az account show + az group list ``` - + {% endraw %} diff --git a/translations/pt-BR/content/actions/guides.md b/translations/pt-BR/content/actions/guides.md index 4024bde312..7ac00d9b29 100644 --- a/translations/pt-BR/content/actions/guides.md +++ b/translations/pt-BR/content/actions/guides.md @@ -1,6 +1,6 @@ --- -title: Guias para o GitHub Actions -intro: 'Estes guias para {% data variables.product.prodname_actions %} incluem casos de uso específicos e exemplos para ajudar você a configurar fluxos de trabalho.' +title: Guides for GitHub Actions +intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -13,6 +13,7 @@ learningTracks: - continuous_integration - continuous_deployment - deploy_to_the_cloud + - '{% ifversion ghec or ghes or ghae %}adopting_github_actions_for_your_enterprise{% endif %}' - hosting_your_own_runners - create_actions includeGuides: diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md deleted file mode 100644 index 30707afe23..0000000000 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ /dev/null @@ -1,235 +0,0 @@ ---- -title: Sobre executores auto-hospedados -intro: 'Você pode hospedar seus próprios executores e personalizar o ambiente usado para executar trabalhos nos seus fluxos de trabalho do {% data variables.product.prodname_actions %}.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/about-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: overview ---- - -{% data reusables.actions.ae-self-hosted-runners-notice %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} - -## Sobre executores auto-hospedados - -{% data reusables.github-actions.self-hosted-runner-description %} Os executores auto-hospedados podem ser físicos, virtuais, estar em um container, no local ou em uma nuvem. - -Você pode adicionar runners auto-hospedados em vários níveis na hierarquia de gerenciamento: -- Runners em nível de repositório são dedicados a um único repositório. -- Executores no nível da organização podem processar trabalhos para vários repositórios em uma organização. -- Runners de nível empresarial podem ser atribuídos a várias organizações em uma conta corporativa. - -A sua máquina do executor conecta-se ao {% data variables.product.product_name %} usando o aplicativo do executor auto-hospedado de {% data variables.product.prodname_actions %}. {% data reusables.github-actions.runner-app-open-source %} Quando uma nova versão é lançada, o aplicativo do executor atualiza-se automaticamente quando uma tarefa é atribuída ao executor, ou dentro de uma semana após a liberação, caso o executor não tenha recebido nenhum trabalho. - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -Para mais informações sobre instalação e uso de executores auto-hospedados, consulte "[Adicionar executores auto-hospedados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" e "[Usar executores auto-hospedados em um fluxo de trabalho](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." - -## Você pode executar fluxos de trabalho nos executores hospedados em {% data variables.product.prodname_dotcom %} ou em executores auto-hospedados - -Os executores auto-hospedados em {% data variables.product.prodname_dotcom %} oferecem uma maneira mais rápida e simples de executar seus fluxos de trabalho, enquanto os executores auto-hospedados são uma maneira altamente configurável de executar fluxos de trabalho em seu próprio ambiente personalizado. - -**Executores hospedados no {% data variables.product.prodname_dotcom %}:** -- Recebe atualizações automáticas para o sistema operacional, pacotes e ferramentas pré-instalados e o aplicativo do executor auto-hospedado. -- São gerenciados e mantidos por {% data variables.product.prodname_dotcom %}. -- Fornece uma instância limpa para cada execução de trabalho. -- Use minutos grátis no seu plano {% data variables.product.prodname_dotcom %}, com taxas por minuto aplicadas após exceder os minutos grátis. - -**Executores auto-hospedados:** -- Recebem atualizações automáticas apenas para o aplicativo do executor auto-hospedado. Você é responsável por atualizar o sistema operacional e todos os outros softwares. -- Pode usar serviços de nuvem ou máquinas locais pelos quais você já paga. -- É personalizável para seu hardware, sistema operacional, software e requisitos de segurança. -- Não é necessário ter uma instância limpa para a execução de cada trabalho. -- São grátis para usar com {% data variables.product.prodname_actions %}, mas você é responsável pelo custo de manutenção das suas máquinas executoras. - -## Requisitos para executores auto-hospedados - -Você pode usar qualquer máquina como um executor auto-hospedado, desde que ela atenda a estes requisitos: - -* Você pode instalar e executar o aplicativo do executor auto-hospedado na máquina. Para obter mais informações, consulte "[Arquiteturas e sistemas operacionais compatíveis com executores auto-hospedados](#supported-architectures-and-operating-systems-for-self-hosted-runners)". -* A máquina pode comunicar-se com {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Comunicação entre os executores auto-hospedados e {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)". -* A máquina tem recursos de hardware suficientes para o tipo de fluxos de trabalho que você planeja executar. O aplicativo do executor auto-hospedado requer apenas recursos mínimos. -* Se você desejar executar fluxos de trabalho que usam ações do contêiner do Docker ou dos contêineres de serviço, você deverá usar uma máquina Linux e o Docker deve estar instalados. - -{% ifversion fpt or ghes > 3.2 or ghec %} -## Dimensionar automaticamente os seus executores auto-hospedados - -Você pode aumentar ou diminuir automaticamente o número de executores auto-hospedados no seu ambiente em resposta aos eventos que você receber. Para obter mais informações, consulte "[Dimensionamento automático com executores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)". - -{% endif %} - -## Limites de uso - -Existem alguns limites sobre o uso de {% data variables.product.prodname_actions %} ao usar executores auto-hospedados. Estes limites estão sujeitos a mudanças. - -{% data reusables.github-actions.usage-workflow-run-time %} -- **Tempo de fila de tarefas** - Cada trabalho para executores auto-hospedados pode ser enfileirado por um máximo de 24 horas. Se um executor auto-hospedado não começar a executar a tarefa dentro deste limite, a tarefa será encerrada e não será concluída. -{% data reusables.github-actions.usage-api-requests %} -- **Matriz de vagas** - {% data reusables.github-actions.usage-matrix-limits %} -{% data reusables.github-actions.usage-workflow-queue-limits %} - -## Continuidade do fluxo de trabalho para executores auto-hospedados - -{% data reusables.github-actions.runner-workflow-continuity %} - -## Arquiteturas e sistemas operacionais compatíveis com executores auto-hospedados - -Os sistemas operacionais a seguir são compatíveis com o aplicativo de execução auto-hospedado. - -### Linux - -- Red Hat Enterprise Linux 7 ou posterior -- CentOS 7 ou posterior -- Oracle Linux 7 -- Fedora 29 ou versão posterior -- Debian 9 ou versão posterior -- Ubuntu 16.04 ou versão posterior -- Linux Hortelã 18 ou versão posterior -- openSUSE 15 ou versão posterior -- SUSE Enterprise Linux (SLES) 12 SP2 ou versão posterior - -### Windows - -- Windows 7 64-bit -- Windows 8.1 64-bit -- Windows 10 64-bit -- Windows Server 2012 R2 64-bit -- Windows Server 2016 64-bit -- Windows Server 2019 64-bit - -### macOS - -- macOS 10.13 (High Sierra) or versão posterior - -### Arquiteturas - -As seguintes arquiteturas de processador são compatíveis com o aplicativo do executor auto-hospedado. - -- `x64` - Linux, macOS, Windows. -- `ARM64` - Apenas Linux. -- `ARM32` - Apenas Linux. - -{% ifversion ghes %} - -## Comunicação entre executores auto-hospedados e {% data variables.product.prodname_dotcom %} - -Algumas configurações extras podem ser necessárias para usar ações de {% data variables.product.prodname_dotcom_the_website %} com {% data variables.product.prodname_ghe_server %} ou para usar as ações `de configuração/configuração LANGUAGE` com executores auto-hospedados sem acesso à internet. Para obter mais informações, consulte "[Comunicação entre os executores auto-hospedados e {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)". - -{% endif %} - -## Comunicação entre executores auto-hospedados e {% data variables.product.product_name %} - -As enquetes dos executores auto-hospedados {% data variables.product.product_name %} para recuperar atualizações do aplicativo e verificar se algum trabalho está na fila para processamento. O executor auto-hospedado usa uma _enquete longa_ HTTPS que abre uma conexão com {% data variables.product.product_name %} por 50 segundos e, se nenhuma resposta for recebida, o período de espera se encerra a uma nova enquete é criada. O aplicativo deve estar rodando na máquina para aceitar e executar trabalhos do {% data variables.product.prodname_actions %}. - -{% ifversion ghae %} -Você deve garantir que o executor auto-hospedado tenha acesso à rede para comunicar-se com a -URL de {% data variables.product.prodname_ghe_managed %} e seus subdomínios. -Por exemplo, se o o nome da sua instância for `octoghae`, você deverá permitir que o executor auto-hospedado acesse `octoghae.githubenterprise.com`, `api.octoghae.githubenterprise.com` e `codeload.octoghae.githubenterprise.com`. -Se você usa uma lista de endereços IP para a - -conta da sua organização ou empresa de {% data variables.product.prodname_dotcom %}, você deverá adicionar o endereço IP do seu executor auto-hospedado à lista de permissão. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)". -{% endif %} - -{% ifversion fpt or ghec %} - -Como o runner auto-hospedado abre uma conexão em {% data variables.product.prodname_dotcom %}, você não precisa permitir que {% data variables.product.prodname_dotcom %} faça conexões de entrada com seu executor auto-hospedado. - -Você deve garantir que a máquina tenha acesso adequado à rede para comunicar-se com os hosts de {% data variables.product.prodname_dotcom %} listados abaixo. Alguns hosts são necessários para operações essenciais de executores, enquanto outros hosts só são necessários para certas funcionalidades. - -{% note %} - -**Observação:** Alguns dos domínios listados abaixo estão configurados usando os registros `CNAME`. Alguns firewalls podem exigir que você adicione regras recursivamente para todos os registros `CNAME`. Observe que os registros `CNAME` podem mudar no futuro, e que apenas os domínios listados abaixo permanecerão constantes. - -{% endnote %} - -**Necessário para operações essenciais:** - -``` -github.com -api.github.com -``` - -**Necessário para fazer o download das ações:** - -``` -codeload.github.com -``` - -**Necessário para atualizações de versão do executor:** - -``` -objects.githubusercontent.com -objects-origin.githubusercontent.com -github-releases.githubusercontent.com -github-registry-files.githubusercontent.com -``` - -**Necessário para upload/download de caches e artefatos de fluxo de trabalho:** - -``` -*.blob.core.windows.net -``` - -**Necessário para recuperar tokens do OIDC:** - -``` -*.actions.githubusercontent.com -``` - -Além disso, seu fluxo de trabalho pode exigir acesso a outros recursos de rede. Por exemplo, se o seu fluxo de trabalho instala pacotes ou publica contêineres em pacotes de {% data variables.product.prodname_dotcom %}, o runner também precisará de acesso a esses pontos de extremidades de rede. - -Se você usar uma lista de endereços IP permitida para a sua a sua organização ou conta corporativa do {% data variables.product.prodname_dotcom %}, você deverá adicionar o endereço IP do executor auto-hospedado à lista de permissões. Para obter mais informações consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" ou "[Aplicar política para as configurações de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)". - -{% else %} - -Você deve garantir que a máquina tenha acesso adequado à rede para comunicar-se com as URLs de {% data variables.product.product_location %} listadas abaixo. - -{% endif %} - -Você também pode usar executores auto-hospedados com um servidor proxy. Para obter mais informações, consulte "[Usar um servidor proxy com executores auto-hospedados](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)." - -{% ifversion ghes %} - -## Comunicação entre executores auto-hospedados e {% data variables.product.prodname_dotcom_the_website %} - -Os executores auto-hospedados não precisam conectar-se a {% data variables.product.prodname_dotcom_the_website %}, a menos que você tenha [habilitado acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %}, usando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect). - -Se você permitiu o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}, o executor auto-hospedado irá conectar-se diretamente a {% data variables.product.prodname_dotcom_the_website %} para fazer o downloa das ações. Você deve garantir que a máquina tenha acesso adequado à rede para comunicar-se com as {% data variables.product.prodname_dotcom %} URLs listadas abaixo. - -{% note %} - -**Observação:** Alguns dos domínios listados abaixo estão configurados usando os registros `CNAME`. Alguns firewalls podem exigir que você adicione regras recursivamente para todos os registros `CNAME`. Observe que os registros `CNAME` podem mudar no futuro, e que apenas os domínios listados abaixo permanecerão constantes. - -{% endnote %} - -``` -github.com -api.github.com -codeload.github.com -``` - -{% endif %} - -{% ifversion fpt or ghec %} - -## Segurança dos executores auto-hospedados com repositórios públicos - -{% data reusables.github-actions.self-hosted-runner-security %} - -Este não é um problema com executores hospedados no {% data variables.product.prodname_dotcom %}, pois cada executor hospedado no {% data variables.product.prodname_dotcom %} é sempre uma máquina virtual limpa e isolada, que é destruída no final da execução do trabalho. - -Os fluxos de trabalho não confiáveis no seu executor auto-hospedado representam riscos de segurança significativos para seu ambiente de rede e máquina, especialmente se sua máquina persistir no ambiente entre os trabalhos. Alguns dos riscos incluem: - -* Programas maliciosos em execução na máquina. -* Sair do sandbox do executor da máquina. -* Expor acesso ao ambiente de rede da máquina. -* Dados persistentes, indesejados ou perigosos na máquina. - -{% endif %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md deleted file mode 100644 index e53e41204e..0000000000 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: Adding self-hosted runners -intro: 'You can add a self-hosted runner to a repository, an organization, or an enterprise.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -shortTitle: Add self-hosted runners ---- - -{% data reusables.actions.ae-self-hosted-runners-notice %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} - -You can add a self-hosted runner to a repository, an organization, or an enterprise. - -If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. - -For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." - -{% ifversion not ghae %} -{% warning %} - -**Warning:** {% data reusables.github-actions.self-hosted-runner-security %} - -For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." - -{% endwarning %} -{% endif %} - -## Adding a self-hosted runner to a repository - -You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." - -{% ifversion fpt or ghec %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.settings-sidebar-actions %} -{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} -1. Click **New self-hosted runner**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% data reusables.github-actions.self-hosted-runner-check-installation-success %} - -## Adding a self-hosted runner to an organization - -You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." - -{% ifversion fpt or ghec %} -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.settings-sidebar-actions %} -{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} -1. Click **New runner**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} - -{% data reusables.github-actions.self-hosted-runner-check-installation-success %} - -{% data reusables.github-actions.self-hosted-runner-public-repo-access %} - -## Adding a self-hosted runner to an enterprise - -You can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. - -New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." - -{% ifversion fpt or ghec %} -To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.enterprise-accounts.actions-runners-tab %} -1. Click **New runner**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} -To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.enterprise-accounts.actions-runners-tab %} -1. Click **Add new**, then click **New runner**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% data reusables.github-actions.self-hosted-runner-check-installation-success %} - -{% data reusables.github-actions.self-hosted-runner-public-repo-access %} - -### Making enterprise runners available to repositories - -By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. - -To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. - -For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md deleted file mode 100644 index 5acdd3ad79..0000000000 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -title: Monitoramento e resolução de problemas dos executores auto-hospedados -intro: Você pode monitorar seus executores auto-hospedados para visualizar sua atividade e diagnosticar problemas comuns. -redirect_from: - - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners - - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -defaultPlatform: linux -shortTitle: Monitorar & solucionar problemas ---- - -{% data reusables.actions.ae-self-hosted-runners-notice %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} - -## Verificar o status de um executor auto-hospedado usando {% data variables.product.prodname_dotcom %} - -{% data reusables.github-actions.self-hosted-runner-management-permissions-required %} - -{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} -{% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Em {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, você pode ver uma lista de executores registrados, incluindo nome do executor, etiqueta e status. - - Pode haver os seguintes status: - - * **Inativo**: O executor está conectado a {% data variables.product.product_name %} e está pronto para executar trabalhos. - * **Ativo**: O executor está executando uma tarefa no momento. - * **Off-line**: O executor não está conectado a {% data variables.product.product_name %}. Isto pode ser porque a máquina está off-line, o aplicativo do executor auto-hospedado não está funcionando na máquina, ou o aplicativo do executor auto-hospedado não pode comunicar-se com {% data variables.product.product_name %}. - - -## Revisar os arquivos de registro do aplicativo do executor auto-hospedado - -Você pode monitorar o status do aplicativo do executor auto-hospedado e suas atividades. Os arquivos de registro são mantidos no diretório `_diag` e um novo é gerado toda vez que o aplicativo é iniciado. O nome do arquivo começa com *Runner_*, e é seguido por uma marca de tempo de UTC para quando o aplicativo foi iniciado. - -Para obter registros detalhados sobre as execuções do fluxo de trabalho, consulte a próxima seção que escreve os arquivos *Worker_*. - -## Revisar o arquivo de registro de um trabalho - -O aplicativo do executor auto-hospedado cria um arquivo de registro detalhado para cada trabalho que processa. Esses arquivos são armazenados no diretório `_diag` e o nome do arquivo começa com *Worker_*. - -{% linux %} - -## Usar journalctl para verificar o serviço do aplicativo do executor auto-hospedado - -Para os executores auto-hospedados baseados no Linux que executam o aplicativo usando um serviço, você pode usar o `journalctl` para monitorar a sua atividade em tempo real. O serviço-padrão baseado no sistema usa a seguinte convenção de nomes: `actions.runner.-..service`. Esse nome será truncado se exceder 80 caracteres. Portanto, a forma preferida de encontrar o nome do serviço é selecionar o arquivo _.service_. Por exemplo: - -```shell -$ cat ~/actions-runner/.service -actions.runner.octo-org-octo-repo.runner01.service -``` - -Você pode usar o `journalctl` para monitorar a atividade em tempo real do executor auto-hospedado: - -```shell -$ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f -``` - -Neste exemplo de saída, você pode ver o início `runner01`, receber um trabalho denominado`testAction` e, em seguida, exibir o status resultante: - -```shell -Feb 11 14:57:07 runner01 runsvc.sh[962]: Iniciando o ouvinte do executor com o tipo de inicialização: serviço -Feb 11 14:57:07 runner01 runsvc.sh[962]: Processo do ouvinte iniciado -Feb 11 14:57:07 runner01 runsvc.sh[962]: Serviço de execução iniciado -Feb 11 14:57:16 runner01 runsvc.sh[962]: √ Conectado ao GitHub -Feb 11 14:57:17 runner01 runsvc.sh[962]: 2020-02-11 14:57:17Z: Escuta para Jobs -Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Trabalho em execução: testAction -Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Trabalho testAction concluído com o resultado: Aprovado -``` - -Para visualizar a configuração do systemd, você pode localizar o arquivo de serviço aqui: `/etc/systemd/system/actions.runner.-..service`. Se você desejar personalizar o serviço de aplicação do executor auto-hospedado, não modifique esse arquivo diretamente. Siga as instruções descritas em "[Configurar o aplicativo do executor auto-hospedado como um serviço](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)". - -{% endlinux %} - -{% mac %} - -## Usar o launchd para verificar o serviço do aplicativo do executor auto-hospedado - -Para executores auto-hospedados baseados em macOS que executam o aplicativo como um serviço, você pode usar o `launchctl` para monitorar suas atividades em tempo real. O serviço-padrão baseado no launchd usa a seguinte convenção de nomes: `actions.runner.-.`. Esse nome será truncado se exceder 80 caracteres. Portanto, a forma preferida de encontrar o nome do serviço será selecionar o arquivo _.service_ no diretório do executor: - -```shell -% cat ~/actions-runner/.service -/Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist -``` - -O script `svc.sh` usa `launchctl` para verificar se o aplicativo está sendo executado. Por exemplo: - -```shell -$ ./svc.sh status -status actions.runner.example.runner01: -/Users/exampleUsername/Library/LaunchAgents/actions.runner.example.runner01.plist -Started: -379 0 actions.runner.example.runner01 -``` - -A saída resultante inclui o ID do processo e o nome do serviço de launchd do aplicativo. - -Para visualizar a configuração do launchd, você pode localizar o arquivo de serviço aqui: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. Se você desejar personalizar o serviço de aplicação do executor auto-hospedado, não modifique esse arquivo diretamente. Siga as instruções descritas em "[Configurar o aplicativo do executor auto-hospedado como um serviço](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)". - -{% endmac %} - - -{% windows %} - -## Usar PowerShell para verificar o serviço do aplicativo do executor auto-hospedado - -Para executores auto-hospedados baseados no Windows que executam o aplicativo como um serviço, você pode usar o PowerShell para monitorar suas atividades em tempo real. O serviço usa a convenção de nome `GitHub Actions Runner (-.)`. Você também pode encontrar o nome do serviço, verificando o arquivo _.service_ no diretório do executor: - -```shell -PS C:\actions-runner> Get-Content .service -actions.runner.octo-org-octo-repo.runner01.service -``` - -Você pode visualizar o status do executor no aplicativo _Services_ no Windows (`services.msc`). Você também pode usar o PowerShell para verificar se o serviço está sendo executado: - -```shell -PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status -Nome Status ----- ------ -actions.runner.octo-org-octo-repo.runner01.service Em execução -``` - -Você pode usar o PowerShell para verificar a atividade recente do executor auto-hospedado. Neste exemplo de saída, você pode ver o início do aplicativo, receba um trabalho denominado `testAction` e, em seguida, exiba o status resultante: - -```shell -PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService - - Índice temporal Tipo de entrada Fonte ID da instância Mensagem - ----- ---- --------- ------ ---------- ------- - 136 Mar 17 13:45 Informação ActionsRunnerService 100 2020-03-17 13:45:48Z: Job Saudação concluída com o resultado: Aprovado - 135 Mar 17 13:45 Informação ActionsRunnerService 100 2020-03-17 13:45:34Z: Trabalho em execução: testAction - 134 Mar 17 13:41 Informação ActionsRunnerService 100 2020-03-17 13:41:54Z: Escuta para trabalhos - 133 Mar 17 13:41 Informação ActionsRunnerService 100 û conectado ao GitHub - 132 Mar 17 13:41 Informação ActionsRunnerService 0 Service iniciado com sucesso. - 131 Mar 17 13:41 Informação ActionsRunnerService 100 Iniciando ações do ouvinte do executor - 130 Mar 17 13:41 Informação ActionsRunnerService 100 Iniciando ações do serviço do executor - 129 Mar 17 13:41 Informação ActionsRunnerService 100 criar fonte de rastreamento de registro de evento para o serviço actions-runner -``` - -{% endwindows %} - -## Monitorar o processo de atualização automática - -Recomendamos que você verifique regularmente o processo de atualização automática, uma vez que o executor auto-hospedado não será capaz de processar os trabalhos se estiver abaixo de um determinado limite de versão. O aplicativo do executor auto-hospedado atualiza-se, mas mas observe que este processo não inclui atualizações do sistema operacional ou de outro software. Será necessário que você gerencie essas atualizações separadamente. - -Você pode ver as atividades de atualização nos arquivos de registro *Runner_*. Por exemplo: - -```shell -[Fevb 12 12:37:07 INFO SelfUpdater] Uma atualização está disponível. -``` - -Além disso, você pode encontrar mais informações nos arquivos de registro _SelfUpdate_ localizados no diretório `_diag`. - -{% linux %} - -## Resolução de problemas de contêineres em executores auto-hospedados - -### Verificar se o Docker está instalado - -Se seus trabalhos exigirem contêineres, o executor auto-hospedado deverá ser baseado no Linux e deverá ter o Docker instalado. Verifique se o seu executor auto-hospedado tem o Docker instalado e se o serviço está em execução. - -Você pode usar o `systemctl` para verificar o status do serviço: - -```shell -$ sudo systemctl is-active docker.service -ativo -``` - -Se o Docker não estiver instalado, ações dependentes irão falhar com as seguintes mensagens de erro: - -```shell -[2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker' -[2020-02-13 16:56:10Z INFO DockerCommandManager] Não encontrado. -[2020-02-13 16:56:10Z ERR StepsRunner] Capturou exceção da etapa: System.IO.FileNotFoundException: Arquivo não encontrado: 'docker' -``` - -### Verificar as permissões do Docker - -Se seu trabalho falhar com o seguinte erro: - -```shell -discar unix /var/run/docker.sock: conexão: permissão negada -``` - -Verifique se a conta de serviço do executor auto-hospedado tem permissão para usar o serviço do Docker. Você pode identificar esta conta verificando a configuração do executor auto-hospedado no systemd. Por exemplo: - -```shell -$ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service -User=runner-user -``` - -{% endlinux %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md deleted file mode 100644 index e3bcc39456..0000000000 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Remover executores auto-hospedados -intro: 'Você pode remover um executor auto-hospedado de {{ site.data.variables.product.prodname_actions }} permantentemente.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -shortTitle: Remover executores auto-hospedados ---- - -{% data reusables.actions.ae-self-hosted-runners-notice %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} - -## Remover um executor de um repositório - -{% note %} - -**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -{% endnote %} - -Para remover um executor auto-hospedado de um repositório de usuário, você deve ser o proprietário do repositório. Para um repositório da organização, você deve ser um proprietário da organização ou ter acesso de administrador ao repositório. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)." - -{% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghec %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.settings-sidebar-actions %} -{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} -{% data reusables.github-actions.settings-sidebar-actions-runner-selection %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.settings-sidebar-actions-runners %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} -{% endif %} -## Remover um executor de uma organização - -{% note %} - -**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -{% endnote %} - -Para remover um executor auto-hospedado de uma organização, você deve ser um proprietário da organização. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)." - -{% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.settings-sidebar-actions %} -{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} -{% data reusables.github-actions.settings-sidebar-actions-runner-selection %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% else %} -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.settings-sidebar-actions-runners %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} -{% endif %} -## Remover um executor de uma empresa - -{% note %} - -**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -{% endnote %} -{% data reusables.github-actions.self-hosted-runner-reusing %} - -{% ifversion fpt or ghec %} -Para remover um executor auto-hospedado de uma conta corporativa, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como adicionar um executor auto-hospedado com a API REST, consulte [as APIs do GitHub Actions da administração da empresa](/rest/reference/enterprise-admin#github-actions). -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.enterprise-accounts.actions-runners-tab %} -{% data reusables.github-actions.settings-sidebar-actions-runner-selection %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% elsif ghae or ghes %} -Para remover um executor auto-hospedado no nível da empresa de -{% data variables.product.product_location %}, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.enterprise-accounts.actions-runners-tab %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} -{% endif %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index f14a317444..9028179143 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Usar um servidor proxy com executores auto-hospedados -intro: 'Você pode configurar executores auto-hospedados para usar um servidor proxy para comunicar-se com {% data variables.product.product_name %}.' +title: Using a proxy server with self-hosted runners +intro: 'You can configure self-hosted runners to use a proxy server to communicate with {% data variables.product.product_name %}.' redirect_from: - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners versions: @@ -9,7 +9,7 @@ versions: ghae: '*' ghec: '*' type: tutorial -shortTitle: Servidores proxy +shortTitle: Proxy servers --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -17,39 +17,41 @@ shortTitle: Servidores proxy {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Configurar um servidor proxy usando variáveis de ambiente +## Configuring a proxy server using environment variables -Se você precisar de um executor auto-hospedado para comunicar-se por meio de um servidor proxy, o aplicativo do executor auto-hospedado usará as configurações proxy definidas nas variáveis do ambiente a seguir: +If you need a self-hosted runner to communicate via a proxy server, the self-hosted runner application uses proxy configurations set in the following environment variables: -* `https_proxy`: URL Proxy para tráfego HTTPS. Se necessário, você também poderá incluir credenciais de autenticação básica. Por exemplo: +* `https_proxy`: Proxy URL for HTTPS traffic. You can also include basic authentication credentials, if required. For example: * `http://proxy.local` * `http://192.168.1.1:8080` * `http://username:password@proxy.local` -* `http_proxy`: URL proxy para tráfego HTTP. Se necessário, você também poderá incluir credenciais de autenticação básica. Por exemplo: +* `http_proxy`: Proxy URL for HTTP traffic. You can also include basic authentication credentials, if required. For example: * `http://proxy.local` * `http://192.168.1.1:8080` * `http://username:password@proxy.local` -* `no_proxy`: Listas de hosts separados vírgula que não devem usar um proxy. São permitidos apenas nomes de host em `no_proxy`. Você não pode usar endereços IP. Por exemplo: +* `no_proxy`: Comma separated list of hosts that should not use a proxy. Only hostnames are allowed in `no_proxy`, you cannot use IP addresses. For example: * `example.com` * `example.com,myserver.local:443,example.org` -As variáveis do ambiente proxy são lidas quando o aplicativo do executor auto-hospedado inicia. Portanto, você deve definir as variáveis do ambiente antes de configurar ou iniciar o aplicativo do executor auto-hospedado. Se a sua configuração de proxy for alterada, você deverá reiniciar o aplicativo do executor auto-hospedado. +The proxy environment variables are read when the self-hosted runner application starts, so you must set the environment variables before configuring or starting the self-hosted runner application. If your proxy configuration changes, you must restart the self-hosted runner application. -No Windows, os nomes da variável do ambiente proxy não diferenciam maiúsculas de minúsculas. Nos sistemas Linux e macOS, recomendamos que você use variáveis de ambiente em minúscula. Se você tiver uma variável de ambiente tanto maiúscula quanto minúscula no Linux ou macOS, como, por exemplo `https_proxy` e `HTTPS_PROXY`, o aplicativo executor auto-hospedado usará a variável minúscula do ambiente. +On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example `https_proxy` and `HTTPS_PROXY`, the self-hosted runner application uses the lowercase environment variable. -## Usar um arquivo .env para definir a configuração de proxy +{% data reusables.actions.self-hosted-runner-ports-protocols %} -Se não for prático definir as variáveis do ambiente, você poderá definir as variáveis da configuração de proxy em um arquivo de nome _.env_ no diretório do aplicativo do executor auto-hospedado. Por exemplo, isso pode ser necessário se você desejar configurar um aplicativo executor como um serviço em uma conta de sistema. Quando o aplicativo executor é iniciado, ele lerá as variáveis definidas em _.env_ para a configuração de proxy. +## Using a .env file to set the proxy configuration -Um exemplo de configuração de proxy _.env_ é mostrado abaixo: +If setting environment variables is not practical, you can set the proxy configuration variables in a file named _.env_ in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in _.env_ for the proxy configuration. + +An example _.env_ proxy configuration is shown below: ```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` -## Definir configuração de proxy para contêineres Docker +## Setting proxy configuration for Docker containers -Se você usar ações do contêiner Dock ou contêineres de serviço nos seus fluxos de trabalho, você também deverá configurar o Docker para usar o seu servidor proxy além de definir as variáveis do ambiente acima. +If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables. -Para obter mais informações sobre a configuração do Docker necessária, consulte "[Configurar Docker para usar um servidor proxy](https://docs.docker.com/network/proxy/)" no documento do Docker. +For information on the required Docker configuration, see "[Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/)" in the Docker documentation. diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md index 448eb048f6..9613ae2f2f 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md @@ -1,7 +1,7 @@ --- -title: Entendendo o GitHub Actions -shortTitle: Entendendo o GitHub Actions -intro: 'Aprenda o básico de {% data variables.product.prodname_actions %}, incluindo conceitos fundamentais e terminologia essencial.' +title: Understanding GitHub Actions +shortTitle: Understanding GitHub Actions +intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.' redirect_from: - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions @@ -21,55 +21,55 @@ topics: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Visão Geral +## Overview -{% data variables.product.prodname_actions %} ajuda você a automatizar tarefas dentro de seu ciclo de vida de desenvolvimento de software. {% data variables.product.prodname_actions %} são orientados por eventos, o que significa que você pode executar uma série de comandos após um evento especificado ocorrer. Por exemplo, cada vez que alguém cria um pull request para um repositório, você pode executar automaticamente um comando que executa um script de teste do software. +{% data reusables.actions.about-actions %} {% data variables.product.prodname_actions %} are event-driven, meaning that you can run a series of commands after a specified event has occurred. For example, every time someone creates a pull request for a repository, you can automatically run a command that executes a software testing script. -Este diagrama demonstra como você pode usar {% data variables.product.prodname_actions %} para executar automaticamente seus scripts de teste de software. Um evento aciona automaticamente o _fluxo de trabalho_, que contém um _trabalho_. Em seguida, o trabalho usa _etapas_ para controlar a ordem em que as _ações_ são executadas. Estas ações são os comandos que automatizam o teste do seu software. +This diagram demonstrates how you can use {% data variables.product.prodname_actions %} to automatically run your software testing scripts. An event automatically triggers the _workflow_, which contains a _job_. The job then uses _steps_ to control the order in which _actions_ are run. These actions are the commands that automate your software testing. -![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-simple.png) +![Workflow overview](/assets/images/help/images/overview-actions-simple.png) -## Componentes de {% data variables.product.prodname_actions %} +## The components of {% data variables.product.prodname_actions %} -Abaixo está uma lista dos múltiplos componentes de {% data variables.product.prodname_actions %} que trabalham em conjunto para executar os trabalhos. Você pode ver como esses componentes interagem uns com os outros. +Below is a list of the multiple {% data variables.product.prodname_actions %} components that work together to run jobs. You can see how these components interact with each other. -![Visão geral do componente e do serviço](/assets/images/help/images/overview-actions-design.png) +![Component and service overview](/assets/images/help/images/overview-actions-design.png) -### Fluxos de trabalho +### Workflows -O fluxo de trabalho é um procedimento automatizado que você adiciona ao seu repositório. Os fluxos de trabalho são constituídos por um ou mais trabalhos e podem ser programados ou ativados por um evento. O fluxo de trabalho pode ser usado para criar, testar, empacotar, publicar ou implantar um projeto em {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}Você pode consultar um fluxo de trabalho dentro de outro fluxo de trabalho. Consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)"{% endif %} +The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %} -### Eventos +### Events -Um evento é uma atividade específica que aciona um fluxo de trabalho. Por exemplo, uma atividade pode originar de {% data variables.product.prodname_dotcom %} quando alguém faz o push de um commit em um repositório ou quando são criados um problema ou um pull request. Também é possível usar o [webhook de envio de repositórios](/rest/reference/repos#create-a-repository-dispatch-event) para acionar um fluxo de trabalho quando ocorre um evento externo. Para obter uma lista completa de eventos que podem ser usados para acionar fluxos de trabalho, consulte [Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows). +An event is a specific activity that triggers a workflow. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone pushes a commit to a repository or when an issue or pull request is created. You can also use the [repository dispatch webhook](/rest/reference/repos#create-a-repository-dispatch-event) to trigger a workflow when an external event occurs. For a complete list of events that can be used to trigger workflows, see [Events that trigger workflows](/actions/reference/events-that-trigger-workflows). -### Trabalhos +### Jobs -Um trabalho é um conjunto de etapas executadas no mesmo executor. Por padrão, um fluxo de trabalho com vários trabalhos executará esses trabalhos em paralelo. Também é possível configurar um fluxo de trabalho para executar trabalhos sequencialmente. Por exemplo, um fluxo de trabalho pode ter dois trabalhos sequenciais que criam e testam códigos. em que o trabalho de teste depende do status do trabalho de criação. Se ocorrer uma falha no trabalho de criação, o trabalho de teste não será executado. +A job is a set of steps that execute on the same runner. By default, a workflow with multiple jobs will run those jobs in parallel. You can also configure a workflow to run jobs sequentially. For example, a workflow can have two sequential jobs that build and test code, where the test job is dependent on the status of the build job. If the build job fails, the test job will not run. -### Etapas +### Steps -Uma etapa é uma tarefa individual que pode executar comandos em um trabalho. Uma etapa pode ser uma _ação_ ou um comando de shell. Cada etapa de um trabalho é executada no mesmo executor, permitindo que as ações naquele trabalho compartilhem dados entre si. +A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. Each step in a job executes on the same runner, allowing the actions in that job to share data with each other. -### Ações +### Actions -_Ações_ são comandos autônomos combinados em _etapas_ para criar um _trabalho_. As ações são o menor bloco de criação portátil de um fluxo de trabalho. Você pode criar as suas próprias ações ou usar ações criadas pela comunidade de {% data variables.product.prodname_dotcom %}. Para usar uma ação em um fluxo de trabalho, você deverá incluí-la como uma etapa. +_Actions_ are standalone commands that are combined into _steps_ to create a _job_. Actions are the smallest portable building block of a workflow. You can create your own actions, or use actions created by the {% data variables.product.prodname_dotcom %} community. To use an action in a workflow, you must include it as a step. -### Executores +### Runners -{% ifversion ghae %}Um executor é um servidor que tem [um aplicativo do executor de {% data variables.product.prodname_actions %}](https://github.com/actions/runner) instalado. Para {% data variables.product.prodname_ghe_managed %}, você pode usar a segurança enrijecida de {% data variables.actions.hosted_runner %}, que são agrupados com sua instância na nuvem. Um executor escuta trabalhos disponíveis, executa um trabalho de cada vez e relata o progresso, os registros e os resultados de volta para {% data variables.product.prodname_dotcom %}. {% data variables.actions.hosted_runner %}s executam cada fluxo de trabalho em um novo ambiente virtual. Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)". +{% ifversion ghae %}A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. For {% data variables.product.prodname_ghe_managed %}, you can use the security hardened {% data variables.actions.hosted_runner %}s which are bundled with your instance in the cloud. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.actions.hosted_runner %}s run each workflow job in a fresh virtual environment. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." {% else %} -Um executor é um servidor que tem o[aplicativo do executor de {% data variables.product.prodname_actions %}](https://github.com/actions/runner) instalado. Você pode usar um executor hospedado em {% data variables.product.prodname_dotcom %} ou você pode hospedar seu próprio. Um executor escuta trabalhos disponíveis, executa um trabalho de cada vez e relata o progresso, os registros e os resultados de volta para {% data variables.product.prodname_dotcom %}. Executores hospedados em {% data variables.product.prodname_dotcom %} são baseados no Ubuntu Linux, Microsoft Windows e macOS, e cada trabalho em um fluxo de trabalho é executado em um novo ambiente virtual. Para obter informações sobre executores hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Sobre executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)." Se você precisar de um sistema operacional diferente ou precisar de uma configuração de hardware específica, você poderá hospedar seus próprios executores. Para obter informações sobre executores auto-hospedados, consulte "[Hospedar seus próprios executores](/actions/hosting-your-own-runners)". +{% data reusables.actions.about-runners %} A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS, and each job in a workflow runs in a fresh virtual environment. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." {% endif %} -## Criar um exemplo de fluxo de trabalho +## Create an example workflow -{% data variables.product.prodname_actions %} usa sintaxe de YAML para definir os eventos, trabalhos e etapas. Esses arquivos de YAML são armazenados no seu repositório de código em um diretório denominado `.github/workflows`. +{% data variables.product.prodname_actions %} uses YAML syntax to define the events, jobs, and steps. These YAML files are stored in your code repository, in a directory called `.github/workflows`. -Você pode criar um exemplo de fluxo de trabalho no repositório que aciona automaticamente uma série de comandos sempre que o código for carregado. Neste fluxo de trabalho, {% data variables.product.prodname_actions %} verifica o código enviado, instala as dependências do software e executa `bats -v`. +You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the software dependencies, and runs `bats -v`. -1. No seu repositório, crie o diretório `.github/workflows/` para armazenar seus arquivos do fluxo de trabalho. -1. No diretório `.github/workflows/`, crie um novo arquivo denominado `learn-github-actions.yml` e adicione o código a seguir. +1. In your repository, create the `.github/workflows/` directory to store your workflow files. +1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code. ```yaml name: learn-github-actions on: [push] @@ -84,13 +84,13 @@ Você pode criar um exemplo de fluxo de trabalho no repositório que aciona auto - run: npm install -g bats - run: bats -v ``` -1. Faça commit dessas alterações e faça push para o seu repositório do {% data variables.product.prodname_dotcom %}. +1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository. -Seu novo arquivo de fluxo de trabalho de {% data variables.product.prodname_actions %} agora está instalado no seu repositório e será executado automaticamente toda vez que alguém fizer push de uma alteração no repositório. Para obter detalhes sobre o histórico de execução de um trabalho, consulte "[Visualizar a atividade do fluxo de trabalho](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)". +Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. For details about a job's execution history, see "[Viewing the workflow's activity](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)." -## Entender o arquivo de fluxo de trabalho +## Understanding the workflow file -Para ajudar você a entender como a sintaxe de YAML é usada para criar um arquivo de fluxo de trabalho, esta seção explica cada linha do exemplo Introdução: +To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example: @@ -101,7 +101,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -112,7 +112,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -123,7 +123,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -134,7 +134,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -145,7 +145,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -156,7 +156,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -167,7 +167,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -180,7 +180,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -191,7 +191,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` @@ -202,42 +202,49 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ```
    - Opcional - Como o nome do fluxo de trabalho irá aparecer na aba Ações do repositório de {% data variables.product.prodname_dotcom %}. + Optional - The name of the workflow as it will appear in the Actions tab of the {% data variables.product.prodname_dotcom %} repository.
    - Especifica o evento que aciona automaticamente o arquivo do fluxo de trabalho. Este exemplo usa o evento push para que os trabalhos sejam executados toda vez que alguém fizer uma alteração no repositório. É possível definir o fluxo de trabalho para ser executado somente em determinados branches, caminhos ou tags. Para obter exemplos de sintaxe, incluindo ou excluindo branches, caminhos ou tags, consulte "Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}" + Specify the event that automatically triggers the workflow file. This example uses the push event, so that the jobs run every time someone pushes a change to the repository. You can set up the workflow to only run on certain branches, paths, or tags. For syntax examples including or excluding branches, paths, or tags, see "Workflow syntax for {% data variables.product.prodname_actions %}."
    - Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho learn-github-actions. + Groups together all the jobs that run in the learn-github-actions workflow file.
    - Define o nome do trabalho check-bats-version armazenado na seção trabalhos. + Defines the name of the check-bats-version job stored within the jobs section.
    - Configura o trabalho a ser executado em um executor do Ubuntu Linux. Isto significa que o trabalho será executado em uma nova máquina virtual hospedada pelo GitHub. Para obter exemplos de sintaxe usando outros executores, consulte "Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}." + Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see "Workflow syntax for {% data variables.product.prodname_actions %}."
    - Agrupa todos os passos são executados no trabalho check-bats-version. Cada item aninhado nesta seção é uma ação separada ou comando de shell. + Groups together all the steps that run in the check-bats-version job. Each item nested under this section is a separate action or shell command.
    - A palavra-chave usa diz ao trabalho para recuperar v2 da ação da comunidade com o nome actions/checkout@v2. Esta é uma ação que verifica seu repositório e o faz o download do runner, permitindo que você execute ações contra seu código (como, por exemplo, ferramentas de teste). Você deve usar a ação de checkout sempre que o fluxo de trabalho for executado no código do repositório ou você estiver usando uma ação definida no repositório. + The uses keyword tells the job to retrieve v2 of the community action named actions/checkout@v2. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
    - Esta etapa usa a ação actions/setup-node@v2 para instalar a versão especificada do pacote de software do nó no executor, que fornece a você acesso ao comando npm. + This step uses the actions/setup-node@v2 action to install the specified version of the node software package on the runner, which gives you access to the npm command.
    - A palavra-chave executar diz ao trabalho para executar um comando no executor. Neste caso, você está usando o npm para instalar o pacote de teste do software bats. + The run keyword tells the job to execute a command on the runner. In this case, you are using npm to install the bats software testing package.
    - Por fim, você executará o comando bats com um parâmetro que produz a versão do software. + Finally, you'll run the bats command with a parameter that outputs the software version.
    -### Visualizar o arquivo de fluxo de trabalho +### Visualizing the workflow file -Neste diagrama, você pode ver o arquivo de fluxo de trabalho que acabou de criar e como os componentes de {% data variables.product.prodname_actions %} estão organizados em uma hierarquia. Cada etapa executa uma única ação ou comando de shell. As etapas 1 e 2 usam ações de comunidade pré-criadas. As etapas 3 e 4 executam comandos de shell diretamente no executor. Para encontrar mais ações pré-criadas para seus fluxos de trabalho, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)". +In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell command. Steps 1 and 2 use prebuilt community actions. Steps 3 and 4 run shell commands directly on the runner. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." -![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-event.png) +![Workflow overview](/assets/images/help/images/overview-actions-event.png) -## Visualizar a atividade do trabalho +## Viewing the job's activity -Assim que o seu trabalho começar a ser executado, você poderá {% ifversion fpt or ghes > 3.0 or ghae or ghec %}ver um gráfico de visualização do progresso da execução e {% endif %}visualizar a atividade de cada etapa em {% data variables.product.prodname_dotcom %}. +Once your job has started running, you can {% ifversion fpt or ghes > 3.0 or ghae or ghec %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}. {% data reusables.repositories.navigate-to-repo %} -1. No nome do seu repositório, clique em **Ações**. ![Acesse o repositório](/assets/images/help/images/learn-github-actions-repository.png) -1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver. ![Captura de tela dos resultados do fluxo de trabalho](/assets/images/help/images/learn-github-actions-workflow.png) -1. Em "Execuções do fluxo de trabalho", clique no nome da execução que você deseja ver. ![Captura de tela das execuções do fluxo de trabalho](/assets/images/help/images/learn-github-actions-run.png) +1. Under your repository name, click **Actions**. + ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png) +1. In the left sidebar, click the workflow you want to see. + ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png) +1. Under "Workflow runs", click the name of the run you want to see. + ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png) {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -1. Em **Trabalhos** ou no gráfico de visualização, clique no trabalho que você deseja ver. ![Selecionar trabalho](/assets/images/help/images/overview-actions-result-navigate.png) +1. Under **Jobs** or in the visualization graph, click the job you want to see. + ![Select job](/assets/images/help/images/overview-actions-result-navigate.png) {% endif %} {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -1. Visualizar os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result-updated-2.png) +1. View the results of each step. + ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png) {% elsif ghes %} -1. Clique no nome do trabalho para ver os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result-updated.png) +1. Click on the job name to see the results of each step. + ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png) {% else %} -1. Clique no nome do trabalho para ver os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result.png) +1. Click on the job name to see the results of each step. + ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png) {% endif %} -## Próximas etapas +## Next steps -Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)". +To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." -Para entender como a cobrança funciona para {% data variables.product.prodname_actions %}, consulte "[Sobre cobrança para {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". +To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". -## Entrar em contato com o suporte +## Contacting support {% data reusables.github-actions.contacting-support %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 5935c2c083..ef1dd1c4bc 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -1,7 +1,7 @@ --- -title: Comandos do fluxo de trabalho para o GitHub Actions -shortTitle: Comandos do fluxo de trabalho -intro: Você pode usar comandos do fluxo de trabalho ao executar comandos do shell em um fluxo de trabalho ou no código de uma ação. +title: Workflow commands for GitHub Actions +shortTitle: Workflow commands +intro: You can use workflow commands when running shell commands in a workflow or in an action's code. redirect_from: - /articles/development-tools-for-github-actions - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions @@ -20,11 +20,11 @@ versions: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Sobre os comandos do fluxo de trabalho +## About workflow commands -As ações podem comunicar-se com a máquina do executor para definir as variáveis de ambiente, valores de saída usados por outras ações, adicionar mensagens de depuração aos registros de saída e outras tarefas. +Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks. -A maioria dos comandos de fluxo de trabalho usa o comando `echo` em um formato específico, enquanto outros são chamados escrevendo um arquivo. Para obter mais informações, consulte ["Arquivos de ambiente".](#environment-files) +Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see ["Environment files".](#environment-files) ``` bash echo "::workflow-command parameter1={data},parameter2={data}::{command value}" @@ -32,25 +32,25 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}" {% note %} -**Observação:** Os nomes do comando do fluxo de trabalho e do parâmetro não diferenciam maiúsculas e minúsculas. +**Note:** Workflow command and parameter names are not case-sensitive. {% endnote %} {% warning %} -**Aviso:** se você estiver usando um prompt do comando, omita as aspas duplas (`"`) ao usar comandos do fluxo de trabalho. +**Warning:** If you are using Command Prompt, omit double quote characters (`"`) when using workflow commands. {% endwarning %} -## Usar comandos do fluxo de trabalho para acessar funções do kit de de ferramentas +## Using workflow commands to access toolkit functions -O [actions/toolkit](https://github.com/actions/toolkit) inclui uma quantidade de funções que podem ser executadas como comandos do fluxo de trabalho. Use a sintaxe `::` para executar os comandos do fluxo de trabalho no arquivo YAML. Em seguida, esses comandos serão enviados para a o executor por meio do `stdout`. Por exemplo, em vez de usar o código para definir uma saída, como abaixo: +The [actions/toolkit](https://github.com/actions/toolkit) includes a number of functions that can be executed as workflow commands. Use the `::` syntax to run the workflow commands within your YAML file; these commands are then sent to the runner over `stdout`. For example, instead of using code to set an output, as below: ```javascript core.setOutput('SELECTED_COLOR', 'green'); ``` -Você pode usar o comando `set-output` no seu fluxo de trabalho para definir o mesmo valor: +You can use the `set-output` command in your workflow to set the same value: {% raw %} ``` yaml @@ -62,52 +62,52 @@ Você pode usar o comando `set-output` no seu fluxo de trabalho para definir o m ``` {% endraw %} -A tabela a seguir mostra quais funções do conjunto de ferramentas estão disponíveis dentro de um fluxo de trabalho: +The following table shows which toolkit functions are available within a workflow: -| Função do kit de ferramentas | Comando equivalente do fluxo de trabalho | -| ---------------------------- | --------------------------------------------------------------------- | -| `core.addPath` | Acessível usando o arquivo de ambiente `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} -| `core.notice` | `notice` -{% endif %} -| `core.error` | `erro` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | Acessível usando o arquivo de ambiente `GITHUB_ENV` | -| `core.getInput` | Acessível por meio do uso da variável de ambiente `INPUT_{NAME}` | -| `core.getState` | Acessível por meio do uso da variável de ambiente `STATE_{NAME}` | -| `core.isDebug` | Acessível por meio do uso da variável de ambiente `RUNNER_DEBUG` | -| `core.saveState` | `save-state` | -| `core.setFailed` | Usado como um atalho para `::error` e `exit 1` | -| `core.setOutput` | `set-output` | -| `core.setSecret` | `add-mask` | -| `core.startGroup` | `grupo` | -| `core.warning` | `aviso` | +| Toolkit function | Equivalent workflow command | +| ----------------- | ------------- | +| `core.addPath` | Accessible using environment file `GITHUB_PATH` | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| `core.notice` | `notice` |{% endif %} +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | +| `core.getInput` | Accessible using environment variable `INPUT_{NAME}` | +| `core.getState` | Accessible using environment variable `STATE_{NAME}` | +| `core.isDebug` | Accessible using environment variable `RUNNER_DEBUG` | +| `core.saveState` | `save-state` | +| `core.setCommandEcho` | `echo` | +| `core.setFailed` | Used as a shortcut for `::error` and `exit 1` | +| `core.setOutput` | `set-output` | +| `core.setSecret` | `add-mask` | +| `core.startGroup` | `group` | +| `core.warning` | `warning` | -## Definir um parâmetro de saída +## Setting an output parameter ``` ::set-output name={name}::{value} ``` -Configura um parâmetro de saída da ação. +Sets an action's output parameter. -Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". +Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." -### Exemplo +### Example ``` bash echo "::set-output name=action_fruit::strawberry" ``` -## Configurar uma mensagem de depuração +## Setting a debug message ``` ::debug::{message} ``` -Imprime uma mensagem de erro no log. Você deve criar um segredo nomeado `ACTIONS_STEP_DEBUG` com o valor `true` para ver as mensagens de erro configuradas por esse comando no log. Para obter mais informações, consulte "[Habilitar o registro de depuração](/actions/managing-workflow-runs/enabling-debug-logging)". +Prints a debug message to the log. You must create a secret named `ACTIONS_STEP_DEBUG` with the value `true` to see the debug messages set by this command in the log. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)." -### Exemplo +### Example ``` bash echo "::debug::Set the Octocat variable" @@ -115,17 +115,17 @@ echo "::debug::Set the Octocat variable" {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} -## Configurando uma mensagem de aviso +## Setting a notice message ``` ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -Cria uma mensagem de aviso e a imprime no registro. {% data reusables.actions.message-annotation-explanation %} +Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} -### Exemplo +### Example ``` bash echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" @@ -133,48 +133,48 @@ echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" {% endif %} -## Configurar uma mensagem de aviso +## Setting a warning message ``` ::warning file={name},line={line},endLine={endLine},title={title}::{message} ``` -Cria uma mensagem de aviso e a imprime no log. {% data reusables.actions.message-annotation-explanation %} +Creates a warning message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} -### Exemplo +### Example ``` bash echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` -## Configurar uma mensagem de erro +## Setting an error message ``` ::error file={name},line={line},endLine={endLine},title={title}::{message} ``` -Cria uma mensagem de erro e a imprime no log. {% data reusables.actions.message-annotation-explanation %} +Creates an error message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} -### Exemplo +### Example ``` bash echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` -## Agrupar linhas dos registros +## Grouping log lines ``` ::group::{title} ::endgroup:: ``` -Cria um grupo expansível no registro. Para criar um grupo, use o comando `grupo` e especifique um `título`. Qualquer coisa que você imprimir no registro entre os comandos `grupo` e `endgroup` estará aninhada dentro de uma entrada expansível no registro. +Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log. -### Exemplo +### Example ```bash echo "::group::My title" @@ -182,44 +182,44 @@ echo "Inside group" echo "::endgroup::" ``` -![Grupo dobrável no registro da execução do fluxo de trabalho](/assets/images/actions-log-group.png) +![Foldable group in workflow run log](/assets/images/actions-log-group.png) -## Mascarar um valor no registro +## Masking a value in log ``` ::add-mask::{value} ``` -Mascarar um valor evita que uma string ou variável seja impressa no log. Cada palavra mascarada separada por espaço em branco é substituída pelo caractere `*`. Você pode usar uma variável de ambiente ou string para o `value` da máscara. +Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`. -### Exemplo de máscara de string +### Example masking a string -Quando você imprime `"Mona The Octocat"` no log, você verá `"***"`. +When you print `"Mona The Octocat"` in the log, you'll see `"***"`. ```bash echo "::add-mask::Mona The Octocat" ``` -### Exemplo de máscara de uma variável de ambiente +### Example masking an environment variable -Ao imprimir a variável `MY_NAME` ou o valor `"Mona The Octocat"` no log, você verá `"***"` em vez de `"Mona The Octocat"`. +When you print the variable `MY_NAME` or the value `"Mona The Octocat"` in the log, you'll see `"***"` instead of `"Mona The Octocat"`. ```bash MY_NAME="Mona The Octocat" echo "::add-mask::$MY_NAME" ``` -## Parar e iniciar os comandos no fluxo de trabalho +## Stopping and starting workflow commands `::stop-commands::{endtoken}` -Para de processar quaisquer comandos de fluxo de trabalho. Esse comando especial permite fazer o registro do que você desejar sem executar um comando do fluxo de trabalho acidentalmente. Por exemplo, é possível parar o log para gerar um script inteiro que tenha comentários. +Stops processing any workflow commands. This special command allows you to log anything without accidentally running a workflow command. For example, you could stop logging to output an entire script that has comments. -Para parar o processamento de comandos de fluxo de trabalho, passe um token único para `stop-commands`. Para retomar os comandos do fluxo de trabalho, passe o mesmo token que você usou para parar os comandos do fluxo de trabalho. +To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands. {% warning %} -**Aviso:** Certifique-se de que o token que você está usando é gerado aleatoriamente e exclusivo para cada execução. Como demonstrado no exemplo abaixo, você pode gerar um hash exclusivo do seu `github.token` para cada execução. +**Warning:** Make sure the token you're using is randomly generated and unique for each run. As demonstrated in the example below, you can generate a unique hash of your `github.token` for each run. {% endwarning %} @@ -227,7 +227,7 @@ Para parar o processamento de comandos de fluxo de trabalho, passe um token úni ::{endtoken}:: ``` -### Exemplo de parar e iniciar comandos de workflow +### Example stopping and starting workflow commands {% raw %} @@ -247,33 +247,73 @@ jobs: {% endraw %} -## Enviar valores para as ações anterior e posterior +## Echoing command outputs -Você pode usar o comando `save-state` para criar variáveis de ambiente para compartilhar com as ações `pre:` ou `post:`. Por exemplo, você pode criar um arquivo com a ação `pre:`, passar o local do arquivo para a ação `main:` e, em seguida, usar a ação `post:` para excluir o arquivo. Como alternativa, você pode criar um arquivo com a ação `main:` ação, passar o local do arquivo para a ação `post:`, além de usar a ação `post:` para excluir o arquivo. +``` +::echo::on +::echo::off +``` -Se você tiver múltiplas ações `pre:` ou `post:` ações, você poderá apenas acessar o valor salvo na ação em que `save-state` foi usado. Para obter mais informações sobre a ação `post:`, consulte "[Sintaxe de metadados para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)". +Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. -O comando `save-state` pode ser executado apenas em uma ação e não está disponível para arquivos YAML. O valor salvo é armazenado como um valor de ambiente com o prefixo `STATE_`. +Command echoing is disabled by default. However, a workflow command is echoed if there are any errors processing the command. -Este exemplo usa o JavaScript para executar o comando `save-state`. A variável de ambiente resultante é denominada `STATE_processID` com o valor de `12345`: +The `add-mask`, `debug`, `warning`, and `error` commands do not support echoing because their outputs are already echoed to the log. + +You can also enable command echoing globally by turning on step debug logging using the `ACTIONS_STEP_DEBUG` secret. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)". In contrast, the `echo` workflow command lets you enable command echoing at a more granular level, rather than enabling it for every workflow in a repository. + +### Example toggling command echoing + +```yaml +jobs: + workflow-command-job: + runs-on: ubuntu-latest + steps: + - name: toggle workflow command echoing + run: | + echo '::set-output name=action_echo::disabled' + echo '::echo::on' + echo '::set-output name=action_echo::enabled' + echo '::echo::off' + echo '::set-output name=action_echo::disabled' +``` + +The step above prints the following lines to the log: + +``` +::set-output name=action_echo::enabled +::echo::off +``` + +Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases. + +## Sending values to the pre and post actions + +You can use the `save-state` command to create environment variables for sharing with your workflow's `pre:` or `post:` actions. For example, you can create a file with the `pre:` action, pass the file location to the `main:` action, and then use the `post:` action to delete the file. Alternatively, you could create a file with the `main:` action, pass the file location to the `post:` action, and also use the `post:` action to delete the file. + +If you have multiple `pre:` or `post:` actions, you can only access the saved value in the action where `save-state` was used. For more information on the `post:` action, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)." + +The `save-state` command can only be run within an action, and is not available to YAML files. The saved value is stored as an environment value with the `STATE_` prefix. + +This example uses JavaScript to run the `save-state` command. The resulting environment variable is named `STATE_processID` with the value of `12345`: ``` javascript console.log('::save-state name=processID::12345') ``` -A variável `STATE_processID` está exclusivamente disponível para o script de limpeza executado na ação `principal`. Este exemplo é executado em `principal` e usa o JavaScript para exibir o valor atribuído à variável de ambiente `STATE_processID`: +The `STATE_processID` variable is then exclusively available to the cleanup script running under the `main` action. This example runs in `main` and uses JavaScript to display the value assigned to the `STATE_processID` environment variable: ``` javascript -console.log("O PID em execução a partir da ação principal é: " + process.env.STATE_processID); +console.log("The running PID from the main action is: " + process.env.STATE_processID); ``` -## Arquivos de Ambiente +## Environment Files -Durante a execução de um fluxo de trabalho, o executor gera arquivos temporários que podem ser usados para executar certas ações. O caminho para esses arquivos são expostos através de variáveis de ambiente. Você precisará usar a codificação UTF-8 ao escrever para esses arquivos para garantir o processamento adequado dos comandos. Vários comandos podem ser escritos no mesmo arquivo, separados por novas linhas. +During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines. {% warning %} -**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão. Certifique-se de escrever os arquivos usando a codificação correta. Por exemplo, você deve definir a codificação UTF-8 ao definir o caminho: +**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. Make sure you write files using the correct encoding. For example, you need to set UTF-8 encoding when you set the path: ```yaml jobs: @@ -284,7 +324,7 @@ jobs: run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Ou mude para PowerShell Core, cujo padrão é UTF-8: +Or switch to PowerShell Core, which defaults to UTF-8: ```yaml jobs: @@ -297,27 +337,26 @@ jobs: More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow answer](https://stackoverflow.com/a/40098904/162694): -> ### Leitura opcional: A perspectiva entre plataformas: PowerShell _Core_: -> -> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - ***defaults to ***BOM-less UTF-8******, in line with Unix-like platforms. +> ### Optional reading: The cross-platform perspective: PowerShell _Core_: +> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - **defaults to *BOM-less UTF-8***, in line with Unix-like platforms. {% endwarning %} -## Definir uma variável de ambiente +## Setting an environment variable ``` bash echo "{name}={value}" >> $GITHUB_ENV ``` -Cria ou atualiza uma variável de ambiente para quaisquer etapas a serem executadas em seguida no trabalho. A etapa que cria ou atualiza a variável de ambiente não tem acesso ao novo valor, mas todos os passos subsequentes em um trabalho terão acesso. As variáveis de ambiente diferenciam maiúsculas de minúsculas e podem ter pontuação. +Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation. {% note %} -**Observação:** As variáveis de ambiente devem ser referenciadas explicitamente usando o [`env` contexto](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) na sintaxe de expressão ou por meio do uso do arquivo `$GITHUB_ENV` diretamente. As variáveisde ambiente não estão implicitamente disponíveis nos comandos do shell. +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. {% endnote %} -### Exemplo +### Example {% raw %} ``` @@ -333,9 +372,9 @@ steps: ``` {% endraw %} -### Strings de linha múltipla +### Multiline strings -Para strings linha múltipla, você pode usar um delimitador com a seguinte sintaxe. +For multiline strings, you may use a delimiter with the following syntax. ``` {name}<<{delimiter} @@ -343,9 +382,9 @@ Para strings linha múltipla, você pode usar um delimitador com a seguinte sint {delimiter} ``` -#### Exemplo +#### Example -Neste exemplo, usamos `EOF` como um delimitador e definimos a variável de ambiente `JSON_RESPONSE` como o valor da resposta de curl. +In this example, we use `EOF` as a delimiter and set the `JSON_RESPONSE` environment variable to the value of the curl response. ```yaml steps: - name: Set the value @@ -356,17 +395,17 @@ steps: echo 'EOF' >> $GITHUB_ENV ``` -## Adicionar um caminho do sistema +## Adding a system path ``` bash echo "{path}" >> $GITHUB_PATH ``` -Prepara um diretório para a variável `PATH` do sistema e disponibiliza automaticamente para todas as ações subsequentes no trabalho atual; a ação atualmente em execução não pode acessar a variável de caminho atualizada. Para ver os caminhos atualmente definidos para o seu trabalho, você pode usar o `echo "$PATH"` em uma etapa ou ação. +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. -### Exemplo +### Example -Este exemplo demonstra como adicionar o diretório `$HOME/.local/bin` ao `PATH`: +This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`: ``` bash echo "$HOME/.local/bin" >> $GITHUB_PATH diff --git a/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index d21047373e..8cafaf8c6b 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -1,7 +1,7 @@ --- -title: Sintaxe de fluxo de trabalho para o GitHub Actions -shortTitle: Sintaxe de fluxo de trabalho -intro: Um fluxo de trabalho é um processo automatizado configurável constituído de um ou mais trabalhos. Você deve criar um arquivo YAML para definir a configuração do seu fluxo de trabalho. +title: Workflow syntax for GitHub Actions +shortTitle: Workflow syntax +intro: A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration. redirect_from: - /articles/workflow-syntax-for-github-actions - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions @@ -18,27 +18,27 @@ versions: {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -## Sobre sintaxe YAML para fluxos de trabalho +## About YAML syntax for workflows -Arquivos de fluxo de trabalho usam sintaxe YAML e devem ter uma extensão de arquivo `.yml` ou `.yaml`. {% data reusables.actions.learn-more-about-yaml %} +Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. {% data reusables.actions.learn-more-about-yaml %} -Você deve armazenar os arquivos de fluxo de trabalho no diretório `.github/workflows` do seu repositório. +You must store workflow files in the `.github/workflows` directory of your repository. ## `name` -Nome do fluxo de trabalho. O {% data variables.product.prodname_dotcom %} exibe os nomes dos fluxos de trabalho na página de ações do repositório. Se você omitir o `nome`, o {% data variables.product.prodname_dotcom %} irá defini-lo como o caminho do arquivo do fluxo de trabalho relativo à raiz do repositório. +The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository. ## `on` -**Obrigatório**. O nome do evento de {% data variables.product.prodname_dotcom %} que aciona o fluxo de trabalho. Você pode fornecer uma única `string` de evento, um `array` de eventos, um `array` de `types` (tipos) de eventos ou um `map` (mapa) de configuração de eventos que programe um fluxo de trabalho ou restrinja a execução do fluxo de trabalho a alterações em determinados arquivos, tags ou branches. Para obter uma lista de eventos disponíveis, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows)". +**Required**. The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. You can provide a single event `string`, `array` of events, `array` of event `types`, or an event configuration `map` that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see "[Events that trigger workflows](/articles/events-that-trigger-workflows)." {% data reusables.github-actions.actions-on-examples %} ## `on..types` -Seleciona os tipos de atividades que acionarão a execução de um fluxo de trabalho. A maioria dos eventos GitHub são acionados por mais de um tipo de atividade. Por exemplo, o evento para o recurso release (versão) é acionado quando uma versão é `published` (publicada), `unpublished` (a publicação é cancelada), `created` (criada), `edited` (editada), `deleted` (excluída) ou `prereleased` (versão prévia). A palavra-chave `types` (tipos) permite que você limite a atividade que faz com que o fluxo de trabalho seja executado. Quando somente um tipo de atividade aciona um evento de webhook, a palavra-chave `types` (tipos) é desnecessária. +Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is `published`, `unpublished`, `created`, `edited`, `deleted`, or `prereleased`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary. -É possível usar um array de `types` (tipos) de evento. Para obter mais informações sobre cada evento e seus tipos de atividades, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows#webhook-events)". +You can use an array of event `types`. For more information about each event and their activity types, see "[Events that trigger workflows](/articles/events-that-trigger-workflows#webhook-events)." ```yaml # Trigger the workflow on release activity @@ -50,13 +50,13 @@ on: ## `on..` -Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado em branches ou tags específicos. Para um evento de `pull_request`, são avaliados apenas os branches e tags na base. Se você definir apenas `tags` ou `branches`, o fluxo de trabalho não será executado para eventos que afetam o Git ref indefinido. +When using the `push` and `pull_request` events, you can configure a workflow to run on specific branches or tags. For a `pull_request` event, only branches and tags on the base are evaluated. If you define only `tags` or only `branches`, the workflow won't run for events affecting the undefined Git ref. -As palavras-chave `branches`, `branches-ignore`, `tags`, and `tags-ignore` aceitam padrões do glob que usam caracteres como `*`, `**`, `+`, `?`, `!` e outros para corresponder a mais de um nome do branch ou tag. Se um nome contiver qualquer um desses caracteres e você quiser uma correspondência literal, você deverá *escapar* de cada um desses caracteres especiais com `\`. Para obter mais informações sobre padrões de glob, consulte a "[Folha de informações para filtrar padrões](#filter-pattern-cheat-sheet)". +The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." -### Exemplo: Incluindo branches e tags +### Example: Including branches and tags -Os padrões definidos nos `branches` e `tags` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**` corresponderá ao Git ref `refs/heads/releases/10`. +The patterns defined in `branches` and `tags` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**` will match the `refs/heads/releases/10` Git ref. ```yaml on: @@ -75,9 +75,9 @@ on: - v1.* # Push events to v1.0, v1.1, and v1.9 tags ``` -### Exemplo: Ignorando branches e tags +### Example: Ignoring branches and tags -Sempre que um padrão corresponde ao padrão `branches-ignore` ou `tags-ignore`, o fluxo de trabalho não será executado. Os padrões definidos em `branches-ignore` e `tags-ignore` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**-alpha` em `branches` corresponderá ao Git ref `refs/releases/beta/3-alpha`. +Anytime a pattern matches the `branches-ignore` or `tags-ignore` pattern, the workflow will not run. The patterns defined in `branches-ignore` and `tags-ignore` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**-alpha` in `branches` will match the `refs/releases/beta/3-alpha` Git ref. ```yaml on: @@ -93,19 +93,19 @@ on: - v1.* # Do not push events to tags v1.0, v1.1, and v1.9 ``` -### Excluir branches e tags +### Excluding branches and tags -Você pode usar dois tipos de filtros para impedir a execução de um fluxo de trabalho em pushes e pull requests para tags e branches. -- `branches` ou `branches-ignore` - não é possível usar os dois filtros `branches` e `branches-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `branches` quando você precisa filtrar branches para correspondências positivas e excluir branches. Use o filtro `branches-ignore` quando você só precisa excluir nomes de branches. -- `tags` ou `tags-ignore` - não é possível usar os dois filtros `tags` e `tags-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `tags` quando você precisa filtrar tags para correspondências positivas e excluir tags. Use o filtro `tags-ignore` quando você só precisa excluir nomes de tags. +You can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches. +- `branches` or `branches-ignore` - You cannot use both the `branches` and `branches-ignore` filters for the same event in a workflow. Use the `branches` filter when you need to filter branches for positive matches and exclude branches. Use the `branches-ignore` filter when you only need to exclude branch names. +- `tags` or `tags-ignore` - You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow. Use the `tags` filter when you need to filter tags for positive matches and exclude tags. Use the `tags-ignore` filter when you only need to exclude tag names. -### Exemplo: Usando padrões positivos e negativos +### Example: Using positive and negative patterns -Você pode excluir `tags` e `branches` usando o caractere `!`. A ordem de definição dos padrões é importante. - - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o Git ref. - - Um padrão positivo correspondente após uma correspondência negativa incluirá a Git ref novamente. +You can exclude `tags` and `branches` using the `!` character. The order that you define patterns matters. + - A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref. + - A matching positive pattern after a negative match will include the Git ref again. -O fluxo de trabalho a seguir será executado em pushes para `releases/10` ou `releases/beta/mona`, mas não em `releases/10-alpha` ou `releases/beta/3-alpha`, pois o padrão negativo `!releases/**-alpha` está na sequência do padrão positivo. +The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern. ```yaml on: @@ -117,13 +117,13 @@ on: ## `on..paths` -Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado quando pelo menos um arquivo não corresponde a `paths-ignore` ou pelo menos um arquivo modificado corresponde ao `paths` configurado. Flitros de caminho não são avaliados em pushes para tags. +When using the `push` and `pull_request` events, you can configure a workflow to run when at least one file does not match `paths-ignore` or at least one modified file matches the configured `paths`. Path filters are not evaluated for pushes to tags. -As palavras-chave `paths-ignore` e `paths` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de caminho. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)". +The `paths-ignore` and `paths` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." -### Exemplo: Ignorando caminhos +### Example: Ignoring paths -Quando todos os caminhos de nome correspondem a padrões em `paths-ignore`, o fluxo de trabalho não será executado. O {% data variables.product.prodname_dotcom %} avalia os padrões definidos em `paths-ignore` com relação ao nome do caminho. Um fluxo de trabalho com o seguinte filtro de caminho só será executado em eventos `push` que tiverem pelo menos um arquivo fora do diretório `docs` na raiz do repositório. +When all the path names match patterns in `paths-ignore`, the workflow will not run. {% data variables.product.prodname_dotcom %} evaluates patterns defined in `paths-ignore` against the path name. A workflow with the following path filter will only run on `push` events that include at least one file outside the `docs` directory at the root of the repository. ```yaml on: @@ -132,9 +132,9 @@ on: - 'docs/**' ``` -### Exemplo: Incluindo caminhos +### Example: Including paths -Se pelo menos um caminho corresponder a um padrão no filtro `paths`, o fluxo de trabalho será executado. Para acionar uma compilação sempre que você fizer push de um arquivo JavaScript, você pode usar um padrão curinga. +If at least one path matches a pattern in the `paths` filter, the workflow runs. To trigger a build anytime you push a JavaScript file, you can use a wildcard pattern. ```yaml on: @@ -143,19 +143,19 @@ on: - '**.js' ``` -### Excluir caminhos +### Excluding paths -Você pode excluir caminhos com dois tipos de filtros. Não é possível usar ambos os filtros para o mesmo evento em um fluxo de trabalho. -- `paths-ignore` - use o filtro `paths-ignore` quando você precisa somente excluir nomes de caminhos. -- `paths` - use o filtro `paths` quando você precisa filtrar caminhos para correspondências positivas e excluir caminhos. +You can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow. +- `paths-ignore` - Use the `paths-ignore` filter when you only need to exclude path names. +- `paths` - Use the `paths` filter when you need to filter paths for positive matches and exclude paths. -### Exemplo: Usando padrões positivos e negativos +### Example: Using positive and negative patterns -Você pode excluir `paths` usando o caractere `!`. A ordem de definição dos padrões é importante: - - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o caminho. - - Um padrão positivo correspondente após uma correspondência negativa incluirá o caminho novamente. +You can exclude `paths` using the `!` character. The order that you define patterns matters: + - A matching negative pattern (prefixed with `!`) after a positive match will exclude the path. + - A matching positive pattern after a negative match will include the path again. -Este exemplo é executado sempre que o evento `push` inclui um arquivo no diretório `sub-project` ou seus subdiretórios, a menos que o arquivo esteja no diretório `sub-project/docs`. Por exemplo, um push que alterou `sub-project/index.js` ou `sub-project/src/index.js` acionará uma execução de fluxo de trabalho, mas um push que altere somente`sub-project/docs/readme.md` não acionará. +This example runs anytime the `push` event includes a file in the `sub-project` directory or its subdirectories, unless the file is in the `sub-project/docs` directory. For example, a push that changed `sub-project/index.js` or `sub-project/src/index.js` will trigger a workflow run, but a push changing only `sub-project/docs/readme.md` will not. ```yaml on: @@ -165,39 +165,39 @@ on: - '!sub-project/docs/**' ``` -### Comparações Git diff +### Git diff comparisons {% note %} -**Observação:** Se você fizer push de mais de 1.000 commits, ou se {% data variables.product.prodname_dotcom %} não gerar o diff devido a um tempo limite, o fluxo de trabalho sempre será executado. +**Note:** If you push more than 1,000 commits, or if {% data variables.product.prodname_dotcom %} does not generate the diff due to a timeout, the workflow will always run. {% endnote %} -O filtro determina se um fluxo de trabalho deve ser executado avaliando os arquivos alterados e comparando-os à lista de `paths-ignore` ou `paths`. Se não houver arquivos alterados, o fluxo de trabalho não será executado. +The filter determines if a workflow should run by evaluating the changed files and running them against the `paths-ignore` or `paths` list. If there are no files changed, the workflow will not run. -O {% data variables.product.prodname_dotcom %} gera a lista de arquivos alterados usando diffs de dois pontos para pushes e diffs de três pontos para pull requests: -- **Pull requests:** diffs de três pontos são uma comparação entre a versão mais recente do branch de tópico e o commit onde o branch de tópico foi sincronizado pela última vez com o branch de base. -- **Pushes para branches existentes:** um diff de dois pontos compara os SHAs head e base, um com o outro. -- **Pushes para novos branches:** um diff de dois pontos compara o principal do ancestral do commit mais extenso que foi feito push. +{% data variables.product.prodname_dotcom %} generates the list of changed files using two-dot diffs for pushes and three-dot diffs for pull requests: +- **Pull requests:** Three-dot diffs are a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch. +- **Pushes to existing branches:** A two-dot diff compares the head and base SHAs directly with each other. +- **Pushes to new branches:** A two-dot diff against the parent of the ancestor of the deepest commit pushed. -Os diffs limitam-se a 300 arquivos. Se houver arquivos alterados que não correspondam aos primeiros 300 arquivos retornados pelo filtro, o fluxo de trabalho não será executado. Talvez seja necessário criar filtros mais específicos para que o fluxo de trabalho seja executado automaticamente. +Diffs are limited to 300 files. If there are files changed that aren't matched in the first 300 files returned by the filter, the workflow will not run. You may need to create more specific filters so that the workflow will run automatically. -Para obter mais informações, consulte "[Sobre comparação de branches em pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)". +For more information, see "[About comparing branches in pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)." {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## `on.workflow_call.inputs` -Ao usar a palavra-chave `workflow_call`, você poderá, opcionalmente, especificar entradas que são passadas para o fluxo de trabalho chamado no fluxo de trabalho de chamada. As entradas para fluxos de trabalho reutilizáveis são especificadas com o mesmo formato que entradas de ações. Para obter mais informações sobre as entradas, consulte "[Sintaxe de metadados para o GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". Para obter mais informações sobre a palavra-chave `workflow_call`, consulte "[Eventos que acionam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." -Além dos parâmetros de entrada padrão que estão disponíveis, `on.workflow_call.inputs` exige um parâmetro `tipo`. Para obter mais informações, consulte [`on.workflow_call.inputs..type`](#onworkflow_callinputsinput_idtype). +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call.inputs..type`](#onworkflow_callinputsinput_idtype). -Se um parâmetro `padrão` não fordefinido, o valor padrão da entrada será `falso` para um booleano, `0` para um número e `""` para uma string. +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. -No fluxo de trabalho chamado, você pode usar o contexto `entradas` para referir-se a uma entrada. +Within the called workflow, you can use the `inputs` context to refer to an input. -Se um fluxo de trabalho de chamada passar uma entrada que não é especificada no fluxo de trabalho de chamada, isso irá gerar um erro. +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. -### Exemplo +### Example {% raw %} ```yaml @@ -209,7 +209,7 @@ on: default: 'john-doe' required: false type: string - + jobs: print-username: runs-on: ubuntu-latest @@ -220,21 +220,21 @@ jobs: ``` {% endraw %} -Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." ## `on.workflow_call.inputs..type` -Necessário se a entrada for definida para a palavra-chave `on.workflow_call`. O valor deste parâmetro é uma string que especifica o tipo de dados da entrada. Este deve ser um dos valores a seguir: `booleano`, `número` ou `string`. +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. ## `on.workflow_call.secrets` -Um mapa dos segredos que pode ser usado no fluxo de trabalho de chamada. +A map of the secrets that can be used in the called workflow. -Dentro do fluxo de trabalho de chamada, você pode usar o contexto `segredos` para consultar um segredo. +Within the called workflow, you can use the `secrets` context to refer to a secret. -Se um fluxo de trabalho de chamada passar um segredo que não é especificado no fluxo de trabalho chamado, isso irá gerar um erro. +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. -### Exemplo +### Example {% raw %} ```yaml @@ -244,7 +244,7 @@ on: access-token: description: 'A token passed from the caller workflow' required: false - + jobs: pass-secret-to-action: runs-on: ubuntu-latest @@ -259,16 +259,16 @@ jobs: ## `on.workflow_call.secrets.` -Um identificador de string para associar ao segredo. +A string identifier to associate with the secret. ## `on.workflow_call.secrets..required` -Um booleano que especifica se o segredo deve ser fornecido. +A boolean specifying whether the secret must be supplied. {% endif %} ## `on.workflow_dispatch.inputs` -Ao usar o evento `workflow_dispatch`, você pode, opcionalmente, especificar as entradas que são passadas para o fluxo de trabalho. As entradas de fluxo de trabalho são especificadas no mesmo formato que as entradas de ações. Para obter mais informações sobre o formato, consulte "[Sintaxe de Metadados para o GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. ```yaml on: @@ -277,33 +277,43 @@ on: logLevel: description: 'Log level' required: true - default: 'warning' + default: 'warning' {% ifversion ghec or ghes > 3.3 or ghae-issue-5511 %} + type: choice + options: + - info + - warning + - debug {% endif %} tags: description: 'Test scenario tags' - required: false + required: false {% ifversion ghec or ghes > 3.3 or ghae-issue-5511 %} + type: boolean + environment: + description: 'Environment to run tests against' + type: environment + required: true {% endif %} ``` -O fluxo de trabalho acionado recebe as entradas no contexto `github.event.inputs`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)". +The triggered workflow receives the inputs in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)." ## `on.schedule` {% data reusables.repositories.actions-scheduled-workflow-example %} -Para obter mais informações sobre a sintaxe cron, consulte "[Eventos que acionam fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)". +For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## `permissões` +## `permissions` -Você pode modificar as permissões padrão concedidas ao `GITHUB_TOKEN`, adicionando ou removendo o acesso conforme necessário, para que você permita apenas o acesso mínimo necessário. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." -Você pode usar as permissões de `` como uma chave de nível superior, para aplicar a todos os trabalhos do fluxo de trabalho ou em trabalhos específicos. Ao adicionar a chave das `permissões` em um trabalho específico, todas as ações e comandos de execução dentro desse trabalho que usam o `GITHUB_TOKEN` ganham os direitos de acesso que você especificar. Para obter mais informações, consulte [`jobs..permissions`](#jobsjob_idpermissions). +You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify. For more information, see [`jobs..permissions`](#jobsjob_idpermissions). {% data reusables.github-actions.github-token-available-permissions %} {% data reusables.github-actions.forked-write-permission %} -### Exemplo +### Example -Este exemplo mostra as permissões que estão sendo definidas para o `GITHUB_TOKEN` que será aplicado a todos os trabalhos do fluxo de trabalho. É concedido acesso de leitura a todas as permissões. +This example shows permissions being set for the `GITHUB_TOKEN` that will apply to all jobs in the workflow. All permissions are granted read access. ```yaml name: "My workflow" @@ -319,30 +329,30 @@ jobs: ## `env` -Um `mapa` das variáveis de ambiente que estão disponíveis para as etapas de todos os trabalhos do fluxo de trabalho. Também é possível definir variáveis de ambiente que estão disponíveis apenas para as etapas de um único trabalho ou para uma única etapa. Para obter mais informações, consulte [`jobs..env`](#jobsjob_idenv) e [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -### Exemplo +### Example ```yaml env: SERVER: production ``` -## `padrões` +## `defaults` -Um `mapa` das configurações-padrão que serão aplicadas a todos os trabalhos do fluxo de trabalho. Você também pode definir as configurações-padrão disponíveis para um trabalho. Para obter mais informações, consulte [`jobs..defaults`](#jobsjob_iddefaults). +A `map` of default settings that will apply to all jobs in the workflow. You can also set default settings that are only available to a job. For more information, see [`jobs..defaults`](#jobsjob_iddefaults). {% data reusables.github-actions.defaults-override %} ## `defaults.run` -Você pode fornecer opções-padrão de `shell` e `working-directory` para todas as etapas de [`executar`](#jobsjob_idstepsrun) em um fluxo de trabalho. Você também pode definir as configurações-padrão para `execução` apenas disponíveis para um trabalho. Para obter mais informações, consulte [`jobs..defaults.run`](#jobsjob_iddefaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave. +You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a workflow. You can also set default settings for `run` that are only available to a job. For more information, see [`jobs..defaults.run`](#jobsjob_iddefaultsrun). You cannot use contexts or expressions in this keyword. {% data reusables.github-actions.defaults-override %} -### Exemplo +### Example ```yaml defaults: @@ -352,32 +362,32 @@ defaults: ``` {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} -## `concorrência` +## `concurrency` -A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão só pode usar o contexto [`github`](/actions/learn-github-actions/contexts#github-context). Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)". +Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." -Você também pode especificar `concorrência` no nível do trabalho. Para obter mais informações, consulte [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). +You can also specify `concurrency` at the job level. For more information, see [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). {% data reusables.actions.actions-group-concurrency %} {% endif %} ## `jobs` -A execução de um fluxo de trabalho consiste em um ou mais trabalhos. Por padrão, os trabalhos são executados paralelamente. Para executar trabalhos sequencialmente, você pode definir dependências em outros trabalhos usando a palavra-chave `jobs..needs`. +A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs..needs` keyword. -Cada trabalho é executado em um ambiente de executor especificado por `runs-on`. +Each job runs in a runner environment specified by `runs-on`. -Você pode executar quantos trabalhos desejar, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados. +You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -Se precisar encontrar o identificador exclusivo de uma tarefa em execução em um fluxo de trabalho, você poderá usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte "[Trabalhos do fluxo de trabalho](/rest/reference/actions#workflow-jobs)". +If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." ## `jobs.` -Crie um identificador para sua tarefa conferindo-lhe um nome único. A chave `job_id` é uma string, e seu valor é um mapa dos dados de configuração do trabalho. Você deve substituir `` por uma string exclusiva para o objeto `jobs`. `` deve começar por uma letra ou `_`, além de conter somente caracteres alfanuméricos, `-` ou `_`. +Create an identifier for your job by giving it a unique name. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `` with a string that is unique to the `jobs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. -### Exemplo +### Example -Neste exemplo, foram criados dois trabalhos e seus valores de `job_id` são `my_first_job` e `my_second_job`. +In this example, two jobs have been created, and their `job_id` values are `my_first_job` and `my_second_job`. ```yaml jobs: @@ -389,13 +399,13 @@ jobs: ## `jobs..name` -Nome do trabalho no {% data variables.product.prodname_dotcom %}. +The name of the job displayed on {% data variables.product.prodname_dotcom %}. ## `jobs..needs` -Identifica todos os trabalhos a serem concluídos com êxito antes da execução deste trabalho. Esse código pode ser uma string ou array de strings. Se houver falha em um trabalho, todos os trabalhos que dependem dele serão ignorados, a menos que os trabalhos usem uma expressão condicional que faça o trabalho continuar. +Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. -### Exemplo: Exigindo que trabalhos dependentes sejam bem-sucedidos +### Example: Requiring dependent jobs to be successful ```yaml jobs: @@ -406,15 +416,15 @@ jobs: needs: [job1, job2] ``` -Neste exemplo, `job1` deve ser concluído com êxito antes do início de `job2`, e `job3` aguarda a conclusão de `job1` e `job2`. +In this example, `job1` must complete successfully before `job2` begins, and `job3` waits for both `job1` and `job2` to complete. -Os trabalhos neste exemplo são executados sequencialmente: +The jobs in this example run sequentially: 1. `job1` 2. `job2` 3. `job3` -### Exemplo: Não exigindo que os trabalhos dependentes sejam bem-sucedidos +### Example: Not requiring dependent jobs to be successful ```yaml jobs: @@ -426,72 +436,72 @@ jobs: needs: [job1, job2] ``` -Neste exemplo, `job3` usa a expressão condicional `always()` para que ela sempre seja executada depois de `job1` e `job2` terem sido concluídos, independentemente de terem sido bem sucedidos. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)". +In this example, `job3` uses the `always()` conditional expression so that it always runs after `job1` and `job2` have completed, regardless of whether they were successful. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." ## `jobs..runs-on` -**Obrigatório**. O tipo de máquina na qual se executa o trabalho. A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado. +**Required**. The type of machine to run the job on. The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner. {% ifversion ghae %} ### {% data variables.actions.hosted_runner %}s -Se você usar um {% data variables.actions.hosted_runner %}, cada trabalho será executado em uma instância atualizada de um ambiente virtual especificado por `runs-on`. +If you use an {% data variables.actions.hosted_runner %}, each job runs in a fresh instance of a virtual environment specified by `runs-on`. -#### Exemplo +#### Example ```yaml runs-on: [AE-runner-for-CI] ``` -Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)". +For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." {% else %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Runners hospedados no {% data variables.product.prodname_dotcom %} +### {% data variables.product.prodname_dotcom %}-hosted runners -Se você usar um executor hospedado no {% data variables.product.prodname_dotcom %}, cada trabalho será executado em uma nova instância de um ambiente virtual especificado por `runs-on`. +If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a virtual environment specified by `runs-on`. -Os tipos de executor disponíveis para {% data variables.product.prodname_dotcom %} são: +Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.supported-github-runners %} -#### Exemplo +#### Example ```yaml runs-on: ubuntu-latest ``` -Para obter mais informações, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". +For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." {% endif %} -### Executores auto-hospedados +### Self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -#### Exemplo +#### Example ```yaml runs-on: [self-hosted, linux] ``` -Para obter mais informações, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" e "[Usar executores auto-hospedados em um fluxo de trabalho](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." +For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} ## `jobs..permissions` -Você pode modificar as permissões padrão concedidas ao `GITHUB_TOKEN`, adicionando ou removendo o acesso conforme necessário, para que você permita apenas o acesso mínimo necessário. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." -Ao especificar a permissão de uma definição de trabalho, você pode configurar um conjunto diferente de permissões para o `GITHUB_TOKEN` para cada trabalho, se necessário. Como alternativa, você pode especificar as permissões para todas as tarefas do fluxo de trabalho. Para informações sobre como definir permissões no nível do fluxo de trabalho, consulte [`permissões`](#permissions). +By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](#permissions). {% data reusables.github-actions.github-token-available-permissions %} {% data reusables.github-actions.forked-write-permission %} -### Exemplo +### Example -Este exemplo mostra as permissões que estão sendo definidas para o `GITHUB_TOKEN` que só se aplicará ao trabalho denominado `stale`. O acesso de gravação é concedido para os escopos dos `problemas` e `pull-requests`. Todos os outros escopos não terão acesso. +This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access. ```yaml jobs: @@ -510,18 +520,18 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae or ghec %} ## `jobs..environment` -O ambiente ao qual o trabalho faz referência. Todas as regras de proteção do ambiente têm de ser aprovadas para que um trabalho que faça referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". +The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." -Você pode fornecer o ambiente apenas como o `nome` do ambiente, ou como um objeto de ambiente com o `nome` e `url`. A URL é mapeada com `environment_url` na API de implantações. Para obter mais informações sobre a API de implantações, consulte "[Implantações](/rest/reference/repos#deployments)". +You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)." -#### Exemplo de uso de um único nome de ambiente +#### Example using a single environment name {% raw %} ```yaml -ambiente: staging_environment +environment: staging_environment ``` {% endraw %} -#### Exemplo de uso de nome de ambiente e URL +#### Example using environment name and URL ```yaml environment: @@ -529,9 +539,9 @@ environment: url: https://github.com ``` -A URL pode ser uma expressão e pode usar qualquer contexto, exceto para o contexto [`segredos`](/actions/learn-github-actions/contexts#contexts). Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)". +The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." -### Exemplo +### Example {% raw %} ```yaml environment: @@ -546,26 +556,26 @@ environment: {% note %} -**Observação:** Quando a concorrência é especificada no nível do trabalho, não se garante a ordem para trabalhos ou execuções que são enfileiradas em 5 minutos uma da outra. +**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other. {% endnote %} -A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão pode usar qualquer contexto, exceto para o contexto de `segredos`. Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)". +Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." -Você também pode especificar `concorrência` no nível do fluxo de trabalho. Para obter mais informações, consulte [`concorrência`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency). +You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency). {% data reusables.actions.actions-group-concurrency %} {% endif %} ## `jobs..outputs` -Um `mapa` de saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs..needs`](#jobsjob_idneeds). +A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs..needs`](#jobsjob_idneeds). -As saídas de trabalho são strings e saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}. +Job outputs are strings, and job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. -Para usar as saídas de trabalho em um trabalho dependente, você poderá usar o contexto `needs`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#needs-context)". +To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)." -### Exemplo +### Example {% raw %} ```yaml @@ -591,11 +601,11 @@ jobs: ## `jobs..env` -Um `map` (mapa) das variáveis de ambiente que estão disponíveis para todos as etapas do trabalho. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou uma etapa individual. Para obter mais informações, consulte [`env`](#env) e [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -### Exemplo +### Example ```yaml jobs: @@ -606,19 +616,19 @@ jobs: ## `jobs..defaults` -Um `mapa` com as configurações- padrão que serão aplicadas a todas as etapas do trabalho. Você também pode definir as configurações-padrão para todo o fluxo de trabalho. Para obter mais informações, consulte [`padrão`](#defaults). +A `map` of default settings that will apply to all steps in the job. You can also set default settings for the entire workflow. For more information, see [`defaults`](#defaults). {% data reusables.github-actions.defaults-override %} ## `jobs..defaults.run` -Forneça o `shell` e `working-directory` para todas as etapas do trabalho `executar`. Não são permitidos contexto e expressão nesta seção. +Provide default `shell` and `working-directory` to all `run` steps in the job. Context and expression are not allowed in this section. -Você pode fornecer as opções-padrão de `shell` e `working-directory` para todas as etapas de [`execução`](#jobsjob_idstepsrun) de um trabalho. Você também pode definir as configurações-padrão para `execução` para todo o fluxo de trabalho. Para obter mais informações, consulte [`jobs.defaults.run`](#defaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave. +You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`jobs.defaults.run`](#defaultsrun). You cannot use contexts or expressions in this keyword. {% data reusables.github-actions.defaults-override %} -### Exemplo +### Example ```yaml jobs: @@ -632,17 +642,17 @@ jobs: ## `jobs..if` -Você pode usar a condicional `if` (se) para evitar que um trabalho seja executado a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional. +You can use the `if` conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional. -{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". +{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." ## `jobs..steps` -Trabalhos contêm sequências de tarefas chamadas `steps`. As etapas podem executar comandos, executar trabalhos de configuração ou executar ações no seu repositório, em repositórios públicos, ou ações publicadas em registros do Docker. Nem todas as etapas executam ações, mas todas as ações são executadas como etapas. Cada etapa é executada em seu próprio processo no ambiente do executor, tendo acesso ao espaço de trabalho e ao sistema de arquivos. Como as etapas são executadas em seus próprios processos, as alterações nas variáveis de ambiente não são preservadas entre as etapas. O {% data variables.product.prodname_dotcom %} fornece etapas integradas para configurar e concluir trabalhos. +A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job. -Você pode executar quantas etapas quiser, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados. +You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. -### Exemplo +### Example {% raw %} ```yaml @@ -668,17 +678,17 @@ jobs: ## `jobs..steps[*].id` -Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à etapa em contextos. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)". +A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." ## `jobs..steps[*].if` -Você pode usar a condicional `if` (se) para evitar que uma etapa trabalho seja executada a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional. +You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional. -{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". +{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." -### Exemplo: Usando contextos +### Example: Using contexts - Essa etapa somente é executada quando o tipo de evento é uma `pull_request` e a ação do evento é `unassigned` (não atribuída). + This step only runs when the event type is a `pull_request` and the event action is `unassigned`. ```yaml steps: @@ -687,9 +697,9 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -### Exemplo: Usando funções de verificação de status +### Example: Using status check functions -A função `my backup step` (minha etapa de backup) somente é executada quando houver falha em uma etapa anterior do trabalho. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)". +The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." ```yaml steps: @@ -702,22 +712,22 @@ steps: ## `jobs..steps[*].name` -Nome da etapa no {% data variables.product.prodname_dotcom %}. +A name for your step to display on {% data variables.product.prodname_dotcom %}. ## `jobs..steps[*].uses` -Seleciona uma ação para executar como parte de uma etapa no trabalho. A ação é uma unidade reutilizável de código. Você pode usar uma ação definida no mesmo repositório que o fluxo de trabalho, um repositório público ou em uma [imagem publicada de contêiner Docker](https://hub.docker.com/). +Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/). -É altamente recomendável incluir a versão da ação que você está usando ao especificar um número de tag Docker, SHA ou ref do Git. Se você não especificar uma versão, ela poderá interromper seus fluxos de trabalho ou causar um comportamento inesperado quando o proprietário da ação publicar uma atualização. -- Usar o commit SHA de uma versão de ação lançada é a maneira mais garantida de obter estabilidade e segurança. -- Usar a versão principal da ação permite receber correções importantes e patches de segurança sem perder a compatibilidade. Fazer isso também garante o funcionamento contínuo do fluxo de trabalho. -- Usar o branch-padrão de uma ação pode ser conveniente, mas se alguém lançar uma nova versão principal com uma mudança significativa, seu fluxo de trabalho poderá ter problemas. +We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update. +- Using the commit SHA of a released action version is the safest for stability and security. +- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work. +- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break. -Algumas ações requerem entradas que devem ser definidas com a palavra-chave [`with`](#jobsjob_idstepswith) (com). Revise o arquivo README da ação para determinar as entradas obrigatórias. +Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required. -Ações são arquivos JavaScript ou contêineres Docker. Se a ação em uso for um contêiner do Docker, você deverá executar o trabalho em um ambiente do Linux. Para obter mais detalhes, consulte [`runs-on`](#jobsjob_idruns-on). +Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on). -### Exemplo: Usando ações de versão +### Example: Using versioned actions ```yaml steps: @@ -731,11 +741,11 @@ steps: - uses: actions/checkout@main ``` -### Exemplo: Usando uma ação pública +### Example: Using a public action `{owner}/{repo}@{ref}` -É possível especificar um branch, ref, ou SHA em um repositório público de {% data variables.product.prodname_dotcom %}. +You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository. ```yaml jobs: @@ -749,11 +759,11 @@ jobs: uses: actions/aws@v2.0.1 ``` -### Exemplo: Usando uma ação pública em um subdiretório +### Example: Using a public action in a subdirectory `{owner}/{repo}/{path}@{ref}` -Subdiretório em um repositório público do {% data variables.product.prodname_dotcom %} em um branch, ref ou SHA específico. +A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA. ```yaml jobs: @@ -763,11 +773,11 @@ jobs: uses: actions/aws/ec2@main ``` -### Exemplo: Usando uma ação no mesmo repositório que o fluxo de trabalho +### Example: Using an action in the same repository as the workflow `./path/to/dir` -Caminho para o diretório que contém a ação no repositório do seu fluxo de trabalho. Você deve reservar seu repositório antes de usar a ação. +The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action. ```yaml jobs: @@ -779,54 +789,54 @@ jobs: uses: ./.github/actions/my-action ``` -### Exemplo: Usando uma ação do Docker Hub +### Example: Using a Docker Hub action `docker://{image}:{tag}` -Imagem Docker publicada no [Docker Hub](https://hub.docker.com/). +A Docker image published on [Docker Hub](https://hub.docker.com/). ```yaml -empregos: +jobs: my_first_job: - passos: - - nome: Meu primeiro passo - usa: docker://alpine:3.8 + steps: + - name: My first step + uses: docker://alpine:3.8 ``` {% ifversion fpt or ghec %} -#### Exemplo: Usando o {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} +#### Example: Using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} `docker://{host}/{image}:{tag}` -Uma imagem Docker em {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}. +A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}. ```yaml jobs: - meu_primeiro_trabalho: + my_first_job: steps: - - name: minha primeira etapa + - name: My first step uses: docker://ghcr.io/OWNER/IMAGE_NAME ``` {% endif %} -#### Exemplo: Usando uma ação do registro público do Docker +#### Example: Using a Docker public registry action `docker://{host}/{image}:{tag}` -Imagem Docker em um registro público. Este exemplo usa o Registro de Contêiner do Google em `gcr.io`. +A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`. ```yaml jobs: - meu_primeiro_trabalho: + my_first_job: steps: - - name: minha primeira etapa + - name: My first step uses: docker://gcr.io/cloud-builders/gradle ``` -### Exemplo: Usando uma ação dentro de um repositório privado diferente do fluxo de trabalho +### Example: Using an action inside a different private repository than the workflow -Seu fluxo de trabalho deve fazer checkout no repositório privado e referenciar a ação localmente. Gere um token de acesso pessoal e adicione o token como um segredo criptografado. Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)". +Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." -Substitua `PERSONAL_ACCESS_TOKEN` no exemplo pelo nome do seu segredo. +Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret. {% raw %} ```yaml @@ -847,20 +857,20 @@ jobs: ## `jobs..steps[*].run` -Executa programas de linha de comando usando o shell do sistema operacional. Se você não informar um `name`, o nome da etapa será configurado por padrão como o texto indicado no comando `run`. +Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command. -Por padrão, os comandos run usam shells de não login. Você pode escolher um shell diferente e personalizar o shell usado para executar comandos. Para obter mais informações, consulte [`trabalhos..steps[*].shell`](#jobsjob_idstepsshell). +Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell). -Cada palavra-chave `run` representa um novo processo e shell no ambiente do executor. Quando você fornece comandos de várias linhas, cada linha será executada no mesmo shell. Por exemplo: +Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example: -* Um comando de linha única: +* A single-line command: ```yaml - name: Install Dependencies run: npm install ``` -* Um comando de várias linhas: +* A multi-line command: ```yaml - name: Clean install dependencies and build @@ -869,7 +879,7 @@ Cada palavra-chave `run` representa um novo processo e shell no ambiente do exec npm run build ``` -Com a palavra-chave `working-directory` (diretório de trabalho), é possível especificar o diretório de trabalho de onde o comando será executado. +Using the `working-directory` keyword, you can specify the working directory of where to run the command. ```yaml - name: Clean temp directory @@ -879,19 +889,19 @@ Com a palavra-chave `working-directory` (diretório de trabalho), é possível e ## `jobs..steps[*].shell` -Você pode anular as configurações padrão de shell no sistema operacional do executor usando a palavra-chave `shell`. É possível usar palavras-chave integradas a `shell` ou definir um conjunto personalizado de opções de shell. O comando do shell que é executado internamente executa um arquivo temporário que contém os comandos especificados na palavra-chave `executar`. +You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword. -| Plataforma compatível | Parâmetro `shell` | Descrição | Comando executado internamente | -| --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| Todas | `bash` | O shell padrão em plataformas que não sejam Windows como uma alternativa para `sh`. Ao especificar um shell bash no Windows, é utilizado o shell bash incluído no Git para Windows. | `bash --noprofile --norc -eo pipefail {0}` | -| Todas | `pwsh` | Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. | `pwsh -command ". '{0}'"` | -| Todas | `python` | Executa o comando python. | `python {0}` | -| Linux / macOS | `sh` | Comportamento alternativo para plataformas que não sejam Windows se nenhum shell for fornecido e o `bash` não for encontrado no caminho. | `sh -e {0}` | -| Windows | `cmd` | O {% data variables.product.prodname_dotcom %} anexa a extensão `.cmd` ao nome do script e a substitui por `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `pwsh` | Essa é a shell padrão usada no Windows. Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. Se o seu executor do Windows auto-hospedado não tiver o _PowerShell Core_ instalado, será usado o _PowerShell Desktop_. | `pwsh -command ". '{0}'"`. | -| Windows | `powershell` | O PowerShell Desktop. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. | `powershell -command ". '{0}'"`. | +| Supported platform | `shell` parameter | Description | Command run internally | +|--------------------|-------------------|-------------|------------------------| +| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | +| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | +| All | `python` | Executes the python command. | `python {0}` | +| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | -### Exemplo: Executando um script usando o bash +### Example: Running a script using bash ```yaml steps: @@ -900,7 +910,7 @@ steps: shell: bash ``` -### Exemplo: Executando um script usando `cmd` do Windows +### Example: Running a script using Windows `cmd` ```yaml steps: @@ -909,7 +919,7 @@ steps: shell: cmd ``` -### Exemplo: Executando um script usando PowerShell Core +### Example: Running a script using PowerShell Core ```yaml steps: @@ -918,7 +928,7 @@ steps: shell: pwsh ``` -### Exemplo: Usar o PowerShell Desktop para executar um script +### Example: Using PowerShell Desktop to run a script ```yaml steps: @@ -927,7 +937,7 @@ steps: shell: powershell ``` -### Exemplo: Executando um script do Python +### Example: Running a python script ```yaml steps: @@ -938,11 +948,11 @@ steps: shell: python ``` -### Shell personalizado +### Custom shell -Você pode usar o valor `shell` em um string modelo usando `command […options] {0} [..more_options]`. O {% data variables.product.prodname_dotcom %} interpreta a primeira palavra da string delimitada por um espaço em branco como o comando e insere o nome do arquivo para o script temporário em `{0}`. +You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`. -Por exemplo: +For example: ```yaml steps: @@ -952,38 +962,38 @@ steps: shell: perl {0} ``` -O comando usado, `perl` neste exemplo, deve ser instalado no executor. +The command used, `perl` in this example, must be installed on the runner. -{% ifversion ghae %}Para instruções instruções sobre como ter certeza de que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". +{% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} -Para informações sobre o software incluído nos executores hospedados no GitHub, consulte "[Especificações para os executores hospedados no GitHub](/actions/reference/specifications-for-github-hosted-runners#supported-software)." +For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." {% endif %} -### Preferências de ação de erro e códigos de saída +### Exit codes and error action preference -Para palavras-chave de shell integradas, fornecemos os seguintes padrões usados por executores hospedados no {% data variables.product.prodname_dotcom %}. Você deve seguir estas diretrizes quando executar scripts shell. +For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts. - `bash`/`sh`: - - Comportamento de falha rápido que usa `set -eo pipefail`: Padrão para `bash` e `shell` embutido. Também é o padrão quando você não der opção em plataformas que não sejam Windows. - - Você pode cancelar o fail-fast e assumir o controle fornecendo uma string de modelo para as opções do shell. Por exemplo, `bash {0}`. - - Shells do tipo sh saem com o código de saída do último comando executado em um script, que também é o comportamento padrão das ações. O executor relatará o status da etapa como falha/êxito com base nesse código de saída. + - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms. + - You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`. + - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code. - `powershell`/`pwsh` - - Comportamento fail-fast quando possível. Para shell integrado `pwsh` e `powershell`, precederemos `$ErrorActionPreference = 'stop'` para conteúdos de script. - - Vincularemos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a scripts powershell para que os status da ação reflitam o código de saída mais recente do script. - - Os usuários podem sempre optar por não usar o shell integrado e fornecer uma opção personalizada, como: `pwsh -File {0}` ou `powershell -Command "& '{0}'"`, dependendo da situação. + - Fail-fast behavior when possible. For `pwsh` and `powershell` built-in shell, we will prepend `$ErrorActionPreference = 'stop'` to script contents. + - We append `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` to powershell scripts so action statuses reflect the script's last exit code. + - Users can always opt out by not using the built-in shell, and providing a custom shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need. - `cmd` - - Parece não haver uma forma de optar totalmente por um comportamento fail-fast que não seja gravar seu script para verificar cada código de erro e reagir de acordo. Como não podemos fornecer esse comportamento por padrão, você precisa gravá-lo em seu script. - - `cmd.exe` sairá com o nível de erro do último programa que executou e retornará o código de erro para o executor. Este comportamento é internamente consistente o padrão de comportamento anterior `sh` e `pwsh`, e é o padrão `cmd.exe`; portanto, ele fica intacto. + - There doesn't seem to be a way to fully opt into fail-fast behavior other than writing your script to check each error code and respond accordingly. Because we can't actually provide that behavior by default, you need to write this behavior into your script. + - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. This behavior is internally consistent with the previous `sh` and `pwsh` default behavior and is the `cmd.exe` default, so this behavior remains intact. ## `jobs..steps[*].with` -Um `map` (mapa) dos parâmetros de entrada definidos pela ação. Cada parâmetro de entrada é um par chave/valor. Parâmetros de entrada são definidos como variáveis de ambiente. A variável é precedida por `INPUT_` e convertida em letras maiúsculas. +A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case. -### Exemplo +### Example -Define os três parâmetros de entrada (`first_name`, `middle_name` e `last_name`) definidos pela ação `hello_world`. Essas variáveis de entrada estarão acessíveis para a ação `hello-world` como variáveis de ambiente `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` e `INPUT_LAST_NAME`. +Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables. ```yaml jobs: @@ -999,9 +1009,9 @@ jobs: ## `jobs..steps[*].with.args` -Uma `string` que define as entradas para um contêiner Docker. O {% data variables.product.prodname_dotcom %} entrega os `args` ao `ENTRYPOINT` do contêiner quando o contêiner inicia. Um `array de strings` não é compatível com esse parâmetro. +A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter. -### Exemplo +### Example {% raw %} ```yaml @@ -1014,17 +1024,17 @@ steps: ``` {% endraw %} -`args` são usados em substituição à instrução `CMD` em um `Dockerfile`. Se você usar `CMD` no `Dockerfile`, use as diretrizes ordenadas por preferência: +The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference: -1. Documente os argumentos necessários no README das ações e omita-os da instrução `CMD`. -1. Use padrões que permitam o uso da ação sem especificação de `args`. -1. Se a ação expõe um sinalizador `--help` ou similar, use isso como padrão para que a ação se documente automaticamente. +1. Document required arguments in the action's README and omit them from the `CMD` instruction. +1. Use defaults that allow using the action without specifying any `args`. +1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting. ## `jobs..steps[*].with.entrypoint` -Anula o `ENTRYPOINT` Docker no `Dockerfile` ou define-o caso ainda não tenha sido especificado. Diferentemente da instrução Docker `ENTRYPOINT` que tem um formulário shell e exec, a palavra-chave `entrypoint` aceita apena uma única string que define o executável. +Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run. -### Exemplo +### Example ```yaml steps: @@ -1034,62 +1044,62 @@ steps: entrypoint: /a/different/executable ``` -A palavra-chave `entrypoint` é para ser usada com ações de contêiner Docker, mas você também pode usá-la com ações JavaScript que não definem nenhuma entrada. +The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. ## `jobs..steps[*].env` -Define variáveis de ambiente para etapas a serem usadas no ambiente do executor. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou para um trabalho. Para obter mais informações, consulte [`env`](#env) e [`jobs..env`](#jobsjob_idenv). +Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs..env`](#jobsjob_idenv). {% data reusables.repositories.actions-env-var-note %} -Ações públicas podem especificar variáveis de ambiente esperadas no arquivo LEIAME. Se você está configurando um segredo em uma variável de ambiente, use o contexto `secrets`. Para obter mais informações, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" e "[Contextos](/actions/learn-github-actions/contexts)". +Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)." -### Exemplo +### Example {% raw %} ```yaml steps: - - name: minha primeira ação - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - FIRST_NAME: Mona - LAST_NAME: Octocat + - name: My first action + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + FIRST_NAME: Mona + LAST_NAME: Octocat ``` {% endraw %} ## `jobs..steps[*].continue-on-error` -Impede a falha de um trabalho se uma etapa não funcionar. Defina `true` (verdadeiro) para permitir que um trabalho aconteça quando essa etapa falhar. +Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails. ## `jobs..steps[*].timeout-minutes` -Número máximo de minutos para executar a etapa antes de interromper o processo. +The maximum number of minutes to run the step before killing the process. ## `jobs..timeout-minutes` -Número máximo de minutos para permitir a execução de um trabalho o antes que o {% data variables.product.prodname_dotcom %} o cancele automaticamente. Padrão: 360 +The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 -Se o tempo-limite exceder o tempo limite de execução do trabalho para o runner, o trabalho será cancelada quando o tempo limite de execução for atingido. Para obter mais informações sobre limites de tempo de execução do trabalho, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#usage-limits)". +If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#usage-limits)." ## `jobs..strategy` -Estratégias criam matrizes de compilação para os trabalhos. Você pode definir variações diferentes variações nas quais executar os trabalhos. +A strategy creates a build matrix for your jobs. You can define different variations to run each job in. ## `jobs..strategy.matrix` -Você pode definir uma matriz de diferentes configurações de trabalho. Uma matriz permite que você crie vários trabalhos que realizam a substituição de variável em uma definição de trabalho único. Por exemplo, você pode usar uma matriz para criar trabalhos para mais de uma versão compatível de uma linguagem de programação, sistema operacional ou ferramenta. Uma matriz reutiliza a configuração do trabalho e cria trabalho para cada matriz que você configurar. +You can define a matrix of different job configurations. A matrix allows you to create multiple jobs by performing variable substitution in a single job definition. For example, you can use a matrix to create jobs for more than one supported version of a programming language, operating system, or tool. A matrix reuses the job's configuration and creates a job for each matrix you configure. {% data reusables.github-actions.usage-matrix-limits %} -Cada opção que você define na `matriz` tem uma chave e um valor. As chaves que você define tornam-se propriedades no contexto da `matriz` e você pode fazer referência à propriedade em outras áreas do seu arquivo de fluxo de trabalho. Por exemplo, se você definir a chave `os` que contém um array de sistemas operacionais, você poderá usar a propriedade `matrix.os` como o valor da palavra-chave `runs-on` para criar um trabalho para cada sistema operacional. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)". +Each option you define in the `matrix` has a key and value. The keys you define become properties in the `matrix` context and you can reference the property in other areas of your workflow file. For example, if you define the key `os` that contains an array of operating systems, you can use the `matrix.os` property as the value of the `runs-on` keyword to create a job for each operating system. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." -A ordem que você define uma `matriz` importa. A primeira opção que você definir será a primeira que será executada no seu fluxo de trabalho. +The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. -### Exemplo: Executando várias versões do Node.js +### Example: Running multiple versions of Node.js -Você pode especificar uma matriz ao fornecer um array para as opções de configuração. Por exemplo, se o executor for compatível com as versões 10, 12 e 14 do Node.js versões, você poderá especificar um array dessas versões na `matriz`. +You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 10, 12, and 14, you could specify an array of those versions in the `matrix`. -Este exemplo cria uma matriz de três trabalhos, definindo a chave `nó` para um array de três versões do Node.js. Para usar a matriz, o exemplo define a propriedade do contexto `matrix.node` como o valor do parâmetro `setup-node` de entrada da ação `node-version`. Como resultado, três trabalhos serão executados, cada uma usando uma versão diferente do Node.js. +This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version. {% raw %} ```yaml @@ -1105,14 +1115,14 @@ steps: ``` {% endraw %} -A ação setup-node `` é a forma recomendada de configurar uma versão do Node.js ao usar executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a ação [`setup-node`](https://github.com/actions/setup-node). +The `setup-node` action is the recommended way to configure a Node.js version when using {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see the [`setup-node`](https://github.com/actions/setup-node) action. -### Exemplo: Executando com vários sistemas operacionais +### Example: Running with multiple operating systems -Você pode criar uma matriz para executar fluxos de trabalho em mais de um sistema operacional do executor. Você também pode especificar mais de uma configuração da matriz. Este exemplo cria uma matriz de 6 trabalhos: +You can create a matrix to run workflows on more than one runner operating system. You can also specify more than one matrix configuration. This example creates a matrix of 6 jobs: -- 2 sistemas operacionais especificados na array `os` -- 3 versões do Node.js especificadas na array do `nó` +- 2 operating systems specified in the `os` array +- 3 Node.js versions specified in the `node` array {% data reusables.repositories.actions-matrix-builds-os %} @@ -1130,13 +1140,13 @@ steps: ``` {% endraw %} -{% ifversion ghae %}Para encontrar opções de configuração suportadas para {% data variables.actions.hosted_runner %}s, consulte "[Especificações de software](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)". -{% else %}Para encontrar opções de configuração compatíveis com executores hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." +{% ifversion ghae %}To find supported configuration options for {% data variables.actions.hosted_runner %}s, see "[Software specifications](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)." +{% else %}To find supported configuration options for {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." {% endif %} -### Exemplo: Incluindo valores adicionais em combinações +### Example: Including additional values into combinations -Você pode adicionar opções de configurações para um trabalho de matriz de compilação existente. Por exemplo, se você quer usar uma versão específica do `npm` quando o trabalho que usa o `windows-latest` e a versão 8 do `nó` é executado, você pode usar `incluir` para especificar a opção adicional. +You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 8 of `node` runs, you can use `include` to specify that additional option. {% raw %} ```yaml @@ -1154,9 +1164,9 @@ strategy: ``` {% endraw %} -### Exemplo: Incluindo novas combinações +### Example: Including new combinations -Você pode usar `incluir` para adicionar novos trabalhos a uma matriz de criação. Qualquer configuração sem correspondência de incluir será adicionadas à matriz. Por exemplo, se você quiser usar a versão 14 do `nó` para compilar em vários sistemas operacionais, mas quiser uma tarefa experimental extra usando o node 15 no Ubuntu, você poderá usar `incluir` para especificar essa tarefa adicional. +You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 14 to build on multiple operating systems, but wanted one extra experimental job using node version 15 on Ubuntu, you can use `include` to specify that additional job. {% raw %} ```yaml @@ -1172,9 +1182,9 @@ strategy: ``` {% endraw %} -### Exemplo: Excluindo configurações de uma matriz +### Example: Excluding configurations from a matrix -Você pode remover uma configuração específica definida na matriz de compilação usando a opção `exclude` (excluir). `exclude` remove um trabalho definido pela matriz de compilação. O número de trabalhos é o produto cruzado do número de sistemas operacionais (`os`) incluídos nos arrays fornecidos por você, menos quaisquer subtrações (`exclude`). +You can remove a specific configurations defined in the build matrix using the `exclude` option. Using `exclude` removes a job defined by the build matrix. The number of jobs is the cross product of the number of operating systems (`os`) included in the arrays you provide, minus any subtractions (`exclude`). {% raw %} ```yaml @@ -1192,23 +1202,23 @@ strategy: {% note %} -**Observação:** Todas as combinações de `incluir` são processadas depois de `excluir`. Isso permite que você use `incluir` para voltar a adicionar combinações que foram excluídas anteriormente. +**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded. {% endnote %} -#### Usando variáveis de ambiente em uma matriz +#### Using environment variables in a matrix -Você pode adicionar variáveis de ambiente personalizadas para cada combinação de testes usando a chave `include`. Em seguida, você pode se referir às variáveis de ambiente personalizadas em um passo posterior. +You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. {% data reusables.github-actions.matrix-variable-example %} ## `jobs..strategy.fail-fast` -Quando definido como `true`, o {% data variables.product.prodname_dotcom %} cancela todos os trabalhos em andamento em caso de falha de algum trabalho de `matrix`. Padrão: `true` +When set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs if any `matrix` job fails. Default: `true` ## `jobs..strategy.max-parallel` -Número máximo de trabalhos que podem ser executados simultaneamente ao usar uma estratégia de trabalho de `matrix`. Por padrão, o {% data variables.product.prodname_dotcom %} maximizará o número de trabalhos executados em paralelo dependendo dos executores disponíveis nas máquinas virtuais hospedadas no {% data variables.product.prodname_dotcom %}. +The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. By default, {% data variables.product.prodname_dotcom %} will maximize the number of jobs run in parallel depending on the available runners on {% data variables.product.prodname_dotcom %}-hosted virtual machines. ```yaml strategy: @@ -1217,11 +1227,11 @@ strategy: ## `jobs..continue-on-error` -Impede que ocorra falha na execução de um fluxo de trabalho quando ocorrer uma falha em um trabalho. Defina como `verdadeiro` para permitir que uma execução de um fluxo de trabalho passe quando este trabalho falhar. +Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails. -### Exemplo: Evitando uma falha específica na matriz de trabalho por falha na execução de um fluxo de trabalho +### Example: Preventing a specific failing matrix job from failing a workflow run -Você pode permitir que as tarefas específicas em uma matriz de tarefas falhem sem que ocorra falha na execução do fluxo de trabalho. Por exemplo, se você deseja permitir apenas um trabalho experimental com o `nó` definido como `15` sem falhar a execução do fluxo de trabalho. +You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run. {% raw %} ```yaml @@ -1242,11 +1252,11 @@ strategy: ## `jobs..container` -Contêiner para executar qualquer etapa em um trabalho que ainda não tenha especificado um contêiner. Se você tiver etapas que usam ações de script e de contêiner, as ações de contêiner serão executadas como contêineres irmãos na mesma rede e com as mesmas montagens de volume. +A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts. -Se você não definir um `container`, todas as etapas serão executadas diretamente no host especificado por `runs-on`, a menos que uma etapa se refira a uma ação configurada para execução em um contêiner. +If you do not set a `container`, all steps will run directly on the host specified by `runs-on` unless a step refers to an action configured to run in a container. -### Exemplo +### Example ```yaml jobs: @@ -1262,7 +1272,7 @@ jobs: options: --cpus 1 ``` -Ao especificar somente uma imagem de contêiner, você pode omitir a palavra-chave `image`. +When you only specify a container image, you can omit the `image` keyword. ```yaml jobs: @@ -1272,13 +1282,13 @@ jobs: ## `jobs..container.image` -Imagem Docker a ser usada como contêiner para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um nome de registro. +The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a registry name. ## `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -### Exemplo +### Example {% raw %} ```yaml @@ -1292,23 +1302,23 @@ container: ## `jobs..container.env` -Define um `mapa` das variáveis de ambiente no contêiner. +Sets a `map` of environment variables in the container. ## `jobs..container.ports` -Define um `array` de portas para expor no contêiner. +Sets an `array` of ports to expose on the container. ## `jobs..container.volumes` -Define um `array` de volumes para uso do contêiner. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host. +Sets an `array` of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. -Para especificar um volume, especifique o caminho de origem e destino: +To specify a volume, you specify the source and destination path: `:`. -`` é um nome de volume ou caminho absoluto na máquina host, e `` é um caminho absoluto no contêiner. +The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -### Exemplo +### Example ```yaml volumes: @@ -1319,11 +1329,11 @@ volumes: ## `jobs..container.options` -Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". +Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." {% warning %} -**Aviso:** A opção `--network` não é compatível. +**Warning:** The `--network` option is not supported. {% endwarning %} @@ -1331,41 +1341,41 @@ Opções adicionais de recursos do contêiner Docker. Para obter uma lista de op {% data reusables.github-actions.docker-container-os-support %} -Usado para hospedar contêineres de serviço para um trabalho em um fluxo de trabalho. Contêineres de serviço são úteis para a criação de bancos de dados ou serviços armazenamento em cache como o Redis. O executor cria automaticamente uma rede do Docker e gerencia o ciclo de vida dos contêineres do serviço. +Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers. -Se você configurar seu trabalho para ser executado em um contêiner, ou a sua etapa usar ações ao contêiner, você não precisará mapear as portas para acessar o serviço ou a ação. O Docker expõe automaticamente todas as portas entre os contêineres da mesma rede de ponte definida pelo usuário. Você pode fazer referência ao contêiner de serviço diretamente pelo seu nome de host. O nome do host é mapeado automaticamente com o nome da etiqueta que você configurar para o serviço no fluxo de trabalho. +If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow. -Se você configurar a tarefa para executar diretamente na máquina do executor e sua etapa não usar uma ação de contêiner, você deverá mapear todas as portas de contêiner de serviço do Docker necessárias para o host do Docker (a máquina do executor). Você pode acessar o contêiner de serviço usando host local e a porta mapeada. +If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port. -Para obter mais informações sobre as diferenças entre os contêineres de serviço de rede, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers)". +For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)." -### Exemplo: Usando host local +### Example: Using localhost -Este exemplo cria dois serviços: nginx e redis. Ao especificar a porta do host do Docker mas não a porta do contêiner, a porta do contêiner será atribuída aleatoriamente a uma porta livre. O {% data variables.product.prodname_dotcom %} define a porta de contêiner atribuída no contexto {% raw %}`${{job.services..ports}}`{% endraw %}. Neste exemplo, você pode acessar as portas do contêiner de serviço usando os contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} e {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}. +This example creates two services: nginx and redis. When you specify the Docker host port but not the container port, the container port is randomly assigned to a free port. {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services..ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts. ```yaml -serviços: +services: nginx: - imagem: nginx - # Mapeia a porta 8080 no host do Docker com a porta 80 no contêiner nginx - portas: + image: nginx + # Map port 8080 on the Docker host to port 80 on the nginx container + ports: - 8080:80 redis: - imagem: redis - # Mapeia a porta port 6379 TCP no host do Docker com uma porta livre aleatória no contêiner Redis - portas: + image: redis + # Map TCP port 6379 on Docker host to a random free port on the Redis container + ports: - 6379/tcp ``` ## `jobs..services..image` -Imagem Docker a ser usada como contêiner de serviço para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um nome de registro. +The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a registry name. ## `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -### Exemplo +### Example {% raw %} ```yaml @@ -1385,23 +1395,23 @@ services: ## `jobs..services..env` -Define um `maá` das variáveis de ambiente no contêiner do serviço. +Sets a `map` of environment variables in the service container. ## `jobs..services..ports` -Define um `array` de portas para expor no contêiner de serviço. +Sets an `array` of ports to expose on the service container. ## `jobs..services..volumes` -Define um `array` de volumes para uso do contêiner de serviço. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host. +Sets an `array` of volumes for the service container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. -Para especificar um volume, especifique o caminho de origem e destino: +To specify a volume, you specify the source and destination path: `:`. -`` é um nome de volume ou caminho absoluto na máquina host, e `` é um caminho absoluto no contêiner. +The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -### Exemplo +### Example ```yaml volumes: @@ -1412,38 +1422,38 @@ volumes: ## `jobs..services..options` -Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". +Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." {% warning %} -**Aviso:** A opção `--network` não é compatível. +**Warning:** The `--network` option is not supported. {% endwarning %} {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## `jobs..uses` -O local e a versão de um arquivo de fluxo de trabalho reutilizável para ser executado como job. +The location and version of a reusable workflow file to run as a job. `{owner}/{repo}/{path}/{filename}@{ref}` -`{ref}` pode ser um SHA, uma tag de de versão ou um nome de branch. Usar o commit SHA é o mais seguro para a estabilidade e segurança. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)." -### Exemplo +### Example {% data reusables.actions.uses-keyword-example %} -Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." ## `jobs..with` -Quando um trabalho é usado para chamar um fluxo de trabalho reutilizável, você pode usar `com` para fornecer um mapa de entradas que são passadas para o fluxo de trabalho de chamada. +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. -Qualquer entrada que você passe deve corresponder às especificações de entrada definidas no fluxo de trabalho de chamada. +Any inputs that you pass must match the input specifications defined in the called workflow. -Diferentemente de [`jobs..steps[*].with`](#jobsjob_idstepswith), as entradas que você passar com `jobs..with` não estão disponíveis como variáveis de ambiente no fluxo de trabalho de chamada. Ao invés disso, você pode fazer referência às entradas usando o contexto `entrada`. +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. -### Exemplo +### Example ```yaml jobs: @@ -1455,17 +1465,17 @@ jobs: ## `jobs..with.` -Um par composto de um identificador de string para a entrada e o valor da entrada. O identificador deve corresponder ao nome de uma entrada definida por [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) no fluxo de trabalho chamado. O tipo de dado do valor deve corresponder ao tipo definido por [`on.workflow_call.inputs..type`](#onworkflow_callinputsinput_idtype) no fluxo de trabalho chamado. +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call.inputs..type`](#onworkflow_callinputsinput_idtype) in the called workflow. -Contextos de expressão permitidos: `github` e `needs`. +Allowed expression contexts: `github`, and `needs`. ## `jobs..secrets` -Quando um trabalho é usado para chamar um fluxo de trabalho reutilizável, você pode usar `segredos` para fornecer um mapa de segredos que foram passados para o fluxo de trabalho chamado. +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. -Qualquer segredo que você passar deve corresponder aos nomes definidos no fluxo de trabalho chamado. +Any secrets that you pass must match the names defined in the called workflow. -### Exemplo +### Example {% raw %} ```yaml @@ -1479,66 +1489,66 @@ jobs: ## `jobs..secrets.` -Um par composto por um identificador string para o segredo e o valor do segredo. O identificador deve corresponder ao nome de um segredo definido por [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) no fluxo de trabalho chamado. +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. -Contextos de expressão permitidos: `github`, `needs` e `segredos`. +Allowed expression contexts: `github`, `needs`, and `secrets`. {% endif %} -## Folha de consulta de filtro padrão +## Filter pattern cheat sheet -Você pode usar caracteres especiais nos filtros de caminhos, branches e tags. +You can use special characters in path, branch, and tag filters. -- `*`: Corresponde a zero ou mais caracteres, mas não Corresponde ao caractere `/`. Por exemplo, `Octo*` corresponde a `Octocat`. -- `**`: Corresponde a zero ou mais de qualquer caractere. -- `?`: Corresponde a zero ou a um dos caracteres anteriores. -- `+`: Corresponde a um ou mais dos caracteres anteriores. -- `[]` Corresponde a um caractere listado entre colchetes ou incluído nos intervalos. Os intervalos só podem incluir valores de `a-z`, `A-Z`, e `0-9`. Por exemplo, o intervalo`[0-9a-z]` corresponde a qualquer letra maiúscula ou minúscula. Por exemplo, `[CB]at` corresponde a `Cat` ou `Bat` e `[1-2]00` corresponde a `100` e `200`. -- `!` No início de um padrão faz com que ele anule padrões positivos anteriores. Não tem nenhum significado especial caso não seja o primeiro caractere. +- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`. +- `**`: Matches zero or more of any character. +- `?`: Matches zero or one of the preceding character. +- `+`: Matches one or more of the preceding character. +- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. +- `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. -Os caracteres `*`, `[` e `!` são caracteres especiais em YAML. Se você iniciar um padrão com `*`, `[` ou `!`, você deverá colocá-lo entre aspas. +The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. ```yaml -# Válido +# Valid - '**/README.md' -# Inválido - Cria um erro de análise que -# impede que o seu fluxo de trabalho seja executado. +# Invalid - creates a parse error that +# prevents your workflow from running. - **/README.md ``` -Para obter mais informações sobre a sintaxe de filtros de branches, tags e caminhos, consulte "[`on..`](#onpushpull_requestbranchestags)" e "[`on..paths`](#onpushpull_requestpaths)". +For more information about branch, tag, and path filter syntax, see "[`on..`](#onpushpull_requestbranchestags)" and "[`on..paths`](#onpushpull_requestpaths)." -### Padrões para corresponder branches e tags +### Patterns to match branches and tags -| Padrão | Descrição | Exemplos de correspondências | -| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -| `feature/*` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). | `feature/my-branch`

    `feature/your-branch` | -| `feature/**` | `**` correspondem a qualquer caractere, incluindo a barra (`/`) em nomes de branches e tags. | `feature/beta-a/my-branch`

    `feature/your-branch`

    `feature/mona/the/octocat` | -| `main`

    `releases/mona-the-octocat` | Corresponde ao nome exato de um branch ou tag. | `main`

    `releases/mona-the-octocat` | -| `'*'` | Corresponde a todos os nomes de branches e tags que não contêm uma barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `main`

    `releases` | -| `'**'` | Corresponde a todos os nomes de branches e tags. Esse é o comportamento padrão quando você não usa um filtro de `branches` ou `tags`. | `all/the/branches`

    `every/tag` | -| `'*feature'` | O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `mona-feature`

    `feature`

    `ver-10-feature` | -| `v2*` | Corresponde aos nomes de branches e tags que iniciam com `v2`. | `v2`

    `v2.0`

    `v2.9` | -| `v[12].[0-9]+.[0-9]+` | Corresponde a todas as tags de versão de branch semântica com a versão principal 1 ou 2 | `v1.10.1`

    `v2.0.0` | +| Pattern | Description | Example matches | +|---------|------------------------|---------| +| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | `feature/my-branch`

    `feature/your-branch` | +| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`

    `feature/your-branch`

    `feature/mona/the/octocat` | +| `main`

    `releases/mona-the-octocat` | Matches the exact name of a branch or tag name. | `main`

    `releases/mona-the-octocat` | +| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `main`

    `releases` | +| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`

    `every/tag` | +| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`

    `feature`

    `ver-10-feature` | +| `v2*` | Matches branch and tag names that start with `v2`. | `v2`

    `v2.0`

    `v2.9` | +| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`

    `v2.0.0` | -### Padrões para corresponder a caminhos de arquivos +### Patterns to match file paths -Padrões de caminhos devem corresponder ao caminho completo e iniciar a partir da raiz do repositório. +Path patterns must match the whole path, and start from the repository's root. -| Padrão | Descrição das correspondências | Exemplos de correspondências | -| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `'*'` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `README.md`

    `server.rb` | -| `'*.jsx?'` | O caractere `?` corresponde a zero ou a um dos caracteres anteriores. | `page.js`

    `page.jsx` | -| `'**'` | `**` corresponde a qualquer caractere incluindo a barra (`/`). Esse é o comportamento padrão quando você não usa um filtro de `path`. | `all/the/files.md` | -| `'*.js'` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). Corresponde a todos os arquivos `.js` na raiz do repositório. | `app.js`

    `index.js` | -| `'**.js'` | Corresponde a todos os arquivos `.js` no repositório. | `index.js`

    `js/index.js`

    `src/js/app.js` | -| `docs/*` | Todos os arquivos dentro da raiz do diretório `docs`, na raiz do repositório. | `docs/README.md`

    `docs/file.txt` | -| `docs/**` | Qualquer arquivo no diretório `docs`, na raiz do repositório. | `docs/README.md`

    `docs/mona/octocat.txt` | -| `docs/**/*.md` | Um arquivo com um sufixo `.md` em qualquer local do diretório `docs`. | `docs/README.md`

    `docs/mona/hello-world.md`

    `docs/a/markdown/file.md` | -| `'**/docs/**'` | Qualquer arquivo no diretório `docs`, em qualquer local do repositório. | `docs/hello.md`

    `dir/docs/my-file.txt`

    `space/docs/plan/space.doc` | -| `'**/README.md'` | Um arquivo README.md em qualquer local do repositório. | `README.md`

    `js/README.md` | -| `'**/*src/**'` | Qualquer arquivo em uma pasta com o sufixo `src` em qualquer local do repositório. | `a/src/app.js`

    `my-src/code/js/app.js` | -| `'**/*-post.md'` | Um arquivo com o sufixo `-post.md` em qualquer local do repositório. | `my-post.md`

    `path/their-post.md` | -| `'**/migrate-*.sql'` | Um arquivo com o prefixo `migrate-` e sufixo `.sql` em qualquer local do repositório. | `migrate-10909.sql`

    `db/migrate-v1.0.sql`

    `db/sept/migrate-v1.sql` | -| `*.md`

    `!README.md` | Usar um sinal de exclamação (`!`) na frente de um padrão o anula. Quando um arquivo corresponde a um padrão e também corresponde a um padrão negativo definido posteriormente no arquivo, o arquivo não será incluído. | `hello.md`

    _Does not match_

    `README.md`

    `docs/hello.md` | -| `*.md`

    `!README.md`

    `README*` | Os padrões são verificados sequencialmente. Um padrão que anula um padrão anterior irá incluir caminhos de arquivos novamente. | `hello.md`

    `README.md`

    `README.doc` | +| Pattern | Description of matches | Example matches | +|---------|------------------------|-----------------| +| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `README.md`

    `server.rb` | +| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`

    `page.jsx` | +| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | `all/the/files.md` | +| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | `app.js`

    `index.js` +| `'**.js'` | Matches all `.js` files in the repository. | `index.js`

    `js/index.js`

    `src/js/app.js` | +| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | `docs/README.md`

    `docs/file.txt` | +| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`

    `docs/mona/octocat.txt` | +| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`

    `docs/mona/hello-world.md`

    `docs/a/markdown/file.md` +| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | `docs/hello.md`

    `dir/docs/my-file.txt`

    `space/docs/plan/space.doc` +| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`

    `js/README.md` +| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`

    `my-src/code/js/app.js` +| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`

    `path/their-post.md` | +| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`

    `db/migrate-v1.0.sql`

    `db/sept/migrate-v1.sql` | +| `*.md`

    `!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`

    _Does not match_

    `README.md`

    `docs/hello.md` | +| `*.md`

    `!README.md`

    `README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`

    `README.md`

    `README.doc`| diff --git a/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md index fb7e2518e5..86d82736f6 100644 --- a/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Deploying GitHub Advanced Security in your enterprise -intro: 'Aprenda a planejar, preparar e implementar uma abordagem em fases para implantar {% data variables.product.prodname_GH_advanced_security %} (GHAS) na sua empresa.' +intro: 'Learn how to plan, prepare, and implement a phased approach for rolling out {% data variables.product.prodname_GH_advanced_security %} (GHAS) in your enterprise.' product: '{% data reusables.gated-features.advanced-security %}' miniTocMaxHeadingLevel: 3 versions: @@ -14,388 +14,409 @@ topics: - Security --- -## Visão geral do processo de implantação +## Overview of the deployment process {% data reusables.security.overview-of-phased-approach-for-ghas-rollout %} -Para um resumo de alto nível dessas diferentes fases, consulte "[Visão geral da implantação de {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/overview-of-github-advanced-security-deployment). " +For a high-level summary of these different phases, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} Deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)." -Antes de iniciar a sua implantação, recomendamos que você reveja os pré-requisitos para a instalação do GHAS e as práticas recomendadas para implantar o GHAS em"[Visão geral da implantação de {% data variables.product.prodname_GH_advanced_security %}"](/admin/advanced-security/overview-of-github-advanced-security-deployment)". +Before starting your deployment, we recommend you review the prerequisites for installing GHAS and best practices for GHAS deployment in "[Overview of {% data variables.product.prodname_GH_advanced_security %} Deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)." -## {% octicon "milestone" aria-label="The milestone icon" %} Fase 0: Planejamento & início +## {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff {% note %} -Tempo estimado de {% octicon "clock" aria-label="Clock" %} **:** Estimamos que a fase 0 pode durar aproximadamente entre 1 e 4 semanas. Esta faixa pode variar dependendo das necessidades da sua versão e quaisquer aprovações necessárias que a sua empresa pode precisar no plano de implantação. +{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 0 may last roughly between 1-4 weeks. This range can vary depending on your release needs and any necessary approvals your company may need on the deployment plan. {% endnote %} -O objetivo da fase de planejamento e arranque é garantir que você tenha as suas pessoas, processos e tecnologias configuradoas e prontas para a implantação do GHAS. +The goal of the planning and kickoff phase is to ensure that you have all of your people, processes, and technologies set up and ready for implementing GHAS. -Para o ajudar a comprar dinheiro do patrocinador executivo, recomendamos preparar-se e alinhar-se em um plano e objetivos implementados antes de lançar o GHAS na sua empresa. +To help you reach buy-in from the executive sponsor, we recommend preparing and aligning on a rollout plan and goals before releasing GHAS in your enterprise. -Como parte de uma estratégia de implementação em fases, recomendamos que você identifique equipes ou aplicativos críticos de alto impacto que devem ser direcionados para se unir-se ao GHAS antes do restante da sua empresa. +As a part of a phased rollout strategy, we recommend that you identify high-impact and critical teams or applications that should be targeted to join GHAS before the rest of your enterprise. -Se uma implementação faseada não funcionar para a sua empresa, você poderá pular para a [fase do projeto piloto](#--phase-1-pilot-projects). +If a phased rollout doesn't work for your enterprise, you can skip to the [pilot project phase](#--phase-1-pilot-projects). -Se você está trabalhando com {% data variables.product.prodname_professional_services %}, durante esta fase, vocêtambém estabelecerá um plano sobre a forma como as suas equipes irão trabalhar em conjunto durante o processo de implementação. A equipe {% data variables.product.prodname_professional_services_team %} pode apoiar você com a criação do plano de implantação e metas faseadas, conforme necessário. +If you’re working with {% data variables.product.prodname_professional_services %}, during this phase you will also establish a plan for how your teams will work together throughout the rollout and implementation process. The {% data variables.product.prodname_professional_services_team %} team can support you with the creation of the phased rollout plan and goals as needed. -### Passo 1: Reunião inicial com {% data variables.product.prodname_professional_services %} (opcional) +### Step 1: Kickoff meeting with {% data variables.product.prodname_professional_services %} (optional) -Se você se inscreveu em {% data variables.product.prodname_professional_services %}, você começará o processo de implementação reunindo-se com o representante dos Serviços. +If you signed up for {% data variables.product.prodname_professional_services %}, you’ll begin the rollout and implementation process by meeting with your Services representative. -Se você não se inscreveu em {% data variables.product.prodname_professional_services %}, você pode pular para a próxima etapa. +If you haven't signed up for {% data variables.product.prodname_professional_services %}, you can skip to the next step. -O objetivo desta reunião é alinhar as duas equipes com as informações necessárias para começar a criar um plano de implementação que funcione melhor para sua empresa. Na preparação desta reunião, criamos um estudo que irá nos ajudar a nos preparar melhor para o debate. Seu representante de serviços irá enviar-lhe esta pesquisa. +The goal of this meeting is to align the two teams on the necessary information to begin crafting a rollout and implementation plan that will work best for your company. In preparation for this meeting, we have created a survey that will help us better prepare for the discussion. Your Services representative will send you this survey. -Para ajudar você a preparar-se para essa reunião inicial, revise esses tópicos. +To help you prepare for this initial meeting, review these topics. -- Alinhar sobre como a sua empresa e {% data variables.product.prodname_professional_services %} trabalharão juntos da melhor forma - - Definindo expectativas sobre como utilizar melhor as horas/dias de serviço adquiridos - - Planos de comunicação/frequência das reuniões - - Funções e responsabilidades -- Revise como o GHAS funciona dentro do ciclo de Vida do Desenvolvimento de Software (SDLC). O seu representante de {% data variables.product.prodname_professional_services %} explicará como o GHAS funciona. -- Revisão das melhores práticas para a implantação do GHAS. Isso é oferecido como uma atualização se sua equipe considerar importante ou se a sua empresa não participou do exercício de Prova de Conceito (POC). Esta revisão inclui uma discussão sobre seu programa de Segurança de Aplicativos existente e seu nível de maturidade em comparação com algo como o modelo de maturidade do DevSecOps. -- Alinhamento nos próximos passos para sua implantação no GHAS. Seu representante de {% data variables.product.prodname_professional_services %} descreverá as suas próximas etapas e o apoio que você pode esperar de sua parceria. +- Aligning on how your company and {% data variables.product.prodname_professional_services %} will work best together + - Setting expectations on how to best utilize service hours/days purchased + - Communications plans/frequency of meetings + - Roles and responsibilities +- Review of how GHAS works within the Software Development Life cycle (SDLC). Your {% data variables.product.prodname_professional_services %} representative will explain how GHAS works. +- Review of best practices for deploying GHAS. This is offered as a refresher if your team finds it valuable or if your enterprise did not participate in the Proof of Concept (POC) exercise. This review includes a discussion of your existing Application Security program and its level of maturity, against something like the DevSecOps maturity model. +- Alignment on next steps for your GHAS deployment. Your {% data variables.product.prodname_professional_services %} representative will outline your next steps and the support you can expect from your partnership. -Para ajudar você a planejar sua estratégia de implementação, você também pode esperar discutir essas questões: - - Quantas equipes serão habilitadas? - - Qual é a anatomia dos repositórios das equipes? (Stack tecnológico, ferramenta atual, etc.) - - Parte disto pode já ter sido coberta durante o exercício da Prova de Conceito se a sua empresa participou. Em caso negativo, este é um momento crucial para discutir este assunto. - - Que nível de adoção esperamos ser orgânico, assistido ou inorgânico? - - Qual é a aparência da adoção assistida a partir de uma perspectiva de recursos e documentação? - - Como você vai gerir a adoção inorgânica mais adiante? (Por exemplo, usando aplicação da política ou fluxos de trabalho gerenciada centralmente.) +To help you plan your rollout strategy, you can also expect to discuss these questions: + - How many teams will be enabled? + - What is the anatomy of the teams’ repositories? (Tech stack, current tooling, etc.) + - Some of this might have already been covered during the Proof of Concept exercise if your company participated. If not, this is a crucial time to discuss this. + - What level of adoption do we expect to be organic, assisted, or inorganic? + - What does assisted adoption look like from a resourcing and documentation perspective? + - How will you manage inorganic adoption down the line? (For example, using policy enforcement or centrally managed workflows.) -### Etapa 2: Início interno na sua empresa +### Step 2: Internal kickoff at your company -Independentemente de a sua empresa escolher ou não trabalhar com {% data variables.product.prodname_professional_services %}, recomendamos sempre que você realize sua própria reunião de início para alinhar sua(s) própria(s) equipe(s). +Whether or not your company chooses to work with {% data variables.product.prodname_professional_services %}, we always recommend you hold your own kickoff meeting to align your own team(s). -Durante essa reunião inicial, é importante garantir que haja uma clara compreensão dos objetivos, expectativas e que esteja em vigor um plano sobre como avançar com a sua implementação. +During this kickoff meeting, it's important to ensure there is a clear understanding of goals, expectations, and that a plan is in place for how to move forward with your rollout and implementation. -Além disso, esse é um bom momento para começar a pensar na formação e preparação para a sua equipe, a fim de garantir que disponham das ferramentas e dos conhecimentos adequados para apoiar a implementação do GHAS. +In addition, this is a good time to begin thinking about training and preparations for your team to ensure they have the right tools and expertise to support the rollout and implementation of GHAS. -#### Tópicos para sua reunião inicial interna +#### Topics for your internal kickoff meeting -Recomendamos que você cubra estes tópicos na sua reunião inicial interna da sua empresa, caso ainda não tenha coberto esses tópicos com o mesmo grupo na sua reunião inicial com {% data variables.product.prodname_professional_services %}. +We recommend you cover these topics in your internal kickoff meeting at your company if you haven't already covered these with the same group in your kickoff meeting with {% data variables.product.prodname_professional_services %}. -- Quais são suas métricas de sucesso de negócios, como você planeja medir e relatar essas medidas? - - Se estes não foram definidos, defina-os. Caso tenham sido definidos, comunique-os e fale sobre como você planeja fornecer atualizações de progresso orientados por dados. -- Analise como o GHAS funciona dentro do SDLC (Ciclo de Vida e Desenvolvimento do Software) e como se espera que isso funcione para sua empresa. -- Revise as práticas recomendadas se a sua empresa não participou do exercício da Prova de Conceito (ou de uma atualização, se sua equipe encontrar valor nesta revisão) - - Como isso pode ser comparado ou contrastado com seu Programa de Segurança de Aplicativos? -- Discuta e concorde como sua equipe interna irá trabalhar melhor em conjunto durante a implementação. - - Alinhe nos seus planos de comunicação e frequência de reuniões para sua equipe interna - - Revise as tarefas de conclusão e execução, definindo funções e responsabilidades. Nós delineamos a maioria das tarefas neste artigo, mas pode haver tarefas adicionais que sua empresa requer que nós não incluímos. - - Considere estabelecer um "Programa de Campeões" para capacitação escalonada - - Comece a discutir tempo para concluir as tarefas -- Comece a trabalhar em abordagens de implantação ideais que funcionarão melhor para sua empresa. Isto incluirá compreender alguns pontos importantes: - - Quantas equipes serão habilitadas? Parte disso já pode ter sido coberta durante o exercício POC (Prova de Conceito), caso a sua empresa tenha participado. Em caso negativo, este é um momento crucial para discutir este assunto. - - Dos aplicativos essenciais identificados para a implantação inicial, quantos são desenvolvidos com base em uma tecnologia compatível com o GHAS? - - Em que medida a preparação organizacional é necessária? Para saber mais, consulte "[Fase 2](#--phase-2-organizational-buy-in--rollout-preparation)". +- What are your business success metrics, how do you plan to measure and report on those measures? + - If these have not been defined, please define them. If they have been defined, communicate them and talk about how you plan to provide data-driven progress updates. +- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is +expected to work for your company. +- Review of best practices if your company did not participate in the Proof of Concept exercise (or a refresher if your team finds value in this review) + - How does this compare/contrast with your existing Application Security Program? +- Discuss and agree how your internal team will work best together throughout rollout and +implementation. + - Align on your communications plans and frequency of meetings for your internal team + - Review tasks for rollout and implementation completion, defining roles and responsibilities. We have outlined the majority of the tasks in this article, but there may be additional tasks your company requires we have not included. + - Consider establishing a “Champions Program” for scaled enablement + - Begin discussing timing for the completion of tasks +- Begin working on ideal rollout approaches that will work best for your company. This will include understanding a few important items: + - How many teams will be enabled? Some of this might have already been covered during the POC (Proof of Concept) exercise if your company participated. If not, this is a crucial time to discuss this. + - Of the critical applications identified for the initial rollout, how many are built on a technology supported by GHAS? + - How much organizational preparation is needed? To learn more, see "[Phase 2](#--phase-2-organizational-buy-in--rollout-preparation)." -### Etapa 3: Prepare sua implementação & plano de implementação e metas +### Step 3: Prepare your rollout & implementation plan and goals -Antes de poder avançar com o(s) projeto(s) piloto(s) para a primeira fase da implementação, é fundamental garantir que um plano de implementação e objetivos de negócios foram estabelecidos sobre como sua empresa planeja prosseguir. +Before you can move forward with pilot project(s) for the first phase of the rollout, it’s crucial to ensure a rollout plan and business goals have been established for how your company plans to proceed. -Se você está trabalhando com {% data variables.product.prodname_professional_services %}, ele pode desempenhar um papel significativo na criação deste plano. +If you’re working with {% data variables.product.prodname_professional_services %}, they can play a significant role in the creation of this plan. -Se você estiver trabalhando de forma independente, esta seção define algumas coisas para garantir que sejam incluídas no seu plano enquanto você se prepara para avançar. +If you’re working independently, this section outlines some things to ensure are included in your plan as you prepare to move forward. -Planos de mudança de processo (se necessário) e treinamento para os integrantes da equipe, conforme necessário: - - As tarefas de equipe documentadas para funções e responsabilidades. Para obter mais informações sobre as permissões necessárias para cada recurso, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)". - - O plano documentado de tarefas e linha do tempo/cronogramas sempre que possível. Isto deve incluir alterações na infraestrutura, mudanças/formação dos processos e todas as fases subsequentes de habilitação do GHAS, permitindo prazos para correções e ajustes de configuração, conforme necessário. Para obter mais informações, consulte "[Fase 1: Projeto(s) piloto(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" abaixo. - - Plano priorizado para quais projetos/equipes terão o GHAS habilitado primeiro e planos subsequentes para quais projetos/equipes estarão nas fases a seguir - - Métricas de sucesso baseadas em objetivos de negócios. Este será um ponto de referência fundamental após o(s) projeto(s) piloto para obter adesão para a implementação completa. +Plans for process changes (if needed) and training for team members as needed: + - Documented team assignments for roles and responsibilities. For more information on the permissions required for each feature, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)." + - Documented plan of tasks and timelines/timeframes where possible. This should include infrastructure changes, process changes/training, and all subsequent phases of enablement of GHAS, allowing for timeframes for remediations and configuration adjustments as needed. For more information, see "[Phase 1: Pilot projects(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" below. + - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent +plans for which projects/teams will come in following phases + - Success metrics based on business goals. This will be a crucial reference point following the Pilot Project(s) to gain buy-in for the full rollout. {% note %} -**Observação:** Para garantir a conscientização, a adesão e a adopção deve vir de todos os grupos da sua empresa, É importante definir expectativas realistas com relação ao tempo de implementação e impacto na infraestrutura da sua empresa, processos e fluxos gerais de trabalho de desenvolvimento do dia a dia. Para uma implantação mais suave e bem-sucedida, garanta que as suas equipes de segurança e desenvolvimento compreendam o impacto do GHAS. +**Note:** To ensure awareness, buy-in, and adoption comes from all groups in your company, it's important to set realistic expectations around the rollout timing and impact on your company's infrastructure, processes, and general day-to-day development workflows. For a smoother and more successful rollout, ensure your security and development teams understand the impact of GHAS. {% endnote %} {% ifversion ghes %} -Para os clientes de {% data variables.product.prodname_ghe_server %}, para ajudar a garantir que sua instância possa apoiar a implementação do GHAS, revise o seguinte: +For {% data variables.product.prodname_ghe_server %} customers, to help ensure your instance can support the rollout and implementation of GHAS, review the following: -- Embora a atualização para GHES 3.0 não seja obrigatória, você precisa atualizar para o GHES 3.0 ou superior aproveitar as combinações de recursos, como digitalização de código e {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)". +- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -- Na configuração de alta disponibilidade, um appliance do {% data variables.product.prodname_ghe_server %} secundário totalmente redundante é mantido em sincronização com o appliance primário pela replicação de todos os principais armazenamentos de dados. Para obter mais informações sobre como configurar alta disponibilidade, consulte "[Configurando Alta Disponibilidade](/admin/enterprise-management/configuring-high-availability)". +- In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores. For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)." -- Para ajudar a apoiar quaisquer discussões sobre possíveis alterações na configuração da sua empresa, você pode revisar a visão geral do sistema de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[System overview](/admin/overview/system-overview)." +- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. For more information, see "[System overview](/admin/overview/system-overview)." {% endif %} -### Passo 4: Estabeleer uma linha base de ideias organizacionais +### Step 4: Establish a baseline of organizational insights -À medida que sua empresa se prepara para iniciar seu(s) projeto(s) piloto(s), é fundamental garantir que você definiu uma linha de base para onde sua empresa está hoje e definiu métricas de sucesso claras para medir o progresso com base no(s) seu(s) projeto(s) piloto. +As your company prepares to begin your pilot project(s), it’s crucial to ensure that you have set a baseline for where your enterprise is today and have defined clear success metrics to measure your pilot project(s) progress against. -Provavelmente, a sua empresa tem metas de negócio que precisam ser medidas, mas existem outras métricas que podemos identificar para ajudar a avaliar o sucesso do seu piloto. +There are likely key business goals your company has that will need to be measured +against, but there are other metrics we can identify to help gauge your pilot’s success. -Como ponto de partida, algumas dessas métricas podem incluir: - - O tempo médio para correção de vulnerabilidades do GHAS em comparação com a ferramenta e praticas anteriores que o(s) projeto(s) piloto / equipe(s) usou(usaram). - - A verificação de código dos resultados da integração para os principais X aplicativos mais essenciais. - - O número de aplicativos que têm o SAST (teste de segurança estático do aplicativo) integrado em comparação com antes da participação. +As a starting point, some of these metrics might include: + - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and +practices the pilot project(s) / team(s) utilized. + - The code scanning integration's findings for the top X most critical applications. + - The number of applications that have SAST (Static application security testing) integrated versus before the engagement. -Se você participou do exercício POC antes de comprar o GHAS, esses objetivos podem parecer familiares. Este critério de sucesso inclui vários objetivos para as seguintes funções de alto nível: - - Equipes de implementação & administração - - Segurança / CISO (Diretor de Segurança da Informação) - - Equipes de Desenvolvimento de Aplicativos +If you participated in the POC exercise prior to purchasing GHAS, these objectives might look familiar. This success criteria includes several objectives for the following high-level roles: + - Implementation & Administration teams + - Security / CISO (Chief Information Security Officer) + - Application Development Teams -Se você gostaria de dar um passo adiante, você pode considerar utilizar o DevSecOps do OWASP Modelo de Maturidade (DSOMM) para alcançar a maturidade nível 1. Existem quatro principais critérios de avaliação no DSOMM: +If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps +Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main +evaluation criteria in DSOMM: -- **Profundidade estática:** O quão abrangente é a digitalização de código estático que você está realizando dentro do pipeline AppSec CI -- **Profundidade Dinâmica:** O quão abrangente é a digitalização dinâmica que está sendo executada dentro do pipeline do AppSec CI -- **Intensidade:** A sua frequência de agendamento para as verificações de segurança em execução no pipeline do AppSec CI -- **Consolidação:** Seu fluxo de trabalho de correção para manipular a completudo dos resultados e processos +- **Static depth:** How comprehensive is the static code scan that you’re performing within +the AppSec CI pipeline +- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the +AppSec CI pipeline +- **Intensity:** Your schedule frequency for the security scans running in AppSec CI pipeline +- **Consolidation:** Your remediation workflow for handling findings and process +completeness -Aprender mais sobre esta abordagem e como implementá-la no GHAS, você pode fazer o download do nosso whitepaper "[Conquistando a Maturidade do DevSecOps com o GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)." +To learn more about this approach and how to implement it in GHAS, +you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)." -Com base nas metas da sua empresa e nos níveis atuais de maturidade do DevSecOps, podemos ajudar você a determinar a melhor forma de medir o progresso e o sucesso do seu piloto. +Based on your wider company’s goals and current levels of DevSecOps maturity, we can help you determine how to best measure your pilot’s progress and success. -## {% octicon "milestone" aria-label="The milestone icon" %} Fase 1: Projeto(s) piloto +## {% octicon "milestone" aria-label="The milestone icon" %} Phase 1: Pilot project(s) {% note %} -Tempo estimado de {% octicon "clock" aria-label="Clock" %} **:** Estimamos que a fase 1 pode durar aproximadamente entre 2 semanas e mais de 3 meses. Esse intervalo pode variar em grande parte dependendo da infraestrutura ou complexidade dos sistemas da sua empresa, processos internos para gerenciar/aprovar essas mudanças, bem como se são necessárias maiores mudanças no processo organizacional para avançar com o GHAS. +{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 1 may last roughly between 2 weeks to 3+ months. This range can vary largely depending on your company’s infrastructure or systems complexity, internal processes to manage/approve these changes, as well as if larger organizational process changes are needed to move forward with GHAS. {% endnote %} -Para começar a habilitar o GHAS em toda a sua empresa, recomendamos começar com alguns projetos de alto impacto ou equipes para fazer a implementação de um projeto piloto inicial. Isso fará com que que um primeiro grupo dentro da sua empresa se familiarize com GHAS e crie uma base sólida no GHAS antes de começar a familiarizar-se com o restante da sua empresa. +To begin enabling GHAS across your company, we recommend beginning with a few +high-impact projects or teams to pilot an initial rollout. This will allow an initial +group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company. -Antes de iniciar seu(s) projeto(s), recomendamos que você agende algumas reuniões de verificação para a(s) sua(s) equipe(s), como uma reunião inicial, uma revisão do ponto intermediário e uma sessão de encerramento quando o piloto estiver concluído. Essas reuniões de verificação ajudarão você a fazer todos os ajustes, conforme necessário, e assegurarão que a(s) sua(s) equipe(s) esteja(m) preparad(a) e suportada(s) para concluir o piloto com sucesso. +Before you start your pilot project(s), we recommend that you schedule some checkpoint meetings for your team(s), such as an initial meeting, midpoint review, and a wrap-up session when the pilot is complete. These checkpoint meetings will help you all make adjustments as needed and ensure your team(s) are prepared and supported to complete the pilot successfully. -Essas etapas ajudarão você a habilitar o GHAS na sua empresa, começar a usar as suas funcionalidades e revisar seus resultados. +These steps will help you enable GHAS on your enterprise, begin using its features, and review your results. -Se você estiver trabalhando com {% data variables.product.prodname_professional_services %}, ele poderá fornecer assistência adicional por meio desse processo com sessões de integração, oficinas do GHAS e solução de problemas, conforme necessário. +If you’re working with {% data variables.product.prodname_professional_services %}, they can provide additional assistance through this process through onboarding sessions, GHAS workshops, and troubleshooting as needed. -### Etapa 1: Configuração do GHAS & instalação +### Step 1: GHAS set-up & installation {% ifversion ghes %} -Se você ainda não habilitou o GHAS para a sua instância de {% data variables.product.prodname_ghe_server %}, consulte[Habilitando a segurança avançada do GitHub Advanced para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +If you haven't already enabled GHAS for your {% data variables.product.prodname_ghe_server %} instance, see "[Enabling GitHub Advanced Security for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." {% endif %} -Você precisa habilitar o GHAS para cada projeto piloto, habilitando o recurso do GHAS para cada repositório ou para todos os repositórios em qualquer organização que participe do projeto. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +You need to enable GHAS for each pilot project, either by enabling the GHAS feature for each repository or for all repositories in any organizations taking part in the project. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" -A grande maioria dos ajustes e instalação do GHAS está centrada em habilitar e configurar a digitalização do código na sua empresa e nos seus repositórios. +The vast majority of GHAS set-up and installation is centered around enabling and configuring code scanning on your enterprise and in your repositories. -A verificação de código permite que você analise o código em um repositório de {% data variables.product.prodname_dotcom %} para encontrar vulnerabilidades de segurança e erros de codificação. A digitalização de código pode ser usada para encontrar, triar e priorizar correções para problemas existentes no seu código, Além de ajudar a impedir que os desenvolvedores introduzam novos problemas que, de outra forma, poderiam chegar à produção. Para obter mais informações, consulte "[Sobre a varredura de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)". +Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)." -### Etapa 2: Configurar {% data variables.product.prodname_code_scanning_capc %} +### Step 2: Set up {% data variables.product.prodname_code_scanning_capc %} {% ifversion ghes %} -Para habilitar {% data variables.product.prodname_code_scanning %} na sua instância de {% data variables.product.prodname_ghe_server %}, consulte[Configurando a digitalização de código de configuração para o seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." +To enable {% data variables.product.prodname_code_scanning %} on your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." {% endif %} -Para configurar a digitalização de código, você deve decidir se irá executar a digitalização de código com [{% data variables.product.prodname_actions %}](#using-github-actions-for-code-scanning) ou com seu próprio [sistema de CI de terceiros](#using-a-third-party-ci-system-with-the-codeql-cli-for-code-scanning). +To set up code scanning, you must decide whether you'll run code scanning with [{% data variables.product.prodname_actions %}](#using-github-actions-for-code-scanning) or your own [third-party CI system](#using-a-third-party-ci-system-with-the-codeql-cli-for-code-scanning). -#### Usando {% data variables.product.prodname_actions %} para {% data variables.product.prodname_code_scanning %} +#### Using {% data variables.product.prodname_actions %} for {% data variables.product.prodname_code_scanning %} {% ifversion ghes %} -Para configurar a varredura de código com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, você deverá fornecer um ou mais executores de {% data variables.product.prodname_actions %} auto-hospedados no seu ambiente. Para obter mais informações, consulte "[Configurando um executor auto-hospedado](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)". +To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your +environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)." {% endif %} -Para {% data variables.product.prodname_ghe_cloud %}, você pode começar a criar um fluxo de trabalho de {% data variables.product.prodname_actions %} usando a ação [CodeQL](https://github.com/github/codeql-action/) para executar a digitalização de código em um repositório. {% data variables.product.prodname_code_scanning_capc %} usa [executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners) por padrão, mas isso pode ser personalizado se você planeja hospedar seu próprio executor com as suas próprias especificações de hardware. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners)." +For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners)." -Para mais informações sobre {% data variables.product.prodname_actions %}, consulte: - - "[Conheça o GitHub Actions](/actions/learn-github-actions)" - - "[Entendendo o GitHub Actions](/actions/learn-github-actions/understanding-github-actions)" - - [Eventos que acionam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows) - - "[Filtrar o padrão da folha de informações](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)" +For more information about {% data variables.product.prodname_actions %}, see: + - "[Learn GitHub Actions](/actions/learn-github-actions)" + - "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)" + - "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)" + - "[Filter Pattern Cheat Sheet](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)" -#### Usando um sistema de CI de terceiros com o a CLI do CodeQL para {% data variables.product.prodname_code_scanning %} +#### Using a third-party CI system with the CodeQL CLI for {% data variables.product.prodname_code_scanning %} -Se você não usar {% data variables.product.prodname_actions %} e tiver o seu próprio sistema de integração contínua, você poderá usar o CLI do CodeQL para executar a digitalização de código do CodeQL em um sistema CI de terceiros. +If you’re not using {% data variables.product.prodname_actions %} and have your own continuous integration system, you can use the CodeQL CLI to perform CodeQL code scanning in a third-party CI system. -Para obter mais informações, consulte: - - "[Sobre a digitalização do código do CodeQL no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)" +For more information, see: + - "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)" -### Etapa 3: Habilitar {% data variables.product.prodname_code_scanning_capc %} nos repositórios +### Step 3: Enable {% data variables.product.prodname_code_scanning_capc %} in repositories -Se você estiver usando uma abordagem faseada para implementar o GHAS, recomendamos habilitar {% data variables.product.prodname_code_scanning %} por repositório como parte do seu plano de implementação. Para obter mais informações, consulte "[Configurando a digitalização de código para um repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository)". +If you’re using a phased approach to roll out GHAS, we recommend enabling {% data variables.product.prodname_code_scanning %} on a repository-by-repository basis as part of your rollout plan. For more information, see "[Setting up code scanning for a repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository)." -Se você não estiver planejando uma abordagem de implementação faseada e quiser habilitar a verificação de código para muitos repositórios, você pode fazer o script do processo. +If you’re not planning on a phased rollout approach and want to enable code scanning for many repositories, you may want to script the process. For an example of a script that opens pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. -### Etapa 4: Execute digitalizações de código e revise seus resultados +### Step 4: Run code scans and review your results -Com a digitalização de código habilitada nos repositórios necessários, você está pronto para ajudar sua(s) equipe(s) de desenvolvimento a entender como executar digitalizações e relatórios de código, ver relatórios e processar resultados. +With code scanning enabled in the necessary repositories, you're ready to help your +development team(s) understand how to run code scans and reports, view reports, and process results. #### {% data variables.product.prodname_code_scanning_capc %} -Com a digitalização de código, você pode encontrar vulnerabilidades e erros no código do seu projeto no GitHub, bem como exibição, triagem, entender e resolver os alertas de {% data variables.product.prodname_code_scanning %} relacionados. +With code scanning, you can find vulnerabilities and errors in your project's code on GitHub, +as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts. -Quando a digitalização de código identifica um problema em um pull request, você poderá revisar o código destacado e resolver o alerta. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)". +When code scanning identifies a problem in a pull request, you can review the highlighted +code and resolve the alert. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)." -Se você tiver permissão de gravação em um repositório, você poderá gerenciar alertas de digitalização de código para esse repositório. Com permissão de gravação em um repositório, você pode visualizar, corrigir, ignorar ou excluir alertas de potenciais vulnerabilidades ou erros no código do seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository). " +If you have write permission to a repository you can manage code scanning alerts for that +repository. With write permission to a repository, you can view, fix, dismiss, or delete alerts for potential +vulnerabilities or errors in your repository's code. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)." -#### Gerar relatórios de alertas de {% data variables.product.prodname_code_scanning %} +#### Generate reports of {% data variables.product.prodname_code_scanning %} alerts -Se você quiser criar um relatório dos seus alertas de digitalização de código, você poderá usar a API de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte o "[API de {% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)". +If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. For more information, see the "[{% data variables.product.prodname_code_scanning_capc %} API](/rest/reference/code-scanning)." -Para um exemplo de como usar a {% data variables.product.prodname_code_scanning_capc %} API, consulte o repositório [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample). +For an example of how to use the {% data variables.product.prodname_code_scanning_capc %} API, see the [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample) repository. -### Etapa5: Configure {% data variables.product.prodname_code_scanning_capc %} para ajustar seus resultados +### Step 5: Configure {% data variables.product.prodname_code_scanning_capc %} to fine tune your results -Ao executar a digitalização inicial de código, você pode descobrir que nenhum resultado foi encontrado ou que um número incomum de resultados foi retornado. Você pode querer ajustar o que é sinalizado em futuras digitalizações. +When running initial code scans, you may find that no results are found or that an unusual number of results are returned. You may want to adjust what is flagged in future scans. -Para obter mais informações, consulte "[Configurar a verificação de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)". +For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)." -Se sua empresa quiser usar outras ferramentas de análise de código de terceiros com a digitalização de código do GitHub, você poderá usar ações para executar essas ferramentas dentro do GitHub. Como alternativa, você pode fazer upload de resultados, gerados por ferramentas de terceiros como arquivos SARIF, para a digitalização de código. Para obter mais informações, consulte "[Integrando à digitalização de código](/code-security/code-scanning/integrating-with-code-scanning)". +If your company wants to use other third-party code analysis tools with GitHub code scanning, you can use actions to run those tools within GitHub. Alternatively, you can upload results, generated by third-party tools as SARIF files, to code scanning. For more information, see "[Integrating with code scanning](/code-security/code-scanning/integrating-with-code-scanning)." -### Etapa 6: Configurar a digitalização de segredos +### Step 6: Set up secret scanning -O GitHub digitaliza repositórios de tipos conhecidos de segredos, para evitar o uso fraudulento de segredos que foram cometidos acidentalmente. +GitHub scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally. {% ifversion ghes %} -Para habilitar a digitalização de segredos para a sua instância de {% data variables.product.prodname_ghe_server %}, consulte "[Configurando a digitalização de segredo para o seu dispositivo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance). " +To enable secret scanning for your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring secret scanning for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance)." {% endif %} -Você precisa habilitar digitalização de segredos para cada projeto piloto, habilitando o recurso para cada repositório ou para todos os repositórios de qualquer organização que participe do projeto. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +You need to enable secret scanning for each pilot project, either by enabling the feature for each repository or for all repositories in any organizations taking part in the project. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" -Para saber como exibir e fechar alertas para segredos verificados em seu repositório, consulte "[Gerenciando alertas do digitalização de segredos](/code-security/secret-scanning/managing-alerts-from-secret-scanning)". +To learn how to view and close alerts for secrets checked into your repository, see "[Managing alerts from secret scanning](/code-security/secret-scanning/managing-alerts-from-secret-scanning)." -### Etapa 7: Configurar gestão de dependências +### Step 7: Set up dependency management -O GitHub ajuda você a evitar o uso de software de terceiros que contém vulnerabilidades conhecidas. Nós fornecemos as seguintes ferramentas para remover e evitar dependências vulneráveis. +GitHub helps you avoid using third-party software that contains known vulnerabilities. We provide the following tools for removing and avoiding vulnerable dependencies. -| Ferramenta Gerenciamento de Dependência | Descrição | -| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Alertas de Dependabot | Você pode acompanhar as dependências do seu repositório e receber alertas de dependências do Dependabot quando sua empresa detectar dependências vulneráveis. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" | -| Gráfico de Dependência | O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Ele mostra os ecossistemas e pacotes dos quais a sua base de código depende (suas dependências) e os repositórios e pacotes que dependem do seu projeto (suas dependências). Para obter mais informações, consulte "[Sobre o gráfico de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)". |{% ifversion ghes > 3.1 or ghec %} -| Revisão de Dependência | Se um pull request tiver alterações nas dependências, você poderá ver um resumo do que alterou e se há vulnerabilidades conhecidas em qualquer uma das dependências. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" ou "[Revisando as alterações de dependência em um pull requestl](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)". |{% endif %} {% ifversion ghec or ghes > 3.2 %} -| Atualizações de segurança do Dependabot | O dependabot pode corrigir dependências vulneráveis levantando pull requests com atualizações de segurança. Para obter mais informações, consulte "[Sobre atualizações de segurança do Dependabot](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)". | -| Atualizações da versão do Dependabot | O dependabot pode ser usado para manter os pacotes que você usa atualizados para as últimas versões. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". | {% endif %} +| Dependency Management Tool | Description | +|----|----| +| Dependabot Alerts | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects vulnerable dependencies. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." | +| Dependency Graph | The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." |{% ifversion ghes > 3.1 or ghec %} +| Dependency Review | If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." | {% endif %} {% ifversion ghec or ghes > 3.2 %} +| Dependabot Security Updates | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." | +| Dependabot Version Updates | Dependabot can be used to keep the packages you use updated to the latest versions. For more information, see "[About Dependabot version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." | {% endif %} {% data reusables.dependabot.beta-security-and-version-updates-onboarding %} -### Etapa 8: Estabelecer um processo de correção +### Step 8: Establish a remediation process -Uma vez que sua(s) equipe(s) puderam de realizar verificações, identificar vulnerabilidades e dependências e puderem consumir os resultados de cada recurso de segurança, o próximo passo é garantir que possam corrigir as vulnerabilidades identificadas em seus processos de desenvolvimento normais sem envolver sua equipe de segurança. +Once your team(s) have been able to run scans, identify vulnerabilities and dependencies, and can consume the results of each security feature, the next step is to ensure that they can remediate the vulnerabilities identified within their normal development processes without involving your security team. -Isto significa que as equipes de desenvolvimento entendem como utilizar as funcionalidades do GHAS durante todo o processo de desenvolvimento, podem executar digitalizações, ler relatórios, usar os resultados e remediar vulnerabilidades dentro de seus fluxos de trabalho normais de desenvolvimento, sem precisar ter uma fase de segurança separada no final do desenvolvimento, ou ter necessidade de envolver sua equipe de segurança para entender relatórios/resultados. +This means that the development teams understand how to utilize the GHAS features throughout the development process, can run scans, read reports, consume the results, and remediate vulnerabilities within their normal development workflows, without having to have a separate security phase at the end of development, or have a need to involve your security team to understand reports/results. -### Etapa 9: Configurar análise personalizada, se necessário +### Step 9: Set up custom analysis if needed -Análise personalizada é um uso opcional mais profundo da varredura de código quando consultas do CodeQL personalizadas são necessárias além do conjunto padrão (e comunidade) disponível de consultas. A necessidade de consultas personalizadas é rara. +Custom analysis is an optional deeper use of code scanning when custom CodeQL queries are needed beyond the available default (and community) set of queries. The need for custom queries is rare. -As consultas personalizadas são usadas para identificar alertas personalizados de segurança ou ajudar os desenvolvedores a seguir os padrões de codificação, detectando certos padrões de código. +Custom queries are used to identify custom security alerts or help developers follow coding standards by detecting certain code patterns. -Se sua empresa estiver interessada em escrever consultas personalizadas do CodeQL, existem certos requisitos que sua empresa deve cumprir. +If your company is interested in writing custom CodeQL queries, there are certain requirements your company should meet. -Se sua equipe puder fornecer alguns exemplos de vulnerabilidades existentes que você gostaria de encontrar via CodeQL, avise a equipe do GitHub e nós poderemos agendar uma sessão introdutória para revisar os fundamentos da linguagem e discutir como resolver um dos seus problemas. Se você quiser cobrir o CodeQL com mais profundidade, oferecemos opções adicionais de envolvimento para cobrir mais tópicos para permitir que a sua equipe crie as suas próprias consultas. +If your team can provide some examples of existing vulnerabilities you'd like to find via CodeQL, please let the GitHub team know and we can schedule an introductory session to review the basics of the language and discuss how to tackle one of your problems. If you want to cover CodeQL in more depth, then we offer additional engagement options to cover more topics to enable your team to build their own queries. -Você pode aprender mais sobre [consultas CodeQL](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) em nossa [Documentação do CodeQL](https://codeql.github.com/docs/codeql-overview/), ou entrar em contato com sua equipe de {% data variables.product.prodname_professional_services %} ou representante de vendas. +You can learn more about [CodeQL queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in our [CodeQL documentation](https://codeql.github.com/docs/codeql-overview/), or reach out to your {% data variables.product.prodname_professional_services %} team or sales representative. -### Passo 10: Criar & manter a documentação +### Step 10: Create & maintain documentation -Em toda a fase piloto, é fundamental criar e manter uma documentação interna de alta qualidade da infraestrutura e processar alterações feitas dentro da sua empresa, bem como o que foi aprendido com o processo piloto e as alterações na configuração feitas conforme o progresso da(s) sua(s) equipe(s) ao longo da implementação. +All throughout the pilot phase, it’s essential to create and maintain high-quality internal documentation of the infrastructure and process changes made within your company, as well as learnings from the pilot process and configuration changes made as your team(s) progress throughout the rollout and implementation process. -Ter uma documentação completa e completa ajuda a fazer das etapas restantes da sua implementação mais de um processo reproduzível. Uma boa documentação também garante que as novas equipes possam ser integradas de forma consistente ao longo do processo de implementação e, uma vez que que novos integrantes da equipe se unem à(s) equipe(s). +Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process. +Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s). -A documentação boa não termina quando a implementação é concluída. A documentação mais útil é atualizada e evolui ativamente à medida que suas equipes expandem sua experiência usando o GHAS e suas necessidades aumentam. +Good documentation doesn’t end when rollout and implementation are complete. The most helpful documentation is actively updated and evolves as your teams expand their experience using GHAS and as their needs grow. -Além da sua documentação, recomendamos que sua empresa forneça canais claros para a(s) sua(s) equipe(s) para suporte e orientação tudo durante e após a implementação. Dependendo do nível de mudança, a sua empresa precisa assumir para apoiar a implementação do GHAS. Ter equipes bem respaldadas ajudará a garantir uma adesão bem-sucedida no fluxo de trabalho diário das suas equipes de desenvolvimento. +In addition to your documentation, we recommend your company provides clear channels to your team(s) for support and guidance all throughout rollout, implementation, and beyond. Depending on the level of change your company needs to take on in order to support the rollout and implementation of GHAS, having well-supported teams will help ensure a successful adoption into your development teams’ daily workflow. -## {% octicon "milestone" aria-label="The milestone icon" %} Fase 2: Adesão organizacional & preparação para implementação +## {% octicon "milestone" aria-label="The milestone icon" %} Phase 2: Organizational buy-in & rollout preparation {% note %} -{% octicon "clock" aria-label="Clock" %} **Tempo estimado:** Estimamos que a fase 2 deverá dura entre 1 semana e 1 mês. Esse intervalo pode variar em grande medida dependendo dos processos internos de aprovação da sua empresa. +{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 2 may last roughly between 1 week to over a month. This range can vary largely depending on your company’s internal approval processes. {% endnote %} -Um dos principais objetivos desta fase é garantir que você tenha a adesão da organização para fazer com que toda a implantação do GHAS seja bem-sucedida. +One of the main goals of this phase is to ensure you have the organizational buy-in to make the full deployment of GHAS successful. -Durante essa fase, a sua empresa analisa os resultados do(s) projeto(s) piloto para determinar se o piloto teve sucesso, que qjustes poderão ser necessários e se a empresa está disposta a prosseguir com a implantação. +During this phase, your company reviews the results of the pilot project(s) to determine if the pilot was successful, what adjustments may need to be made, and if the company is ready to continue forward with the rollout. -Dependendo do processo de aprovação da sua empresa, poderá ser necessário continuar com a adesão da organização do seu patrocinador executivo. Na maioria dos casos, a adesão da(s) sua(s) equipe(s) organizacionais é necessária para começar a utilizar o valor do GHAS para a sua empresa. +Depending on your company’s approval process, organizational buy-in from your executive sponsor may be necessary to continue forward. In most cases, organizational buy-in from your team(s) is necessary to begin utilizing the value of GHAS for your company. -Antes de passar para a próxima fase de implementação do GHAS em toda a sua empresa, as modificações são frequentemente feitas no plano original de implementação, com base no que aprendermos com o piloto. +Before moving forward to the next phase of rolling out GHAS more widely across your company, modifications are often made to the original rollout plan based on learnings from the pilot. -Todas as alterações que possam ter impacto na documentação deverão também ser introduzidas para assegurar a sua implantação contínua. +Any changes that may impact the documentation should also be made to ensure it is current for continued rollout. -Também recomendamos que você considere seu plano de treinar todas as equipes ou integrantes da equipe que serão apresentados ao GHAS nas próximas fases da sua implementação, se você ainda não o fez. +We also recommend that you consider your plan to train any teams or team members that will be introduced to GHAS in the next phases of your rollout if you haven't already. -### Etapa 1: Organizar resultados +### Step 1: Organize results -Na conclusão da fase 1, sua(s) equipe(s) deve(m) ter {% ifversion ghes %} o GHAS habilitado na instância de {% data variables.product.prodname_ghe_server %} e{% endif %} poder ter usado todos os principais recursos do GHAS com sucesso, potencialmente com algumas alterações de configuração para otimizar os resultados. Se a sua empresa definiu claramente métricas de sucesso na Fase 0, você poderá medir com base nessas métricas para determinar o sucesso do seu piloto. +At the completion of Phase 1, your team(s) should have {% ifversion ghes %} GHAS enabled on your {% data variables.product.prodname_ghe_server %} instance and have{% endif %} been able to utilize all of the key features of GHAS successfully, potentially with some configuration changes to optimize results. If your company clearly defined success metrics in Phase 0, you should be able to measure against these metrics to determine the success of your pilot. -É importante revisitar suas métricas de linha de base ao preparar seus resultados para garantir que o progresso adicional possa ser demonstrado com base em métricas coletadas do piloto com base nas metas originais do seu negócio. Se você precisar de ajuda com estas informações, o GitHub pode ajudar, garantindo que sua empresa tenha as métricas certas com base nas quais o seu progresso será medido. Para obter mais informações sobre a ajuda disponível, consulte "[Serviços e suporte do GitHub](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)". +It’s important to revisit your baseline metrics when preparing your results to ensure that incremental progress can be demonstrated based on metrics collected from the pilot against your original business goals. If you need assistance with this information, GitHub can help by ensuring that your company has the right metrics to measure your progress against. For more information on help available, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)." -### Etapa 2: Adesão segura pela organização +### Step 2: Secure organizational buy-in -A adesão organizacional irá variar com base em uma série de fatores, incluindo o tamanho da sua empresa, processo de aprovação, ou nível de mudança necessário para implantar o GHAS, para citar alguns exemplos. +Organizational buy-in will vary depending on a variety of factors, including your company’s size, approval process, or even the level of change required to rollout GHAS to name a few. -Para algumas empresas, garantir a adesão é uma reunião única, mas, para outras, este processo pode levar algum tempo (possivelmente semanas ou meses). A adesão poderá exigir a aprovação do seu patrocinador executivo ou exigir a adoção do GHAS nos fluxos diários das suas equipes. +For some companies, securing buy-in is a one-time meeting, but for others, this process can take quite some time (potentially weeks or months). Buy-in may require approval from your executive sponsor or may require the adoption of GHAS into your teams’ daily workflows. -A duração desta fase depende inteiramente da sua empresa e da rapidez com que você gostaria de prosseguir. Recomendamos buscar suporte ou serviços a partir do GitHub sempre que possível para ajudar a responder a perguntas e fornecer todas recomendações que possam ser necessárias para ajudar a apoiar este processo. Para obter mais informações sobre a ajuda disponível, consulte "[Serviços e suporte do GitHub](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)". +This duration of this stage is entirely up to your company and how quickly you would like to proceed. We recommend seeking support or services from GitHub where possible to help answer questions and provide any recommendations that may be needed to help support this process. For more information on help available, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)." -### Passo 3: Revisar e atualizar a documentação +### Step 3: Revise and update documentation -Analise os resultados e conclusões de seu projeto piloto e as necessidades dos das equipes restantes da sua empresa. Com base nos seus resultados e análises de necessidades, atualize e revise a sua documentação. +Review the results and findings from your pilot project(s) and the needs of the remaining teams at your company. Based on your findings and needs analysis, update/revise your documentation. -Descobrimos que é essencial garantir que a sua documentação esteja atualizada antes de continuar a implantação para os demais negócios da sua empresa. +We've found that it’s essential to ensure that your documentation is up-to-date before continuing with the rollout to the remainder of your company's enterprise. -### Passo 4: Prepare um plano de implantação completo para sua empresa +### Step 4: Prepare a full rollout plan for your company -Com base no que você aprendeu com o(s) seu(s) projeto(s) piloto, atualize o plano de implantação que você projetou na fase 0. Para se preparar para a implementação na sua empresa, considere todos os treinamentos que suas equipes precisarem como, por exemplo, o treinamento sobre o uso do GHAS, mudanças de processo ou treinamento de migração se seu negócio estiver fazendo a migração para o GitHub. +Based on what you learned from your pilot project(s), update the rollout plan you designed in stage 0. To prepare for rolling out to your company, consider any training your teams will need, such as training on using GHAS, process changes, or migration training if your enterprise is migrating to GitHub. -## {% octicon "milestone" aria-label="The milestone icon" %} Fase 3: Execução completa da organização & gestão de mudanças +## {% octicon "milestone" aria-label="The milestone icon" %} Phase 3: Full organizational rollout & change management {% note %} -{% octicon "clock" aria-label="Clock" %} **Tempo estimado:** Estimamos que a fase 3 pode -durar entre 2 semanas e vários meses. Este intervalo pode variar em grande parte dependendo do tamanho da sua empresa, número de repositórios/equipes, o nível de mudança que a implantação do GHAS irá representar para a sua empresa, etc. +{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 3 may +last anywhere from 2 weeks to multiple months. This range can vary largely depending on +your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc. {% endnote %} -Assim que sua empresa estiver alinhada com os resultados e conclusões do(s) seu(s) projeto(s) piloto e todas as etapas de preparação forem concluídas a partir da Fase 2, você pode seguir em frente com a implementação completa para sua empresa com base no seu plano. +Once your company has aligned on the results and findings from your pilot project(s) and all rollout preparation steps have been completed from Phase 2, you can move forward with the full rollout to your company based on your plan. -### Etapa 1: Avalie sua implantação à medida que você avança +### Step 1: Evaluate your rollout as you go -Se você está usando uma abordagem faseada para implementar o GHAS, recomendamos que você faça uma breve pausa e realize uma curta avaliação depois de implementar o GHAS em um segmento diferente da sua empresa para garantir que a implantação avance sem problemas. Sua avaliação pode garantir que as equipes sejam habilitadas e treinadas adequadamente, que todas as necessidades únicas de configuração do GHAS foram atendidas e que os planos e a documentação podem ser ajustados conforme necessário. +If you're using a phased approach to rolling out GHAS, we recommend taking a brief pause and completing a short evaluation after rolling out GHAS to a different segment of your company to ensure the rollout is moving forward smoothly. Your evaluation can ensure that teams are enabled and trained properly, that any unique GHAS configuration needs are met, and that plans and documentation can be adjusted as needed. -### Passo 2: Configure todos os treinamentos necessários +### Step 2: Set up any needed training -Ao implementar o GHAS em qualquer equipe além da sua equipe de projeto(s) piloto(s), é importante garantir que as equipes sejam treinadas ou que existam recursos de treinamento disponíveis para fornecer suporte adicional quando necessário. +When rolling GHAS out to any teams beyond your pilot project team(s), it’s important to ensure teams are either trained or there are training resources available to provide additional support where needed. -Estas são as principais áreas em que vemos que as empresas necessitam de suporte adicional: - - treinamento no GHAS - - treinamento para clientes novos no GitHub - - treinamento sobre como migrar para o GitHub +These are the main areas where we see companies needing further support: + - training on GHAS + - training for customers new to GitHub + - training on how to migrate to GitHub -Nossa equipe de {% data variables.product.prodname_professional_services_team %} fornece uma série de serviços de treinamento, bootcamps e apenas aconselhamento geral para ajudar a(s) sua(s) equipe(s) durante todo o processo de implementação. Para obter mais informações, consulte "[Serviços e suporte do GitHub](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)". +Our {% data variables.product.prodname_professional_services_team %} team provides a variety of training services, bootcamps, and just general advice to help support your team(s) throughout the rollout and implementation process. For more information, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)." -Para ajudar as suas equipes, aqui está um resumo da documentação relevante do GitHub. +To help support your teams, here's a recap of relevant GitHub documentation. -Para conhecer a documentação sobre como habilitar o GHAS, consulte: - - "[Habilitando as funcionalidades avançadas de segurança](/get-started/learning-about-github/about-github-advanced-security)" - - "[Gerenciando configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" - - "[Gerenciar as configurações de segurança e análise para o seu repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" +For documentation on how to enable GHAS, see: + - "[Enabling Advanced Security features](/get-started/learning-about-github/about-github-advanced-security)" + - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" + - "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" -Para conhecer a documentação sobre como migrar para o GitHub, consulte: - - "[Importar código-fonte para o GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)" +For documentation on how to migrate to GitHub, see: + - "[Importing source code to GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)" -Para ler a documentação sobre como começar a usar o GitHub, consulte: - - "[Primeiros passos](/get-started)" +For documentation on getting started with GitHub, see: + - "[Get started](/get-started)" -### Etapa 3: Ajude a sua empresa a gerenciar as alterações +### Step 3: Help your company manage change -Na etapa 4 da segunda fase, recomendamos que você atualize o plano inicial de implementação com base nos seus aprendizados do(s) projeto(s) piloto. Certifique-se de que você continue atualizando seu plano à medida que implementa quaisquer alterações organizacionais necessárias para implementar o GHAS com sucesso na sua empresa. +In step 4 of phase 2, we recommended that you update the initial rollout plan based on your learnings from the pilot project(s). Ensure that you continue to update your plan as you implement any necessary organizational changes to successfully roll out GHAS to your company. -A implementação bem-sucedida do GHAS e a adoção das práticas recomendadas nos fluxos de trabalho diários dependem de garantir que suas equipes entendem por que é necessário incluir a segurança em seu trabalho. +Successful GHAS rollouts and the adoption of best practices into daily workflows depend on ensuring that your teams understand why it’s necessary to include security in their work. -### Passo 4: Personalização contínua +### Step 4: Continued customization -A configuração e personalização do GHAS não estão completas até que sejam implementadas em toda a sua empresa. Outras alterações na configuração personalizada devem continuar a ser feitas ao longo do tempo para garantir que o GHAS continue a apoiar as necessidades de alteração da sua empresa. +Configuration and customization of GHAS are not complete once it’s rolled out across your company's enterprise. Further custom configuration changes should continue to be made over time to ensure GHAS continues to support your company's changing needs. -À medida que a sua equipe torna-se mais experiente e qualificada com GHAS ao longo do tempo, isso criará oportunidades adicionais para uma melhor personalização. +As your team becomes more experienced and skilled with GHAS over time, this will create additional opportunities for further customization. diff --git a/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md b/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md index 1e2f769ed3..a05ce5a4c5 100644 --- a/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md +++ b/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md @@ -1,7 +1,7 @@ --- -title: Visão geral da implantação de Segurança Avançada do GitHub -intro: 'Ajude sua empresa a se preparar para adotar {% data variables.product.prodname_GH_advanced_security %} (GHAS) de forma bem-sucedida revisando e entendendo as práticas recomendadas, exemplos de implementação e a nossa abordagem em fases testada pela empresa.' -product: '{% data variables.product.prodname_GH_advanced_security %} é um conjunto de funcionalidades de segurança projetado para tornar o código corporativo mais seguro. Está disponível para {% data variables.product.prodname_ghe_server %} 3.0 ou superior, {% data variables.product.prodname_ghe_cloud %} e para repositórios de código aberto. Para saber mais sobre as funcionalidades, incluído em {% data variables.product.prodname_GH_advanced_security %}, consulte "[Sobre o GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."' +title: Overview of GitHub Advanced Security deployment +intro: 'Help your company successfully prepare to adopt {% data variables.product.prodname_GH_advanced_security %} (GHAS) by reviewing and understanding these best practices, rollout examples, and our enterprise-tested phased approach.' +product: '{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features, included in {% data variables.product.prodname_GH_advanced_security %}, see "[About GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."' miniTocMaxHeadingLevel: 3 versions: ghes: '*' @@ -14,133 +14,135 @@ topics: - Security --- -{% data variables.product.prodname_GH_advanced_security %} (GHAS) ajuda equipes a criar mais rapidamente um código mais seguro, usando ferramentas integradas, como CodeQL, o mecanismo de análise de código semântico mais avançado do mundo. O GHAS é um conjunto de ferramentas que requer a participação ativa de desenvolvedores na sua empresa. Para obter o melhor retorno do seu investimento, você deverá aprender a usar, aplicar e manter o GHAS para proteger realmente seu código. +{% data variables.product.prodname_GH_advanced_security %} (GHAS) helps teams build more secure code faster using integrated tooling such as CodeQL, the world’s most advanced semantic code analysis engine. GHAS is a suite of tools that requires active participation from developers across your enterprise. To realize the best return on your investment, you must learn how to use, apply, and maintain GHAS to truly protect your code. -Um dos maiores desafios em lidar com novos softwares para uma empresa pode ser o processo de implementação, bem como promover a mudança cultural para impulsionar a aquisição organizacional necessária para que a implementação seja bem sucedida. +One of the biggest challenges in tackling new software for an company can be the rollout and implementation process, as well as bringing about the cultural change to drive the organizational buy-in needed to make the rollout successful. -Para ajudar sua empresa a entender melhor e preparar-se para esse processo com o GHAS, essa visão geral destina-se a: - - Dar a você uma visão geral da aparência da implantação do GHAS para sua empresa. - - Ajudando você a preparar sua empresa para uma implementação. - - Compartilhe as práticas recomendadas fundamentais para ajudar a aumentar o sucesso da implementação da sua empresa. +To help your company better understand and prepare for this process with GHAS, this overview is aimed at: + - Giving you an overview of what a GHAS rollout might look like for your + company. + - Helping you prepare your company for a rollout. + - Sharing key best practices to help increase your company’s rollout + success. -Para entender as funcionalidades de segurança disponíveis por meio de {% data variables.product.prodname_GH_advanced_security %}, consulte "[funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". +To understand the security features available through {% data variables.product.prodname_GH_advanced_security %}, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." -## Abordagem faseada recomendada para implementações do GHAS +## Recommended phased approach for GHAS rollouts -Criamos uma abordagem faseada para implementações do GHAS desenvolvidas com base nas práticas recomendadas do setor e do GitHub. Você pode utilizar essa abordagem para a sua implementação, em parceria com {% data variables.product.prodname_professional_services %} ou de forma independente. +We’ve created a phased approach to GHAS rollouts developed from industry and GitHub best practices. You can utilize this approach for your rollout, either in partnership with {% data variables.product.prodname_professional_services %} or independently. -Embora a abordagem faseada seja recomendada, os ajustes podem ser feitos com base nas necessidades da sua empresa. Sugerimos também a criação e o cumprimento de um calendário para a sua implementação. À medida que você começa o seu planejamento, podemos trabalhar juntos para identificar a abordagem ideal e a linha do tempo que funciona melhor para sua empresa. +While the phased approach is recommended, adjustments can be made based on the needs of your company. We also suggest creating and adhering to a timeline for your rollout and implementation. As you begin your planning, we can work together to identify the ideal approach and timeline that works best for your company. -![Diagrama que mostra as três fases da implementação do GitHub Advanced Security, incluindo a Fase 0: Planejamento & introdução, Fase 1: Projetos piloto, Fase 2: Adesão e implementação corporativas para os primeiros a aderirem e Fase 3: Implementação completa & Gestão de mudanças](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png) +![Diagram showing the three phases of GitHub Advanced Security rollout and deployment, including Phase 0: Planning & Kickoff, Phase 1: Pilot projects, Phase 2: Org Buy-in and Rollout for early adopters, and Phase 3: Full org rollout & change management](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png) -Com base na nossa experiência ajudando clientes com uma implantação bem-sucedida de {% data variables.product.prodname_GH_advanced_security %}, esperamos que a maioria dos clientes queira seguir essas fases. Dependendo das necessidades da sua empresa, talvez seja necessário modificar esta abordagem e alterar ou remover algumas fases ou etapas. +Based on our experience helping customers with a successful deployment of {% data variables.product.prodname_GH_advanced_security %}, we expect most customers will want to follow these phases. Depending on the needs of your company, you may need to modify this approach and alter or remove some phases or steps. -Para um guia detalhado sobre a implementação de cada uma dessas etapas, consulte "[Implantando {% data variables.product.prodname_GH_advanced_security %} na sua empresa](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)". A próxima seção fornece um resumo de alto nível de cada uma destas fases. +For a detailed guide on implementing each of these phases, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." The next section gives you a high-level summary of each of these phases. -### {% octicon "milestone" aria-label="The milestone icon" %} Fase 0: Planejamento & início +### {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff -Durante essa fase, o objetivo geral é planejar e preparar-se para a sua implantação, garantindo que você tenha seu pessoal, processos e tecnologias prontos para sua implementação. Você também deve considerar quais critérios de sucesso serão usados para medir a adoção e o uso do GHAS nas suas equipes. +During this phase, the overall goal is to plan and prepare for your rollout, ensuring that you have your people, processes, and technologies in place and ready for your rollout. You should also consider what success criteria will be used to measure GHAS adoption and usage across your teams. -### {% octicon "milestone" aria-label="The milestone icon" %} Fase 1: Projeto(s) piloto +### {% octicon "milestone" aria-label="The milestone icon" %} Phase 1: Pilot project(s) -Para começar a implementar o GHAS, recomendamos começar com alguns projetos/equipes de alto impacto com que pilotar uma primeira implantação. Isto permitirá que um grupo inicial da sua empresa se familiarize com o GHAS, aprenda a habilitar e configurar o GHAS e construa uma base sólida no GHAS antes de fazer a implementação no restante da sua empresa. +To begin implementing GHAS, we recommend beginning with a few high-impact projects/teams with which to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS, learn how to enable and configure GHAS, and build a solid foundation on GHAS before rolling out to the remainder of your company. -### {% octicon "milestone" aria-label="The milestone icon" %} Fase 2: Adesão organizacional & preparação para implementação +### {% octicon "milestone" aria-label="The milestone icon" %} Phase 2: Organizational buy-in & rollout preparation -A fase 2 é um resumo das fases anteriores e a preparação para uma implantação maior do restante da empresa. Nesta fase, a adesão organizacional pode referir-se à decisão da sua empresa de avançar depois do(s) projeto(s) piloto ou o uso e adoção da empresa GHAS ao longo do tempo (isto é mais comum). Se sua empresa decidir adotar o GHAS ao longo do tempo, a fase 2 poderá continuar na fase 3 e assim por diante. +Phase 2 is a recap of previous phases and preparing for a larger rollout across the remainder of the company. In this phase, organizational buy-in can refer to your company’s decision to move forward after the pilot project(s) or the company’s use and adoption of GHAS over time (this is most common). If your company decides to adopt GHAS over time, then phase 2 can continue into phase 3 and beyond. -### {% octicon "milestone" aria-label="The milestone icon" %} Fase 3: Execução completa da organização & gestão de mudanças +### {% octicon "milestone" aria-label="The milestone icon" %} Phase 3: Full organizational rollout & change management -Uma vez que sua empresa está alinhada, você pode começar a implementar o GHAS para o restante da empresa com base no seu plano de implementação. Durante esta fase, é fundamental garantir que um plano foi feito para quaisquer mudanças organizacionais que possam ser feitas durante sua implementação do GHAS e garantir que as equipes entendam a necessidade, valor e impacto da mudança nos fluxos de trabalho atuais. +Once your company is in alignment, you can begin rolling GHAS out to the remainder of the company based on your rollout plan. During this phase, it’s crucial to ensure that a plan has been made for any organizational changes that may need to be made during your rollout of GHAS and ensuring teams understand the need, value, and impact of the change on current workflows. -## Práticas recomendadas para uma implantação bem-sucedida do GHAS +## Best practices for a successful GHAS rollout -Descobrimos que as empresas que concluíram com sucesso as implementações do GHAS têm várias características semelhantes que ajudam a impulsionar seu sucesso. Para ajudar sua empresa a promover o sucesso da implementação do seu GHAS, revise essas práticas recomendadas. +We’ve found that companies that have completed successful GHAS rollouts have several similar characteristics that help drive their success. To help your company increase the success of your GHAS rollout, review these best practices. -### {% octicon "checklist" aria-label="The checklist icon" %} Estabeleça objetivos claros para a implantação da sua empresa +### {% octicon "checklist" aria-label="The checklist icon" %} Set clear goals for your company’s rollout -O estabelecimento de objetivos pode parecer óbvio, mas vemos que algumas empresas que iniciam o GHAS não têm em mente objetivos claros. É mais difícil para essas empresas obter a adesão organizacional verdadeira necessária para concluir o processo de implantação e perceber o valor da GHAS dentro da sua empresa. +Setting goals may seem obvious, but we do see some companies that begin GHAS rollouts with no clear goals in mind. It’s more difficult for these companies to gain the true organizational buy-in that’s needed to complete the rollout process and realize the value of GHAS within their company. -À medida que você começa a planejar para sua implementação, comece a definir os objetivos para o GHAS dentro da sua empresa e certifique-se de que sejam comunicados à sua equipe. Os seus objetivos podem ser altamente detalhados ou simples, desde que haja um ponto de partida e um alinhamento. Isso ajudará a construir uma base para a direção da implantação da sua empresa e poderá ajudar você a construir um plano para chegar lá. Se precisar de ajuda com as suas metas, {% data variables.product.prodname_professional_services %} pode ajudar com as recomendações baseadas na nossa experiência com a sua empresa e compromissos anteriores com outros clientes. +As you begin planning for your rollout and implementation, begin outlining goals for GHAS within your company and ensure these are communicated to your team. Your goals can be highly detailed or something simple, as long as there is a starting point and alignment. This will help build a foundation for the direction of your company’s rollout and can help you build a plan to get there. If you need assistance with your goals, {% data variables.product.prodname_professional_services %} can help with recommendations based on our experience with your company and prior engagements with other customers. -Aqui estão alguns exemplos de alto nível de como seus objetivos para implementar GHAS podem parecer: - - **Reduzindo o número de vulnerabilidades:** Isso pode ser geral ou porque sua empresa foi recentemente afetada por uma vulnerabilidade significativa que você acredita que poderia ter sido prevenida por uma ferramenta como o GHAS. - - **Identificando repositórios de alto risco:** Algumas empresas podem simplesmente querer direcionar repositórios que contenham maior risco, pronto para começar a corrigir vulnerabilidades e reduzir o risco. - - **Aumentando as taxas de remediação:** Isso pode ser feito pela adoção de conclusões do desenvolvedor e por garantir que essas vulnerabilidades sejam corrigidas em tempo hábil. prevenindo a acumulação de dívida de segurança. - - **Requisitos de conformidade da reunião:** Isto pode ser tão simples quanto criar novos requisitos de conformidade ou algo mais específico. Encontramos muitas empresas de saúde que utilizam o GHAS para prevenir a exposição do PHI (Informações sobre saúde pessoal). - - **Evitar a fuga de segredos:** De modo geral, isso é um objetivo das empresas que tiveram (ou querem evitar) vazamento de informações confidenciais como, por exemplo, chaves de software, dados financeiros, dados do cliente, etc. - - **Gerenciamento de dependência:** Este é frequentemente um objetivo para empresas que podem ter sido vítimas devido a hackers de dependências não corrigidas, ou aqueles que procuram prevenir esses tipos de ataques atualizando dependências vulneráveis. +Here are some high-level examples of what your goals for rolling out GHAS might look like: + - **Reducing the number of vulnerabilities:** This may be in general, or because your company was recently impacted by a significant vulnerability that you believe could have been prevented by a tool like GHAS. + - **Identifying high-risk repositories:** Some companies may simply want to target repositories that contain the most risk, ready to begin remediating vulnerabilities and reducing risk. + - **Increasing remediation rates:** This can be accomplished by driving developer adoption of findings and ensuring these vulnerabilities are remediated in a timely manner, preventing the accumulation of security debt. + - **Meeting compliance requirements:** This can be as simple as creating new compliance requirements or something more specific. We find many healthcare companies use GHAS to prevent the exposure of PHI (Personal Health Information). + - **Preventing secrets leakage:** This is often a goal of companies that have had (or want to prevent) critical information leaked such as software keys, customer or financial data, etc. + - **Dependency management:** This is often a goal for companies that may have fallen victim due to hacks from unpatched dependencies, or those seeking to prevent these types of attacks by updating vulnerable dependencies. -### {% octicon "checklist" aria-label="The checklist icon" %} Estabeleça uma comunicação e alinhamento claros entre suas equipes +### {% octicon "checklist" aria-label="The checklist icon" %} Establish clear communication and alignment between your teams -Uma comunicação e um alinhamento claros são essenciais para o sucesso de qualquer projeto, e a implantação do GHAS não é diferente. Descobrimos que as empresas que têm uma comunicação e alinhamento claros entre seus grupos de segurança e desenvolvimento, além do seu patrocinador executivo (CISO ou VP) da compra do GHAS por meio da implantação, muitas vezes têm mais sucesso com a sua implantação. +Clear communication and alignment are critical to the success of any project, and the rollout of GHAS is no different. We’ve found that companies that have clear communication and alignment between their security and development groups, as well as their executive sponsor (either CISO or VP) from the purchase of GHAS through rollout, often have more success with their rollouts. -Além de garantir que estes grupos estejam alinhados ao longo de toda a implementação do GHAS, recomendamos que nos concentremos em algumas áreas específicas. +In addition to ensuring these groups are aligned throughout your GHAS rollout, there are a few specific areas we recommend focusing on. -#### Planejamento da implementação +#### Rollout planning -Como você implementará o GHAS na sua empresa? Provavelmente, haverá muitas ideias e opiniões. Aqui estão algumas perguntas que você deve considerar responder e alinhar antes de avançar: - - Quais equipes serão incluídas no piloto? - - Quais projetos estão focados no piloto? - - Como os projetos devem ser priorizados na execução? - - Como você planeja medir o sucesso no piloto e para além dele? - - Qual é o nível de mudança diária que suas equipes irão enfrentar? Como isso será comunicado? - - Como seus planos de implementação serão comunicados em toda a empresa? - - Como você planeja treinar suas equipes? - - Como você planeja gerenciar os resultados de digitalização inicialmente? (Para obter mais informações, consulte a próxima seção sobre "Processando resultados") +How will you roll out GHAS to your company? There will likely be many ideas and opinions. Here are some questions you should consider answering and aligning on before moving forward: + - What teams will be included in the pilot? + - What projects are focused on in the pilot? + - How should projects be prioritized for rollout? + - How do you plan to measure success in the pilot and beyond? + - What is the level of daily change your teams will be taking on? How will that be communicated? + - How will your rollout plans be communicated across the company? + - How do you plan to train your teams? + - How do you plan to manage scan results initially? (For more information, see the next section on "Processing results") -#### Processando resultados +#### Processing results -Antes de o GHAS ser implementado nas suas equipes, deve haver um claro alinhamento sobre como os resultados devem ser gerenciados ao longo do tempo. We recommend initially looking at results as more informative and non-blocking. É provável que a sua empresa tenha um pipeline de CI/CD completo. Portanto, recomendamos esta abordagem para evitar bloquear o processo da sua empresa. À medida que você se acostuma com o processamento desses resultados, você poderá aumentar gradualmente o nível de restrição para um ponto que você considera mais preciso para sua empresa. +Before GHAS is rolled out to your teams, there should be clear alignment on how results should be managed over time. We recommend initially looking at results as more informative and non-blocking. It’s likely your company has a full CI/CD pipeline, so we recommend this approach to avoid blocking your company’s process. As you get used to processing these results, then you can incrementally increase the level of restriction to a point that feels more accurate for your company. -### {% octicon "checklist" aria-label="The checklist icon" %} lidere a sua implementação com seus grupos de segurança e desenvolvimento +### {% octicon "checklist" aria-label="The checklist icon" %} Lead your rollout with both your security and development groups -Muitas empresas lideram seus esforços do GHAS com seu grupo de segurança. Muitas vezes, as equipes de desenvolvimento não são incluídas no processo de implementação até que o piloto seja concluído. No entanto, descobrimos que as empresas que lideram as implementações tanto com as equipes de segurança quanto de desenvolvimento tendem a ter mais sucesso com a implementação do GHAS. +Many companies lead their GHAS rollout efforts with their security group. Often, development teams aren’t included in the rollout process until the pilot has concluded. However, we’ve found that companies that lead their rollouts with both their security and development teams tend to have more success with their GHAS rollout. -Por que? O GHAS adota uma abordagem centrada no desenvolvedor para a segurança do software, integrando-se perfeitamente ao fluxo de trabalho do desenvolvedor. Não ter uma representação chave do seu grupo de desenvolvimento no início do processo aumenta o risco de sua implantação e cria um caminho rápido para adesões organizacionais. +Why? GHAS takes a developer-centered approach to software security by integrating seamlessly into the developer workflow. Not having key representation from your development group early in the process increases the risk of your rollout and creates an uphill path towards organizational buy-in. -Quando os grupos de desenvolvimento são envolvidos mais cedo (idealmente a partir da compra), os grupos de segurança e desenvolvimento podem alcançar um alinhamento precoce no processo. Isso ajuda a remover silos entre os dois grupos, a construir e a reforçar as suas relações de trabalho, e ajuda a afastar os grupos de uma mentalidade comum de “arremessar as coisas pelo muro”. Todas estas coisas ajudam você a apoiar o objetivo geral de ajudar as empresas a se deslocarem e começarem a utilizar o GHAS para abordar as questões de segurança mais cedo no processo de desenvolvimento. +When development groups are involved earlier (ideally from purchase), security and development groups can achieve alignment early in the process. This helps to remove silos between the two groups, builds and strengthens their working relationships, and helps shift the groups away from a common mentality of “throwing things over the wall.” All of these things help support the overall goal to help companies shift and begin utilizing GHAS to address security concerns earlier in the development process. -#### {% octicon "people" aria-label="The people icon" %} Funções-chave recomendadas para sua equipe de implementação +#### {% octicon "people" aria-label="The people icon" %} Recommended key roles for your rollout team -Recomendamos algumas funções essenciais para a sua equipe a fim de garantir que os seus grupos estejam bem representados durante todo o planejamento e execução da sua implementação. +We recommend a few key roles to have on your team to ensure that your groups are well represented throughout the planning and execution of your rollout and implementation. -É altamente recomendável que a sua equipe de implementação inclua estas funções: -- **Patrocinador Executivo:** De modo geral, é CISO, CIO, VP de Segurança ou VP de Engenharia. -- **Líder de Segurança Técnica:** A liderança de segurança técnica fornece suporte técnico em nome da equipe de segurança durante todo o processo de implementação. -- **Líder de Desenvolvimento Técnico:** A liderança de desenvolvimento técnico fornece suporte técnico e provavelmente liderará o esforço de implementação com a equipe de desenvolvimento. +We highly recommend your rollout team include these roles: +- **Executive Sponsor:** This is often the CISO, CIO, VP of Security, or VP of Engineering. +- **Technical Security Lead:** The technical security lead provides technical support on behalf of the security team throughout the implementation process. +- **Technical Development Lead:** The technical development lead provides technical support and will likely lead the implementation effort with the development team. -Também recomendamos que a sua equipe de implementação inclua estas funções: -- **Gerente de Projeto:** Descobrimos que quanto mais cedo um gerente de projeto pode ser introduzido no processo de execução, maior é a probabilidade de sucesso. -- **Engenheiro de Garantia de Qualidade:** Incluir um integrante da equipe de Garantia de Qualidade da sua empresa ajuda a garantir que as alterações no processo sejam levadas em conta para a equipe de controle de qualidade. +We also recommend your rollout team include these roles: +- **Project Manager:** We’ve found that the earlier a project manager can be introduced into the rollout process the higher the likelihood of success. +- **Quality Assurance Engineer:** Including a member of your company’s Quality Assurance team helps ensure process changes are taken into account for the QA team. -### {% octicon "checklist" aria-label="The checklist icon" %} Entenda os principais fatos do GHAS para evitar equívocos comuns +### {% octicon "checklist" aria-label="The checklist icon" %} Understand key GHAS facts to prevent common misconceptions Going into a GHAS implementation, it’s important to understand some key basic facts about what GHAS is and can do, to prevent many common misconceptions companies have going into their GHAS rollouts. {% note %} -**Observação:** Se estiver interessado em promover a sua formação no GHAS, {% data variables.product.prodname_professional_services %} oferece uma série de opções para formação e treinamento adicionais, incluindo tópicos para os quais a sua empresa precisa se preparar para o GHAS. Estas ofertas podem assumir a forma de oficinas, demonstrações e bootcamps. Os tópicos podem variar desde a implementação do GHAS e do uso básico do GHAS a tópicos mais avançados para continuar desenvolvendo as habilidades da sua equipe. Para obter mais informações sobre como trabalhar com a equipe de {% data variables.product.prodname_professional_services_team %}, consulte "[{% data variables.product.prodname_professional_services %}](#github-professional-services)". +**Note:** If you’re interested in furthering your GHAS education, {% data variables.product.prodname_professional_services %} provides a variety of options for additional education and training, including topics that your company needs to prepare for GHAS. These offerings may take the form of workshops, demonstrations, and bootcamps. Topics can range from deploying GHAS and basic usage of GHAS to more advanced topics to continue to build your team’s skills. For more information on working with the {% data variables.product.prodname_professional_services_team %} team, see "[{% data variables.product.prodname_professional_services %}](#github-professional-services)." {% endnote %} -#### Fato 1: O GHAS é um conjunto de ferramentas de segurança que requerem ação para proteger seu código. +#### Fact 1: GHAS is a suite of security tools that require action to protect your code. -Não é um software de segurança instalado e esquecido — ter apenas um GHAS não protege seu código. O GHAS é um conjunto de ferramentas que aumentam com valor quando configurados, mantidos, usados em fluxos de trabalho diários e em combinação com outras ferramentas. +It’s not security software that is installed and forgotten—just having GHAS on its own does not protect your code. GHAS is a suite of tools that increases with value when configured, maintained, used in daily workflows, and in combination with other tools. -#### Fato 2: O GHAS exigirá um ajuste inovador. +#### Fact 2: GHAS will require adjustment out of the box. -Uma vez que o GHAS é definido nos repositórios, há outras etapas que precisam ser realizadas para garantir o funcionamento das necessidades da empresa. A digitalização de código em particular exige uma configuração adicional para ajustar seus resultado como, por exemplo, a personalização do que é sinalizado pelas verificações para ajustar o que é detectado em futuras digitalizações. Muitos clientes descobrem que as digitalizações iniciais ou não obtêm resultados ou obtêm resultados que não são relevantes com base no modelo de ameaça da aplicação e precisam ser ajustados de acordo com as necessidades da empresa. +Once GHAS is set up on your repositories, there are additional steps that need to be taken to ensure it works for your company’s needs. Code scanning in particular requires further configuration to fine-tune your results, for example, customizing what is flagged by the scans to adjust what is picked up in future scans. Many customers find that initial scans either pick up no results or results that are not relevant based on the application's threat model and need to be adjusted to their company’s needs. -#### Facto 3: As ferramentas do GHAS são mais efetivas quando usadas em conjunto, mas os programas mais eficientes do AppSec envolvem o uso de ferramentas/atividades adicionais. +#### Fact 3: GHAS tools are most effective when used together, but the most effective AppSec programs involve the use of additional tools/activities. -O GHAS é mais eficaz quando todas as ferramentas são utilizadas em conjunto. Quando as empresas integram o GHAS a outras ferramentas e atividades como, por exemplo, testes de penetração e scanners dinâmicos, ele melhora ainda a eficácia do programa AppSec. Recomendamos sempre a utilização de múltiplas camadas de proteção. +GHAS is most effective when all of the tools are used together. When companies integrate GHAS with other tools and activities, such as penetration testing and dynamic scans, it further improves the effectiveness of the AppSec program. We recommend always utilizing multiple layers of protection. -#### Fato 4: Nem todas as empresas irão usar/precisar de consultas personalizadas de {% data variables.product.prodname_codeql %}, mas elas podem ajudar você a personalizar/apontar para resultados de verificação. +#### Fact 4: Not all companies will use/need custom {% data variables.product.prodname_codeql %} queries, but they can help you customize/target scan results. -A digitalização de código é fornecida por {% data variables.product.prodname_codeql %} — o mecanismo de análise de código mais poderoso do mundo. Embora muitas empresas estejam entusiasmadas com a perspectiva de serem capazes de escrever consultas personalizadas, para uma grande parte dos nossos clientes, o conjunto base de consultas e consultas adicionais disponíveis na comunidade é, de modo geral, mais do que suficiente. However, many companies may find the need for custom {% data variables.product.prodname_codeql %} queries to help reduce false positives rates in results or crafting new queries to target results your company may need. +Code scanning is powered by {% data variables.product.prodname_codeql %}—the world’s most powerful code analysis engine. While many companies are excited at the prospect of being able to write custom queries, for a large portion of our customers the base query set and additional queries available in the community are typically more than sufficient. However, many companies may find the need for custom {% data variables.product.prodname_codeql %} queries to help reduce false positives rates in results or crafting new queries to target results your company may need. However, if your company is interested in writing custom {% data variables.product.prodname_codeql %} queries, we recommend you complete your rollout and implementation of GHAS before exploring custom queries. @@ -150,7 +152,7 @@ However, if your company is interested in writing custom {% data variables.produ {% endnote %} -When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use cases for custom queries. +When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use cases for custom queries. #### Fact 5: {% data variables.product.prodname_codeql %} scans the whole code base, not just the changes made in a pull request. @@ -160,7 +162,7 @@ When code scanning is run from a pull request, the scan will include the full co Now that you have a better understanding of some of the keys to a successful GHAS rollout and implementation, here are some examples of how our customers made their rollouts successful. Even if your company is in a different place, {% data variables.product.prodname_dotcom %} can help you with building a customized path that suits the needs of your rollout. -### Example rollout for a mid-sized healthcare technology company +### Example rollout for a mid-sized healthcare technology company A mid-sized healthcare technology company based out of San Francisco completed a successful GHAS rollout process. While they may not have had a large number of repositories that needed to be enabled, this company’s keys to success included having a well-organized and aligned team for the rollout, with a clearly established key contact to work with {% data variables.product.prodname_dotcom %} to troubleshoot any issues during the process. This allowed them to complete their rollout within two months. @@ -192,11 +194,11 @@ There are a few different paths that can be taken for your GHAS installation bas It’s important that you’re utilizing a version of {% data variables.product.prodname_ghe_server %} (GHES) that will support your company’s needs. -If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. Para obter mais informações, consulte: +If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. For more information, see: - "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)" - "[Upgrade requirements](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)" -If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. Para obter mais informações, consulte "[Sobre a verificação de código CodeQL no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." +If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." If you're working with {% data variables.product.prodname_professional_services %} for your GHAS rollout, please be prepared to discuss these items at length in your kickoff meeting. diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md deleted file mode 100644 index 68611bb123..0000000000 --- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Permitir a autenticação integrada para usuários de fora do provedor de identidade -intro: 'Com a autenticação integrada, você pode autenticar usuários que não têm acesso ao seu provedor de identidade que usa LDAP, SAML ou CAS.' -redirect_from: - - /enterprise/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider - - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider -versions: - ghes: '*' -type: how_to -topics: - - Accounts - - Authentication - - Enterprise - - Identity -shortTitle: Autenticação fora do IdP ---- - -## Sobre a autenticação integrada para usuários de fora do provedor de identidade - -É possível usar a autenticação integrada para usuários externos quando você não conseguir adicionar contas específicas ao seu provedor de identidade (IdP), como contas de contratados ou usuários de máquinas. Você também pode usar a autenticação integrada para acessar uma conta de fallback se o provedor de identidade não estiver disponível. - -Após a configuração da autenticação integrada, quando um usuário se autenticar com êxito via SAML ou CAS, ele não poderá se autenticar com nome de usuário e senha. Se o usuário se autenticar com êxito via LDAP, as credenciais não serão mais consideradas internas. - -A autenticação integrada para um IdP específico fica desabilitada por padrão. - -{% warning %} - -**Aviso:** se desabilitar a autenticação integrada, você terá que suspender individualmente todos os usuários que não devem mais ter acesso à instância. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)". - -{% endwarning %} - -## Configurar a autenticação integrada para usuários de fora do provedor de identidade - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -4. Selecione seu provedor de identidade. ![Opção Select identity provider (Selecionar provedor de identidade) -](/assets/images/enterprise/management-console/identity-provider-select.gif) -5. Selecione **Allow creation of accounts with built-in authentication** (Permitir a criação de contas com autenticação integrada). ![Opção Select built-in authentication (Selecionar autenticação integrada)](/assets/images/enterprise/management-console/built-in-auth-identity-provider-select.png) -6. Leia o aviso e clique em **Ok**. - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.2fa_is_available %} - -## Convidar usuários de fora do provedor de identidade para autenticação na sua instância - -Quando aceitar o convite, o usuário poderá fazer login com seu próprio nome de usuário e senha, em vez de fazer login via IdP. - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} -{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} - -## Leia mais - -- /enterprise/{{ page.version }}/admin/guides/user-management/using-ldap -- [Usar SAML](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-saml) -- [Usar CAS](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-cas) diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md deleted file mode 100644 index 60178e6778..0000000000 --- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -title: Usar SAML -redirect_from: - - /enterprise/admin/articles/configuring-saml-authentication/ - - /enterprise/admin/articles/about-saml-authentication/ - - /enterprise/admin/user-management/using-saml - - /enterprise/admin/authentication/using-saml - - /admin/authentication/using-saml -intro: 'O SAML é um padrão de autenticação e autorização baseado em XML. O {% data variables.product.prodname_ghe_server %} pode agir como provedor de serviços (SP, Service Provider) com seu provedor de identidade (IdP, Identity Provider) SAML interno.' -versions: - ghes: '*' -type: how_to -topics: - - Accounts - - Authentication - - Enterprise - - Identity - - SSO ---- - -{% data reusables.enterprise_user_management.built-in-authentication %} - -## Serviços SAML compatíveis - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.saml.saml-single-logout-not-supported %} - -## Considerações de nome de usuário no SAML - -Cada nome de usuário do {% data variables.product.prodname_ghe_server %} é determinado por uma das seguintes afirmações na resposta SAML, ordenada por prioridade: - -- Nome de usuário personalizado, se houver; -- Declaração `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`, se houver; -- Declaração `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`, se houver; -- Elemento `NameID`. - -O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam presentes. - -É criado um mapeamento entre `NameID` e o nome de usuário do {% data variables.product.prodname_ghe_server %}. Portanto, o `NameID` deve ser persistente, exclusivo e não estar sujeito a alterações no ciclo de vida do usuário. - -{% note %} - -**Observação**: Se o `NameID` para um usuário for alterado no IdP, o usuário verá uma mensagem de erro ao tentar entrar na sua instância do {% data variables.product.prodname_ghe_server %}. {% ifversion ghes %}Para restaurar o acesso do usuário, você precisa atualizar o mapeamento do `NameID` da conta do usuário. Para obter mais informações, consulte "[Atualizar o `NameIDo`](#updating-a-users-saml-nameid) do SAML.{% else %} Para obter mais informações, consulte "[Erro: 'Outro usuário já possui a conta'](#error-another-user-already-owns-the-account)."{% endif %} - -{% endnote %} - -{% data reusables.enterprise_management_console.username_normalization %} - -{% data reusables.enterprise_management_console.username_normalization_sample %} - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.external_auth_disables_2fa %} - -## Metadados SAML - -Os metadados do seu provedor de serviço da instância de {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`. - -Para configurar seu provedor de identidade manualmente, a URL do serviço de consumidor de declaração (ACS, Assertion Consumer Service) é `http(s)://[hostname]/saml/consume` e usa a associação `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. - -## Atributos SAML - -Os atributos a seguir estão disponíveis. Você pode alterar seus nomes no [console de gerenciamento](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), exceto o atributo `administrator`. - -| Nome padrão do atributo | Tipo | Descrição | -| ----------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `NameID` | Obrigatório | Identificador de usuário persistente. Qualquer formato de identificador de nome persistente pode ser usado. O elemento `NameID` será usado para um nome de usuário do {% data variables.product.prodname_ghe_server %}, a menos que uma das declarações alternativas seja fornecida. | -| `administrador` | Opcional | Quando o valor for 'true', o usuário será promovido automaticamente como administrador. Qualquer outro valor ou um valor não existente rebaixará o usuário para uma conta regular. | -| `nome de usuário` | Opcional | Nome do usuário no {% data variables.product.prodname_ghe_server %}. | -| `full_name` | Opcional | Nome do usuário exibido na página de perfil. Após o provisionamento, os usuários podem alterar seus nomes. | -| `emails` | Opcional | Endereços de e-mail para o usuário. É possível especificar mais de um. | -| `public_keys` | Opcional | Chaves SSH públicas para o usuário. É possível especificar mais de um. | -| `gpg_keys` | Opcional | Chaves chaves GPG para o usuário. É possível especificar mais de um. | - -## Definir configurações SAML - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -3. Selecione **SAML**. ![Autenticação SAML](/assets/images/enterprise/management-console/auth-select-saml.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -5. Para habilitar SSO de resposta não solicitada, selecione **IdP initiated SSO** (SSO iniciado pelo IdP). Por padrão, o {% data variables.product.prodname_ghe_server %} responderá a uma solicitação iniciada pelo Provedor de identidade (IdP) não solicitado com `AuthnRequest`. ![SAML idP SSO](/assets/images/enterprise/management-console/saml-idp-sso.png) - - {% tip %} - - **Observação**: é recomendável manter esse valor **desmarcado**. Você deve habilitar esse recurso **somente ** na rara instância em que sua implementação SAML não oferecer suporte ao SSO iniciado pelo provedor de serviços e quando recomendado pelo {% data variables.contact.enterprise_support %}. - - {% endtip %} - -5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. ![Configuração de desabilitar administrador de SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTP ou HTTPS do seu IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o nome do host só estiver disponível na rede interna, talvez seja necessário [configurar a {% data variables.product.product_location %} para usar servidores de nomes internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticação SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png) -7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Fazer isso verifica a autenticidade das mensagens enviadas para a {% data variables.product.product_location %}. ![Emissor SAML](/assets/images/enterprise/management-console/saml-issuer.png) -8. Nos menus suspensos **Signature Method** (Método de assinatura) e **Digest Method** (Método de compilação), escolha o algoritmo de hash usado pelo emissor SAML para verificar a integridade das solicitações do {% data variables.product.product_location %}. Especifique o formato no menu suspenso **Name Identifier Format** (Formato de identificador de nome). ![Método SAML ](/assets/images/enterprise/management-console/saml-method.png) -9. Em **Verification certificate** (Certificado de verificação), clique em **Choose File** (Escolher arquivo) e escolha um certificado para validar as respostas SAML do IdP. ![Autenticação SAML](/assets/images/enterprise/management-console/saml-verification-cert.png) -10. Modifique os nomes do atributo SAML para corresponder ao IdP, se necessário, ou aceite os nomes padrão. ![Nomes de atributos SAML](/assets/images/enterprise/management-console/saml-attributes.png) - -{% ifversion ghes %} - -## Revogar o acesso à {{ site.data.variables.product.product_location_enterprise }} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -2. Selecione **SAML**. ![Barra lateral "Todos os usuários" nas configurações de administrador do site](/assets/images/enterprise/site-admin-settings/all-users.png) -3. Na lista de usuários, clique no nome de usuário para o qual você gostaria de atualizar o mapeamento de `NameID`. ![Nome de usuário na lista de contas do usuário da instância](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) -{% data reusables.enterprise_site_admin_settings.security-tab %} -5. À direita de "Atualizar o NameID do SAML", clique em **Editar**. ![Botão "Editar" em "autenticação do SAML" e à direita "Atualizar o NameID do SAML"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) -6. No campo "NameID", digite o novo `NameID` para o usuário. ![Campo "NameID" na caixa de diálogo modal com NameID digitado](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) -7. Em **Verification certificate** (Certificado de verificação), clique em **Choose File** (Escolher arquivo) e escolha um certificado para validar as respostas SAML do IdP. ![Botão "Atualizar o NameID" com o valor do NameID atualizado dentro do modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) - -{% endif %} - -## Revogar o acesso à {% data variables.product.product_location %} - -Se remover um usuário do seu provedor de identidade, você também deverá suspendê-lo manualmente. Caso contrário, ele continuará podendo fazer autenticação usando tokens de acesso ou chaves SSH. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". - -## Requisitos de mensagem de resposta - -A mensagem de resposta deve atender aos seguintes requisitos: - -- O `` elemento deve sempre ser fornecido no documento de resposta raiz e deve corresponder ao URL do ACS somente quando o documento de resposta raiz estiver assinado. Se for assinada, a declaração será ignorada. -- O elemento `` deve sempre ser fornecido como parte do elemento ``. O elemento `` deve sempre ser fornecido como parte do elemento ``. Esta é a URL para a instância do {% data variables.product.prodname_ghe_server %}, como `https://ghe.corp.example.com`. -- Todas as declarações na resposta **devem** ser precedidas de assinatura digital. É possível fazer isso assinando cada elemento `` ou assinando o elemento ``. -- Um elemento `` deve ser fornecido como parte do elemento ``. Qualquer formato de identificador de nome persistente pode ser usado. -- O atributo `Recipient` deve estar presente e definido na URL do ACS. Por exemplo: - -```xml - - - - ... - - - - - - - monalisa - - - - -``` - -## Autenticação SAML - -Mensagens de erro de registro de {% data variables.product.prodname_ghe_server %} para autenticação do SAML falhada no registro de autenticação em _/var/log/github/auth.log_. Para obter mais informações sobre os requisitos de resposta do SAML, consulte "[Requisitos de mensagem de resposta](#response-message-requirements)". - -### Erro: "Outro usuário já possui a conta" - -Quando um usuário inicia a sessão em {% data variables.product.prodname_ghe_server %} pela primeira vez com autenticação do SAML, {% data variables.product.prodname_ghe_server %} cria uma conta de usuário na instância e mapeia o `NameID` do SAML com a conta. - -Quando o usuário inicia a sessão novamente, {% data variables.product.prodname_ghe_server %} compara o mapeamento do `NameID` da conta com a resposta do IdP. Se o `NameID` na resposta do IdP não corresponder mais ao `NameID` que {% data variables.product.prodname_ghe_server %} espera para o usuário. ocorrerá uma falha no login. O usuário receberá a seguinte mensagem. - -> Outro usuário já possui a conta. Solicite ao administrador que verifique o registro de autenticação. - -De modo geral, a mensagem indica que o nome de usuário ou endereço de email da pessoa foi alterado no IdP. {% ifversion ghes %}Certifique-se de que o mapeamento do `NameID` para a conta do usuário no {% data variables.product.prodname_ghe_server %} corresponde ao `NameID` do usuário no seu IdP. Para obter mais informações, consulte "[Atualizar o `NameID`](#updating-a-users-saml-nameid) do SAML.{% else %}Para obter ajuda para atualizar o mapeamento do `NameID`, entre em contato com {% data variables.contact.contact_ent_support %}.{% endif %} - -### Se a resposta SAML não estiver assinada ou se a assinatura não corresponder ao conteúdo, o log de autenticação mostrará a seguinte mensagem de erro: - -Se `Recipient` não corresponder à URL do ACS, o log de autenticação mostrará a seguinte mensagem de erro: - -``` -Recipient na resposta SAML não pode ficar em branco. -``` - -``` -Recipient na resposta SAML não era válido. -``` - -Certifique-se de definir o valor de `Destinatário` no seu IdP como a URL do ACS completo para a sua instância do {% data variables.product.prodname_ghe_server %}. Por exemplo, `https://ghe.corp.example.com/saml/consume`. - -### Erro: "Resposta do SAML não foi assinada ou foi modificada" - -Se seu IdP não assinar a resposta do SAML ou a assinatura não corresponder ao conteúdo, será exibida a seguinte mensagem de erro no registro de autenticação. - -``` -Resposta SAML não assinada ou modificada. -``` - -Certifique-se de que você configurou as declarações assinadas para o aplicativo de {% data variables.product.prodname_ghe_server %} no seu IdP. - -### Erro: "Audiência é inválida" ou "Nenhuma declaração encontrada" - -Se a resposta do IdP tiver um valor ausente ou incorreto para `Audiência`, a seguinte mensagem de erro aparecerá no registro de autenticação. - -```shell -Audience inválido. O atributo Audience não corresponde a url_sua_instância -``` - -Certifique-se de definir o valor para `Audiência` no seu IdP para a `EntityId` para a sua instância do {% data variables.product.prodname_ghe_server %}, que é a URL completa para sua instância do {% data variables.product.prodname_ghe_server %}. Por exemplo, `https://ghe.corp.example.com`. diff --git a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md index bf2031fcb0..2700c6ee2e 100644 --- a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md +++ b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: Sobre usuários gerenciados pela empresa -shortTitle: Sobre usuários gerenciados -intro: 'Você pode gerenciar centralmente a identidade e o acesso dos integrantes da empresa em {% data variables.product.prodname_dotcom %} a partir do seu provedor de identidade.' +title: About Enterprise Managed Users +shortTitle: About managed users +intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' product: '{% data reusables.gated-features.emus %}' redirect_from: - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise @@ -16,54 +16,54 @@ topics: - SSO --- -## Sobre o {% data variables.product.prodname_emus %} +## About {% data variables.product.prodname_emus %} -Com {% data variables.product.prodname_emus %}, você pode controlar as contas de usuário dos integrantes da empresa por meio do provedor de identidade (IdP). Você pode simplificar a autenticação com o logon único SAML (SSO) e provisionar atualizar e cancelar o provisionamento das contas de usuário para os membors da sua empresa. Os usuários atribuídos ao aplicativo {% data variables.product.prodname_emu_idp_application %} no seu IdP são provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} e adicionados à sua empresa. Você controla nomes de usuários, dados de perfil, associação de equipe e acesso ao repositório a partir do seu IdP. +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. -No seu IdP, você pode dar a cada {% data variables.product.prodname_managed_user %} a função do proprietário da empresa, usuário ou gerente de cobrança. {% data variables.product.prodname_managed_users_caps %} pode possuir organizações dentro da sua empresa e pode adicionar outros {% data variables.product.prodname_managed_users %} às organizações e equipes internamente. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" e "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Você também pode gerenciar a associação à equipe de uma organização na sua empresa diretamente por meio do seu IdP, permitindo que você gerencie o acesso ao repositório usando grupos no seu IdP. Os integrantes da organização podem ser gerenciados manualmente ou atualizados automaticamente pois {% data variables.product.prodname_managed_users %} são adicionados às equipes da organização. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". +You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." -Você pode conceder {% data variables.product.prodname_managed_users %} acesso e a capacidade de contribuir para repositórios na sua empresa, mas {% data variables.product.prodname_managed_users %} não pode criar conteúdo público ou colaborar com outros usuários, organizações e empresas no resto de {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_managed_users %} provisionado para sua empresa não pode ser convidado para organizações ou repositórios fora da empresa, nem {% data variables.product.prodname_managed_users %} pode ser convidado para outras empresas. Os colaboradores externos não são compatíveis com {% data variables.product.prodname_emus %}. +You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. -Os nomes de usuário do {% data variables.product.prodname_managed_users %} da empresa e as suas informações de perfil como, por exemplo, nomes de exibição e endereços de e-mail, são definidos por meio do seu IdP e não podem ser alterados pelos próprios usuários. Para obter mais informações, consulte "[Nomes de usuário e informações do perfil](#usernames-and-profile-information)". +The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." {% data reusables.enterprise-accounts.emu-forks %} -Os proprietários de empresas podem auditar todas as ações de {% data variables.product.prodname_managed_users %}' em {% data variables.product.prodname_dotcom %}. +Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. -Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para obter mais informações sobre a criação desta conta, consulte "[Sobre empresas com usuários gerenciados](#about-enterprises-with-managed-users)". +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." -## Suporte do provedor de identidade +## Identity provider support -{% data variables.product.prodname_emus %} é compatível com os seguintes IdPs: +{% data variables.product.prodname_emus %} supports the following IdPs: {% data reusables.enterprise-accounts.emu-supported-idps %} -## Habilidades e restrições de {% data variables.product.prodname_managed_users %} +## Abilities and restrictions of {% data variables.product.prodname_managed_users %} -O {% data variables.product.prodname_managed_users_caps %} só pode contribuir para repositórios privados e internos da sua empresa e repositórios privados pertencentes à sua conta de usuário. {% data variables.product.prodname_managed_users_caps %} tem acesso somente leitura a toda a comunidade de {% data variables.product.prodname_dotcom %} em geral. +{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. -* {% data variables.product.prodname_managed_users_caps %} não pode criar problemas ou pull requests, comentar ou adicionar reações, nem estrelas, inspeção ou repositórios de bifurcação fora da empresa. -* {% data variables.product.prodname_managed_users_caps %} não pode fazer push de código para repositórios fora da empresa. -* {% data variables.product.prodname_managed_users_caps %} e o conteúdo que criaa é visível apenas para outros integrantes da empresa. -* {% data variables.product.prodname_managed_users_caps %} não pode seguir os usuários fora da empresa. -* {% data variables.product.prodname_managed_users_caps %} não pode criar gists ou comentários em gists. -* {% data variables.product.prodname_managed_users_caps %} não pode instalar {% data variables.product.prodname_github_apps %} nas suas contas de usuário. -* Outros usuários de {% data variables.product.prodname_dotcom %} não podem ver, mencionar ou convidar um {% data variables.product.prodname_managed_user %} para colaborar. -* {% data variables.product.prodname_managed_users_caps %} só pode criar repositórios privados e {% data variables.product.prodname_managed_users %} só pode convidar outros integrantes da empresa para colaborar nos seus próprios repositórios. -* Apenas repositórios privados e internos podem ser criados em organizações pertencentes a um {% data variables.product.prodname_emu_enterprise %}, dependendo das configurações de visibilidade da organização e do repositório corporativo. +* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. +* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. -## Sobre empresas com usuários gerenciados +## About enterprises with managed users -Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para experimentar {% data variables.product.prodname_emus %} ou para discutir opções para a migração da sua empresa existente, entre em contato com a [Equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). -Seu contato na equipe do GitHub de vendas vai trabalhar com você para criar seu novo {% data variables.product.prodname_emu_enterprise %}. Você deverá fornecer o endereço de e-mail para o usuário que irá configurar sua empresa e um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} Para obter mais informações, consulte "[Nomes de usuário e informações do perfil](#usernames-and-profile-information)" +Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." -Após criarmos sua empresa, você receberá um e-mail de {% data variables.product.prodname_dotcom %} convidando você a escolher uma senha para o usuário de configuração da sua empresa, que será o primeiro proprietário da empresa. O usuário de configuração é usado apenas para configurar o logon único SAML e o provisionamento do SCIM para a empresa. Ele não terá mais acesso para administrar a conta corporativa assim que o SAML for habilitado com sucesso. +After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled. -O nome do usuário de configuração é o código curto da sua empresa com o sufixo `_admin`. Depois de efetuar o login no seu usuário de configuração, você pode começar configurando o SAML SSO para a sua empresa. Para obter mais informações, consulte "[Configurando o logon único SAML para Usuários Gerenciados pela Empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." +The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." {% note %} @@ -71,18 +71,18 @@ O nome do usuário de configuração é o código curto da sua empresa com o suf {% endnote %} -## Efetuar a autenticação um {% data variables.product.prodname_managed_user %} +## Authenticating as a {% data variables.product.prodname_managed_user %} -{% data variables.product.prodname_managed_users_caps %} deve efetuar a autenticação por meio de seu provedor de identidade. +{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. -Para efetuar a autenticação, {% data variables.product.prodname_managed_users %} deverá acessar o portal do aplicativo do IdP ou **https://github.com/enterprises/ENTERPRISE_NAME**, substituindo **ENTERPRISE_NAME** pelo nome da sua empresa. +To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name. -## Nome de usuário e informações de perfil +## Usernames and profile information -Quando o seu {% data variables.product.prodname_emu_enterprise %} for criado, você escolherá um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} O usuário configurado que configurar o SAML SSO terá um nome de usuário no formato de **@SHORT-CODE_admin**. +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. -Ao fornecer um novo usuário a partir do provedor de identidade, o novo {% data variables.product.prodname_managed_user %} terá um nome de usuário de {% data variables.product.product_name %} no formato de **@IDP-USERNAME_SHORT-CODE**. Ao usar o Diretório Ativo do Azure (Azure AD), _IDP-USERNAME_ é formado, normalizando os caracateres anteriores ao caractere `@` no UPN (Nome Principal do usuário) fornecido pelo Azure AD. Ao usar o Okta, o _IDP-USERNAME_ é o atributo de nome de usuário normalizado fornecido pelo Okta. +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@IDP-USERNAME_SHORT-CODE**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta. -O nome de usuário da nova conta provisionada em {% data variables.product.product_name %}, incluindo sublinhado e código curto, não deverá exceder 39 caracteres. +The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters. -O nome do perfil e endereço de email de um {% data variables.product.prodname_managed_user %} também é fornecido pelo IdP. {% data variables.product.prodname_managed_users_caps %} não pode alterar seu nome de perfil ou endereço de e-mail em {% data variables.product.prodname_dotcom %}. +The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md new file mode 100644 index 0000000000..c334869985 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md @@ -0,0 +1,38 @@ +--- +title: Configuring custom footers +intro: 'You can give users easy access to enterprise-specific links by adding custom footers to {% data variables.product.product_name %}.' +versions: + ghec: '*' + ghes: '>=3.4' +type: how_to +topics: + - Enterprise + - Fundamentals +shortTitle: Configure custom footers +--- +Enterprise owners can configure {% data variables.product.product_name %} to show custom footers with up to five additional links. + +![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png) + +The custom footer is displayed above the {% data variables.product.prodname_dotcom %} footer {% ifversion ghes or ghae %}to all users, on all pages of {% data variables.product.product_name %}{% else %}to all enterprise members and collaborators, on all repository and organization pages for repositories and organizations that belong to the enterprise{% endif %}. + +## Configuring custom footers for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} + +1. Under "Settings", click **Profile**. +{%- ifversion ghec %} +![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png) +{%- else %} +![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png) +{%- endif %} + +1. At the top of the Profile section, click **Custom footer**. +![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png) + +1. Add up to five links in the fields shown. +![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png) + +1. Click **Update custom footer** to save the content and display the custom footer. +![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md index 1f84ff046f..d5d41ee13a 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Configurar o GitHub Pages para a sua empresa -intro: 'Você pode habilitar ou desabilitar {% data variables.product.prodname_pages %} para a sua empresa e escolher se deseja tornar os sites acessíveis ao público.' +title: Configuring GitHub Pages for your enterprise +intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.' redirect_from: - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/ - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/ @@ -16,55 +16,54 @@ type: how_to topics: - Enterprise - Pages -shortTitle: Configurar o GitHub Pages +shortTitle: Configure GitHub Pages --- -## Habilitar sites públicos para {% data variables.product.prodname_pages %} +{% ifversion ghes %} -{% ifversion ghes %}Se o modo privado for habilitado na sua empresa, o {% else %}O {% endif %}público não poderá acessar sites de {% data variables.product.prodname_pages %} hospedados pela sua empresa, a menos que você habilite os sites públicos. +## Enabling public sites for {% data variables.product.prodname_pages %} + +If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites. {% warning %} -**Aviso:** Se você habilitar sites públicos para {% data variables.product.prodname_pages %}, todos os sites em cada repositório da sua empresa serão acessíveis ao público. +**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public. {% endwarning %} -{% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -4. Selecione **Public Pages** (Pages público). ![Caixa de seleção para deixar o Pages acessível publicamente](/assets/images/enterprise/management-console/public-pages-checkbox.png) +4. Select **Public Pages**. + ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} -{% elsif ghae %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.pages-tab %} -5. Em "Páginas políticas", selecione **{% data variables.product.prodname_pages %}públicas**. ![Caixa de seleção para habilitar as {% data variables.product.prodname_pages %} públicas](/assets/images/enterprise/business-accounts/public-github-pages-checkbox.png) -{% data reusables.enterprise-accounts.pages-policies-save %} -{% endif %} -## Desabilitar {% data variables.product.prodname_pages %} para a sua empresa +## Disabling {% data variables.product.prodname_pages %} for your enterprise -{% ifversion ghes %} -Se o isolamento de subdomínio estiver desabilitado para sua empresa, você também deverá desabilitar {% data variables.product.prodname_pages %} para se proteger de possíveis vulnerabilidades de segurança. Para obter mais informações, consulte "[Habilitar o isolamento de subdomínio](/admin/configuration/enabling-subdomain-isolation)". -{% endif %} +If subdomain isolation is disabled for your enterprise, you should also disable {% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. For more information, see "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)." -{% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -4. Desmarque a seleção na caixa **Enable Pages** (Habilitar Pages). ![Caixa de seleção para desabilitar o{% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) +4. Unselect **Enable Pages**. + ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) {% data reusables.enterprise_management_console.save-settings %} -{% elsif ghae %} + +{% endif %} + +{% ifversion ghae %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.pages-tab %} -5. Em "Páginas políticas", desmarque **{% data variables.product.prodname_pages %}públicas**. ![Caixa de seleção para desabilitar o{% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) +5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**. + ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} + {% endif %} {% ifversion ghes %} -## Leia mais +## Further reading -- "[Habilitar o modo privado](/admin/configuration/enabling-private-mode)" +- "[Enabling private mode](/admin/configuration/enabling-private-mode)" {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md deleted file mode 100644 index ed9ee19b6c..0000000000 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Configurar limites de taxa -intro: 'É possível definir limites de taxa no {% data variables.product.prodname_ghe_server %} usando o {% data variables.enterprise.management_console %}.' -redirect_from: - - /enterprise/admin/installation/configuring-rate-limits - - /enterprise/admin/configuration/configuring-rate-limits - - /admin/configuration/configuring-rate-limits -versions: - ghes: '*' -type: how_to -topics: - - Enterprise - - Infrastructure - - Performance ---- - -## Habilitar limites de taxa para a {% data variables.product.prodname_enterprise_api %} - -Habilitar limites de taxa na {% data variables.product.prodname_enterprise_api %} pode impedir o uso excessivo de recursos por usuários individuais ou não autenticados. Para obter mais informações, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)". - -{% ifversion ghes %} -Habilitar limites de taxa na {{ site.data.variables.product.prodname_enterprise_api }} pode impedir o uso excessivo de recursos por usuários individuais ou não autenticados. Para obter mais informações, consulte "[Limitação de taxa](/enterprise/{{ page.version }}/v3/#rate-limiting)". -{% endif %} - -{% note %} - -**Observação:** o {% data variables.enterprise.management_console %} lista o período (por minuto ou hora) para cada limite de taxa. - -{% endnote %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. Em "Limitede taxa", selecione **Habilitar limite de taxa para a API HTTP**. ![Caixa de seleção para habilitar limite de taxas de API](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png) -3. Informe os limites para solicitações autenticadas e não autenticadas de cada API ou aceite os limites padrão sugeridos. -{% data reusables.enterprise_management_console.save-settings %} - -## Habilitar limites de taxa secundária - -A configuração dos limites de taxa secundária protege o nível geral do serviço em {% data variables.product.product_location %}. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% ifversion ghes > 3.1 %} -2. Em "Limite de taxa", selecione **Habilitar taxa de limite secundária**. ![Caixa de seleção para habilitar o limite de taxa secundária](/assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png) -{% else %} -2. Em "Limites de taxa", selecione **Enable Abuse Rate Limiting** (Habilitar limite de taxa de abuso). ![Caixa de seleção para habilitar limite de taxas de abuso](/assets/images/enterprise/management-console/abuse-rate-limits-checkbox.png) -{% endif %} -3. Informe os limites para Solicitações totais, Limite de CPU e Limite de CPU para pesquisa ou aceite os limites padrão sugeridos. -{% data reusables.enterprise_management_console.save-settings %} - -## Habilitar limites de taxa do Git - -É possível aplicar limites de taxa do Git por rede de repositório ou ID do usuário. Os limites da taxa do Git são expressos em operações simultâneas por minuto e são adaptáveis com base na carga atual da CPU. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. Em "Rate Limiting" (Limites de taxa), selecione **Enable Git Rate Limiting** (Habilitar limite de taxa do Git). ![Caixa de seleção para habilitar limite de taxas do Git](/assets/images/enterprise/management-console/git-rate-limits-checkbox.png) -3. Digite limites para cada rede de repositório ou ID do usuário. ![Campos para limites de rede de repositório e ID do usuário](/assets/images/enterprise/management-console/example-git-rate-limits.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md index 94c4ad5990..d92f270477 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Configurar a sua empresa -intro: 'Depois que {% data variables.product.product_name %} estiver pronto e funcionando, você poderá configurar a sua empresa para atender às necessidades da sua organização.' +title: Configuring your enterprise +intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.' redirect_from: - /enterprise/admin/guides/installation/basic-configuration/ - /enterprise/admin/guides/installation/administrative-tools/ @@ -34,6 +34,7 @@ children: - /restricting-network-traffic-to-your-enterprise - /configuring-github-pages-for-your-enterprise - /configuring-the-referrer-policy-for-your-enterprise -shortTitle: Configure sua empresa + - /configuring-custom-footers +shortTitle: Configure your enterprise --- diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md deleted file mode 100644 index b0b0748a9d..0000000000 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -title: Painel de administração do site -intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}' -redirect_from: - - /enterprise/admin/articles/site-admin-dashboard/ - - /enterprise/admin/installation/site-admin-dashboard - - /enterprise/admin/configuration/site-admin-dashboard - - /admin/configuration/site-admin-dashboard -versions: - ghes: '*' - ghae: '*' -type: reference -topics: - - Enterprise - - Fundamentals ---- - -Para acessar o painel, clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) - -{% ifversion ghes or ghae %} - -## Pesquisar - -Neste espaço, é possível iniciar o {{ site.data.variables.enterprise.management_console }} para gerenciar configurações do appliance virtual, como domínio, autenticação e SSL. - -{% else %} - -## Informações de licença e pesquisa - -Consulte esta seção do painel de administração do site para verificar sua licença atual do {% data variables.product.prodname_enterprise %}, pesquisar usuários e repositórios e consultar o [log de auditoria](#audit-log). - -{% endif %} -{% ifversion ghes %} -## {% data variables.enterprise.management_console %} - -Neste espaço, é possível iniciar o {% data variables.enterprise.management_console %} para gerenciar configurações do appliance virtual, como domínio, autenticação e SSL. -{% endif %} -## Explorar - -Os dados da [página de tendências][] do GitHub são calculados em intervalos diários, semanais e mensais para repositórios e desenvolvedores. Veja qual foi a última vez que os dados ficaram em cache e organize em fila os trabalhos de cálculo de tendências na seção **Explorar**. - -## Log de auditoria - -O {% data variables.product.product_name %} mantém um log de execução das ações auditadas, e essas informações ficam disponíveis para consulta. - -Por padrão, o log de auditoria mostra uma lista de todas as ações auditadas em ordem cronológica inversa. Você pode filtrar essa lista inserindo pares chave-valor na caixa de texto **Query** (Consulta) e clicando em **Search** (Pesquisar), conforme a explicação em "[Pesquisar no log de auditoria](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)". - -Para obter mais informações sobre o log de auditoria em geral, consulte "[Log de auditoria](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". Para obter uma lista completa de ações auditadas, consulte "[Ações auditas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". - -## Relatórios - -Para obter informações sobre usuários, organizações e repositórios da {% data variables.product.product_location %}, você normalmente faria fetch de dados JSON na [API do GitHub](/rest). Infelizmente, a API pode não fornecer todos os dados necessários e ainda requer um pouco de conhecimento técnico. O painel de administração do site oferece uma seção **Reports** (Relatórios) como alternativa, facilitando o download de relatórios CSV com a maioria das informações necessárias para usuários, organizações e repositórios. - -Especificamente, é possível baixar relatórios CSV que listem o seguinte: - -- todos os usuários; -- todos os usuários ativos no último mês; -- todos os usuários inativos por um mês (ou mais); -- todos os usuários suspensos; -- todas as organizações; -- todos os repositórios. - -Você também pode acessar esses relatórios de forma programática pela autenticação HTTP padrão com uma conta de administrador do site. Você deve usar um token de acesso pessoal com o escopo `site_admin`. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." - -Por exemplo, veja uma forma de baixar o relatório "todos os usuários" com cURL: - -```shell -curl -L -u username:token http(s)://hostname/stafftools/reports/all_users.csv -``` - -Para acessar os outros relatórios de forma programática, substitua `all_users` por `active_users`, `dormant_users`, `suspended_users`, `all_organizations` ou `all_repositories`. - -{% note %} - -**Observação:** a solicitação inicial `curl` retornará uma resposta HTTP 202 se não houver relatórios em cache disponíveis; em segundo plano, será gerado um relatório. Você pode enviar uma segunda solicitação para baixar o relatório. Em vez de usar uma senha, você pode definir uma senha ou token OAuth com escopo `site_admin`. - -{% endnote %} - -### Relatórios de usuário - -| Tecla | Descrição | -| -----------------:| ---------------------------------------------------------------------- | -| `created_at` | Momento da criação da conta do usuário (carimbo de data/hora ISO 8601) | -| `id` | ID da conta de usuário ou organização | -| `login` | Nome de login da conta | -| `e-mail` | Endereço de e-mail principal da conta | -| `função` | Conta de administrador ou usuário regular | -| `suspended?` | Se a conta foi suspensa | -| `last_logged_ip` | Endereço IP mais recente a fazer login na conta | -| `repos` | Número de repositórios pertencentes à conta | -| `ssh_keys` | Número de chaves SSH registradas na conta | -| `org_memberships` | Número de organizações às quais a conta pertence | -| `dormant?` | Se a conta está inativa | -| `last_active` | Última vez em que a conta ficou ativa (carimbo de data/hora ISO 8601) | -| `raw_login` | Informações brutas de login (formato JSON) | -| `2fa_enabled?` | Se o usuário habilitou a autenticação de dois fatores | - -### Relatórios da organização - -| Tecla | Descrição | -| ---------------:| --------------------------------------------------- | -| `id` | ID da organização | -| `created_at` | Momento de criação da organização | -| `login` | Nome de login da organização | -| `e-mail` | Endereço de e-mail principal da organização | -| `owners` | Número de proprietários da organização | -| `members` | Número de integrantes da organização | -| `teams` | Número de equipes da organização | -| `repos` | Número de repositórios da organização | -| `2fa_required?` | Se a organização exige autenticação de dois fatores | - -### Relatórios do repositório - -| Tecla | Descrição | -| ---------------:| ----------------------------------------------------- | -| `created_at` | Momento de criação do repositório | -| `owner_id` | ID do proprietário do repositório | -| `owner_type` | Se o repositório pertence a um usuário ou organização | -| `owner_name` | Nome do proprietário do repositório | -| `id` | ID do repositório | -| `name` | Nome do repositório | -| `visibilidade` | Se o repositório é público ou privado | -| `readable_size` | Tamanho do repositório em formato legível por humanos | -| `raw_size` | Tamanho do repositório como número | -| `collaborators` | Número de colaboradores do repositório | -| `fork?` | Se o repositório é uma bifurcação | -| `deleted?` | Se o repositório foi excluído | - -{% ifversion ghes %} -## Índices - -Os recursos de [pesquisa de códigos][] do GitHub têm tecnologia [ElasticSearch][]. Esta seção do painel de administração do site mostra o status atual do cluster do ElasticSearch e oferece várias ferramentas para controlar o comportamento de pesquisa e geração de índices. Essas ferramentas se dividem em três categorias: - -### Pesquisa de código - -Esta ação permite habilitar ou desabilitar as operações de pesquisa e índice no código-fonte. - -### Reparo de índice de pesquisa de códigos - -Esta categoria controla a forma como ocorre o reparo do índice de pesquisa de códigos. Você pode: - -- habilitar ou desabilitar trabalhos de reparo de índice; -- iniciar um novo trabalho de reparo de índice; -- redefinir o estado de todo o reparo de índice. - -O {% data variables.product.prodname_enterprise %} usa trabalhos de reparo para reconciliar o estado do índice de pesquisa com dados armazenados em bancos de dados (problemas, pull requests, repositórios e usuários) e dados armazenados em repositórios do Git (código-fonte). Isso acontece quando: - -- um novo índice de pesquisa é criado; -- dados ausentes precisam ser aterrados; ou -- dados antigos de pesquisa precisam ser atualizados. - -Em outras palavras, os trabalhos de reparo são iniciados conforme necessário e executados em segundo plano. Esses trabalhos não são programados pelos administradores do site. - -Além disso, trabalhos de reparo usam uma "compensação de reparo" para paralelização. Trata-se de uma compensação na tabela do banco de dados para o registro a ser reconciliado. Vários trabalhos em segundo plano podem sincronizar tarefas com base nessa compensação. - -Uma barra de progresso mostra o status atual de um trabalho de reparo em todos os trabalhadores relacionados em segundo plano. Trata-se da diferença percentual da compensação do reparo com o ID de registro mais alto no banco de dados. Não se preocupe com o valor mostrado na barra de progresso após a conclusão de um trabalho de reparo; ele mostra a diferença entre a compensação do reparo e o ID de registro mais alto no banco de dados, e diminuirá à medida que mais repositórios forem adicionados à {% data variables.product.product_location %}, mesmo que esses repositórios estejam indexados no momento. - -Você pode iniciar um novo trabalho de reparo do índice de pesquisa de código a qualquer momento. Ele usará uma única CPU, pois reconcilia o índice de pesquisa com os dados do banco de dados e do repositório Git. Para minimizar os efeitos no desempenho de E/S e reduzir as chances de tempo limite das operações, tente fazer um trabalho de reparo fora dos horários de pico. Monitore as médias de carga do sistema e o uso da CPU usando um utilitário como `top`. Se você notar que não houve alterações significativas, isso indica que provavelmente será seguro fazer um trabalho de reparo de índice nos horários de pico. - -### Reparo de índice de problemas - -Esta categoria controla a forma como o índice [Problemas][] é reparado. Você pode: - -- habilitar ou desabilitar trabalhos de reparo de índice; -- iniciar um novo trabalho de reparo de índice; -- redefinir o estado de todo o reparo de índice. -{% endif %} -## Logins reservados - -Certas palavras são reservadas para uso interno em {% data variables.product.product_location %}, o que significa que essas palavras não podem ser usadas como nomes de usuário. - -Por exemplo, as palavras a seguir são reservadas, entre outras: - -- `administrador` -- `enterprise` -- `login` -- `equipe` -- `suporte` - -Para a lista completa ou palavras reservadas, acesse "Logins reservados" no painel de administração do site. - -{% ifversion ghes or ghae %} - -## Todos os usuários - -Aqui você verá todos os usuários que foram suspensos da {{ site.data.variables.product.product_location_enterprise }} e poderá [iniciar uma auditoria de chave SSH](/enterprise/{{ page.version }}/admin/guides/user-management/auditing-ssh-keys). - -{% endif %} - -## Repositórios - -Este espaço lista os repositórios da {% data variables.product.product_location %}. Você pode clicar no nome de um repositório e acessar suas funções de administração. - -- [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) -- [Configurar o {% data variables.large_files.product_name_long %};](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) -- [Arquivar e cancelar o arquivamento de repositórios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) - -## Todos os usuários - -Aqui você pode ver todos os usuários em {% data variables.product.product_location %}, e [iniciar uma auditoria de chave SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - -## Administradores do site - -Aqui você verá todos os administradores da {% data variables.product.product_location %} e poderá [iniciar uma auditoria de chave SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - -## Usuários inativos -{% ifversion ghes %} -Aqui você pode ver e [suspender](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) todos os usuários inativos da {% data variables.product.product_location %}. Uma conta de usuário é considerada inativa quando: -{% endif %} -{% ifversion ghae %} -Aqui você pode ver e suspender todos os usuários inativos em {% data variables.product.product_location %}. Uma conta de usuário é considerada inativa quando: -{% endif %} - -- Seu tempo de existência supera o limite de inatividade configurado na {% data variables.product.product_location %}; -- Não gerou qualquer atividade em seu período de existência; -- Não é uma conta de administrador do site. - -{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} Para obter mais informações, consulte "[Gerenciar usuários inativos](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)". - -## Usuários suspensos - -Aqui você verá todos os usuários que foram suspensos da {% data variables.product.product_location %} e poderá [iniciar uma auditoria de chave SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - - [página de tendências]: https://github.com/blog/1585-explore-what-is-trending-on-github - - [pesquisa de códigos]: https://github.com/blog/1381-a-whole-new-code-search - [ElasticSearch]: http://www.elasticsearch.org/ - - [Problemas]: https://github.com/blog/831-issues-2-0-the-next-generation diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md deleted file mode 100644 index fcf9a7c017..0000000000 --- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Conectar a sua conta corporativa ao GitHub Enterprise Cloud -shortTitle: Conectar as contas corporativas -intro: 'Ao habilitar o {% data variables.product.prodname_github_connect %}, você poderá compartilhar recursos e fluxos de trabalho específicos entre a {% data variables.product.product_location %} e o {% data variables.product.prodname_ghe_cloud %}.' -redirect_from: - - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ - - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com - - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ - - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud - - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud - - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud -permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' -versions: - ghes: '*' - ghae: next -type: how_to -topics: - - Enterprise - - GitHub Connect - - Infrastructure - - Networking ---- - -{% data reusables.github-connect.beta %} - -## Sobre o {% data variables.product.prodname_github_connect %} - -Para habilitar o {% data variables.product.prodname_github_connect %}, você deve configurar a conexão na {% data variables.product.product_location %} e na sua organização do {% data variables.product.prodname_ghe_cloud %} ou na conta corporativa. - -{% ifversion ghes %} -Para configurar uma conexão, sua configuração de proxy deve permitir conectividade com o `github.com` e o `api.github.com`. Para obter mais informações, consulte "[Configurar servidor proxy web de saída](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)". -{% endif %} - -Após habilitar o {% data variables.product.prodname_github_connect %}, você poderá ativar recursos como a pesquisa unificada e as contribuições unificadas. Para obter mais informações sobre todas as funcionalidades disponíveis, consulte "[Gerenciando conexões entre as suas contas corporativas](/admin/configuration/managing-connections-between-your-enterprise-accounts)". - -Ao conectar a {% data variables.product.product_location %} ao {% data variables.product.prodname_ghe_cloud %}, um registro no {% data variables.product.prodname_dotcom_the_website %} armazena as informações sobre a conexão: -{% ifversion ghes %} -- A parte da chave pública da sua licença do {% data variables.product.prodname_ghe_server %}; -- Um hash da sua licença do {% data variables.product.prodname_ghe_server %}; -- O nome do cliente da sua licença do {% data variables.product.prodname_ghe_server %}; -- A versão de {% data variables.product.product_location_enterprise %}{% endif %} -- O nome do host da sua instância de {% data variables.product.product_name %} -- A conta da organização ou empresa em {% data variables.product.prodname_dotcom_the_website %} que estiver conectada a {% data variables.product.product_location %} -- O token de autenticação usado pela {% data variables.product.product_location %} para fazer solicitações ao {% data variables.product.prodname_dotcom_the_website %}. - -Habilitar o {% data variables.product.prodname_github_connect %} também cria um {% data variables.product.prodname_github_app %} pertencente à sua conta corporativa ou organização do {% data variables.product.prodname_ghe_cloud %}. O {% data variables.product.product_name %} usa as credenciais do {% data variables.product.prodname_github_app %} para fazer solicitações ao {% data variables.product.prodname_dotcom_the_website %}. -{% ifversion ghes %} -O {% data variables.product.prodname_ghe_server %} armazena as credenciais do {% data variables.product.prodname_github_app %}. Essas credenciais serão replicadas em qualquer ambiente de clustering ou alta disponibilidade e serão armazenadas em qualquer backup, inclusive os instantâneos criados pelo {% data variables.product.prodname_enterprise_backup_utilities %}. -- Um token de autenticação válido por uma hora; -- Uma chave privada usada para gerar um novo token de autenticação. -{% endif %} - -Habilitar o {% data variables.product.prodname_github_connect %} não permitirá que os usuários do {% data variables.product.prodname_dotcom_the_website %} façam alterações no {% data variables.product.product_name %}. - -Para obter mais informações sobre o gerenciamento de contas corporativas usando a API GraphQL, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". -## Habilitar o {% data variables.product.prodname_github_connect %} - -{% ifversion ghes %} -1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Em "{% data variables.product.prodname_github_connect %} ainda não está habilitado", clique em **Habilitar {% data variables.product.prodname_github_connect %}**. Ao clicar em **Habilitar {% data variables.product.prodname_github_connect %}**, você concorda com os "Termos para Produtos e Funcionalidades adicionais de {% data variables.product.prodname_dotcom %}.". -{% ifversion ghes %} -![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} -![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) -{% endif %} -1. Ao lado da conta corporativa ou organização que você pretende conectar, clique em **Connect** (Conectar). ![Botão Connect (Conectar) ao lado de uma conta corporativa ou empresa](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) - -## Desconectando uma organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %} da sua conta corporativa - -Ao se desconectar do {% data variables.product.prodname_ghe_cloud %}, o {% data variables.product.prodname_github_app %} do {% data variables.product.prodname_github_connect %} é excluído da sua conta corporativa ou organização e as credenciais armazenadas na {% data variables.product.product_location %} são excluídas. - -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} -1. Ao lado da conta corporativa ou organização que você gostaria de desconectar, clique em **Disable {% data variables.product.prodname_github_connect %})** (Desabilitar o {% data variables.product.prodname_github_connect %}). -{% ifversion ghes %} - ![Desabilitar o botão GitHub Connect ao lado do nome de uma conta corporativa ou organização](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) -1. Leia as informações sobre a desconexão e clique em **Disable {% data variables.product.prodname_github_connect %}** (Desabilitar o {% data variables.product.prodname_github_connect %}). ![Botão Modal com informações de aviso sobre desconexão e confirmação](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) -{% else %} - ![Desabilitar o botão GitHub Connect ao lado do nome de uma conta corporativa ou organização](/assets/images/enterprise/github-ae/disable-github-connect-button.png) -1. Leia as informações sobre a desconexão e clique em **Disable {% data variables.product.prodname_github_connect %}** (Desabilitar o {% data variables.product.prodname_github_connect %}). ![Botão Modal com informações de aviso sobre desconexão e confirmação](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) -{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md deleted file mode 100644 index e132d0ad21..0000000000 --- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Habilitar contribuições unificadas entre a conta corporativa e o GitHub.com -shortTitle: Habilitar contribuições unificadas -intro: 'Depois de habilitar o {% data variables.product.prodname_github_connect %}, você pode permitir que os integrantes do {% data variables.product.prodname_ghe_cloud %} destaquem o próprio trabalho no {% data variables.product.product_name %} enviando as contagens de contribuição para seus respectivos perfis do {% data variables.product.prodname_dotcom_the_website %}.' -redirect_from: - - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ - - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ - - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ - - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom -permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' -versions: - ghes: '*' - ghae: next -type: how_to -topics: - - Enterprise - - GitHub Connect ---- - -{% data reusables.github-connect.beta %} - -Como proprietário de uma empresa, você pode permitir que os usuários finais enviem contagens de contribuições anônimas pelo trabalho deles de {% data variables.product.product_location %} para seu gráfico de contribuição de {% data variables.product.prodname_dotcom_the_website %}. - -Após habilitar a opção {% data variables.product.prodname_github_connect %} e habilitar {% data variables.product.prodname_unified_contributions %} em ambos os ambientes usuários finais na sua conta corporativa poderão conectar-se às suas contas de {% data variables.product.prodname_dotcom_the_website %} e enviar contagens de contribuição de {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} Para obter mais informações, consulte "[Enviar contribuições corporativas para seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)". - -Se o proprietário da empresa desabilitar a funcionalidade ou o os desenvolvedores optarem pelo cancelamento da conexão, as contagens de contribuição de {% data variables.product.product_name %} serão excluídas em {% data variables.product.prodname_dotcom_the_website %}. Se o desenvolvedor reconectar os perfis após desabilitá-los, as contagens de contribuição dos últimos 90 dias serão restauradas. - -O {% data variables.product.product_name %} envia a contagem de contribuição e a origem **somente** para os usuários conectados ({% data variables.product.product_name %}). Nenhuma informação sobre a contribuição ou sobre como ela foi feita é enviada. - -Antes de habilitar o {% data variables.product.prodname_unified_contributions %} no {% data variables.product.product_location %}, conecte o {% data variables.product.product_location %} ao {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". - -{% ifversion ghes %} -{% data reusables.github-connect.access-dotcom-and-enterprise %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Em "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}" (Usuários podem compartilhar contagens de contribuição com o {% data variables.product.prodname_dotcom_the_website %}), clique em **Request access** (Solicitar acesso). ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} -2. [Faça login](https://enterprise.github.com/login) no site do {% data variables.product.prodname_ghe_server %} para obter mais instruções. - -Ao solicitar acesso, podemos redirecioná-lo para o site {% data variables.product.prodname_ghe_server %} para verificar os termos de serviço atuais. -{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md deleted file mode 100644 index e342be536a..0000000000 --- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Habilitar a pesquisa unificada entre a sua conta corporativa e o GitHub.com -shortTitle: Habilitar pesquisa unificada -intro: 'Após habilitar a opção {% data variables.product.prodname_github_connect %}, você poderá permitir a pesquisa de {% data variables.product.prodname_dotcom_the_website %} para os integrantes da sua sua empresa em {% data variables.product.product_name %}.' -redirect_from: - - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ - - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ - - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ - - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom - - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom - - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom -permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' -versions: - ghes: '*' - ghae: next -type: how_to -topics: - - Enterprise - - GitHub Connect - - GitHub search ---- - -{% data reusables.github-connect.beta %} - -Ao habilitar a pesquisa unificada, os usuários poderão visualizar os resultados da pesquisa de conteúdo público e privado em {% data variables.product.prodname_dotcom_the_website %} ao pesquisar em {% data variables.product.product_location %}{% ifversion ghae %} em {% data variables.product.prodname_ghe_managed %}{% endif %}. - -Os usuários não conseguirão pesquisar na {% data variables.product.product_location %} pelo {% data variables.product.prodname_dotcom_the_website %}, mesmo se tiverem acesso aos dois ambientes. Eles só poderão pesquisar nos repositórios privados em que você habilitou a {% data variables.product.prodname_unified_search %} e não terão acesso às organizações conectadas do {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Sobre a pesquisa em {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" e "[Habilitando uma pesquisa de repositório privado de {% data variables.product.prodname_dotcom_the_website %} na sua conta corporativa](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." - -A pesquisa via APIs REST e GraphQL não inclui resultados do {% data variables.product.prodname_dotcom_the_website %}. Não há suporte para a pesquisa avançada e a pesquisa de wikis no {% data variables.product.prodname_dotcom_the_website %}. - -{% ifversion ghes %} -{% data reusables.github-connect.access-dotcom-and-enterprise %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Em "Users can search {% data variables.product.prodname_dotcom_the_website %}" (Usuários podem pesquisar no {% data variables.product.prodname_dotcom_the_website %}), use o menu suspenso e clique em **Enabled** (Habilitado). ![Habilitar a opção de pesquisa no menu suspenso de pesquisa do GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) -1. Em "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}" (Usuários podem pesquisar em repositórios privados no {% data variables.product.prodname_dotcom_the_website %}), use o menu suspenso e clique em **Enabled** (Habilitado). ![Habilitar a opção de pesquisa em repositórios privados no menu suspenso de pesquisa do GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) - -## Leia mais - -- "[Conectando a sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" - diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md deleted file mode 100644 index 80004d7af9..0000000000 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Aprimorar os recursos de CPU ou memória -intro: 'Se houver lentidão das operações na {% data variables.product.product_location_enterprise %}, pode ser necessário adicionar recursos de CPU ou memória.' -redirect_from: - - /enterprise/admin/installation/increasing-cpu-or-memory-resources - - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources - - /admin/enterprise-management/increasing-cpu-or-memory-resources -versions: - ghes: '*' -type: how_to -topics: - - Enterprise - - Infrastructure - - Performance -shortTitle: Aumentar CPU ou memória ---- - -{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} - -## Adicionar recursos de CPU ou memória para AWS - -{% note %} - -**Observação:** para adicionar recursos de CPU ou memória ao AWS, você deve saber usar o console de gerenciamento do AWS ou a interface da linha de comandos `aws ec2` para gerenciar instâncias do EC2. Para obter detalhes sobre o uso das ferramentas do AWS escolhidas para o redimensionamento, consulte a documentação do AWS sobre [redimensionar uma instância da Amazon com EBS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html). - -{% endnote %} - -### Considerações de redimensionamento - -Antes de aumentar recursos de CPU ou memória do {% data variables.product.product_location %}: - -- **Amplie sua memória com CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} -- **Atribua um endereço IP elástico à instância**. Se não houver IP elástica atribuída, você terá que ajustar os registros DNS A do seu host do {% data variables.product.prodname_ghe_server %} após o reinício para explicar a alteração no endereço IP público. Depois que a instância for reiniciada, a IP elástica (EIP) será automaticamente mantida se a instância for iniciada em uma VPC. Se a instância for iniciada no EC2-Classic, a IP elástica deverá ser associada outra vez manualmente. - -### Tipos de instância do AWS compatíveis - -É necessário determinar o tipo de instância para a qual você pretende atualizar com base nas especificações de CPU/memória. - -{% data reusables.enterprise_installation.warning-on-scaling %} - -{% data reusables.enterprise_installation.aws-instance-recommendation %} - -### Redimensionar para o AWS - -{% note %} - -**Observação:** para instâncias iniciadas no EC2-Classic, anote o endereço IP elástico associado à instância e o ID da instância. Depois de reiniciar a instância, reassocie o endereço IP elástico. - -{% endnote %} - -Não é possível adicionar recursos de CPU ou memória a uma instância atual do AWS/EC2. Faça o seguinte: - -1. Interrompa a instância. -2. Altere o tipo de instância. -3. Inicie a instância. -{% data reusables.enterprise_installation.configuration-recognized %} - -## Adicionar recursos de CPU ou memória para OpenStack KVM - -Não é possível adicionar recursos de CPU ou memória a uma instância atual do OpenStack KVM. Faça o seguinte: - -1. Tire um instantâneo da instância atual; -2. Interrompa a instância. -3. Selecione um novo tipo de instância que tenha os recursos de CPU e/ou memória desejados. - -## Adicionar recursos de memória ou CPU para VMware - -{% data reusables.enterprise_installation.increasing-cpus-req %} - -1. Use o cliente vSphere para conexão com o host VMware ESXi. -2. Desligue a {% data variables.product.product_location %}. -3. Selecione a máquina virtual e clique em **Edit Settings** (Editar configurações). -4. Em "Hardware", ajuste a CPU e/ou os recursos de memória alocados à máquina virtual, conforme necessário. ![Recursos de configuração VMware](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) -5. Para iniciar a máquina virtual, clique em **OK**. -{% data reusables.enterprise_installation.configuration-recognized %} diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index 98d4a107b2..829cdf411e 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -1,6 +1,6 @@ --- -title: Requisitos de atualização -intro: 'Antes de atualizar o {% data variables.product.prodname_ghe_server %}, veja as recomendações e requisitos a seguir para planejar sua estratégia de atualização.' +title: Upgrade requirements +intro: 'Before upgrading {% data variables.product.prodname_ghe_server %}, review these recommendations and requirements to plan your upgrade strategy.' redirect_from: - /enterprise/admin/installation/upgrade-requirements - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release/ @@ -13,39 +13,37 @@ topics: - Enterprise - Upgrades --- - {% note %} -**Notas:** -- Para atualizar do {% data variables.product.prodname_enterprise %} 11.10.348 até o {% data variables.product.current-340-version %}, você deve migrar para o {% data variables.product.prodname_enterprise %} 2.1.23. Para obter mais informações, consulte "[Migrar do {% data variables.product.prodname_enterprise %} 11.10.x para o 2.1.23](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23)". -- Nas versões com suporte, há pacotes de atualização disponíveis em [enterprise.github.com](https://enterprise.github.com/releases). Verifique a disponibilidade dos pacotes de atualização necessários para concluir a atualização. Se um pacote não estiver disponível, entre em contato com o {% data variables.contact.contact_ent_support %} para obter assistência. -- Se estiver usando o clustering do {% data variables.product.prodname_ghe_server %}, consulte "[Atualizar cluster](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" no guia de clustering do {% data variables.product.prodname_ghe_server %} para obter instruções específicas. -- As notas de versão do {% data variables.product.prodname_ghe_server %} mostram uma lista abrangente dos novos recursos de cada versão do {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte a [página de versões](https://enterprise.github.com/releases). +**Notes:** +- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance. +- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering. +- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases). {% endnote %} -## Recomendações +## Recommendations -- Inclua o mínimo possível de atualizações no seu processo. Por exemplo, em vez de atualizar do {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} para o {{ enterpriseServerReleases.supported[1] }} e depois para o {{ enterpriseServerReleases.latest }}, atualize do {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} para o {{ enterpriseServerReleases.latest }}. -- Se a sua versão estiver muito defasada, atualize a {% data variables.product.product_location %} para a versão mais atual disponível a cada etapa do processo. Ao usar a versão mais recente em cada atualização, você pode aproveitar as melhorias de desempenho e as correções de erros. Por exemplo, você poderia atualizar do {% data variables.product.prodname_enterprise %} 2.7 para o 2.8 e depois para o 2.10. No entanto, atualizar do {% data variables.product.prodname_enterprise %} 2.7 para o 2.9 e depois para o 2.10 usa uma versão mais recente na segunda etapa. -- Ao atualizar, use a versão mais recente do patch. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} -- Use uma instância de preparo para testar as etapas da atualização. Para obter mais informações, consulte "[Configurar instância de preparo](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)". -- Ao executar várias atualizações, espere pelo menos 24 horas entre atualizações de recursos para permitir que as migrações de dados e as tarefas de atualização executadas em segundo plano sejam totalmente concluídas. +- Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. +- If you’re several versions behind, upgrade {% data variables.product.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step. +- Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} +- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)." +- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete. -## Requisitos +## Requirements -- Você deve atualizar quando a versão do recurso estiver defasada por **no máximo** duas versões. Por exemplo, ao atualizar para o {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, você deve estar nas versões {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} ou {{ enterpriseServerReleases.supported[2] }}. +- You must upgrade from a feature release that's **at most** two releases behind. For example, to upgrade to {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, you must be on {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} or {{ enterpriseServerReleases.supported[2] }}. - {% data reusables.enterprise_installation.hotpatching-explanation %} -- Um hotpatch pode causar tempo de inatividade se os serviços afetados (como kernel, MySQL ou Elasticsearch) exigirem reinicialização da VM ou do serviço. Você receberá uma notificação quando/se a reinicialização for necessária. Será possível reinicializar em outro momento. -- Procure disponibilizar um armazenamento adicional na raiz durante a atualização, já que o hotpatching instala várias versões de alguns serviços até a conclusão da atualização. Caso não haja espaço suficiente, você receberá uma notificação das verificações preliminares. -- Ao atualizar pelo hotpatching, sua instância não pode ficar carregada demais (isso pode afetar o processo). As verificações preliminares avaliarão se a média de carga e a atualização irão falhar se a média de carga for muito alta. - Atualizar para {% data variables.product.prodname_ghe_server %} 2.17 migra seus logs de auditoria do Elasticsearch para MySQL. Além disso, essa migração aumenta a quantidade de tempo e espaço em disco necessários para restaurar um instantâneo. Antes de migrar, verifique o número de bytes nos índices de log de auditoria do Elasticsearch com este comando: +- A hotpatch may require downtime if the affected services (like kernel, MySQL, or Elasticsearch) require a VM reboot or a service restart. You'll be notified when a reboot or restart is required. You can complete the reboot or restart at a later time. +- Additional root storage must be available when upgrading through hotpatching, as it installs multiple versions of certain services until the upgrade is complete. Pre-flight checks will notify you if you don't have enough root disk storage. +- When upgrading through hotpatching, your instance cannot be too heavily loaded, as it may impact the hotpatching process. Pre-flight checks will consider the load average and the upgrade will fail if the load average is too high.- Upgrading to {% data variables.product.prodname_ghe_server %} 2.17 migrates your audit logs from Elasticsearch to MySQL. This migration also increases the amount of time and disk space it takes to restore a snapshot. Before migrating, check the number of bytes in your Elasticsearch audit log indices with this command: ``` shell curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes ``` -Use o número para estimar o espaço em disco necessário para os logs de auditoria do MySQL. O script também monitora seu espaço livre em disco durante o andamento da importação. Monitorar esse número é útil principalmente se o espaço livre em disco estiver próximo da quantidade de espaço em disco necessária para a migração. +Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration. {% data reusables.enterprise_installation.upgrade-hardware-requirements %} -## Próximas etapas +## Next steps -Após ler essas recomendações e requisitos, você poderá atualizar para o {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)". +After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md b/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md deleted file mode 100644 index c2b4bc6513..0000000000 --- a/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -title: Sobre o Suporte do GitHub Enterprise -intro: '{% data variables.contact.github_support %} pode ajudar você a resolver problemas que surgem em {% data variables.product.product_name %}.' -redirect_from: - - /enterprise/admin/enterprise-support/about-github-enterprise-support - - /admin/enterprise-support/about-github-enterprise-support -versions: - ghes: '*' - ghae: '*' -type: overview -topics: - - Enterprise - - Support -shortTitle: Suporte do GitHub Enterprise ---- - -{% note %} - -**Observação**: {% data reusables.support.data-protection-and-privacy %} - -{% endnote %} - -## Sobre o {% data variables.contact.enterprise_support %} - -{% data variables.product.product_name %} inclui {% data variables.contact.enterprise_support %} em inglês{% ifversion ghes %} e japonês{% endif %}. - -{% ifversion ghes %} -Você pode entrar em contato {% data variables.contact.enterprise_support %} através de {% data variables.contact.contact_enterprise_portal %} para obter ajuda: - - Instalar e usar o {% data variables.product.product_name %}; - - Identificar e verificar as causas dos erros. - -Além de todos os benefícios de {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} de suporte para ofertas de {% data variables.product.product_name %}: - - Suporte gravado por meio de nosso portal de suporte 24 horas por dias, 7 dias por semana - - Suporte por telefone 24 horas por dia, 7 dias por semana - - Um Contrato de nível de serviço (SLA, Service Level Agreement) com tempos de resposta inicial garantidos - - Engenheiros de Confiabilidade do Cliente - - Acesso a conteúdo premium - - Verificação de integridade agendadas - - Horas administrativas gerenciadas -{% endif %} - -{% ifversion ghes %} -Para obter mais informações, consulte a seção "[Sobre o {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". -{% endif %} - -{% data reusables.support.scope-of-support %} - -## Entrar em contato com o {% data variables.contact.enterprise_support %} - -{% ifversion ghes %} -{% data reusables.support.zendesk-old-tickets %} -{% endif %} - - -Você pode entrar em contato com {% data variables.contact.enterprise_support %} através de {% ifversion ghes %}{% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} o {% data variables.contact.ae_azure_portal %}{% endif %} para relatar problemas por escrito. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". - -{% ifversion ghes %} -## Horas de operação - -### Suporte em inglês - -Para problemas não urgentes, oferecemos suporte em inglês 24 horas por dia e 5 dias por semana, exceto nos fins de semana e feriados nacionais dos EUA. feriados. O tempo padrão de resposta é de 24 horas. - -Para problemas urgentes, estamos disponíveis 24 horas por dia, 7 dias por semana, mesmo durante os feriados nacionais nos EUA. feriados. - -### Suporte em japonês - -Para problemas não urgentes, o suporte em japonês está disponível de segunda-feira à sexta-feira, das 9h às 17h JST, exceto durante os feriados nacionais no Japão. Para problemas urgentes, oferecemos suporte em inglês 24 horas por dia, 7 dias por semana, mesmo durante os feriados nacionais nos EUA. feriados. - -Para obter uma lista completa dos EUA. Para ver a lista completa de feriados nacionais dos EUA e do Japão segundo o {% data variables.contact.enterprise_support %}, consulte o "[Calendário de feriados](#holiday-schedules)". - -## Calendário de feriados - -Para problemas urgentes, fornecemos suporte em inglês 44 horas por dia, 7 dias por semana, incluindo nos EUA. e feriados japoneses. - -### Feriados nos Estados Unidos - -O {% data variables.contact.enterprise_support %} observa esses feriados dos EUA. O {{ site.data.variables.contact.enterprise_support }} observa os feriados americanos, embora nossa equipe de suporte global esteja disponível para responder tíquetes urgentes. - -{% data reusables.enterprise_enterprise_support.support-holiday-availability %} - -### Feriados no Japão - -O {% data variables.contact.enterprise_support %} não oferece suporte na língua japonesa no período de 28 de dezembro a 3 de janeiro, nem nos feriados listados em [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html). - -{% data reusables.enterprise_enterprise_support.installing-releases %} -{% endif %} - -## Atribuindo uma prioridade a um tíquete de suporte - -Ao entrar em contato com {% data variables.contact.enterprise_support %}, você pode escolher uma das quatro prioridades para o tíquete: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}. - -{% data reusables.support.github-can-modify-ticket-priority %} - -{% ifversion ghes %} -{% data reusables.support.ghes-priorities %} -{% elsif ghae %} -{% data reusables.support.ghae-priorities %} -{% endif %} - -## Resolução e fechamento de tíquete de suporte - -{% data reusables.support.enterprise-resolving-and-closing-tickets %} - -## Leia mais - -{% ifversion ghes %} -- Seção 10 sobre suporte no Contrato de Licença de "[{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/license)"{% endif %} -- "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% ifversion ghes %} -- "[Preparar para enviar um tíquete](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} -- [Enviar um tíquete](/enterprise/admin/guides/enterprise-support/submitting-a-ticket) diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md deleted file mode 100644 index cf2c43f814..0000000000 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: Primeiros passos com o GitHub Actions para o GitHub Enterprise Server -shortTitle: Indrodução ao GitHub Actions -intro: 'Saiba mais sobre como habilitar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} pela primeira vez.' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -redirect_from: - - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server -versions: - ghes: '*' -type: how_to -topics: - - Actions - - Enterprise ---- - -{% data reusables.actions.enterprise-beta %} - -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% ifversion ghes %} - -Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_server %} para usar {% data variables.product.prodname_actions %}. Ele abrange os requisitos de hardware e software, apresenta as opções de armazenamento e descreve as políticas de gestão de segurança. - -{% endif %} - -## Revise as considerações de hardware - -{% ifversion ghes = 3.0 %} - -{% note %} - -**Observação**: Se você estiver atualizando uma instância de {% data variables.product.prodname_ghe_server %} existente para 3.0 ou posterior e deseja configurar {% data variables.product.prodname_actions %}, observe que os requisitos mínimos de hardware aumentaram. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)". - -{% endnote %} - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -Os recursos da CPU e memória disponíveis para {% data variables.product.product_location %} determinam o rendimento máximo do trabalho para {% data variables.product.prodname_actions %}. - -O teste interno em {% data variables.product.company_short %} demonstrou o rendimento máximo a seguir para instâncias de {% data variables.product.prodname_ghe_server %} com um intervalo de configurações da CPU e memória. Você pode ver diferentes tipos de transferência, dependendo dos níveis gerais de atividade na sua instância. - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho. - -O pico de trabalhos simultâneos rodando sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios em execução de ações, e quanto outro trabalho sua instância está fazendo não relacionado a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória: - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -| vCPUs | Memória | Rendimento máximo do trabalho | -|:----- |:------- |:------------------------------ | -| 4 | 32 GB | Demonstração ou testes rápidos | -| 8 | 64 GB | 25 trabalhos | -| 16 | 160 GB | 35 trabalhos | -| 32 | 256 GB | 100 trabalhos | - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -| vCPUs | Memória | Simultaneidade máxima* | -|:----- |:------- |:---------------------- | -| 32 | 128 GB | 1500 trabalhos | -| 64 | 256 GB | 1900 trabalhos | -| 96 | 384 GB | 2200 trabalhos | - -*A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente 10 minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. - -{%- endif %} - -Se você planeja habilitar {% data variables.product.prodname_actions %} para os usuários de uma instância existente, revise os níveis de atividade para usuários e automações na instância e garanta que você tenha fornecido CPU e memória adequadas para seus usuários. Para obter mais informações sobre o monitoramento da capacidade e desempenho de {% data variables.product.prodname_ghe_server %}, consulte "[Monitoramento do seu aplicativo](/admin/enterprise-management/monitoring-your-appliance)". - -Para obter mais informações sobre os requisitos mínimos de hardware para {% data variables.product.product_location %}, consulte as considerações sobre hardware para a plataforma da sua instância. - -- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) -- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) -- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) -- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) -- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) -- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %} -- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %} - -{% data reusables.enterprise_installation.about-adjusting-resources %} - -## Requisitos de armazenamento externo - -Para habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você deve ter acesso ao armazenamento externo do blob. - -O {% data variables.product.prodname_actions %} usa armazenamento do blob para armazenar artefatos gerados pelas execuções do fluxo de trabalho, como registros de fluxo de trabalho e artefatos de criação enviados pelo usuário. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo. - -{% data variables.product.prodname_actions %} é compatível com estes provedores de armazenamento: - -* Armazenamento do Azure Blob -* Amazon S3 -* MinIO Gateway compatível com S3 para NAS - -{% note %} - -**Observação:** Estes são os únicos provedores de armazenamento com os quais {% data variables.product.company_short %} é compatível e podem fornecer ajuda. Outros provedores de armazenamento compatíveis com a API do S3 provavelmente não funcionarão devido a diferenças em relação à API do S3. [Entre em contato conosco](https://support.github.com/contact) para pedir suporte para provedores de armazenamento adicionais. - -{% endnote %} - -## Considerações de rede - -{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre o uso de um proxy com {% data variables.product.prodname_ghe_server %}, consulte "[Configurando um servidor de proxy web de saída](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)". - -{% ifversion ghes %} - -## Habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento - -Siga um dos procedimentos abaixo para habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento escolhido: - -* [Habilitar o o GitHub Actions com armazenamento do Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) -* [Habilitar o GitHub Actions com armazenamento do Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) -* [Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) - -## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres - -Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". - -## Adicionar executores auto-hospedados - -{% data reusables.actions.enterprise-github-hosted-runners %} - -Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores auto-hospedados. Você pode adicionar executores auto-hospedados nos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". - -## Gerenciar quais ações podem ser usadas na sua empresa - -Você pode controlar quais ações os usuários têm permissão para usar na sua empresa. Isso inclui a configuração de {% data variables.product.prodname_github_connect %} para acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %}, ou a sincronização manual das ações de {% data variables.product.prodname_dotcom_the_website %}. - -Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)". - -## Fortalecimento geral de segurança para {% data variables.product.prodname_actions %} - -Se você quiser saber mais sobre as práticas de segurança para {% data variables.product.prodname_actions %}, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". - -{% endif %} - -## Nomes reservados - -Ao habilitar {% data variables.product.prodname_actions %} para a sua empresa, serão criadas duas organizações: `github` e `actions`. Se sua empresa já usa o nome da organização `github`, `github-org` (ou `github-github-org` se `github-org` também estiver em uso) será usado. Se sua empresa já usa o nome da organização `actions`, `github-actions` (ou `github-actions-org` se `github-actions` também estiver em uso) será usado. Uma vez que as ações são habilitadas, você não poderá usar mais esses nomes. diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index e8af5614eb..ee0f477635 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -1,16 +1,15 @@ --- -title: Habilitar GitHub Actions para o GitHub Enterprise Server -intro: 'Aprenda como configurar o armazenamento e habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}.' +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' versions: ghes: '*' topics: - Enterprise children: - - /getting-started-with-github-actions-for-github-enterprise-server - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - /setting-up-dependabot-updates -shortTitle: Habilitar GitHub Actions +shortTitle: Enable GitHub Actions --- diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md new file mode 100644 index 0000000000..6b94aa303c --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md @@ -0,0 +1,43 @@ +--- +title: Getting started with GitHub Actions for GitHub AE +shortTitle: Get started +intro: 'Learn about configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise +redirect_from: + - /admin/github-actions/getting-started-with-github-actions-for-github-ae + - /admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae +--- + +{% data reusables.actions.ae-beta %} + +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}. + +{% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_managed %} by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you need to manage access permissions for {% data variables.product.prodname_actions %} and add runners to run workflows. + +{% data reusables.actions.introducing-enterprise %} + +{% data reusables.actions.migrating-enterprise %} + +## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +## Adding runners + +{% note %} + +**Note:** To add {% data variables.actions.hosted_runner %}s to {% data variables.product.prodname_ghe_managed %}, you will need to contact {% data variables.product.prodname_dotcom %} support. + +{% endnote %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add runners. You can add runners at the enterprise, organization, or repository levels. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." + +{% data reusables.actions.general-security-hardening %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md new file mode 100644 index 0000000000..8680be8654 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md @@ -0,0 +1,34 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Cloud +shortTitle: Get started +intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}.' +permissions: 'Enterprise owners can configure {% data variables.product.prodname_actions %}.' +versions: + ghec: '*' +type: how_to +topics: + - Actions + - Enterprise +--- + +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %} + +{% data variables.product.prodname_actions %} is enabled for your enterprise by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you can manage the policies that control how enterprise members use {% data variables.product.prodname_actions %} and optionally add self-hosted runners to run workflows. + +{% data reusables.actions.introducing-enterprise %} + +{% data reusables.actions.migrating-enterprise %} + +## Managing policies for {% data variables.product.prodname_actions %} + +You can use policies to control how enterprise members use {% data variables.product.prodname_actions %}. For example, you can restrict which actions are allowed and configure artifact and log retention. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +## Adding runners + +To run {% data variables.product.prodname_actions %} workflows, you need to use runners. {% data reusables.actions.about-runners %} If you use {% data variables.product.company_short %}-hosted runners, you will be be billed based on consumption after exhausting the minutes included in {% data variables.product.product_name %}, while self-hosted runners are free. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." + +For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." + +If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" + +{% data reusables.actions.general-security-hardening %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000..cdddcb3c87 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,151 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Server +shortTitle: Get started +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server +versions: + ghes: '*' +type: how_to +topics: + - Actions + - Enterprise +--- +{% data reusables.actions.enterprise-beta %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. + +{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. + +{% data reusables.actions.introducing-enterprise %} + +{% data reusables.actions.migrating-enterprise %} + +## Review hardware considerations + +{% ifversion ghes = 3.0 %} + +{% note %} + +**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." + +{% endnote %} + +{% endif %} + +{%- ifversion ghes < 3.2 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}. + +Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance. + +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + +| vCPUs | Memory | Maximum job throughput | +| :--- | :--- | :--- | +| 4 | 32 GB | Demo or light testing | +| 8 | 64 GB | 25 jobs | +| 16 | 160 GB | 35 jobs | +| 32 | 256 GB | 100 jobs | + +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +| vCPUs | Memory | Maximum Concurrency*| +| :--- | :--- | :--- | +| 32 | 128 GB | 1500 jobs | +| 64 | 256 GB | 1900 jobs | +| 96 | 384 GB | 2200 jobs | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + +If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." + +For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %} +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %} + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +## External storage requirements + +To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. + +{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. + +{% data variables.product.prodname_actions %} supports these storage providers: + +* Azure Blob storage +* Amazon S3 +* S3-compatible MinIO Gateway for NAS + +{% note %} + +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. + +{% endnote %} + +## Networking considerations + +{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)." + +{% ifversion ghes %} + +## Enabling {% data variables.product.prodname_actions %} with your storage provider + +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: + +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +## Adding self-hosted runners + +{% data reusables.actions.enterprise-github-hosted-runners %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +## Managing which actions can be used in your enterprise + +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. + +For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." + +{% data reusables.actions.general-security-hardening %} + +{% endif %} + +## Reserved Names + +When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore. diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md new file mode 100644 index 0000000000..7a7069a145 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md @@ -0,0 +1,19 @@ +--- +title: Getting started with GitHub Actions for your enterprise +intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise." +versions: + ghec: '*' + ghes: '*' + ghae: '*' +topics: + - Enterprise + - Actions +children: + - /introducing-github-actions-to-your-enterprise + - /migrating-your-enterprise-to-github-actions + - /getting-started-with-github-actions-for-github-enterprise-cloud + - /getting-started-with-github-actions-for-github-enterprise-server + - /getting-started-with-github-actions-for-github-ae +shortTitle: Get started +--- + diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md new file mode 100644 index 0000000000..85a750a3f9 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -0,0 +1,124 @@ +--- +title: Introducing GitHub Actions to your enterprise +shortTitle: Introduce Actions +intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise." +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise +--- + +## About {% data variables.product.prodname_actions %} for enterprises + +{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)." + +![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png) + +Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs. + +## Governance and compliance + +Your should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations. + +Determine which actions your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)." + +Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions that were not created by {% data variables.product.company_short %}. You can configure the actions that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions, you can limit allowed actions to those created by verified creators or a list of specific actions. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)." + +![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png) + +{% ifversion ghec or ghae-issue-4757-and-5856 %} +Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." +{% endif %} + +You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %} + +![Audit log entries](/assets/images/help/repository/audit-log-entries.png) + +## Security + +You should plan your approach to security hardening for {% data variables.product.prodname_actions %}. + +### Security hardening individual workflows and repositories + +Make a plan to enforce good security practices for people using {% data variables.product.prodname_actions %} features within your enterprise. For more information about these practices, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)." + +You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "[Innersourcing](#innersourcing)." + +### Securing access to secrets and deployment resources + +You should plan where you'll store your secrets. We recommend storing secrets in {% data variables.product.prodname_dotcom %}, but you might choose to store secrets in a cloud provider. + +In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +![Screenshot of a list of secrets](/assets/images/help/settings/actions-org-secrets-list.png) + +You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see "[Using environments for deployments](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." + +### Security considerations for third-party actions + +There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that enourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)." + +## Innersourcing + +Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource workflows. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources. + +{% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %} +With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + +To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)." + +## Managing resources + +You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}. + +### Runners + +{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %} + +{% ifversion ghec %}If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers.{% else %}Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners.{% endif %} Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container. + +You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." + +{% ifversion ghec or ghes > 3.2 %} +You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." +{% endif %} + +Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)." + +### Storage + +{% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)." + +![Screenshot of artifact](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) + +{% ifversion ghes %} +You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." +{% endif %} + +{% data reusables.github-actions.artifact-log-retention-statement %} + +If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data. + +{% ifversion ghec %} +Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." +{% endif %} + +## Tracking usage + +You should consider making a plan to track your enterprise's usage of {% data variables.product.prodname_actions %}, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows. + +{% ifversion ghec %} +You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)." + +For more detailed usage data, you{% else %}You{% endif %} can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)." + +Make a plan for how your enterprise can pass the information from these webhooks into a data archiving system. You can consider using "CEDAR.GitHub.Collector", an open source tool that collects and processes webhook data from {% data variables.product.prodname_dotcom %}. For more information, see the [`Microsoft/CEDAR.GitHub.Collector` repository](https://github.com/microsoft/CEDAR.GitHub.Collector/). + +You should also plan how you'll enable your teams to get the data they need from your archiving system. \ No newline at end of file diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md new file mode 100644 index 0000000000..2936f4d27f --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md @@ -0,0 +1,87 @@ +--- +title: Migrating your enterprise to GitHub Actions +shortTitle: Migrate to Actions +intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider." +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise +--- + +## About enterprise migrations to {% data variables.product.prodname_actions %} + +To migrate your enterprise to {% data variables.product.prodname_actions %} from an existing system, you can plan the migration, complete the migration, and retire existing systems. + +This guide addresses specific considerations for migrations. For additional information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)." + +## Planning your migration + +Before you begin migrating your enterprise to {% data variables.product.prodname_actions %}, you should identify which workflows will be migrated and how those migrations will affect your teams, then plan how and when you will complete the migrations. + +### Leveraging migration specialists + +{% data variables.product.company_short %} can help with your migration, and you may also benefit from purchasing {% data variables.product.prodname_professional_services %}. For more information, contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}. + +### Identifying and inventorying migration targets + +Before you can migrate to {% data variables.product.prodname_actions %}, you need to have a complete understanding of the workflows being used by your enterprise in your existing system. + +First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind. + +Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)." + +With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}. + +### Determine team impacts from migrations + +When you change the tools being used within your enterprise, you influence how your team works. You'll need to consider how moving a workflow from your existing systems to {% data variables.product.prodname_actions %} will affect your developers' day-to-day work. + +Identify any processes, integrations, and third-party tools that will be affected by your migration, and make a plan for any updates you'll need to make. + +Consider how the migration may affect your compliance concerns. For example, will your existing credential scanning and security analysis tools work with {% data variables.product.prodname_actions %}, or will you need to use new tools? + +Identify the gates and checks in your existing system and verify that you can implement them with {% data variables.product.prodname_actions %}. + +### Identifying and validating migration tools + +Automated migration tools can translate your enterprise's workflows from the existing system's syntax to the syntax required by {% data variables.product.prodname_actions %}. Identify third-party tooling or contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %} to ask about tools that {% data variables.product.company_short %} can provide. + +After you've identified a tool to automate your migrations, validate the tool by running the tool on some test workflows and verifying that the results are as expected. + +Automated tooling should be able to migrate the majority of your workflows, but you'll likely need to manually rewrite at least a small percentage. Estimate the amount of manual work you'll need to complete. + +### Deciding on a migration approach + +Determine the migration approach that will work best for your enterprise. Smaller teams may be able to migrate all their workflows at once, with a "rip-and-replace" approach. For larger enterprises, an iterative approach may be more realistic. You can choose to have a central body manage the entire migration or you can ask individual teams to self serve by migrating their own workflows. + +We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too. + +Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. + +Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable. + +### Defining your migration schedule + +After you decide on a migration approach, build a schedule that outlines when each of your teams will migrate their workflows to {% data variables.product.prodname_actions %}. + +First, decide the date you'd like your migration to be complete. For example, you can plan to complete your migration by the time your contract with your current provider ends. + +Then, work with your teams to create a schedule that meets your deadline without sacrificing their team goals. Look at your business's cadence and the workload of each individual team you're asking to migrate. Coordinate with each team to understand their delivery schedules and create a plan that allows the team to migrate their workflows at a time that won't impact their ability to deliver. + +## Migrating to {% data variables.product.prodname_actions %} + +When you're ready to start your migration, translate your existing workflows to {% data variables.product.prodname_actions %} using the automated tooling and manual rewriting you planned for above. + +You may also want to maintain old build artifacts from your existing system, perhaps by writing a scripted process to archive the artifacts. + +## Retiring existing systems + +After your migration is complete, you can think about retiring your existing system. + +You may want to run both systems side-by-side for some period of time, while you verify that your {% data variables.product.prodname_actions %} configuration is stable, with no degradation of experience for developers. + +Eventually, decommission and shut off the old systems, and ensure that no one within your enterprise can turn the old systems back on. diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md index b4f22b3001..808fdae5b0 100644 --- a/translations/pt-BR/content/admin/github-actions/index.md +++ b/translations/pt-BR/content/admin/github-actions/index.md @@ -1,19 +1,21 @@ --- -title: Gerenciar o GitHub Actions para a sua empresa -intro: 'Habilite {% data variables.product.prodname_actions %} em {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} e gerencie as políticas e configurações de {% data variables.product.prodname_actions %}.' +title: Managing GitHub Actions for your enterprise +intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, and manage {% data variables.product.prodname_actions %} policies and settings.' redirect_from: - /enterprise/admin/github-actions versions: + ghec: '*' ghes: '*' ghae: '*' topics: - Enterprise children: + - /getting-started-with-github-actions-for-your-enterprise - /using-github-actions-in-github-ae - /enabling-github-actions-for-github-enterprise-server - /managing-access-to-actions-from-githubcom - /advanced-configuration-and-troubleshooting -shortTitle: Gerenciar o GitHub Actions +shortTitle: Manage GitHub Actions --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index f793e38a7f..c04ba00eea 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Sobre como usar ações na sua empresa -intro: '{% data variables.product.product_name %} inclui a maioria das ações de autoria de {% data variables.product.prodname_dotcom %} e tem opções para permitir o acesso a outras ações de {% data variables.product.prodname_dotcom_the_website %} e {% data variables.product.prodname_marketplace %}.' +title: About using actions in your enterprise +intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' redirect_from: - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server @@ -13,35 +13,35 @@ type: overview topics: - Actions - Enterprise -shortTitle: Adicionar ações à sua empresa +shortTitle: Add actions in your enterprise --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %} -Os fluxos de trabalho de {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que você pode combinar para criar tarefas e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. {% data reusables.actions.enterprise-no-internet-actions %} -## Ações oficiais agrupadas com a sua instância corporativa +## Official actions bundled with your enterprise instance -A maioria das ações oficiais de autoria de {% data variables.product.prodname_dotcom %} são automaticamente agrupadas com {% data variables.product.product_name %} e são capturadas em um momento a partir do {% data variables.product.prodname_marketplace %}. +{% data reusables.actions.actions-bundled-with-ghes %} -As ações oficiais empacotadas incluem `ações/checkout`, `actions/upload-artefact`, `actions/download-artefact`, `actions/labeler`, e várias ações de `actions/setup-`, entre outras. Para ver todas as ações oficiais incluídas na instância da sua empresa, acesse a organização das `ações` na sua instância: https://HOSTNAME/actions. +The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. -Cada ação é um repositório na organização de `ações`, e cada repositório de ação inclui as tags necessárias, branches e commit de SHAs que seus fluxos de trabalho podem usar para fazer referência à ação. Para obter informações sobre como atualizar as ações oficiais empacotadas, consulte "[Usar a versão mais recente das ações oficiais empacotadas](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)". +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)." {% note %} -**Observação:** Ao usar ações de configuração (como `actions/setup-LANGUAGE`) em {% data variables.product.product_name %} com executores auto-hospedados, você pode precisar configurar o cache de ferramentas em executores que não possuem acesso à Internet. Para obter mais informações, consulte "[Configurar o cache da ferramenta em executores auto-hospedados sem acesso à internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". +**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." {% endnote %} -## Configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} +## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} -Se os usuários da sua empresa precisam de acesso a outras ações a partir de {% data variables.product.prodname_dotcom_the_website %} ou {% data variables.product.prodname_marketplace %}, há algumas opções de configuração. +{% data reusables.actions.access-actions-on-dotcom %} -A abordagem recomendada é habilitar o acesso automático para todas as ações a partir de {% data variables.product.prodname_dotcom_the_website %}. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} com {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} -Como alternativa, se você quiser ter um controle mais rigoroso sobre quais as ações que são permitidas na sua empresa, você pode fazer o download e sincronizar manualmente as ações na instância da sua empresa usando a ferramenta de `actions-sync`. Para obter mais informações, consulte "[Sincronizando ações manualmente com o {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 215d62ea7d..3470da6098 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -1,6 +1,6 @@ --- -title: Habilitar o acesso automático às ações do GitHub.com usando o GitHub Connect -intro: 'Para permitir que {% data variables.product.prodname_actions %} na sua empresa use ações a partir de {% data variables.product.prodname_dotcom_the_website %}, você pode conectar a sua instância corporativa a {% data variables.product.prodname_ghe_cloud %}.' +title: Enabling automatic access to GitHub.com actions using GitHub Connect +intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.' permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.' redirect_from: - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect @@ -13,21 +13,25 @@ topics: - Actions - Enterprise - GitHub Connect -shortTitle: Usar GitHub Connect para ações +shortTitle: Use GitHub Connect for actions --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} em {% data variables.product.product_name %} não podem usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %} ou [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). +## About automatic access to {% data variables.product.prodname_dotcom_the_website %} actions -Para tornar todas as ações de {% data variables.product.prodname_dotcom_the_website %} disponíveis na sua instância corporativa, você pode usar {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} a {% data variables.product.prodname_ghe_cloud %}. Para saber outras formas de acessar ações a partir da {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)". +By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -## Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %} +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." + +To use actions from {% data variables.product.prodname_dotcom_the_website %}, your self-hosted runners must be able to download public actions from `api.github.com`. + +## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions {% data reusables.actions.enterprise-github-connect-warning %} -Antes de habilitar o acesso a todas as ações de {% data variables.product.prodname_dotcom_the_website %} na sua instância corporativa, você deve conectar sua empresa a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectando sua empresa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% data reusables.enterprise-accounts.access-enterprise %} {%- ifversion ghes < 3.1 %} @@ -35,30 +39,33 @@ Antes de habilitar o acesso a todas as ações de {% data variables.product.prod {%- endif %} {% data reusables.enterprise-accounts.github-connect-tab %} {%- ifversion ghes > 3.0 or ghae %} -1. Em "Os usuários podem usar as ações do GitHub.com em execuções do fluxo de trabalho", use o menu suspenso e selecione **Habilitado**. ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. + ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) {%- else %} -1. Em "Servidor pode usar ações do GitHub.com em execuções de fluxos de trabalho", use o menu suspenso e selecione **Habilitado**. ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. + ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) {%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} {% ifversion ghes > 3.2 or ghae-issue-4815 %} -## Retirada automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %} +## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} -Ao habilitar {% data variables.product.prodname_github_connect %}, os usuários não verão nenhuma alteração no comportamento para fluxos de trabalho existentes porque {% data variables.product.prodname_actions %} procura {% data variables.product.product_location %} para cada ação antes de voltar a {% data variables.product.prodname_dotcom_the_website%}. Isso garante que todas as versões personalizadas de ações que a sua empresa criou sejam usadas em preferência para suas contrapartes em {% data variables.product.prodname_dotcom_the_website%}. +When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.product.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}. -A desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %} bloqueia o potencial de um ataque de um intermediário por um usuário malicioso com acesso a {% data variables.product.product_location %}. Quando uma ação em {% data variables.product.prodname_dotcom_the_website %} é usada pela primeira vez, esse namespace fica desativado em {% data variables.product.product_location %}. Isso bloqueia qualquer usuário que criar uma organização e repositório na sua empresa que corresponda a essa organização e nome do repositório em {% data variables.product.prodname_dotcom_the_website %}. Isso garante que, quando um fluxo de trabalho é executado, a ação pretendida é sempre executada. +Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} blocks the potential for a man-in-the-middle attack by a malicious user with access to {% data variables.product.product_location %}. When an action on {% data variables.product.prodname_dotcom_the_website %} is used for the first time, that namespace is retired in {% data variables.product.product_location %}. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on {% data variables.product.prodname_dotcom_the_website %}. This ensures that when a workflow runs, the intended action is always run. -Depois de usar uma ação de {% data variables.product.prodname_dotcom_the_website %}, se você deseja criar uma ação em {% data variables.product.product_location %} com o mesmo nome, primeiro você precisa tornar o namespace para a organização e repositório disponíveis. +After using an action from {% data variables.product.prodname_dotcom_the_website %}, if you want to create an action in {% data variables.product.product_location %} with the same name, first you need to make the namespace for that organization and repository available. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. Na barra lateral esquerda, em **administrador do site** clique em **namespaces desativados**. -3. Localize o namespace que você quer usar em {% data variables.product.product_location %} e clique em **Cancelar desativação**. ![Cancelar desativação do namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) -4. Acesse a organização relevante e crie um novo repositório. +2. In the left sidebar, under **Site admin** click **Retired namespaces**. +3. Locate the namespace that you want use in {% data variables.product.product_location %} and click **Unretire**. + ![Unretire namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) +4. Go to the relevant organization and create a new repository. {% tip %} - **Dica:** quando você cancelar a desativação de um namespace, sempre crie o novo repositório com esse nome o mais rápido possível. Se um fluxo de trabalho chamar a ação associada em {% data variables.product.prodname_dotcom_the_website %} antes de criar o repositório local, o namespace será desativado novamente. Para ações usadas em fluxos de trabalho frequentemente, você pode considerar que um namespace foi desativado novamente antes de ter tempo para criar o repositório local. Neste caso, você pode desabilitar temporariamente os fluxos de trabalho relevantes até criar o novo repositório. + **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository. {% endtip %} diff --git a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md deleted file mode 100644 index 1ab69d89f1..0000000000 --- a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Introdução ao GitHub Actions para GitHub AE -shortTitle: Indrodução ao GitHub Actions -intro: 'Aprenda a configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_managed %}.' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -versions: - ghae: '*' -type: how_to -topics: - - Actions - - Enterprise -redirect_from: - - /admin/github-actions/getting-started-with-github-actions-for-github-ae ---- - -{% data reusables.actions.ae-beta %} - -Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_managed %} para usar {% data variables.product.prodname_actions %}. - -## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres - -Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". - -## Adicionar executores - -{% note %} - -**Observação:** Para adicionar {% data variables.actions.hosted_runner %}a {% data variables.product.prodname_ghe_managed %}, você precisará entrar em contato com o suporte de {% data variables.product.prodname_dotcom %}. - -{% endnote %} - -Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores. Você pode adicionar executores aos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)". - - -## Fortalecimento geral de segurança para {% data variables.product.prodname_actions %} - -Se você quiser saber mais sobre as práticas de segurança para {% data variables.product.prodname_actions %}, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". diff --git a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md index 3861561506..ed67e364c7 100644 --- a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md +++ b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md @@ -1,11 +1,10 @@ --- -title: Usar o GitHub Actions no GitHub AE -intro: 'Aprenda como configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_managed %}.' +title: Using GitHub Actions in GitHub AE +intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' versions: ghae: '*' children: - - /getting-started-with-github-actions-for-github-ae - /using-actions-in-github-ae -shortTitle: Usar Ações no GitHub AE +shortTitle: Use Actions in GitHub AE --- diff --git a/translations/pt-BR/content/admin/guides.md b/translations/pt-BR/content/admin/guides.md index f96b94774a..6eee293a97 100644 --- a/translations/pt-BR/content/admin/guides.md +++ b/translations/pt-BR/content/admin/guides.md @@ -1,7 +1,7 @@ --- -title: Guias do GitHub Enterprise -shortTitle: Guias -intro: 'Aprenda a aumentar a produtividade do desenvolvedor e a qualidade do código com {% data variables.product.product_name %}.' +title: GitHub Enterprise guides +shortTitle: Guides +intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -9,14 +9,15 @@ versions: ghes: '*' ghae: '*' learningTracks: + - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' - '{% ifversion ghae %}get_started_with_github_ae{% endif %}' - '{% ifversion ghes %}deploy_an_instance{% endif %}' - '{% ifversion ghes %}upgrade_your_instance{% endif %}' + - adopting_github_actions_for_your_enterprise - '{% ifversion ghes %}increase_fault_tolerance{% endif %}' - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}' - - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' includeGuides: - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - /admin/authentication/changing-authentication-methods diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index ea9738e0dc..6c2bd6b7ce 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Aplicando políticas para o GitHub Actions na sua empresa -intro: 'Você pode exigir políticas para {% data variables.product.prodname_actions %} dentro das organizações de sua empresa ou permitir que as políticas sejam definidas em cada organização.' +title: Enforcing policies for GitHub Actions in your enterprise +intro: 'You can enforce policies for {% data variables.product.prodname_actions %} within your enterprise''s organizations, or allow policies to be set in each organization.' permissions: 'Enterprise owners can enforce policies for {% data variables.product.prodname_actions %} in an enterprise.' miniTocMaxHeadingLevel: 3 redirect_from: @@ -22,50 +22,50 @@ topics: - Actions - Enterprise - Policies -shortTitle: Políticas do GitHub Actions +shortTitle: GitHub Actions policies --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.ae-beta %} -## Sobre as políticas para {% data variables.product.prodname_actions %} na sua empresa +## About policies for {% data variables.product.prodname_actions %} in your enterprise -{% data variables.product.prodname_actions %} ajuda os inetgrantes da sua empresa a automatizar os fluxos de trabalho de desenvolvimento de software em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)". +{% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)." -{% ifversion ghes %}Se você habilitar {% data variables.product.prodname_actions %}, qualquer{% else %}Qualquer{% endif %} organização em {% data variables.product.product_location %} poderá usar {% data variables.product.prodname_actions %}. Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} usam {% data variables.product.prodname_actions %}. Por padrão, os proprietários da organização podem gerenciar como os integrantes usam {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)". +{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." -## Aplicando uma política para restringir o uso de ações na sua empresa +## Enforcing a policy to restrict the use of actions in your enterprise -Você pode optar por desativar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou permitir apenas organizações específicas. Você também pode limitar o uso de ações públicas, de modo que as pessoas só possam usar ações locais que existem na sua empresa. +You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.actions.enterprise-actions-permissions %} -1. Clique em **Salvar**. +1. Click **Save**. {% ifversion ghec or ghes or ghae %} -### Permitir selecionar ações para executar +### Allowing select actions to run {% data reusables.actions.allow-specific-actions-intro %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. - {%- ifversion ghes or ghae-issue-5094 %} - ![Adicionar ações para permitir lista](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes > 3.0 or ghae-issue-5094 %} + ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} - ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) {%- endif %} {% endif %} {% ifversion ghec or ghes or ghae %} -## Aplicando uma política de artefato e registrando a retenção na sua empresa +## Enforcing a policy for artifact and log retention in your enterprise -{% data variables.product.prodname_actions %} pode armazenar artefatos e arquivos de registro. Para obter mais informações, consulte "[Fazendo o download dos artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)". +{% data variables.product.prodname_actions %} can store artifact and log files. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." {% data reusables.actions.about-artifact-log-retention %} @@ -77,13 +77,13 @@ Você pode optar por desativar {% data variables.product.prodname_actions %} par {% endif %} -## Aplicando uma política para bifurcar pull requests na sua empresa +## Enforcing a policy for fork pull requests in your enterprise -Você pode aplicar políticas para controlar como {% data variables.product.prodname_actions %} comporta-se para {% data variables.product.product_location %} quando os integrantes da sua empresa{% ifversion ghec %} ou colaboradores externos{% endif %} executarem fluxos de trabalho a partir das bifurcações. +You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.product.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks. {% ifversion ghec %} -### Aplicando uma política de aprovação de pull requests dos colaboradores externos +### Enforcing a policy for approval of pull requests from outside collaborators {% data reusables.actions.workflow-run-approve-public-fork %} @@ -98,7 +98,7 @@ Você pode aplicar políticas para controlar como {% data variables.product.prod {% ifversion ghec or ghes or ghae %} -### Aplicando uma política para bifurcar pull requests em repositórios privados +### Enforcing a policy for fork pull requests in private repositories {% data reusables.github-actions.private-repository-forks-overview %} @@ -111,20 +111,19 @@ Você pode aplicar políticas para controlar como {% data variables.product.prod {% ifversion ghec or ghes > 3.1 or ghae-next %} -## Aplicando uma política de permissões de fluxo de trabalho na sua empresa +## Enforcing a policy for workflow permissions in your enterprise {% data reusables.github-actions.workflow-permissions-intro %} -Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para sua empresa, organizações ou repositórios. Se você escolher a opção restrita como padrão nas configurações da empresa, isto impedirá que a configuração mais permissiva seja escolhida nas configurações da organização ou repositório. +You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings. {% data reusables.github-actions.workflow-permissions-modifying %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Em **permissões do fluxo de trabalho**, escolha se você quer que o `GITHUB_TOKEN` tenha acesso de leitura e gravação para todos os escopos, ou apenas acesso de leitura para o escopo do     conteúdo. -Definir permissões do GITHUB_TOKEN para esta empresa

    -

  • Clique em Salvar para aplicar as configurações.

    • - +1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. + ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png) +1. Click **Save** to apply the settings. -

    {% endif %}

    +{% endif %} diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md deleted file mode 100644 index 0fab4b4ac8..0000000000 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Criar equipes -intro: 'As organizações usam as equipes para criar grupos de integrantes e controlar o acesso aos repositórios. Os integrantes da equipe podem receber permissões de leitura, gravação ou administração em determinados repositórios.' -redirect_from: - - /enterprise/admin/user-management/creating-teams - - /admin/user-management/creating-teams -versions: - ghes: '*' -type: how_to -topics: - - Access management - - Enterprise - - Teams - - User account ---- - -As equipes são essenciais para vários recursos de colaboração do {% data variables.product.prodname_dotcom %}, como as @menções, que chamam a atenção dos integrantes envolvidos em alguma questão específica. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." - -Uma equipe pode representar um grupo dentro da empresa ou incluir pessoas com determinados interesses ou experiências. Por exemplo, uma equipe de especialistas em acessibilidade da {% data variables.product.product_location %} pode envolver pessoas de vários departamentos. As equipes podem representar interesses funcionais que complementam a hierarquia das divisões de uma empresa. - -As organizações podem criar vários níveis de equipes aninhadas para refletir a estrutura hierárquica de uma empresa ou grupo. Para obter mais informações, consulte "[Sobre equipes](/enterprise/{{ currentVersion }}/user/articles/about-teams/#nested-teams)". - -## Criar equipes - -Fazer uma combinação prudente de equipes é uma forma poderosa de controlar o acesso ao repositório. Por exemplo, se a sua organização permitir que somente a equipe de engenharia da versão faça push do código para o branch de qualquer repositório, você poderia conceder permissões de **administração** aos repositórios da organização somente à equipe de engenharia, enquanto todas as outras equipes teriam permissão de **leitura**. - -{% data reusables.profile.access_org %} -{% data reusables.user_settings.access_org %} -{% data reusables.organizations.new_team %} -{% data reusables.organizations.team_name %} -{% data reusables.organizations.team_description %} -{% data reusables.organizations.team_visibility %} -{% data reusables.organizations.create-team-choose-parent %} -{% data reusables.organizations.create_team %} - -## Criar equipes com a Sincronização LDAP habilitada - -Instâncias que usam o LDAP para fazer autenticação de usuários podem usar a Sincronização LDAP para gerenciar os integrantes de uma equipe. Configurar o **Distinguished Name (DN)** (nome diferenciado) no campo **LDAP group** (grupo LDAP) mapeará uma equipe a um grupo LDAP ou servidor LDAP. Se você usar a Sincronização LDAP para gerenciar os integrantes de uma equipe, não será possível gerenciar a sua equipe na {% data variables.product.product_location %}. Quando a Sincronização LDAP estiver habilitada, a equipe mapeada sincronizará seus integrantes em segundo plano e periodicamente no intervalo configurado. Para obter mais informações, consulte "[Habilitar a Sincronização LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". - -Você deve ser um administrador do site e um proprietário da organização para criar uma equipe com a sincronização LDAP habilitada. - -{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} - -{% warning %} - -**Notas:** -- A Sincronização LDAP gerencia somente a lista de integrantes da equipe. Você deve gerenciar os repositórios e permissões da equipe pelo {% data variables.product.prodname_ghe_server %}. -- Se um grupo LDAP mapeado para um DN for removido, por exemplo, se o grupo LDAP for excluído, todos os integrantes serão removidos da equipe sincronizada do {% data variables.product.prodname_ghe_server %}. Para corrigir o problema, mapeie a equipe para um novo DN, adicione novamente os integrantes e [sincronize manualmente o mapeamento](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#manually-syncing-ldap-accounts). -- Quando a Sincronização LDAP estiver ativada, se uma pessoa for removida de um repositório, ela perderá o acesso. No entanto, suas bifurcações não serão excluídas. Se a pessoa for adicionada a uma equipe e tiver acesso ao repositório original da organização dentro de três meses, seu acesso às bifurcações será restaurado automaticamente na sincronização seguinte. - -{% endwarning %} - -1. Verifique se a [sincronização LDAP está habilitada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync). -{% data reusables.profile.access_org %} -{% data reusables.user_settings.access_org %} -{% data reusables.organizations.new_team %} -{% data reusables.organizations.team_name %} -6. Pesquise um DN do grupo do LDAP ao qual a equipe será mapeada. Se você não souber o DN, digite o nome do grupo do LDAP. O {% data variables.product.prodname_ghe_server %} vai buscar correspondências e preenchimentos automáticos. ![Mapear grupo LDAP para DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) -{% data reusables.organizations.team_description %} -{% data reusables.organizations.team_visibility %} -{% data reusables.organizations.create-team-choose-parent %} -{% data reusables.organizations.create_team %} diff --git a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md deleted file mode 100644 index fb55b3646a..0000000000 --- a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -title: Configurar o Large File Storage do Git para a sua sempresa -intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' -redirect_from: - - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise/ - - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server - - /enterprise/admin/installation/configuring-git-large-file-storage - - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server - - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server - - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository/ - - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization/ - - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance/ - - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server/ - - /enterprise/admin/user-management/configuring-git-large-file-storage-for-your-enterprise - - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise -versions: - ghes: '*' - ghae: '*' -type: how_to -topics: - - Git - - Enterprise - - LFS - - Storage -shortTitle: Configurar o LFS do Git ---- - -## Sobre o {% data variables.large_files.product_name_long %} - -{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} Você pode usar {% data variables.large_files.product_name_long %} com um único repositório, todos os seus repositórios pessoais ou organizacionais, ou com cada repositório na sua empresa. Antes de habilitar {% data variables.large_files.product_name_short %} para repositórios ou organizações específicos, você deve habilitar {% data variables.large_files.product_name_short %} para a sua empresa. - -{% data reusables.large_files.storage_assets_location %} -{% data reusables.large_files.rejected_pushes %} - -Para obter mais informações, consulte "[Sobre o {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Controlar versões em arquivos grandes](/enterprise/user/articles/versioning-large-files/)" e acesse o [site do projeto do {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/). - -{% data reusables.large_files.can-include-lfs-objects-archives %} - -## Configurar {% data variables.large_files.product_name_long %} para a sua empresa - -{% data reusables.enterprise-accounts.access-enterprise %} -{% ifversion ghes or ghae %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. No menu suspenso em "{% data variables.large_files.product_name_short %} access" (Acesso ao {% data variables.large_files.product_name_short %}), clique em **Enabled** (Habilitado) ou **Disabled** (Desabilitado). ![Acesso ao Git LFS](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) - -## Configurar o {% data variables.large_files.product_name_long %} em um repositório específico - -{% data reusables.enterprise_site_admin_settings.override-policy %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.repository-search %} -{% data reusables.enterprise_site_admin_settings.click-repo %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} - -## Configurar o {% data variables.large_files.product_name_long %} para cada repositório pertencente a uma conta ou organização - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user-or-org %} -{% data reusables.enterprise_site_admin_settings.click-user-or-org %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} - -{% ifversion ghes %} -## Configurar o Git Large File Storage para uso em servidores de terceiros - -{% data reusables.large_files.storage_assets_location %} -{% data reusables.large_files.rejected_pushes %} - -1. Desabilite {% data variables.large_files.product_name_short %} em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar {% data variables.large_files.product_name_long %} para a sua empresa](#configuring-git-large-file-storage-for-your-enterprise)". - -2. Crie um arquivo de configuração do {% data variables.large_files.product_name_short %} que aponte para o servidor de terceiros. - ```shell - # Show default configuration - $ git lfs env - > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) - > git version 2.7.4 (Apple Git-66) -   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) -   - # Create .lfsconfig that points to third party server. - $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo - $ git lfs env - > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) - > git version 2.7.4 (Apple Git-66) -   - > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none) -   - # Show the contents of .lfsconfig - $ cat .lfsconfig - [remote "origin"] - lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo - ``` - -3. Para manter a mesma configuração do {% data variables.large_files.product_name_short %} em todos os usuários, faça commit de um arquivo `.lfsconfig` personalizado no repositório. - ```shell - $ git add .lfsconfig - $ git commit -m "Adding LFS config file" - ``` -3. Migre qualquer ativo do {% data variables.large_files.product_name_short %}. Para obter mais informações, consulte "[Migrar para um servidor diferente do {% data variables.large_files.product_name_long %}](#migrating-to-a-different-git-large-file-storage-server)". - -## Migrar para outro servidor do Git Large File Storage - -Antes de migrar para outro servidor do {% data variables.large_files.product_name_long %}, configure o {% data variables.large_files.product_name_short %} para usar um servidor de terceiros. Para obter mais informações, consulte "[Configurar o {% data variables.large_files.product_name_long %} para utilizar um servidor de terceiros](#configuring-git-large-file-storage-to-use-a-third-party-server)". - -1. Configure o repositório com outro remote. - ```shell - $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo -   - $ git lfs env - > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) - > git version 2.7.4 (Apple Git-66) -   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) - > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) - ``` - -2. Faça fetch de todos os objetos do remote antigo. - ```shell - $ git lfs fetch origin --all - > Scanning for all objects ever referenced... - > ✔ 16 objects found - > Fetching objects... - > Git LFS: (16 de 16 arquivos) 48.71 MB / 48.85 MB - ``` - -3. Faça push de todos os objetos para o remote novo. - ```shell - $ git lfs push NEW-REMOTE --all - > Scanning for all objects ever referenced... - > ✔ 16 objects found - > Pushing objects... - > Git LFS: (16 de 16 arquivos) 48.00 MB / 48.85 MB, 879.10 KB ignorados - ``` -{% endif %} - -## Leia mais - -- [Site de projeto do {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/) diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md deleted file mode 100644 index 324cffacda..0000000000 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Promover ou rebaixar administradores de site -redirect_from: - - /enterprise/admin/articles/promoting-a-site-administrator/ - - /enterprise/admin/articles/demoting-a-site-administrator/ - - /enterprise/admin/user-management/promoting-or-demoting-a-site-administrator - - /admin/user-management/promoting-or-demoting-a-site-administrator -intro: Os administradores do site podem promover qualquer conta de usuário como administrador do site e rebaixar administradores do site para usuários regulares. -versions: - ghes: '*' -type: how_to -topics: - - Access management - - Accounts - - User account - - Enterprise -shortTitle: Gerenciar administradores ---- - -{% tip %} - -**Observação:** se a [Sincronização LDAP estiver habilitada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) e o atributo `Administrators group` estiver definido ao [configurar o acesso LDAP para os usuários](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance), esses usuários terão automaticamente acesso de administrador do site em suas respectivas instâncias. Nesse caso, você não pode promover manualmente os usuários pelas etapas abaixo.Será preciso adicioná-los ao grupo de administradores LDAP. - -{% endtip %} - -Para obter mais informações sobre como promover um usuário a proprietário da organização, consulte a seção `ghe-org-admin-promote` de "[Utilitários da linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-admin-promote)". - -## Promover usuários pelas configurações empresariais - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.enterprise-accounts.administrators-tab %} -5. No canto superior direito da página, clique em **Add owner** (Adicionar proprietário). ![Botão para adicionar administrador](/assets/images/help/business-accounts/business-account-add-admin-button.png) -6. No campo de pesquisa, digite o nome do usuário e clique em **Add** (Adicionar). ![Campo de pesquisa para adicionar administrador](/assets/images/help/business-accounts/business-account-search-to-add-admin.png) - -## Rebaixar administrador do site pelas configurações empresariais - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.enterprise-accounts.administrators-tab %} -1. No canto superior esquerdo da página, no campo de pesquisa "Find an administrator" (Localizar administrador), digite o nome de usuário da pessoa que você pretende rebaixar. ![Campo de pesquisa para localizar administrador](/assets/images/help/business-accounts/business-account-search-for-admin.png) - -1. Nos resultados da pesquisa, localize o nome de usuário da pessoa que você deseja rebaixar e, em seguida, use o {% octicon "gear" %} menu suspenso e selecione **Remover proprietário**. ![Remover da opção empresa](/assets/images/help/business-accounts/demote-admin-button.png) - -## Promover usuários pela linha de comando - -1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) no seu appliance. -2. Execute [ghe-user-promote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-promote) com o nome de usuário para promover. - ```shell - $ ghe-user-promote username - ``` - -## Rebaixar administrador do site pela linha de comando - -1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) no seu appliance. -2. Execute [ghe-user-demote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-demote) com nome de usuário para rebaixar. - ```shell - $ ghe-user-demote username - ``` diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md deleted file mode 100644 index 4e67831d0c..0000000000 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Suspender e cancelar a suspensão de usuários -redirect_from: - - /enterprise/admin/articles/suspending-a-user/ - - /enterprise/admin/articles/unsuspending-a-user/ - - /enterprise/admin/articles/viewing-suspended-users/ - - /enterprise/admin/articles/suspended-users/ - - /enterprise/admin/articles/suspending-and-unsuspending-users/ - - /enterprise/admin/user-management/suspending-and-unsuspending-users - - /admin/user-management/suspending-and-unsuspending-users -intro: 'Se um usuário sair da empresa ou mudar para outro departamento, você deve remover ou modificar a forma como ele acessa a {% data variables.product.product_location %}.' -versions: - ghes: '*' -type: how_to -topics: - - Access management - - Enterprise - - Security - - User account -shortTitle: Gerenciar suspensão do usuário ---- - -Se funcionários saírem da empresa, você poderá suspender suas contas do {% data variables.product.prodname_ghe_server %} para disponibilizar licenças de usuário em sua licença {% data variables.product.prodname_enterprise %}, embora os problemas, comentários, repositórios, gists e outros dados que eles criaram continuem existindo. Usuários suspensos não podem entrar na sua instância nem fazer push ou pull de códigos. - -Quando você suspende um usuário, a alteração entra em vigor na mesma hora e o usuário não recebe notificações a respeito. Se tentar fazer pull ou push em um repositório, o usuário receberá este erro: - -```shell -$ git clone git@[hostname]:john-doe/test-repo.git -Clonando em 'test-repo'... -ERRO: sua conta foi suspensa. Verifique com o administrador de instalação. -fatal: o remote desligou inesperadamente -``` - -Antes de suspender os administradores do site, você deve rebaixá-los para usuários regulares. Para obter mais informações, consulte "[Promover ou rebaixar administradores de site](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)". - -{% tip %} - -**Observação:** se a [Sincronização LDAP estiver habilitada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) para a {% data variables.product.product_location %}, os usuários serão suspensos automaticamente quando forem removidos do servidor de diretório LDAP. Quando a Sincronização LDAP estiver habilitada para a sua instância, os métodos normais de suspensão do usuário ficarão desabilitados. - -{% endtip %} - -## Suspender usuários pelo painel de administração de usuários - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user %} -{% data reusables.enterprise_site_admin_settings.click-user %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -5. Em "Account suspension" (Suspensão de conta) na caixa Danger Zone (Zona de perigo), clique em **Suspend** (Suspender). ![Botão Suspend (Suspender)](/assets/images/enterprise/site-admin-settings/suspend.png) -6. Informe um motivo para a suspensão do usuário. ![Motivo da suspensão](/assets/images/enterprise/site-admin-settings/suspend-reason.png) - -## Cancelar a suspensão de usuários pelo painel de administração de usuários - -Assim como na suspensão, o cancelamento da suspensão de um usuário ocorre na mesma hora. O usuário não receberá notificações. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -3. Na barra lateral esquerda, clique em **Suspended users** (Usuários suspensos). ![Guia Suspended users (Usuários suspensos)](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) -2. Clique no nome da conta de usuário que você deseja suspender. ![Usuário suspenso](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -4. Em "Account suspension" (Suspensão de conta) na caixa Danger Zone (Zona de perigo), clique em **Unuspend** (Cancelar suspensão). ![Botão Unsuspend (Cancelar suspensão)](/assets/images/enterprise/site-admin-settings/unsuspend.png) -5. Informe um motivo para o cancelamento da suspensão do usuário. ![Motivo do cancelamento da suspensão](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) - -## Suspender usuários pela linha de comando - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Execute [ghe-user-suspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-suspend) com o nome de usuário para suspender. - ```shell - $ ghe-user-suspend username - ``` - -## Criar mensagem personalizada para usuários suspensos - -É possível criar uma mensagem personalizada que os usuários suspensos verão ao tentar fazer login. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.messages-tab %} -5. Clique em **Add message** (Adicionar mensagem). ![Adicionar mensagem](/assets/images/enterprise/site-admin-settings/add-message.png) -6. Digite a mensagem na caixa **Suspended user message** (Mensagem para usuários suspensos). Você pode digitar Markdown ou usar a barra de ferramentas Markdown para estilizar a mensagem. ![Mensagem para usuários suspensos](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) -7. Clique no botão **Preview** (Visualizar) no campo **Suspended user message** (Mensagem para usuários suspensos) para ver a mensagem renderizada. ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) -8. Revise a mensagem renderizada. ![Mensagem renderizada para usuário suspenso](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} - -## Cancelar a suspensão de usuários pela linha de comando - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Execute [ghe-user-unsuspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) com o nome de usuário para cancelar a suspensão. - ```shell - $ ghe-user-unsuspend username - ``` - -## Leia mais -- "[Suspender um usuário](/rest/reference/enterprise-admin#suspend-a-user)" diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md index bd4a535a26..cc9bf504b9 100644 --- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md +++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md @@ -1,6 +1,6 @@ --- -title: Encaminhamento de logs -intro: '{% data variables.product.product_name %} usa `syslog-ng` para encaminhar {% ifversion ghes %}sistema{% elsif ghae %}Git{% endif %} e logs de aplicativo para o servidor que você especificou.' +title: Log forwarding +intro: '{% data variables.product.product_name %} uses `syslog-ng` to forward {% ifversion ghes %}system{% elsif ghae %}Git{% endif %} and application logs to the server you specify.' redirect_from: - /enterprise/admin/articles/log-forwarding/ - /enterprise/admin/installation/log-forwarding @@ -20,33 +20,40 @@ topics: ## About log forwarding -Qualquer sistema de coleta de logs com suporte a fluxos de logs do estilo syslog é compatível (por exemplo, [Logstash](http://logstash.net/) e [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)). +Any log collection system that supports syslog-style log streams is supported (e.g., [Logstash](http://logstash.net/) and [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)). When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received. -## Habilitar o encaminhamento de logs +## Enabling log forwarding {% ifversion ghes %} -1. Na página de configurações do {% data variables.enterprise.management_console %}, na barra lateral esquerda, clique em **Monitoring** (Monitoramento). -1. Selecione **Enable log forwarding** (Habilitar encaminhamento de logs). -1. No campo **Server address** (Endereço do servidor), digite o endereço do servidor para o qual você pretende encaminhar os logs. É possível especificar vários endereços em uma lista separada por vírgulas. -1. No menu suspenso Protocol (Protocolo), selecione o protocolo a ser usado para comunicação com o servidor de logs. O protocolo será aplicado a todos os destinos de log especificados. -1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers. -1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. Toda a cadeia de certificados será validada e deverá terminar em um certificado raiz. Para obter mais informações, consulte [as opções de TLS na documentação syslog-ng](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599). +1. On the {% data variables.enterprise.management_console %} settings page, in the left sidebar, click **Monitoring**. +1. Select **Enable log forwarding**. +1. In the **Server address** field, type the address of the server to which you want to forward logs. You can specify multiple addresses in a comma-separated list. +1. In the Protocol drop-down menu, select the protocol to use to communicate with the log server. The protocol will apply to all specified log destinations. +1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers. +1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. The entire certificate chain will be validated, and must terminate in a root certificate. For more information, see [TLS options in the syslog-ng documentation](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599). {% elsif ghae %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**, clique em **Encaminhamento de registro**. ![Aba de encaminhamento de log](/assets/images/enterprise/business-accounts/log-forwarding-tab.png) -1. Em "Encaminhamento de registro", selecione **Habilitar o encaminhamento de registro**. ![Caixa de seleção para habilitar o encaminhamento de registro](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png) -1. Em "Endereço do servidor, digite o endereço do servidor para o qual você deseja encaminhar o registro. ![Campo endereço do servidor](/assets/images/enterprise/business-accounts/server-address-field.png) -1. Use o menu suspenso "Protocolo" e selecione um protocolo. ![Menu suspenso de protocolo](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png) -1. Opcionalmente, para habilitar comunicação encriptada TLS entre os pontos de extremidade do syslog, selecione **Habilitar TLS**. ![Caixa de seleção para habilitar TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png) -1. Em "Certificado público", cole o seu certificado x509. ![Caixa de texto para certificado público](/assets/images/enterprise/business-accounts/public-certificate-text-box.png) -1. Clique em **Salvar**. ![Botão Salvar para encaminhamento de registro](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) +1. Under {% octicon "gear" aria-label="The Settings gear" %} **Settings**, click **Log forwarding**. + ![Log forwarding tab](/assets/images/enterprise/business-accounts/log-forwarding-tab.png) +1. Under "Log forwarding", select **Enable log forwarding**. + ![Checkbox to enable log forwarding](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png) +1. Under "Server address", enter the address of the server you want to forward logs to. + ![Server address field](/assets/images/enterprise/business-accounts/server-address-field.png) +1. Use the "Protocol" drop-down menu, and select a protocol. + ![Protocol drop-down menu](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png) +1. Optionally, to enable TLS encrypted communication between syslog endpoints, select **Enable TLS**. + ![Checkbox to enable TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png) +1. Under "Public certificate", paste your x509 certificate. + ![Text box for public certificate](/assets/images/enterprise/business-accounts/public-certificate-text-box.png) +1. Click **Save**. + ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) {% endif %} {% ifversion ghes %} -## Solução de Problemas +## Troubleshooting -Em caso de problemas com o encaminhamento de logs, entre em contato com o {% data variables.contact.contact_ent_support %} e anexe o arquivo de saída de `http(s)://[hostname]/setup/diagnostics` ao seu e-mail. +If you run into issues with log forwarding, contact {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email. {% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index bf93ecc523..9056bc0961 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -1,6 +1,6 @@ --- -title: Remover dados confidenciais do repositório -intro: 'Se você fizer commit de dados confidenciais, como uma senha ou chave SSH em um repositório Git, poderá removê-los do histórico. Para remover completamente arquivos indesejados do histórico de um repositório, você pode usar a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner.' +title: Removing sensitive data from a repository +intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.' redirect_from: - /remove-sensitive-data/ - /removing-sensitive-data/ @@ -16,66 +16,65 @@ versions: topics: - Identity - Access management -shortTitle: Remover dados confidenciais +shortTitle: Remove sensitive data --- +The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository. -A ferramenta `git filter-repo` e o BFG Repo-Cleaner reescrevem o histórico do seu repositório, que muda os SHAs para os commits existentes que você altera e quaisquer commits dependentes. Os SHAs do commit alterados podem afetar as pull requests abertas no repositório. Recomendamos que você faça merge ou feche todas todas as pull requests abertas antes de remover os arquivos do repositório. - -Você pode remover o arquivo com o commit mais recente com `git rm`. Para obter informações sobre a remoção de um arquivo que foi adicionado com o commit mais recente, consulte "[Sobre arquivos grandes em {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)". +You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)." {% warning %} -Este artigo diz a você como tornar commits com dados confidenciais inacessíveis a partir de quaisquer branches ou tags do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. No entanto, é importante destacar que esses commits talvez ainda possam ser acessados em clones ou bifurcações do repositório diretamente por meio de hashes SHA-1 em visualizações em cache no {% data variables.product.product_name %} e por meio de qualquer pull request que faça referência a eles. Não é possível remover dados confidenciais dos clones ou bifurcações de usuários do seu repositório, mas você pode remover permanentemente as visualizações e referências em cache para os dados confidenciais em pull requests no {% data variables.product.product_name %} entrando em contato com {% data variables.contact.contact_support %}. +This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. -**Aviso: Depois de ter feito o push de um commit para {% data variables.product.product_name %}, você deve considerar todos os dados confidenciais no commit comprometido.** Se você fez o commit de uma senha, altere-a! Se tiver feito commit de uma chave, crie outra. A remoção dos dados comprometidos não resolve sua exposição inicial, especialmente em clones ou bifurcações existentes do seu repositório. Considere essas limitações ao tomar a decisão de reescrever a história do repositório. +**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. {% endwarning %} -## Remover um arquivo do histórico do repositório +## Purging a file from your repository's history -É possível limpar um arquivo do histórico do seu repositório usando a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner. +You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool. -### Usar o BFG +### Using the BFG -O [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) é uma ferramenta desenvolvida e mantida pela comunidade de código aberto. Ele fornece uma alternativa mais rápida e simples ao `git filter-branch` para remover dados não desejados. +The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. -Por exemplo: para remover o arquivo com dados confidenciais sem alterar o commit mais recente, execute: +For example, to remove your file with sensitive data and leave your latest commit untouched, run: ```shell $ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA ``` -Para substituir todo o texto relacionado no `passwords.txt` sempre que ele for encontrado no histórico do repositório, execute: +To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run: ```shell $ bfg --replace-text passwords.txt ``` -Depois que os dados confidenciais são removidos, você deve fazer push forçado das suas alterações para {% data variables.product.product_name %}. +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on. ```shell $ git push --force ``` -Consulte as instruções completas de download e uso na documentação do [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/). +See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. -### Usando arquivo git filter-repo +### Using git filter-repo {% warning %} -**Aviso:** se você executar `git filter-repo` após acumular as alterações, você não poderá recuperar suas alterações com outros comandos acumulados. Antes de executar `git filter-repo`, recomendamos cancelar a acumulação de todas as alterações que você fez. Para desfazer o stash do último conjunto de alterações no qual você fez stash, execute `git stash show -p | git apply -R`. Para obter mais informações, consulte [Ferramentas do Git - Acúmulo e limpeza](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). +**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). {% endwarning %} -Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arquivo com dados confidenciais do histórico do repositório e adicioná-lo a `. itignore` para garantir que não se faça o commit novamente de forma acindelal. +To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed. -1. Instale a versão mais recente da ferramenta [git filter-repo](https://github.com/newren/git-filter-repo). Você pode instalar `git-filter-repo` manualmente ou usando um gerenciador de pacotes. Por exemplo, para instalar a ferramenta com o HomeBrew, use o comando `brew install`. +1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command. ``` brew install git-filter-repo ``` - Para obter mais informações, consulte [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) no repositório `newren/git-filter-repo`. + For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository. -2. Se você ainda não tiver uma cópia local do repositório com dados confidenciais no histórico, [faça um clone do repositório](/articles/cloning-a-repository/) no computador local. +2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer. ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ @@ -85,22 +84,22 @@ Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arqu > Receiving objects: 100% (1301/1301), 164.39 KiB, done. > Resolving deltas: 100% (724/724), done. ``` -3. Acesse o diretório de trabalho do repositório. +3. Navigate into the repository's working directory. ```shell $ cd YOUR-REPOSITORY ``` -4. Execute o seguinte comando substituindo `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` pelo **caminho do arquivo que deseja remover, não apenas o nome do arquivo**. Esses argumentos vão: - - Forçar o Git a processar, mas não fazer checkout, do histórico completo de cada branch e tag - - Remover o arquivo especificado, bem como qualquer commit vazio gerado como resultado - - Remova algumas configurações, como a URL remota, armazenada no arquivo *.git/config*. Você deverá fazer backup deste arquivo com antecedência para a restauração mais adiante. - - **Sobrescrever as tags existentes** +4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will: + - Force Git to process, but not check out, the entire history of every branch and tag + - Remove the specified file, as well as any empty commits generated as a result + - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later. + - **Overwrite your existing tags** ```shell $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA Parsed 197 commits New history written in 0.11 seconds; now repacking/cleaning... Repacking your repo and cleaning out old unneeded objects Enumerating objects: 210, done. - Contando objetos: 100% (210/210), concluído. + Counting objects: 100% (210/210), done. Delta compression using up to 12 threads Compressing objects: 100% (127/127), done. Writing objects: 100% (210/210), done. @@ -111,11 +110,11 @@ Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arqu {% note %} - **Observação:** se o arquivo com dados confidenciais existir em qualquer outro caminho (porque foi movido ou renomeado), execute esse comando nesses caminhos também. + **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well. {% endnote %} -5. Adicione o arquivo com dados confidenciais ao `.gitignore` para impedir a repetição acidental do commit. +5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again. ```shell $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore @@ -124,8 +123,8 @@ Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arqu > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore > 1 files changed, 1 insertions(+), 0 deletions(-) ``` -6. Verifique se você removeu todo o conteúdo desejado do histórico do repositório e fez checkout de todos os branches. -7. Quando você estiver satisfeito com o estado do seu repositório, faça push forçado das alterações locais para sobrescrever o repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, bem como de todos os branches para os quais você fez o push: +6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out. +7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history. ```shell $ git push origin --force --all > Counting objects: 1074, done. @@ -136,7 +135,7 @@ Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arqu > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git > + 48dc599...051452f main -> main (forced update) ``` -8. Para remover o arquivo com dados confidenciais das [versões com tag](/articles/about-releases), você também precisará forçar o push das tags do Git: +8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags: ```shell $ git push origin --force --tags > Counting objects: 321, done. @@ -148,15 +147,15 @@ Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arqu > + 48dc599...051452f main -> main (forced update) ``` -## Remover completamente os dados de {% data variables.product.prodname_dotcom %} +## Fully removing the data from {% data variables.product.prodname_dotcom %} -Depois de usar a ferramenta BFG ou `git filter-repo` para remover os dados confidenciais e fazer push das suas alterações para {% data variables.product.product_name %}, você deve seguir mais algumas etapas para remover completamente os dados de {% data variables.product.product_name %}. +After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}. -1. Entre em contato com o {% data variables.contact.contact_support %} e solicite a remoção das visualizações em cache e das referências aos dados confidenciais em pull requests no {% data variables.product.product_name %}. Forneça o nome do repositório e/ou um link para o commit que você precisa que seja removido. +1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed. -2. Peça para os colaboradores [fazerem rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *e não* merge, nos branches criados a partir do histórico antigo do repositório. Um commit de merge poderia reintroduzir o histórico antigo completo (ou parte dele) que você acabou de se dar ao trabalho de corrigir. +2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging. -3. Após decorrido um tempo e você estiver confiante de que a ferramenta BFG / `git filter-repo` não teve efeitos colaterais, você poderá forçar todos os objetos no seu repositório local a serem dereferenciados e lixo coletado com os seguintes comandos (usando o Git 1.8.5 ou mais recente): +3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer): ```shell $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin $ git reflog expire --expire=now --all @@ -169,21 +168,21 @@ Depois de usar a ferramenta BFG ou `git filter-repo` para remover os dados confi ``` {% note %} - **Observação:** você também pode conseguir isso fazendo push do histórico filtrado em um repositório novo ou vazio e, em seguida, criando um clone usando o {% data variables.product.product_name %}. + **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}. {% endnote %} -## Evitar commits acidentais no futuro +## Avoiding accidental commits in the future -Há alguns truques simples para evitar fazer commit de coisas não desejadas: +There are a few simple tricks to avoid committing things you don't want committed: -- Use um programa visual, como o [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) e o [gitk](https://git-scm.com/docs/gitk), para fazer commit das alterações. Nos programas visuais, geralmente é mais fácil ver exatamente quais arquivos serão adicionados, excluídos e modificados em cada commit. -- Evite os comandos catch-all `git add .` e `git commit -a` na linha de comando— use `git add filename` e `git rm filename` para fazer stage de arquivos individuais. -- Use o `git add --interactive` para revisar e fazer stage das alterações em cada arquivo de forma individual. -- Use o `git diff --cached` para revisar as alterações que você incluiu no stage para commit. Esse é o diff exato que o `git commit` produzirá, contanto que você não use o sinalizador `-a`. +- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit. +- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead. +- Use `git add --interactive` to individually review and stage changes within each file. +- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag. -## Leia mais +## Further reading -- [página man de `git filter-repo`](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) -- [Pro Git: Ferramentas do Git - Reescrevendo o Histórico](https://git-scm.com/book/en/Git-Tools-Rewriting-History) -- "[Sobre a digitalização de segredos](/code-security/secret-security/about-secret-scanning)" +- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) +- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History) +- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)" diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md index 892208e95a..ad03fae2b2 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md @@ -1,6 +1,6 @@ --- -title: Assinar commits -intro: Você pode assinar commits localmente usando GPG ou S/MIME. +title: Signing commits +intro: You can sign commits locally using GPG or S/MIME. redirect_from: - /articles/signing-commits-and-tags-using-gpg/ - /articles/signing-commits-using-gpg/ @@ -16,45 +16,45 @@ topics: - Identity - Access management --- - {% data reusables.gpg.desktop-support-for-commit-signing %} {% tip %} -**Dicas:** +**Tips:** -Para configurar seu cliente Git para assinar commits por padrão para um repositório local, em versões 2.0.0 e acima do Git, execute `git config commit.gpgsign true`. Para assinar todos os commits por padrão em qualquer repositório local no seu computador, execute `git config --global commit.gpgsign true`. +To configure your Git client to sign commits by default for a local repository, in Git versions 2.0.0 and above, run `git config commit.gpgsign true`. To sign all commits by default in any local repository on your computer, run `git config --global commit.gpgsign true`. -Para armazenar a frase secreta da chave GPG e não precisar inseri-la sempre que assinar um commit, recomendamos o uso das seguintes ferramentas: - - Para usuários do Mac, o [GPG Suite](https://gpgtools.org/) permite armazenar a frase secreta da chave GPG no keychain do sistema operacional do Mac. - - Para usuários do Windows, o [Gpg4win](https://www.gpg4win.org/) se integra a outras ferramentas do Windows. +To store your GPG key passphrase so you don't have to enter it every time you sign a commit, we recommend using the following tools: + - For Mac users, the [GPG Suite](https://gpgtools.org/) allows you to store your GPG key passphrase in the Mac OS Keychain. + - For Windows users, the [Gpg4win](https://www.gpg4win.org/) integrates with other Windows tools. -Você também pode configurar manualmente o [gpg-agent](http://linux.die.net/man/1/gpg-agent) para salvar a frase secreta da chave GPG, mas ele não se integra ao keychain do sistema operacional do Mac, como o ssh-agent, e exige mais configuração. +You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent) to save your GPG key passphrase, but this doesn't integrate with Mac OS Keychain like ssh-agent and requires more setup. {% endtip %} -Se você tiver várias chaves ou estiver tentando assinar commits ou tags com uma chave que não corresponde a sua identidade de committer, precisará [informar o Git a chave de assinatura](/articles/telling-git-about-your-signing-key). +If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key). -1. Ao fazer commit das alterações no branch local, adicione o sinalizador -S flag ao comando git commit: +1. When committing changes in your local branch, add the -S flag to the git commit command: ```shell - $ git commit -S -m your commit message + $ git commit -S -m "your commit message" # Creates a signed commit ``` -2. Ao usar o GPG, depois de criar o commit, forneça a frase secreta configurada quando você [gerou a chave GPG](/articles/generating-a-new-gpg-key). -3. Quando terminar de criar os commits localmente, faça o push para o repositório remoto no {% data variables.product.product_name %}: +2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key). +3. When you've finished creating commits locally, push them to your remote repository on {% data variables.product.product_name %}: ```shell $ git push # Pushes your local commits to the remote repository ``` -4. No {% data variables.product.product_name %}, navegue até sua pull request. +4. On {% data variables.product.product_name %}, navigate to your pull request. {% data reusables.repositories.review-pr-commits %} -5. Para exibir informações mais detalhadas sobre a assinatura verificada, clique em Verified (Verificada). ![Commit assinado](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) +5. To view more detailed information about the verified signature, click Verified. +![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) -## Leia mais +## Further reading -* "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -* "[Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)" -* "[Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -* "[Avisar o Git sobre sua chave de assinatura](/articles/telling-git-about-your-signing-key)" -* "[Associar um e-mail à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)" -* "[Assinar tags](/articles/signing-tags)" +* "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +* "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +* "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)" +* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)" +* "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)" +* "[Signing tags](/articles/signing-tags)" diff --git a/translations/pt-BR/content/billing/index.md b/translations/pt-BR/content/billing/index.md index 0c02ce8c82..067b356ef5 100644 --- a/translations/pt-BR/content/billing/index.md +++ b/translations/pt-BR/content/billing/index.md @@ -1,15 +1,46 @@ --- -title: Cobrança e pagamentos para o GitHub -shortTitle: Faturamento e pagamentos -intro: '{% ifversion fpt %}{% data variables.product.product_name %} oferece produtos grátis e pagos para cada conta. Você pode atualizar, fazer o downgrade e visualizar as alterações pendentes da assinatura da sua conta a qualquer momento.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} cobranças para os integrantes da sua empresa {% ifversion ghec or ghae %}uso de {% data variables.product.product_name %}{% elsif ghes %} estações de licença para {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} e quaisquer serviços adicionais que você comprar{% endif %}{% endif %}.{% endif %}' +title: Billing and payments on GitHub +shortTitle: Billing and payments +intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github +introLinks: + overview: '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/about-billing-on-github{% elsif ghes%}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' +featuredLinks: + guides: + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method{% endif %}' + - '{% ifversion fpt %}/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription{% endif %}' + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/setting-your-billing-email{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/about-per-user-pricing{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + popular: + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + guideCards: + - /billing/managing-your-github-billing-settings/removing-a-payment-method + - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process + - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud{% endif %}' +layout: product-landing versions: fpt: '*' - ghec: '*' ghes: '*' ghae: '*' + ghec: '*' +topics: + - Billing children: - /managing-your-github-billing-settings - /managing-billing-for-your-github-account @@ -23,5 +54,4 @@ children: - /managing-billing-for-github-marketplace-apps - /managing-billing-for-git-large-file-storage - /setting-up-paid-organizations-for-procurement-companies ---- - +--- \ No newline at end of file diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md index 843c2f2bf0..86724905ed 100644 --- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md @@ -16,36 +16,36 @@ type: overview topics: - Enterprise - Licensing -shortTitle: Sobre +shortTitle: About --- -## Sobre o {% data variables.product.prodname_vss_ghe %} +## About {% data variables.product.prodname_vss_ghe %} -{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. Para obter mais informações, consulte [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) no site {% data variables.product.prodname_vs %} +{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -To use the {% data variables.product.prodname_enterprise %} portion of the license, each subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. To accomplish this, organization owners can invite new members to an organization by email address. O assinante pode aceitar o convite com uma conta de usuário existente em {% data variables.product.prodname_dotcom_the_website %} ou criar uma nova conta. +To use the {% data variables.product.prodname_enterprise %} portion of the license, each subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. To accomplish this, organization owners can invite new members to an organization by email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. For more information about the setup of {% data variables.product.prodname_vss_ghe %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." -## Sobre as licenças para {% data variables.product.prodname_vss_ghe %} +## About licenses for {% data variables.product.prodname_vss_ghe %} -After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise with a user account on {% data variables.product.prodname_dotcom_the_website %}. Se o endereço de e-mail para a conta de usuário de um integrante corporativo em {% data variables.product.prodname_dotcom_the_website %} corresponde ao Nome Principal do Usuário (UPN) de um assinante da sua conta {% data variables.product.prodname_vs %} o {% data variables.product.prodname_vs %} assinante consumirá automaticamente uma licença para {% data variables.product.prodname_vss_ghe %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. -A quantidade total de suas licenças para a sua empresa em {% data variables.product.prodname_dotcom %} é a soma de qualquer licença padrão de {% data variables.product.prodname_enterprise %} e o número de licenças de assinatura {% data variables.product.prodname_vs %} que incluem acesso a {% data variables.product.prodname_dotcom %}. Se a conta de usuário de um integrante corporativo não corresponde ao endereço de e-mail de um assinante de {% data variables.product.prodname_vs %}, a licença que a conta de usuário consome não estará disponível para um assinante de {% data variables.product.prodname_vs %}. +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. -Para obter mais informações sobre o {% data variables.product.prodname_enterprise %}, consulte "[Produtos do {% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)". Para obter mais informações sobre contas em {% data variables.product.prodname_dotcom_the_website %}, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)". +For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.product.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)." {% tip %} -**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](https://docs-internal-19656--vss-ghe-s.herokuapp.com/en/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. +**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. {% endtip %} -Você também pode ver convites pendentes de {% data variables.product.prodname_enterprise %} para inscritos em {% data variables.product.prodname_vss_admin_portal_with_url %}. +You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}. -## Leia mais +## Further reading - [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in Microsoft Docs -- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs +- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs \ No newline at end of file diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 6797a71add..fddb22eb95 100644 --- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -1,18 +1,18 @@ --- title: Setting up Visual Studio subscriptions with GitHub Enterprise -intro: 'Your team''s subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}.' +intro: "Your team's subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}." versions: ghec: '*' type: how_to topics: - Enterprise - Licensing -shortTitle: Configurar +shortTitle: Set up --- ## About setup of {% data variables.product.prodname_vss_ghe %} -{% data reusables.enterprise-accounts.vss-ghe-description %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_vss_ghe %}de](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)." +{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)." This guide shows you how your team can get {% data variables.product.prodname_vs %} subscribers licensed and started with {% data variables.product.prodname_enterprise %}. @@ -20,27 +20,28 @@ This guide shows you how your team can get {% data variables.product.prodname_vs Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering. -| Role | Serviço | Descrição | Mais informações | -|:---------------------------- |:----------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs | -| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs | -| **Proprietário corporativo** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %} | "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" | -| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | -| **Integrante da empresa** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %} | "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" | +| Role | Service | Description | More information | +| :- | :- | :- | :- | +| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs | +| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs | +| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" | +| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | +| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" | -## Pré-requisitos +## Prerequisites -- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs. +- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and + [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs. + + - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." - - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". - -## Configurar o {% data variables.product.prodname_vss_ghe %} +## Setting up {% data variables.product.prodname_vss_ghe %} To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks. One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)." -1. An [enterprise owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) must create at least one organization in your enterprise on {% data variables.product.product_location %}. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". +1. An [enterprise owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) must create at least one organization in your enterprise on {% data variables.product.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." 1. The [subscription admin](#roles-for-visual-studio-subscriptions-with-github-enterprise) must assign a license for {% data variables.product.prodname_vs %} to a [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs. @@ -52,7 +53,7 @@ One person may be able to complete the tasks because the person has all of the r {% tip %} - **Dicas**: + **Tips**: - While not required, we recommend that the [organization owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) sends an invitation to the same email address used for the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise)'s User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise)'s UPN, you can ensure that another [enterprise member](#roles-for-visual-studio-subscriptions-with-github-enterprise) does not claim the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise)'s license. - If the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)." @@ -60,8 +61,8 @@ One person may be able to complete the tasks because the person has all of the r {% endtip %} -After {% data variables.product.prodname_vss_ghe %} is set up for [subscribers](#roles-for-visual-studio-subscriptions-with-github-enterprise) on your team, [enterprise owners](#roles-for-visual-studio-subscriptions-with-github-enterprise) can review licensing information on {% data variables.product.product_location %}. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". +After {% data variables.product.prodname_vss_ghe %} is set up for [subscribers](#roles-for-visual-studio-subscriptions-with-github-enterprise) on your team, [enterprise owners](#roles-for-visual-studio-subscriptions-with-github-enterprise) can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## Leia mais +## Further reading - "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)" diff --git a/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md deleted file mode 100644 index 61b3af8d13..0000000000 --- a/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Criar e pagar uma organização em nome de um cliente -intro: 'Você pode criar e pagar por uma organização do {% data variables.product.prodname_dotcom %} em nome de um cliente.' -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client - - /articles/creating-and-paying-for-an-organization-on-behalf-of-a-client - - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client -versions: - fpt: '*' - ghec: '*' -type: quick_start -topics: - - User account - - Organizations - - Upgrades -shortTitle: Em nome de um cliente ---- - -## Requisitos - -Antes de iniciar, certifique-se de que sabe: -- O nome de usuário no {% data variables.product.prodname_dotcom %} do cliente que se tornará o proprietário da organização que você cria -- O nome do cliente que deseja usar para a organização -- O endereço de e-mail para onde deseja que os recibos sejam enviados -- O [produto](/articles/github-s-products) que o cliente deseja comprar -- O número de [estações pagas](/articles/about-per-user-pricing/) que o cliente deseja comprar para a organização - -## Etapa 1: Criar sua conta pessoal no {% data variables.product.prodname_dotcom %} - -Você usará sua conta pessoal para configurar a organização. Você também precisará entrar nessa conta para renovar ou fazer alterações na assinatura do seu cliente no futuro. - -Se você já tem uma conta de usuário pessoal no {% data variables.product.prodname_dotcom %}, pule para a [etapa 2](#step-2-create-the-organization). - -1. Acesse a página para [ingressar no GitHub](https://github.com/join). -2. Em "Create your personal account" (Criar sua conta pessoal), digite seu nome de usuário, endereço de e-mail e senha, e clique em **Create an account** (Criar uma conta). ![Formulário de entrada para criar conta pessoal](/assets/images/help/billing/billing_create_your_personal_account_form.png) -3. Selecione {% data variables.product.prodname_free_user %} para sua conta pessoal. -4. Clique em **Finish sign up** (Finalizar inscrição). - -## Etapa 2: Criar a organização - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -{% data reusables.organizations.new-organization %} -3. Em "Choose a plan" (Escolher um plano), clique em **Choose {% data variables.product.prodname_free_team %}** (Escolher {% data variables.product.prodname_team_os %}). Você atualizará a organização na próxima etapa. -{% data reusables.organizations.organization-name %} -5. Em "Contact email" (E-mail de contato), digite um endereço de e-mail de contato para seu cliente. ![Campo Contact email (E-mail de contato)](/assets/images/help/organizations/contact-email-field.png) -{% data reusables.dotcom_billing.owned_by_business %} -8. Clique em **Próximo**. - -## Etapa 3: Atualizar a organização para uma assinatura paga anual - - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.billing_plans %} -{% data reusables.dotcom_billing.upgrade_org %} -{% data reusables.dotcom_billing.choose_org_plan %} (Você pode adicionar mais estações na organização na próxima etapa.) -6. Em "Upgrade summary" (Atualizar resumo), selecione **Pay yearly** (Pagar anualmente) para pagar pela organização anualmente. ![Botão de rádio para cobrança anual](/assets/images/help/billing/choose-annual-billing-org-resellers.png) -{% data reusables.dotcom_billing.enter-payment-info %} -{% data reusables.dotcom_billing.finish_upgrade %} - -## Etapa 4: Atualizar o número de estações pagas na organização - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.billing_plans %} -{% data reusables.dotcom_billing.add-seats %} -{% data reusables.dotcom_billing.number-of-seats %} -{% data reusables.dotcom_billing.confirm-add-seats %} - -## Etapa 5: Convidar cliente para ingressar na organização - -{% data reusables.profile.access_org %} -{% data reusables.user_settings.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.invite_member_from_people_tab %} -5. Digite o nome de usuário do cliente no {% data variables.product.prodname_dotcom %} e pressione **Enter**. ![Campo para digitar nome de usuário do cliente](/assets/images/help/organizations/org-invite-modal.png) -6. Escolha a função *owner* (proprietário) para o cliente e clique em **Send invitation** (Enviar convite). ![Botão de opção Owner (Proprietário) e botão Send invitation (Enviar convite)](/assets/images/help/organizations/add-owner-send-invite-reseller.png) -7. O cliente receberá um e-mail convidando-o para a organização. Ele precisará aceitar o convite para que você possa passar para a próxima etapa. - -## Etapa 6: Transferir a propriedade da organização para seu cliente - -{% data reusables.profile.access_org %} -{% data reusables.user_settings.access_org %} -{% data reusables.organizations.people %} -4. Confirme se o cliente está listado entre os integrantes da organização e recebeu a função *owner* (proprietário). -5. À direita do seu nome de usuário, use o menu suspenso {% octicon "gear" aria-label="The Settings gear" %} e clique em **Manage** (Gerenciar). ![Link para manage access (gerenciar acesso)](/assets/images/help/organizations/member-manage-access.png) -6. À esquerda, clique em **Remove from organization** (Remover da organização). ![Botão Remove from organization (Remover da organização)](/assets/images/help/organizations/remove-from-org-button.png) -7. Confirme sua escolha e clique em **Remove members** (Remover membros). ![Botão de confirmação Remove members (Remover integrantes)](/assets/images/help/organizations/confirm-remove-from-org.png) - -## Próximas etapas - -1. Entre em contato com o cliente e peça a ele para [adicionar você à organização como um gerente de cobrança](/articles/adding-a-billing-manager-to-your-organization). Você precisará ser um gerente de cobrança da organização para que possa renovar ou fazer alterações na assinatura do seu cliente no futuro. -2. Se quiser que o cartão de crédito seja removido da organização para que não seja cobrado novamente, contate o {% data variables.contact.contact_support %}. -3. Quando chegar o momento de renovar a assinatura paga do cliente, consulte "[Renovar a organização paga do cliente](/articles/renewing-your-client-s-paid-organization)". - -## Leia mais - -- "[Sobre organizações para empresas de compras](/articles/about-organizations-for-procurement-companies)" -- "[Atualizar ou fazer downgrade da organização paga do cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" -- "[Renovar a organização paga do cliente](/articles/renewing-your-client-s-paid-organization)" diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md deleted file mode 100644 index d2d613ab92..0000000000 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ /dev/null @@ -1,481 +0,0 @@ ---- -title: Configurar a varredura do código -intro: 'Você pode configurar como o {% data variables.product.prodname_dotcom %} faz a varredura do código no seu projeto com relação a vulnerabilidades e erros.' -product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning - - /code-security/secure-coding/configuring-code-scanning - - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: how_to -topics: - - Advanced Security - - Code scanning - - Actions - - Repositories - - Pull requests - - JavaScript - - Python -shortTitle: Configurar varredura de código ---- - - - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} - -## Sobre a configuração do {% data variables.product.prodname_code_scanning %} - -Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}, usando {% data variables.product.prodname_actions %} ou a partir do seu sistema de integração contínua (CI). Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" ou -{%- ifversion fpt or ghes > 3.0 or ghae-next %} -"[Sobre {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". -{%- else %} -"[Executar {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." -{% endif %} - -Este artigo é sobre a execução de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} usando ações. - -Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve configurar {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". - -{% data reusables.code-scanning.edit-workflow %} - -A análise de {% data variables.product.prodname_codeql %} é apenas um tipo de {% data variables.product.prodname_code_scanning %} que você pode fazer em {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} em {% data variables.product.prodname_dotcom_the_website %}{% endif %} contém outros fluxos de trabalho de {% data variables.product.prodname_code_scanning %} que você pode usar. {% ifversion fpt or ghec %}Você pode encontrar uma seleção destes na página "Comece com {% data variables.product.prodname_code_scanning %}", que você pode acessar na aba **{% octicon "shield" aria-label="The shield symbol" %} Segurança**.{% endif %} Os exemplos específicos fornecidos neste artigo estão relacionados ao arquivo de {% data variables.product.prodname_codeql_workflow %}. - -## Editing a code scanning workflow - -O {% data variables.product.prodname_dotcom %} salva arquivos de fluxo de trabalho no diretório _.github/workflows_ do seu repositório. Você pode encontrar um fluxo de trabalho que você adicionou procurando o nome do seu arquivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. - -1. No seu repositório, pesquise o arquivo do fluxo de trabalho que você deseja editar. -1. No canto superior direito da vista do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %} para abrir o editor do fluxo de trabalho. ![Edite o botão do arquivo do fluxo de trabalho](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. Depois de ter editado o arquivo, clique em **Iniciar commit** e preencha o formulário "Alterações do commit". Você pode escolher o "commit" diretamente no branch atual ou criar um novo branch e iniciar um pull request. ![Atualização do commit para o fluxo de trabalho do codeql.yml](/assets/images/help/repository/code-scanning-workflow-update.png) - -Para obter mais informações sobre a edição de arquivos do fluxo de trabalho, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". - -## Configurar a frequência - -Você pode fazer a varredura de código de forma pré-programada ou quando ocorrerem eventos específicos em um repositório. - -A varredura do código a cada push para o repositório, e toda vez que um pull request é criado, isso impede que os desenvolvedores introduzam novas vulnerabilidades e erros no código. A varredura do código de forma pré-programada informa as últimas vulnerabilidades e erros de {% data variables.product.company_short %}, que os pesquisadores de segurança e da comunidade, mesmo quando desenvolvedores não estão mantendo o repositório de forma ativa. - -### Fazer a varredura no push - -Se você usar o fluxo de trabalho padrão, o {% data variables.product.prodname_code_scanning %} fará a varredura do código no repositório uma vez por semana, além das varreduras acionadas pelos eventos. Para ajustar essa programação, edite o valor `CRON` no fluxo de trabalho. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)". - -Se você fizer uma varredura no push, os resultados aparecerão na aba **Segurança** do repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). " - -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} -Além disso, quando uma verificação de `on:push` retorna resultados que podem ser mapeados com um pull request aberto, esses alertas serão automaticamente exibidos no pull request nos mesmos lugares que outros alertas de pull request. Os alertas são identificados comparando a análise existente do cabeçalho do branch com a análise do branch de destino. Para obter mais informações sobre alertas de {% data variables.product.prodname_code_scanning %} em pull requests, consulte "[Triando alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". -{% endif %} - -### Fazer a varredura de pull requests - -O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% ifversion ghes %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. Para obter mais informações, consulte "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %} - -Para obter mais informações sobre o evento `pull_request` , consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". - -Se você realizar uma varredura de pull requests, os resultados aparecerão como alertas em uma verificação de pull request. Para obter mais informações, consulte "[Alertas de varredura de código de triagem em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". - -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} - O uso o gatilho `pull_request`, configurado para verificar o commit de merge do pull request, em vez do commit do cabeçalho, produzirá resultados mais eficientes e precisos do que digitalizar o cabeçalho do branch em cada push. No entanto, se você usa um sistema de CI/CD que não pode ser configurado para acionar em pull requests, você ainda poderá usar o gatilho `on:push` e {% data variables.product.prodname_code_scanning %} mapeará os resultados para abrir os pull requests no branch e adicionar os alertas como anotações no pull request. Para obter mais informações, consulte "[Digitalizando ao enviar por push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)". -{% endif %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -### Definindo as severidades que causam falha na verificação de pull request - -Por padrão, apenas os alertas com o nível de gravidade `Error`{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} ou nível de segurança `Critical` ou `High`{% endif %} farão com que ocorra uma falha no pull request e uma verificação será bem-sucedida com alertas de menor gravidade. É possível alterar os níveis de gravide dos alertas{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} e de gravidades de segurança{% endif %} que causarão uma falha de verificação de pull request nas configurações do seu repositório. Para obter mais informações sobre os níveis de gravidade, consulte "[Gerenciar alertas de digitalização de códigos para o seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details). - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -1. Em "Varredura de código", à direita de "Verificar falha", use o menu suspenso para selecionar o nível de gravidade que você gostaria de fazer com que um pull request falhasse. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -![Verificar falha de configuração](/assets/images/help/repository/code-scanning-check-failure-setting.png) -{% else %} -![Verificar falha de configuração](/assets/images/help/repository/code-scanning-check-failure-setting-ghae.png) -{% endif %} -{% endif %} - -### Evitar varreduras desnecessárias de pull requests - -Você pode querer evitar que uma varredura de código seja acionada em pull requests específicos para o branch padrão, Independentemente de os arquivos terem sido alterados. Você pode configurar isso, especificando `no:pull_request:paths-ignore` ou `on:pull_request:paths` no fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. Por exemplo, se as únicas alterações em um pull request são para arquivos com extensões de arquivo `.md` ou `.txt`, você poderá usar o seguinte array `paths-ignore`. - -``` yaml -on: - push: - branches: [main, protected] - pull_request: - branches: [main] - paths-ignore: - - '**/*.md' - - '**/*.txt' -``` - -{% note %} - -**Observações** - -* `on:pull_request:paths-ignore` e `on:pull_request:paths` definem condições que determinam se as ações no fluxo de trabalho serão executadas em um pull request. Eles não determinam quais arquivos serão analisados quando as ações _são_ executadas. Quando uma pull request contém quaisquer arquivos não correspondidos por `on:pull_request:paths-ignore` ou `on:pull_request:paths`, o fluxo de trabalho executa as ações e faz a varredura de todos os arquivos alterados no pull request, incluindo aqueles que correspondidos por `on:pull_request:paths-ignore` ou `on:pull_request:paths`, a menos que os arquivos tenham sido excluídos. Para obter informações sobre como excluir arquivos da análise, consulte "[Especificar diretórios a serem varridos](#specifying-directories-to-scan)". -* Para arquivos do fluxo de trabalho de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, não use as palavras-chave `paths-ignore` ou `paths` com o evento `on:push`, pois é provável que isso gere análises ausentes. Para resultados precisos, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} precisam conseguir comparar novas alterações com a análise do commit anterior. - -{% endnote %} - -Para mais informações sobre como usar `on:pull_request:paths-ignore` e `on:pull_request:paths` para determinar quando um fluxo de trabalho será executado para um pull request, consulte "[sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". - -### Fazer a varredura de forma pré-programada - -O fluxo de trabalho padrão do {% data variables.product.prodname_code_scanning %} usa o evento `on.push` para acionar uma varredura de código em cada push para qualquer branch que contém o arquivo de fluxo de trabalho. Para ajustar essa programação, edite o valor `CRON` no fluxo de trabalho. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)". - -{% note %} - -**Observação**: {% data variables.product.prodname_dotcom %} executa apenas trabalhos programados que estão em fluxos de trabalho no branch-padrão. Alterar a programação de um fluxo de trabalho em qualquer outro branch não terá efeito até que você mescle o branch com o branch-padrão. - -{% endnote %} - -### Exemplo - -O exemplo a seguir mostra um {% data variables.product.prodname_codeql_workflow %} para um repositório em particular que possui um branch-padrão denominado `principal` e um branch protegido denominado `protegido`. - -``` yaml -on: - push: - branches: [main, protected] - pull_request: - branches: [main] - schedule: - - cron: '20 14 * * 1' -``` - -Este fluxo de trabalho faz a varredura: -* Cada push para o branch-padrão e o branch protegido -* Cada pull request para o branch-padrão -* O branch padrão toda segunda-feira às 14h20 UTC - -## Especificar um sistema operacional - -Se seu código exigir um sistema operacional específico para compilar, você poderá configurar o sistema operacional em seu {% data variables.product.prodname_codeql_workflow %}. Edite o valor de `jobs.analyze.runs-on` para especificar o sistema operacional para a máquina que executa suas ações de {% data variables.product.prodname_code_scanning %}. {% ifversion ghes %}Você especifica o sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos, após `auto-hospedado`.{% else %} - -Se você optar por usar um executor auto-hospedado para varredura de código, você pode especificar um sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos, após `auto-hospedado`.{% endif %} - -``` yaml -jobs: - analyze: - name: Analyze - runs-on: [self-hosted, ubuntu-latest] -``` - -{% ifversion fpt or ghec %}Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} - -O {% data variables.product.prodname_code_scanning_capc %} é compatível com as versões mais recentes do macOS, Ubuntu, e Windows. Portanto, os valores típicos para essa configuração são `ubuntu-latest`, `windows-latest` e `macos-latest`. Para obter mais informações, consulte {% ifversion ghes %}" %}"[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" e "[Usando rótulos com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." - -{% ifversion ghes %}Você deve garantir que o Git esteja na variável do PATH em seus executores auto-hospedados.{% else %}Se você usa um executor auto-hospedado, você deve garantir que o Git esteja na variável de PATH.{% endif %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Especificar o local para bancos de dados de {% data variables.product.prodname_codeql %} - -Em geral você não precisa se preocupar com o lugar em que {% data variables.product.prodname_codeql_workflow %} coloca bancos de dados de {% data variables.product.prodname_codeql %}, uma vez que as etapas posteriores encontrarão automaticamente bancos de dados criados nas etapas anteriores. No entanto, se estiver escrevendo um fluxo de trabalho personalizado que exige que o banco de dados de {% data variables.product.prodname_codeql %} esteja em um local específico do disco, por exemplo, para fazer o upload do banco de dados como um artefato de fluxo de trabalho você pode especificar essa localização usando o parâmetro `db-location` na ação `init`. - -{% raw %} -``` yaml -- uses: github/codeql-action/init@v1 - with: - db-location: '${{ github.workspace }}/codeql_dbs' -``` -{% endraw %} - -O {% data variables.product.prodname_codeql_workflow %} esperará que o caminho fornecido no `db-location` tenha permissão de gravação, e não exista ou seja um diretório vazio. Ao usar este parâmetro em um trabalho em execução em um executor auto-hospedado ou usando um contêiner Docker, é responsabilidade do usuário garantir que o diretório escolhido seja limpo entre execuções, ou que os bancos de dados sejam removidos depois de deixarem de ser necessários. {% ifversion fpt or ghec or ghes %} This is not necessary for jobs running on {% data variables.product.prodname_dotcom %}-hosted runners, which obtain a fresh instance and a clean filesystem each time they run. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."{% endif %} - -Se este parâmetro não for usado, o {% data variables.product.prodname_codeql_workflow %} criará bancos de dados em um local temporário da sua própria escolha. -{% endif %} - -## Alterar as linguagens que são analisadas - -O {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} detecta automaticamente código escrito nas linguagens compatíveis. - -{% data reusables.code-scanning.codeql-languages-bullets %} - -O arquivo padrão do {% data variables.product.prodname_codeql_workflow %} contém uma matriz de criação denominada `linguagem` que lista as linguagens no seu repositório que são analisadas. O {% data variables.product.prodname_codeql %} preenche automaticamente esta matriz quando você adiciona o {% data variables.product.prodname_code_scanning %} a um repositório. Usar a matriz de `linguagem` otimiza {% data variables.product.prodname_codeql %} para executar cada análise em paralelo. Recomendamos que todos os fluxos de trabalho adotem esta configuração devido aos benefícios de desempenho de criações paralelas. Para obter mais informações sobre matrizes de criação, consulte "[Gerenciar fluxos de trabalho complexos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)". - -{% data reusables.code-scanning.specify-language-to-analyze %} - -Se o seu fluxo de trabalho usar a matriz de     linguagem `, o {% data variables.product.prodname_codeql %} será codificado para analisar apenas as linguagens da matriz. Para alterar as linguagens que você deseja analisar, edite o valor da variável da matriz. Você pode remover uma linguagem para evitar que ele seja analisado ou adicionar uma linguagem que não estava presente no repositório quando o {% data variables.product.prodname_code_scanning %} estava configurado. Por exemplo, se o repositório inicialmente continha apenas JavaScript quando {% data variables.product.prodname_code_scanning %} foi configurado e, posteriormente, você adicionou o código Python, você precisará adicionar o python` à matriz. - -```yaml -jobs: - analyze: - name: Analyze - ... - strategy: - fail-fast: false - matrix: - language: ['javascript', 'python'] -``` - -Se o seu fluxo de trabalho não contiver uma matriz denominada `linguagem`, o {% data variables.product.prodname_codeql %} será configurado para executar a análise sequencialmente. Se você não especificar as linguagens no fluxo de trabalho, o {% data variables.product.prodname_codeql %} irá detectar automaticamente e tentará analisar quaisquer linguagens compatíveis no repositório. Se você quiser escolher quais linguagens analisar sem usar uma matriz, você poderá usar o parâmetro `linguagens` na ação `init`. - -```yaml -- uses: github/codeql-action/init@v1 - with: - languages: cpp, csharp, python -``` -{% ifversion fpt or ghec %} -## Analisar as dependências do Python - -Para executores hospedados no GitHub, que usam apenas Linux, o {% data variables.product.prodname_codeql_workflow %} tentará instalar automaticamente as dependências do Python para dar mais resultados para a análise do CodeQL. Você pode controlar este comportamento especificando o parâmetro `setup-python-dependencies` para a ação chamada pela etapa "Initialize CodeQL". Por padrão, esse parâmetro é definido como `verdadeiro`: - -- Se o repositório contiver código escrito em Python, a etapa "Initialize CodeQL" instalará as dependências necessárias no executor hospedado pelo GitHub. Se a instalação automática for bem-sucedida, a ação também definirá a variável de ambiente `CODEQL_PYTHON` para o arquivo Python executável que inclui as dependências. - -- Se o repositório não tiver dependências do Python ou se as dependências forem especificadas de forma inesperada, você receberá um aviso e a ação continuará com os trabalhos restantes. A ação pode ser executada com sucesso, mesmo quando houver problemas de interpretação de dependências, mas os resultados podem estar incompletos. - -Alternativamente, você pode instalar as dependências do Python manualmente em qualquer sistema operacional. Você precisará adicionar as `setup-python-dependencies` e definir como `falso`, além de definir `CODEQL_PYTHON` como o executável do Python que inclui as dependências, conforme mostrado neste trecho do fluxo de trabalho: - -```yaml -jobs: - CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - permissions: - security-events: write - actions: read{% endif %} - - steps: - - name: Checkout repository - uses: actions/checkout@v2 - - name: Set up Python - uses: actions/setup-python@v2 - with: - python-version: '3.x' - - name: Install dependencies - run: | - python -m pip install --upgrade pip - if [ -f requirements.txt ]; - then pip install -r requirements.txt; - fi - # Set the `CODEQL-PYTHON` environment variable to the Python executable - # that includes the dependencies - echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - - name: Initialize CodeQL - uses: github/codeql-action/init@v1 - with: - languages: python - # Override the default behavior so that the action doesn't attempt - # to auto-install Python dependencies - setup-python-dependencies: false -``` -{% endif %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Configurar uma categoria para a análise - -Use a `categoria` para distinguir entre múltiplas análises para a mesma ferramenta e commit, mas executada em diferentes linguagens ou diferentes partes do código. A categoria especificada no seu fluxo de trabalho será incluída no arquivo de resultados SARIF. - -Esse parâmetro é particularmente útil se você trabalhar com monorepos e tiver vários arquivos SARIF para diferentes componentes do monorepo. - -{% raw %} -``` yaml - - name: Perform CodeQL Analysis - uses: github/codeql-action/analyze - with: - # Optional. Specify a category to distinguish between multiple analyses - # for the same tool and ref. If you don't use `category` in your workflow, - # GitHub will generate a default category name for you - category: "my_category" -``` -{% endraw %} - -Se você não especificar um parâmetro da `categoria` no seu fluxo de trabalho, {% data variables.product.product_name %} irá gerar um nome de categoria para você, com base no nome do arquivo de fluxo de trabalho que ativa a ação, o nome da ação e todas as variáveis de matrizes. Por exemplo: -- O fluxo de trabalho `.github/workflows/codeql-analyis.yml` e a ação `analyze` produzirão a categoria `.github/workflows/codeql.yml:analyze`. -- O fluxo de trabalho `.github/workflows/codeql-analyis.yml`, a ação `analyze` e as variáveis da matriz `{language: javascript, os: linux}` irão produzir a categoria `.github/workflows/codeql-analyis.yml:analyze/language:javascript/os:linux`. - -A `categoria` será exibida como a propriedade `.automationDetails.id` no SARIF v2.1.0. Para obter mais informações, consulte "[Suporte SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)". - -Sua categoria especificada não substituirá os detalhes do objeto `runAutomationDetails` no arquivo SARIF, se incluído. - -{% endif %} - -## Executar consultas adicionais - -{% data reusables.code-scanning.run-additional-queries %} - -{% if codeql-packs %} -### Usando pacotes de consulta de {% data variables.product.prodname_codeql %} - -{% data reusables.code-scanning.beta-codeql-packs-cli %} - -Para adicionar um ou mais pacotes de consulta (beta) de {% data variables.product.prodname_codeql %}, adicione uma entrada `with: packs` à seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. Dentro de `pacotes` você especifica um ou mais pacotes para usar e, opcionalmente, qual versão baixar. Quando você não especificar uma versão, será feito o download da versão mais recente. Se você quiser usar pacotes que não estão disponíveis publicamente, você precisa definir a variável de ambiente `GITHUB_TOKEN` para um segredo que tenha acesso aos pacotes. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)". - -{% note %} - -**Observação:** Para fluxos de trabalho que geram bancos de dados de {% data variables.product.prodname_codeql %} para várias linguagens, você deverá especificar pacotes de consulta de {% data variables.product.prodname_codeql %} em um arquivo de configuração. Para obter mais informações, consulte "[Especificando pacotes de consulta {% data variables.product.prodname_codeql %}](#specifying-codeql-query-packs)" abaixo. - -{% endnote %} - -No exemplo abaixo, `escopo` é toda organização ou conta pessoal que publicou o pacote. Quando o fluxo de trabalho é executado, os três pacotes de consulta de {% data variables.product.prodname_codeql %} são baixados de {% data variables.product.product_name %} e das consultas ou conjunto de consultas padrão para cada execução de pacote. É feito o download da versão mais recente do `pack1`, pois nenhuma versão é especificada. A versão 1.2.3 de `pack2` é baixada, bem como a última versão de `pack3` que é compatível com a versão 1.2.3. - -{% raw %} -``` yaml -- uses: github/codeql-action/init@v1 - with: - # Comma-separated list of packs to download - packs: scope/pack1,scope/pack2@1.2.3,scope/pack3@~1.2.3 -``` -{% endraw %} - -### Usando consultas em pacotes QL -{% endif %} -Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. Se as consultas estiverem em um repositório privado, use o parâmetro `external-repository-token` para especificar um token que tenha acesso ao check-out do repositório privado. - -{% raw %} -``` yaml -- uses: github/codeql-action/init@v1 - with: - queries: COMMA-SEPARATED LIST OF PATHS - # Optional. Forneça um token de acesso para consultas armazenadas em repositórios privados. - external-repository-token: ${{ secrets.ACCESS_TOKEN }} -``` -{% endraw %} - -Você também pode executar suítes de consultas adicionais especificando-os em um arquivo de configuração. Os suítes de consulta são coleções de consultas, geralmente agrupados por finalidade ou linguagem. - -{% data reusables.code-scanning.codeql-query-suites %} - -{% if codeql-packs %} -### Trabalhando com arquivos de configuração personalizados -{% endif %} - -Se você também usar um arquivo de configuração para configurações personalizadas, todas os {% if codeql-packs %}pacotes ou {% endif %}consultas especificadas no seu fluxo de trabalho serão usados em vez daqueles especificados no arquivo de configuração. Se você quiser executar o conjunto combinado de {% if codeql-packs %}pacotes adicionais ou {% endif %}consultas, prefixe o valor de {% if codeql-packs %}`pacotes` ou {% endif %}`consultas` no fluxo de trabalho com o símbolo `+`. Para obter exemplos de arquivos de configuração, consulte "[Exemplo de arquivos de configuração](#example-configuration-files)". - -No exemplo a seguir, o símbolo `+` garante que os {% if codeql-packs %}pacotes e {% endif %}consultas especificados sejam usados em conjunto com qualquer um especificado no arquivo de configuração referenciado. - -``` yaml -- uses: github/codeql-action/init@v1 - with: - config-file: ./.github/codeql/codeql-config.yml - queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main - {%- if codeql-packs %} - packs: +scope/pack1,scope/pack2@v1.2.3 - {% endif %} -``` - -## Usar uma ferramenta de varredura de código de terceiros - -Um arquivo de configuração personalizado é uma forma alternativa de especificar as consultas adicionais de {% if codeql-packs %}e {% endif %}a serem executadas. Você também pode usar o arquivo para desabilitar as consultas padrão e especificar quais diretórios digitalizar durante a análise. - -No arquivo de workflow use o parâmetro `config-file` da ação `init` para especificar o caminho para o arquivo de configuração que você deseja usar. Este exemplo carrega o arquivo de configuração _./.github/codeql/codeql-config.yml_. - -``` yaml -- uses: github/codeql-action/init@v1 - with: - config-file: ./.github/codeql/codeql-config.yml -``` - -{% data reusables.code-scanning.custom-configuration-file %} - -Se o arquivo de configuração estiver localizado em um repositório privado externo, use o parâmetro `external-repository-token` da ação `init` para especificar um token que tenha acesso ao repositório privado. - -{% raw %} -```yaml -- uses: github/codeql-action/init@v1 - with: - external-repository-token: ${{ secrets.ACCESS_TOKEN }} -``` -{% endraw %} - -As configurações no arquivo de configuração estão escritas no formato YAML. - -{% if codeql-packs %} -### Especificando pacotes de consulta de {% data variables.product.prodname_codeql %} - -{% data reusables.code-scanning.beta-codeql-packs-cli %} - -Você especificou pacotes de consulta de {% data variables.product.prodname_codeql %} em uma matriz. Observe que o formato é diferente do formato usado pelo arquivo do fluxo de trabalho. - -{% raw %} -``` yaml -packs: - # Use the latest version of 'pack1' published by 'scope' - - scope/pack1 - # Use version 1.23 of 'pack2' - - scope/pack2@v1.2.3 - # Use the latest version of 'pack3' compatible with 1.23 - - scope/pack3@~1.2.3 -``` -{% endraw %} - -Se tiver um fluxo de trabalho que gera mais de um banco de dados de {% data variables.product.prodname_codeql %}, você poderá especificar todos os pacotes de consulta de {% data variables.product.prodname_codeql %} para executar em um arquivo de configuração personalizado usando um mapa aninhado de pacotes. - -{% raw %} -``` yaml -packs: - # Use these packs for JavaScript analysis - javascript: - - scope/js-pack1 - - scope/js-pack2 - # Use these packs for Java analysis - java: - - scope/java-pack1 - - scope/java-pack2@v1.0.0 -``` -{% endraw %} -{% endif %} - -### Especificar consultas adicionais - -Você especifica consultas adicionais em um array de `consultas`. Cada elemento do array contém um parâmetro de `uso` com um valor que identifica um único arquivo de consulta, um diretório que contém arquivos de consulta ou um arquivo de definição do conjunto de consulta. - -``` yaml -queries: - - uses: ./my-basic-queries/example-query.ql - - uses: ./my-advanced-queries - - uses: ./query-suites/my-security-queries.qls -``` - -Opcionalmente, você pode dar um nome a cada elemento do array, conforme mostrado nos exemplos de arquivos de configuração abaixo. Para obter mais informações sobre consultas adicionais, consulte "[Executar consultas adicionais](#running-additional-queries) acima. - -### Desativar as consultas-padrão - -Se você desejar apenas executar consultas personalizadas, você poderá desabilitar as consultas de segurança padrão adicionando `disable-default-queries: true` ao seu arquivo de configuração. - -### Especificar diretórios para serem varridos - -Para as linguagens interpretadas com as quais {% data variables.product.prodname_codeql %} é compatível (Python{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %}, Ruby{% endif %} e JavaScript/TypeScript), você pode restringir {% data variables.product.prodname_code_scanning %} para arquivos em diretórios específicos adicionando uma matriz `caminhos` matriz ao arquivo de configuração. Você pode excluir os arquivos em diretórios específicos das análises, adicionando um array de `paths-ignore`. - -``` yaml -paths: - - src -paths-ignore: - - src/node_modules - - '**/*.test.js' -``` - -{% note %} - -**Observação**: - -* As palavras-chave `caminhos` e `paths-ignore`, usados no contexto do arquivo de configuração do {% data variables.product.prodname_code_scanning %}, não deve ser confundido com as mesmas palavras-chave usadas para `on..paths` em um fluxo de trabalho. Quando estão acostumados a modificar `on.` em um fluxo de trabalho, eles determinam se as ações serão executadas quando alguém modifica o código nos diretórios especificados. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". -* Os caracteres de filtros padrão `?`, `+`, `[`, `]` e `!` não são compatíveis e serão correspondidos literalmente. -* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por exemplo, `foo/**`, `**/foo` e `foo/**/bar` são todos de sintaxe permitida, mas `**foo` não é. No entanto, você pode usar estrelas únicas junto com outros caracteres, conforme mostrado no exemplo. Você precisará colocar entre aspas qualquer coisa que contenha um caractere `*`. - -{% endnote %} - -Para linguagens compiladas, se você deseja limitar {% data variables.product.prodname_code_scanning %} a diretórios específicos no seu projeto, você deverá especificar os passos de compilação adequados no fluxo de trabalho. Os comandos que você precisa usar para excluir um diretório da criação dependerão do seu sistema de criação. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". - -Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o código em diretórios específicos. Você deverá excluir diretórios nas suas etapas de criação e usar as palavras-chave `paths-ignore` e `caminhos` para [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) no seu arquivo de fluxo de trabalho. - -### Exemplo de arquivo de configuração - -{% data reusables.code-scanning.example-configuration-files %} - -## Configurar o {% data variables.product.prodname_code_scanning %} para linguagens compiladas - -{% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} - -{% data reusables.code-scanning.autobuild-add-build-steps %} Para obter mais informações sobre como configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para linguagens compiladas, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)". - -## {% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}. - -Você pode exibir análise de código de uma ferramenta de terceiros em {% data variables.product.prodname_dotcom %}, adicionando a ação de `upload-sarif` ao seu fluxo de trabalho. Você pode fazer o upload de dados de análise de código com a ação `upload-sarif`. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)". diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md deleted file mode 100644 index b336aaa485..0000000000 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Analisar automaticamente seu código com relação a vulnerabilidades e erros -shortTitle: Fazer a varredura de código automaticamente -intro: 'Você pode encontrar vulnerabilidades e erros no código do seu projeto no {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors - - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Advanced Security - - Code scanning -children: - - /about-code-scanning - - /triaging-code-scanning-alerts-in-pull-requests - - /setting-up-code-scanning-for-a-repository - - /managing-code-scanning-alerts-for-your-repository - - /tracking-code-scanning-alerts-in-issues-using-task-lists - - /configuring-code-scanning - - /about-code-scanning-with-codeql - - /configuring-the-codeql-workflow-for-compiled-languages - - /troubleshooting-the-codeql-workflow - - /running-codeql-code-scanning-in-a-container - - /viewing-code-scanning-logs ---- - - diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md deleted file mode 100644 index f10b2e28c8..0000000000 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -title: Gerenciar alertas de verificação de código para o seu repositório -shortTitle: Gerenciar alertas -intro: 'Da visão de segurança, você pode visualizar, corrigir, ignorar ou excluir alertas de potenciais vulnerabilidades ou erros no código do seu projeto.' -product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /github/managing-security-vulnerabilities/managing-alerts-from-automated-code-scanning - - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning - - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository - - /code-security/secure-coding/managing-code-scanning-alerts-for-your-repository - - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository -type: how_to -topics: - - Advanced Security - - Code scanning - - Alerts - - Repositories ---- - - - -{% data reusables.code-scanning.beta %} - -## Sobre os alertas de {% data variables.product.prodname_code_scanning %} - -Você pode configurar {% data variables.product.prodname_code_scanning %} para verificar o código em um repositório usando a análise-padrão de {% data variables.product.prodname_codeql %}, uma análise de terceiros ou vários tipos de análise. Quando a análise for concluída, os alertas resultantes serão exibidos lado a lado na visualização de segurança do repositório. Os resultados de ferramentas de terceiros ou de consultas personalizadas podem não incluir todas as propriedades que você vê para alertas detectados pela análise-padrão {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". - -Por padrão, {% data variables.product.prodname_code_scanning %} analisa seu código periodicamente no branch-padrão e durante os pull requests. Para obter informações sobre o gerenciamento de alertas em um pull request, consulte "[Triar aletras de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". - -{% data reusables.code-scanning.upload-sarif-alert-limit %} - -## Sobre detalhes de alertas - -Cada alerta destaca um problema com o código e o nome da ferramenta que o identificou. Você pode ver a linha de código que acionou o alerta, bem como as propriedades do alerta, como, por exemplo, a gravidade{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, gravidade da segurança,{% endif %} e a natureza do problema. Os alertas também informam quando o problema foi introduzido pela primeira vez. Para os alertas identificados pela análise do {% data variables.product.prodname_codeql %} , você também verá informações sobre como corrigir o problema. - -![Exemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) - -Se você configurar o {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql %}, isso também poderá detectar problemas no fluxo de dados no seu código. A análise do fluxo de dados encontra potenciais problemas de segurança no código, tais como: usar dados de forma insegura, passar argumentos perigosos para funções e vazar informações confidenciais. - -Quando {% data variables.product.prodname_code_scanning %} relata alertas de fluxo de dados, {% data variables.product.prodname_dotcom %} mostra como os dados se movem através do código. {% data variables.product.prodname_code_scanning_capc %} permite que você identifique as áreas do seu código que vazam informações confidenciais que poderia ser o ponto de entrada para ataques de usuários maliciosos. - -### Sobre os níveis de gravidade - -Níveis de gravidade do alerta podem ser `Error`, `Warning` ou `Note`. - -Por padrão, qualquer resultado de digitalização de código com uma gravidade de `error` irá gerar uma falha de verificação. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}Você pode especificar o nível de gravidade no qual os pull requests que habilitam alertas de verificação de código devem falhar. Para obter mais informações, consulte[Definir as gravidades causadoras da falha de verificação de pull request](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -### Sobre níveis de gravidade de segurança - -{% data variables.product.prodname_code_scanning_capc %} exibe níveis de gravidade de segurança para alertas gerados por consultas de segurança. Níveis de severidade de segurança podem ser `graves`, `altos`, `médios` ou `baixos`. - -Para calcular a gravidade da segurança de um alerta, usamos dados de Pontuação do Sistema de Vulnerabilidade Comum (CVSS). O CVSS é uma estrutura aberta para comunicar as características e gravidade das vulnerabilidades de software, e é comumente usado por outros produtos de segurança para pontuar alertas. Para obter mais informações sobre como os níveis de gravidade são calculados, consulte [o post do blogue](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). - -Por padrão, qualquer resultado de verificação de código com uma gravidade de segurança de `Grave` ou `Alta` irá causar uma falha de verificação. Você pode especificar qual nível de segurança para os resultados da digitalização do código deve causar uma falha de verificação. Para obter mais informações, consulte[Definir as gravidades causadoras da falha de verificação de pull request](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} - -### Sobre etiquetas para alertas não encontrados no código do aplicativo - -{% data variables.product.product_name %} atribui uma etiqueta de categoria para alertas que não são encontrados no código do aplicativo. A etiqueta está relacionado à localização do alerta. - -- **Gerado**: Código gerado pelo processo de compilação -- **Teste**: Código de teste -- **Biblioteca**: Biblioteca ou código de terceiros -- **Documentação**: Documentação - -{% data variables.product.prodname_code_scanning_capc %} categoriza arquivos por caminho do arquivo. Você não pode categorizar manualmente os arquivos de origem. - -Aqui está um exemplo da lista de alerta de {% data variables.product.prodname_code_scanning %} de um alerta marcado como ocorrendo no código da biblioteca. - -![Código digitalizando o alerta de biblioteca na lista](/assets/images/help/repository/code-scanning-library-alert-index.png) - -Na página de alerta, você pode ver que o caminho do arquivo é marcado como código da biblioteca (etiqueta `Biblioteca`). - -![Código digitalizando as informações do alerta de biblioteca](/assets/images/help/repository/code-scanning-library-alert-show.png) - -## Visualizar os alertas de um repositório - -Qualquer pessoa com permissão de leitura para um repositório pode ver anotações de {% data variables.product.prodname_code_scanning %} em pull requests. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". - -Você precisa de permissão de gravação para visualizar um resumo de todos os alertas para um repositório na aba **Segurança**. - -Por padrão, a página de verificação de código de alertas é filtrada para mostrar alertas apenas para o branch padrão do repositório. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -1. Opcionalmente, use a caixa de pesquisa de texto livre ou os menus suspensos para filtrar alertas. Por exemplo, você pode filtrar pela ferramenta usada para identificar alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} -{% data reusables.code-scanning.explore-alert %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Resumo dos alertas](/assets/images/help/repository/code-scanning-click-alert.png) -{% else %} - ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) -{% endif %} -1. Opcionalmente, se o alerta destacar um problema com o fluxo de dados, clique em **Mostrar caminhos** para exibir o caminho da fonte de dados até o destino onde é usado. ![O link "Exibir caminhos" em um alerta](/assets/images/help/repository/code-scanning-show-paths.png) -1. Alertas da análise de {% data variables.product.prodname_codeql %} incluem uma descrição do problema. Clique em **Mostrar mais** para obter orientação sobre como corrigir seu código. ![Detalhes para um alerta](/assets/images/help/repository/code-scanning-alert-details.png) - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -{% note %} - -**Observação:** Para análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}, você pode ver informações sobre a última execução em um cabeçalho na parte superior da lista de alertas de {% data variables.product.prodname_code_scanning %} para o repositório. - -Por exemplo, você pode ver quando o último scanner foi executada, o número de linhas de código analisadas em comparação com o número total de linhas de código no seu repositório, e o número total de alertas gerados. ![Banner de interface do usuário](/assets/images/help/repository/code-scanning-ui-banner.png) - -{% endnote %} -{% endif %} - -## Filtrando alertas de {% data variables.product.prodname_code_scanning %} - -Você pode filtrar os alertas exibidos no modo de exibição de alertas de {% data variables.product.prodname_code_scanning %}. Isso é útil caso haja muitos alertas pois você pode se concentrar em um determinado tipo de alerta. Existem alguns filtros predefinidos e uma série de palavras-chave que você pode usar para refinar a lista de alertas exibidos. - -- Para usar um filtro predefinido, clique **Filtros** ou em um filtro exibido no cabeçalho da lista de alertas e escolha um filtro na lista suspensa. - {% ifversion fpt or ghes > 3.0 or ghec %}![Filtros predefinidos](/assets/images/help/repository/code-scanning-predefined-filters.png) - {% else %}![Predefined filters](/assets/images/enterprise/3.0/code-scanning-predefined-filters.png){% endif %} -- Para usar uma palavra-chave, digite diretamente na caixa de texto dos filtros ou: - 1. Clique na caixa de filtros para exibir uma lista de todas as palavras-chave de filtro disponíveis. - 2. Clique na palavra-chave que deseja usar e, em seguida, selecione um valor na lista suspensa. ![Lista de filtros de palavra-chave](/assets/images/help/repository/code-scanning-filter-keywords.png) - -O benefício de usar filtros de palavra-chave é que apenas os valores com resultados são exibidos nas listas suspensas. Isso facilita evitar filtros de configuração que não encontram resultados. - -Se você inserir vários filtros, a visualização mostrará alertas que correspondem a _todos_ esses filtros. Por exemplo, `is:closed severity:high branch:main` só exibirá alertas de alta gravidade fechados e que estão presentes no branch `principal`. A exceção são os filtros relacionados a refs (`ref`, `branch` e `pr`): `is:open branch:main branch:next` irá mostrar alertas abertos do branch `principal` do `próximo` branch. - -### Restringir resultados apenas ao código do aplicativo - -Você pode usar o filtro "Apenas alertas no código do aplicativo" ou a palavra-chave `autofilter:true` e valor para restringir os resultados de alertas no código do aplicativo. Consulte "[Sobre etiquetas para alertas que não estão no código de aplicativos](#about-labels-for-alerts-that-are-not-found-in-application-code)" acima para mais informações sobre os tipos de código que não são código do aplicativo. - -{% ifversion fpt or ghes > 3.1 or ghec %} - -## Pesquisando alertas de {% data variables.product.prodname_code_scanning %} - -Você pode pesquisar na lista de alertas. Isso é útil se houver um grande número de alertas no seu repositório, ou, por exemplo, se você não souber o nome exato de um alerta. {% data variables.product.product_name %} realiza a pesquisa de texto livre: -- O nome do alerta -- A descrição do alerta -- Os detalhes do alerta (isso também inclui as informações ocultas da visualização por padrão na seção ocultável **Mostrar mais**) - - ![Informações de alerta usadas em pesquisas](/assets/images/help/repository/code-scanning-free-text-search-areas.png) - -| Pesquisa compatível | Exemplo de sintaxe | Resultados | -| -------------------------------------------------------- | ------------------ | ----------------------------------------------------------------------- | -| Pesquisa de uma palavra | `injeção` | Retorna todos os alertas que contêm a palavra `injeção` | -| Pesquisa de múltiplas palavras | `injeção sql` | Retorna todos os alertas que contêm `sql` ou `injeção` | -| Pesquisa de correspondência exata
    (use aspas duplas) | `"injeção sql"` | Retorna todos os alertas que contém a frase exata `injection sql` | -| OU pesquisa | `sql OU injeção` | Retorna todos os alertas que contêm `sql` ou `injeção` | -| Pesquisa E | `sql E injeção` | Retorna todos os alertas que contêm ambas as palavras `sql` e `injeção` | - -{% tip %} - -**Dicas:** -- A busca múltipla de palavras é equivalente a uma busca OU. -- A busca E retornará resultados em que os termos da pesquisa são encontrados _em qualquer lugar_, em qualquer ordem no nome do alerta, descrição ou detalhes. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-code-scanning-alerts %} -1. À direita dos menus suspensos de **Filtros**, digite as palavras-chave a serem pesquisadas na caixa de pesquisa de texto livre. ![A caixa de pesquisa de texto livre](/assets/images/help/repository/code-scanning-search-alerts.png) -2. Pressione retornar. O anúncio do alerta conterá os alertas {% data variables.product.prodname_code_scanning %} alertas abertos correspondentes aos seus critérios de busca. - -{% endif %} - -{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %} -## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues - -{% data reusables.code-scanning.beta-alert-tracking-in-issues %} -{% data reusables.code-scanning.github-issues-integration %} -{% data reusables.code-scanning.alert-tracking-link %} - -{% endif %} - -## Corrigir um alerta - -Qualquer pessoa com permissão de gravação para um repositório pode corrigir um alerta, fazendo o commit de uma correção do código. Se o repositório tiver {% data variables.product.prodname_code_scanning %} agendado para ser executado em pull requests, recomenda-se registrar um pull request com sua correção. Isso ativará a análise de {% data variables.product.prodname_code_scanning %} referente às alterações e irá testar se sua correção não apresenta nenhum problema novo. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" e " "[Testar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". - -Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra alertas e alertas corrigidos que os usuários ignoraram. - -Você pode usar{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, marcar, por sua vez, todos os alertas correspondentes como fechados. - -Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico. - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -![Filtrar alertas por branch](/assets/images/help/repository/code-scanning-branch-filter.png) -{% else %} -![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) -{% endif %} - -## Ignorar ou excluir alertas - -Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você configurou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você configurou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**. - -Ignorar um alerta é uma maneira de fechar um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Você pode ignorar alertas de anotações de {% data variables.product.prodname_code_scanning %} no código ou da lista de resumo dentro na aba **Segurança**. - -Ao descartar um alerta: - -- Ele é ignorado em todos os branches. -- O alerta é removido do número de alertas atuais para o seu projeto. -- O alerta é movido para a lista "Fechado" no resumo dos alertas, onde você pode reabri-lo, se necessário. -- O motivo pelo qual você fechou o alerta foi gravado. -- Da próxima vez que {% data variables.product.prodname_code_scanning %} for executado, o mesmo código não gerará um alerta. - -Ao excluir um alerta: - -- Ele é excluído em todos os branches. -- O alerta é removido do número de alertas atuais para o seu projeto. -- Ele _não é_ adicionado à lista "Fechado" no resumo dos alertas. -- Se o código que gerou o alerta permanecer o mesmo, e a mesma ferramenta {% data variables.product.prodname_code_scanning %} for executada novamente sem qualquer alteração de configuração, o alerta será exibido novamente nos resultados das análises. - -Para ignorar ou excluir alertas: - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-code-scanning-alerts %} -1. Se você tem permissões de administrador para o repositório e deseja excluir alertas para esta ferramenta de {% data variables.product.prodname_code_scanning %}, selecione algumas ou todas as caixas de seleção e clique em **Excluir**. - - ![Excluir alertas](/assets/images/help/repository/code-scanning-delete-alerts.png) - - Opcionalmente, você pode usar{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas correspondentes de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas. - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Filtrar alertas por regra](/assets/images/help/repository/code-scanning-filter-by-rule.png) -{% else %} - ![Filtrar alertas por regra](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) -{% endif %} - -1. Se você deseja ignorar um alerta, é importante explorar primeiro o alerta para que você possa escolher o motivo correto para ignorá-lo. Clique no alerta que você deseja explorar. - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - ![Abrir um alerta da lista de resumo](/assets/images/help/repository/code-scanning-click-alert.png) -{% else %} - ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) -{% endif %} -1. Revise o alerta e clique em **Ignorar** e escolha um motivo para fechar o alerta. ![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) - - {% data reusables.code-scanning.choose-alert-dismissal-reason %} - - {% data reusables.code-scanning.false-positive-fix-codeql %} - -### Ignorar múltiplos alertas de uma vez - -Se um projeto tem vários alertas que você deseja ignorar pelo mesmo motivo, você pode ignorá-los em massa do resumo de alertas. Normalmente, você pode querer filtrar a lista e, em seguida, ignorar todos os alertas correspondentes. Por exemplo, você pode querer ignorar todos os alertas atuais no projeto que foram marcados para uma vulnerabilidade específica de Enumeração de Fraqueza Comum (CWE). - -## Leia mais - -- "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" -- "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" -- "[Sobre a integração com {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)" diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md index 7766f05984..3503af009c 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md @@ -28,54 +28,54 @@ Você também pode criar um novo problema para rastrear um alerta: - Através da API como você normalmente faria e, em seguida, fornecer o link de digitalização de código dentro do texto do problema. Você deve usar a sintaxe da lista de tarefas para criar o relacionamento rastreado: - `- [ ] ` - - For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the "Security" tab of the `octocat-repo` repository in the `octocat-org` organization. + - Por exemplo, se você adiciionar `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` a um problema, este irá rastrear o alerta de digitalização de código que tem um número de identificação 17 na aba "Segurança" do repositório `octocat-repo` na organização `octocat-org`. Você pode usar mais de um problema para rastrear o mesmo alerta de {% data variables.product.prodname_code_scanning %} e os problemas podem pertencer a diferentes repositórios onde o alerta {% data variables.product.prodname_code_scanning %} foi encontrado. -{% data variables.product.product_name %} provides visual cues in different locations of the user interface to indicate when you are tracking {% data variables.product.prodname_code_scanning %} alerts in issues. +{% data variables.product.product_name %} fornece instruções visuais em diferentes locais da interface de usuário para indicar quando você está monitorando alertas de {% data variables.product.prodname_code_scanning %} em problemas. -- The code scanning alerts list page will show which alerts are tracked in issues so that you can view at a glance which alerts still require processing. +- A página da lista de alertas de digitalização de código mostrará quais alertas são rastreados nos problemas para que você possa ver com rapidamente quais alertas ainda precisam de processamento. ![Tracked in pill on code scanning alert page](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png) -- A "tracked in" section will also show in the corresponding alert page. +- Uma seção "rastreado em" também será exibida na página de alerta correspondente. - ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png) + ![A anotação rastreada na página de alerta de digitalização do código](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png) -- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard. +- No problema de rastreado, {% data variables.product.prodname_dotcom %} exibe um ícone do selo de segurança na lista de tarefas e no hovercard. {% note %} - Only users with write permissions to the repository will see the unfurled URL to the alert in the issue, as well as the hovercard. For users with read permissions to the repository, or no permissions at all, the alert will appear as a plain URL. + Somente os usuários com permissões de gravação no repositório verão a URL não desenvolvida para o alerta na issue, bem como o hovercard. Para usuários com permissões de leitura no repositório, ou sem qualquer permissão, o alerta aparecerá como uma URL simples. {% endnote %} - The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change. + A cor do ícone é cinza porque um alerta tem um status de "aberto" ou "fechado" em cada branch. O problema rastreia um alerta para que o alerta não possa ter um único estado aberto/fechado no problema. Se o alerta for fechado em um branch, a cor do ícone não será alterada. - ![Hovercard in tracking issue](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png) + ![Hovercard no problema rastreado](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png) -The status of the tracked alert won't change if you change the checkbox state of the corresponding task list item (checked/unchecked) in the issue. +O status do alerta rastreado não mudará se você alterar o status da caixa de seleção do item da lista de tarefas correspondente (marcado/desmarcado) no problema. -## Creating a tracking issue from a code scanning alert +## Criando um problema de rastreamento a partir de um alerta de digitalização de código {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} {% ifversion fpt or ghes or ghae-next %} {% data reusables.code-scanning.explore-alert %} -1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts). " +1. Opcionalmente, para encontrar o alerta a rastrear, você pode usar a pesquisa de texto livre ou os menus suspensos para filtrar e localizar o alerta. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts). " {% endif %} -1. Towards the top of the page, on the right side, click **Create issue**. ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png) - {% data variables.product.prodname_dotcom %} automatically creates an issue to track the alert and adds the alert as a task list item. - {% data variables.product.prodname_dotcom %} prepopulates the issue: - - The title contains the name of the {% data variables.product.prodname_code_scanning %} alert. - - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert. -2. Optionally, edit the title and the body of the issue. +1. Na parte superior da página, no lado direito, clique em **Criar problema**. ![Crie um problema de rastreamento para o alerta de digitalização de código](/assets/images/help/repository/code-scanning-create-issue-for-alert.png) + {% data variables.product.prodname_dotcom %} cria automaticamente um problema para acompanhar o alerta e adiciona o alerta como um item da lista de tarefas. + {% data variables.product.prodname_dotcom %} preenche o problema: + - O título contém o nome do alerta de {% data variables.product.prodname_code_scanning %}. + - O texto contém o item da lista de tarefas com a URL completa para o alerta de {% data variables.product.prodname_code_scanning %}. +2. Opcionalmente, edite o título e o texto do problema. {% warning %} - **Warning:** You may want to edit the title of the issue as it may expose security information. You can also edit the body of the issue, but do not edit the task list item or the issue will no longer track the alert. + **Aviso:** Você deverá editar o título do problema, pois pode expor informações de segurança. Você também pode editar o texto do problema, mas não edite o item da lista de tarefas ou o problema não irá mais rastrear o alerta. {% endwarning %} - ![New tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-new-tracking-issue.png) -3. Click **Submit new issue**. + ![Novo problema de rastreamento para o alerta de digitalização de código](/assets/images/help/repository/code-scanning-new-tracking-issue.png) +3. Clique em **Enviar novo problema**. diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 3a30bd6dad..7fd2a101be 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -36,6 +36,24 @@ topics: Para produzir a saída de log mais detalhada, você pode habilitar o log de depuração da etapa. Para obter mais informações, consulte "[Habilitar o registro de depuração](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)". +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5601 %} + +## Criando artefatos de depuração de {% data variables.product.prodname_codeql %} + +Você pode obter artefatos para ajudar você a depurar {% data variables.product.prodname_codeql %}, definindo um sinalizador da configuração de depuração. Modifique a etapa `init` do seu arquivo de fluxo de trabalho {% data variables.product.prodname_codeql %} e defina `debug: true`. + +``` +- name: Initialize CodeQL + uses: github/codeql-action/init@v1 + with: + debug: true +``` +Os artefatos de depuração serão carregados para a execução do fluxo de trabalho como um artefato denominado `debug-artifacts`. Os dados contém os registros de {% data variables.product.prodname_codeql %}, banco(s) de dados de {% data variables.product.prodname_codeql %}, e todo(s) o(s) outro(s) arquivo(s) SARIF produzido(s) pelo fluxo de trabalho. + +Estes artefatos ajudarão você a depurar problemas com digitalização de código de {% data variables.product.prodname_codeql %}. Se você entrar em contato com o suporte do GitHub, eles poderão pedir estes dados. + +{% endif %} + ## Ocorreu uma falha durante a criação automática para uma linguagem compilada Se ocorrer uma falha na uma criação automática de código para uma linguagem compilada dentro de seu projeto, tente as seguintes etapas para a solução de problemas. diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md deleted file mode 100644 index 34fecb1068..0000000000 --- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ /dev/null @@ -1,752 +0,0 @@ ---- -title: Suporte SARIF para a varredura de código -shortTitle: Suporte SARIF -intro: 'Para exibir os resultados de uma ferramenta de análise estática de terceiros no seu repositório no {% data variables.product.prodname_dotcom %}, você precisará dos resultados armazenados em um arquivo SARIF que seja compatível com um subconjunto específico do esquema SARIF 2.1.0 JSON para varredura de código. Se você usar o mecanismo de análise estática padrão do {% data variables.product.prodname_codeql %}, os resultados aparecerão automaticamente no seu repositório no {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning - - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning - - /code-security/secure-coding/sarif-support-for-code-scanning - - /code-security/secure-coding/integrating-with-code-scanning/sarif-support-for-code-scanning -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: reference -topics: - - Advanced Security - - Code scanning - - Integration - - SARIF ---- - - - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.deprecation-codeql-runner %} - -## Sobre o suporte SARIF - -SARIF (Formato de Intercâmbio de Resultados de Análise Estática) é um [OASIS Padrão](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) que define um formato do arquivo de saída. O padrão SARIF é usado para simplificar como as ferramentas de análise estáticas compartilham seus resultados. O {% data variables.product.prodname_code_scanning_capc %} é compatível com um subconjunto do esquema SARIF 2.1.0 JSON. - -Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)". Para obter mais informações sobre o esquema SARIF 2.1.0 JSON, consulte [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json). - -Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" ou "[Executar {% data variables.product.prodname_codeql_runner %} no seu sistema CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)". - -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -Se você estiver usando o {% data variables.product.prodname_codeql_cli %}, especifique a versão do SARIF a ser usada. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -Você pode fazer upload de vários arquivos SARIF para a mesma ferramenta e commit, e analisar cada arquivo usando {% data variables.product.prodname_code_scanning %}. Você pode indicar uma "categoria" para cada análise, especificando um `runAutomationDetails.id` em cada arquivo. Apenas arquivos SARIF com a mesma categoria irão sobrescrever um ao outro. Para obter mais informações sobre esta propriedade, consulte o objeto [`runAutomationDetails`](#runautomationdetails-object) abaixo. -{% endif %} - -{% data variables.product.prodname_dotcom %} usa propriedades no arquivo SARIF para exibir alertas. Por exemplo, `shortDescription` e `fullDescription` aparecem na parte superior de um alerta de {% data variables.product.prodname_code_scanning %}. O `local` permite que {% data variables.product.prodname_dotcom %} mostre anotações no seu arquivo de código. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". - -Se você for novo no SARIF e quiser saber mais, consulte o repositório da Microsoft de[`Tutoriais do SARIF`](https://github.com/microsoft/sarif-tutorials). - -## Impedir alertas duplicados usando impressões digitais - -Cada vez que um fluxo de trabalho do {% data variables.product.prodname_actions %} executa uma nova varredura de código, os resultados de cada execução são processados e os alertas são adicionados ao repositório. Para evitar alertas duplicados para o mesmo problema, {% data variables.product.prodname_code_scanning %} usa impressões digitais para corresponder aos resultados em várias execuções, para que apareçam apenas uma vez na última execução do ramo selecionado. Isto torna possível combinar alertas com a linha de código correta quando os arquivos são editados. - -O {% data variables.product.prodname_dotcom %} usa a propriedade `partialFingerprints` no padrão OASIS para detectar quando dois resultados são idênticos logicamente. Para obter mais informações, consulte a entrada "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" na documentação do OASIS. - -OS arquivos do SARIF criados pelo {% data variables.product.prodname_codeql_workflow %} ou usando {% data variables.product.prodname_codeql_runner %} incluem dados de impressão digital. Se você enviar um arquivo SARIF usando a ação `upload-sarif` e estes dados estiverem faltando, {% data variables.product.prodname_dotcom %} tenta preencher o campo `partialFingerprints` a partir dos arquivos de origem. Para obter mais informações sobre o upload de resultados, consulte "[Fazer o upload de um arquivo SARIF para o {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)". - -Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. Para evitar ver alertas duplicados, você deve calcular dados de impressão digital e preencher a propriedade `partialFingerprints` antes de enviar o arquivo SARIF. Você pode encontrar o script que a ação `upload-sarif` usa como um ponto inicial útil: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. Para obter mais informações sobre a API, consulte "[Fazer o upload de uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)". - -## Validar seu arquivo SARIF - - - -Você pode marcar um arquivo SARIF compatível com {% data variables.product.prodname_code_scanning %} testando-o com as regras de ingestão de {% data variables.product.prodname_dotcom %}. Para obter mais informações, acesse o [validador do Microsoft SARIF](https://sarifweb.azurewebsites.net/). - -{% data reusables.code-scanning.upload-sarif-alert-limit %} - -## Propriedades compatíveis do arquivo de saída SARIF - -Se você usar um mecanismo de análise de código diferente de {% data variables.product.prodname_codeql %}, você poderá revisar as propriedades do SARIF compatíveis para otimizar como seus resultados de análise aparecerão em {% data variables.product.prodname_dotcom %}. - -É possível fazer o upload de qualquer arquivo de saída SARIF 2.1.0 válido, no entanto, {% data variables.product.prodname_code_scanning %} usará apenas as seguintes propriedades compatíveis. - -### Objeto `sarifLog` - -| Nome | Descrição | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `$schema` | **Obrigatório.** A URI do esquema SARIF JSON para a versão 2.1.0. Por exemplo, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. | -| `versão` | **Obrigatório.** {% data variables.product.prodname_code_scanning_capc %} é compatível apenas com a versão `2.1.0` do SARIF. | -| `runs[]` | **Obrigatório.** Um arquivo SARIF contém um array de uma ou mais execuções. Cada execução representa uma execução única de uma ferramenta de análise. Para obter mais informações sobre uma `execução`, consulte o objeto [`executar`](#run-object). | - -### Objeto `run` - -O {% data variables.product.prodname_code_scanning_capc %} usa o objeto `executar` para filtrar resultados por ferramenta e fornecer informações sobre a fonte de um resultado. O objeto `executar` contém o objeto `tool.driver` do componente da ferramenta, que contém informações sobre a ferramenta que gerou os resultados. Cada `execução` pode ter resultados apenas para uma ferramenta de análise. - -| Nome | Descrição | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `tool.driver.name` | **Obrigatório.** O nome da ferramenta de análise. {% data variables.product.prodname_code_scanning_capc %} exibe o nome em {% data variables.product.prodname_dotcom %} para permitir que você filtre resultados por ferramenta. | -| `tool.driver.version` | **Opcional.** A versão da ferramenta de análise. O {% data variables.product.prodname_code_scanning_capc %} usa o número da versão para fazer o monitoramento quando os resultados podem ter mudado devido a uma mudança na versão da ferramenta em vez de uma mudança no código que está sendo analisado. Se o arquivo SARIF incluir o campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} não usará `versão`. | -| `tool.driver.semanticVersion` | **Opcional.** A versão da ferramenta de análise especificada pelo formato Semantic Versioning 2.0. O {% data variables.product.prodname_code_scanning_capc %} usa o número da versão para fazer o monitoramento quando os resultados podem ter mudado devido a uma mudança na versão da ferramenta em vez de uma mudança no código que está sendo analisado. Se o arquivo SARIF incluir o campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} não usará `versão`. Para obter mais informações, consulte "[Semantic Versioning 2.0.0](https://semver.org/)" na documentação de Semantic Versioning. | -| `tool.driver.rules[]` | **Obrigatório.** Um array de objetos `reportingDescriptor` que representam regras. A ferramenta de análise usa regras para encontrar problemas no código que está sendo analisado. Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). | -| `results[]` | **Obrigatório.** Os resultados da ferramenta de análise. {% data variables.product.prodname_code_scanning_capc %} exibe os resultados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte o objeto [`resultado`](#result-object). | - -### Objeto `reportingDescriptor` - -| Nome | Descrição | -| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | **Obrigatório.** Um identificador exclusivo para a regra. O id `` é referenciado a partir de outras partes do arquivo SARIF e pode ser usado por {% data variables.product.prodname_code_scanning %} para exibir URLs em {% data variables.product.prodname_dotcom %}. | -| `name` | **Opcional.** O nome da regra. {% data variables.product.prodname_code_scanning_capc %} exibe o nome para permitir que os resultados sejam filtrados pela regra em {% data variables.product.prodname_dotcom %}. | -| `shortDescription.text` | **Obrigatório.** Uma descrição concisa da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a breve descrição em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. | -| `fullDescription.text` | **Obrigatório.** Uma descrição da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a descrição completa em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. O número máximo de caracteres é 1000. | -| `defaultConfiguration.level` | **Opcional.** Gravidade-padrão da regra. {% data variables.product.prodname_code_scanning_capc %} usa níveis de gravidade para ajudar você a entender quão crítico é o resultado para uma determinada regra. Esse valor pode ser substituído pelo atributo de `nível` no objeto `resultado`. Para obter mais informações, consulte o objeto [`resultado`](#result-object). Padrão: `alerta`. | -| `help.text` | **Obrigatório.** Documentação para a regra usando o formato de texto. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. | -| `help.markdown` | **Recomendado.** Documentação para a regra que o formato Markdown. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. Quando `help.markdown` estiver disponível, será exibido em vez de `help.text`. | -| `properties.tags[]` | **Opcional.** Um array de strings. {% data variables.product.prodname_code_scanning_capc %} usa `tags` para permitir que você filtre resultados em {% data variables.product.prodname_dotcom %}. Por exemplo, é possível filtrar para todos os resultados que têm a tag `segurança`. | -| `properties.precision` | **Recomendado.** Uma string que indica quantas vezes os resultados indicados por esta regra são verdadeiros. Por exemplo, se uma regra tem uma alta taxa conhecida de falsos-positivos, a precisão deve ser `baixa`. {% data variables.product.prodname_code_scanning_capc %} ordena os resultados por precisão em {% data variables.product.prodname_dotcom %} de modo que os resultados com o mais alto `nível` e a mais alta `precisão` sejam exibidos primeiro. Pode ser: `very-high`, `high`, `medium` ou `low`. |{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -| `properties.problem.severity` | **Recomendado.** Uma string indica o nível de gravidade de qualquer alerta gerado por uma consulta que não é segurança. Isso, com a propriedade `properties.precision`, determina se os resultados são exibidos por padrão em {% data variables.product.prodname_dotcom %} para que os resultados com `problem.severity` e `precision` mais altos sejam exibidos primeiro. Pode ser um dos valores a seguir `erro`, `aviso` ou `recomendação`. | -| `properties.security-severity` | **Recomendado.** A pontuação indica o nível de gravidade, entre 0,0 e 10, para consultas de segurança (`@tags` inclui `segurança`). Isso, com a propriedade `properties.precision`, determina se os resultados são exibidos por padrão em {% data variables.product.prodname_dotcom %} para que os resultados com `security-severity` e `precision` mais altos sejam exibidos primeiro. {% data variables.product.prodname_code_scanning_capc %} traduz pontuações numéricas da seguinte forma: acima de 9.0 é `crítico`, de 7.0 a 8. é `alto`, de 4.0 a 6. é `médio` e inferio a 3,9 é `baixo`. {% endif %} - -### Objeto `resultado` - -{% data reusables.code-scanning.upload-sarif-alert-limit %} - -| Nome | Descrição | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ruleId` | **Opcional.** O identificador exclusivo da regra (`reportingDescriptor.id`). Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} usa o identificador da regra para filtrar os resultados por regra em {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Opcional.** O índice da regra associada (objeto `reportingDescriptor`) no array `regras` no componente da ferramenta. Para obter mais informações, consulte o objeto [`executar`](#run-object). | -| `rule` | **Opcional.** Uma referência usada para localizar a regra (descritor de relatório) para este resultado. Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). | -| `level` | **Opcional.** A gravidade do resultado. Esse nível sobrepõe a severidade-padrão definida pela regra. {% data variables.product.prodname_code_scanning_capc %} usa o nível para filtrar resultados por gravidade em {% data variables.product.prodname_dotcom %}. | -| `message.text` | **Obrigatório.** Uma mensagem que descreve o resultado. {% data variables.product.prodname_code_scanning_capc %} exibe o texto da mensagem como o título do resultado. Apenas a primeira frase da mensagem será exibida quando o espaço visível for limitado. | -| `locations[]` | **Obrigatório.** O conjunto de locais onde o resultado foi detectado até o máximo de 10. Só um local deve ser incluído, a não ser que o problema só possa ser corrigido fazendo uma alteração em cada local especificado. **Observação:** Pelo menos um local é necessário para {% data variables.product.prodname_code_scanning %} apresentar um resultado. {% data variables.product.prodname_code_scanning_capc %} usará essa propriedade para decidir qual arquivo fazer anotações com o resultado. Apenas o primeiro valor desse array é usado. Todos os outros valores são ignorados. | -| `partialFingerprints` | **Obrigatório.** Um conjunto de strings usado para rastrear a identidade única do resultado. {% data variables.product.prodname_code_scanning_capc %} usa `partialFingerprints` para identificar com precisão quais resultados são os mesmos em todos os commits e branches. O {% data variables.product.prodname_code_scanning_capc %} tentará usar `partialFingerprints`, se existirem. Se você estiver fazendo upload de arquivos SARIF de terceiros com `upload-action`, a ação irá criar `partialFingerprints` para você quando não estiverem incluídos no arquivo SARIF. Para obter mais informações, consulte "[Prevenir alertas duplicados usando impressões digitais](#preventing-duplicate-alerts-using-fingerprints)". **Observação:** {% data variables.product.prodname_code_scanning_capc %} usa apenas `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Uma array de objetos `local` para um objeto `threadFlow`, que descreve o progresso de um programa por meio de um thread de execução. Um objeto `codeFlow` descreve um padrão de execução de código usado para detectar um resultado. Se forem fornecidos fluxos de código, {% data variables.product.prodname_code_scanning %} irá expandir os fluxos de código em {% data variables.product.prodname_dotcom %} para o resultado relevante. Para obter mais informações, consulte o objeto [`local`](#location-object). | -| `relatedLocations[]` | Um conjunto de locais relevantes para este resultado. {% data variables.product.prodname_code_scanning_capc %} irá vincular a locais relacionados quando forem incorporados à mensagem do resultado. Para obter mais informações, consulte o objeto [`local`](#location-object). | - -### Objeto `local` - -Um local dentro de um artefato de programação, como, por exemplo, um arquivo no repositório ou um arquivo gerado durante uma criação. - -| Nome | Descrição | -| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -| `location.id` | **Opcional.** Um identificador exclusivo que distingue este local de todos os outros locais dentro de um único objeto de resultado. | -| `location.physicalLocation` | **Obrigatório.** Identifica o artefato e a região. Para obter mais informações, consulte [`physicalLocation`](#physicallocation-object). | -| `location.message.text` | **Opcional.** Uma mensagem relevante para o local. | - -### Objeto `physicalLocation` - -| Nome | Descrição | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `artifactLocation.uri` | **Obrigatório.** Um URI indicando o local de um artefato, geralmente um arquivo no repositório ou gerado durante uma criação. Se o URI for relativo, ele deverá ser relativo à raiz do repositório do {% data variables.product.prodname_dotcom %} que está sendo analisado. Por exemplo, main.js ou src/script.js são relativos à raiz do repositório. Se o URI for absoluto, o {% data variables.product.prodname_code_scanning %} poderá usar o URI para fazer checkout do artefato e corresponder os arquivos no repositório. Por exemplo, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. | -| `region.startLine` | **Obrigatório.** O número da linha do primeiro caractere na região. | -| `region.startColumn` | **Obrigatório.** O número da coluna do primeiro caractere na região. | -| `region.endLine` | **Requerido.** O número da linha do último caractere na região. | -| `region.endColumn` | **Obrigatório.** O número da coluna do caractere após o final da região. | - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -### objeto `ExecutarDetalhes` - -O objeto `runAutomationDetails` contém informações que especificam a identidade de uma execução. - -{% note %} - -**Observação:** `runAutomationDetails` é um objeto do SARIF v2.1.0. Se você estiver usando {% data variables.product.prodname_codeql_cli %}, você poderá especificar a versão do SARIF a ser usada. O objeto equivalente ao `runAutomationDetails` é `.automationId` para o SARIF v1 e `.automationLogicalId` para o SARIF v2. - -{% endnote %} - -| Nome | Descrição | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `id` | **Opcional.** Uma sequência de caracteres que identifica a categoria da análise e o ID de execução. Use se você quiser fazer upload de vários arquivos SARIF para a mesma ferramenta e commit, mas executado em diferentes idiomas ou diferentes partes do código. | - -O uso do objeto `runAutomationDetails` é opcional. - -O campo `id` pode incluir uma categoria de análise e um ID de execução. Não usamos a parte do ID de execução do campo `id`, mas o armazenamos. - -Use a categoria para distinguir entre múltiplas análises para a mesma ferramenta ou commit, mas executada em diferentes linguagens ou partes diferentes do código. Use o ID de execução para identificar a execução específica da análise, como a data em que a análise foi executada. - -`id` é interpretado como `category/run-id`. Se o `id` não cntiver uma barra (`/`), toda a string será `run_id` e a `categoria` ficará vazia. Caso contrário, `categoria` será tudo na string até a última barra, e `run_id` será tudo que vem depois. - -| `id` | categoria | `run_id` | -| ---------------------------- | ----------------- | --------------------- | -| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01 | -| my-analysis/tool1/ | my-analysis/tool1 | _sem `run-id`_ | -| my-analysis for tool1 | _sem categoria_ | my-analysis for tool1 | - -- A execução com um `id` de "my-analysis/tool1/2021-02-01" pertence à categoria "my-analysis/tool1". Provavelmente, esta é a execução de 2 de fevereiro de 2021. -- A execução com um `id` de "my-analysis/tool1/" pertence à categoria "my-analysis/tool1", mas não é distinta das outras execuções nessa categoria. -- A execução cujo `id` é "my-analysis for tool1" tem um identificador único, mas não pode ser inferido para pertencer a qualquer categoria. - -Para obter mais informações sobre o objeto `runAutomationDetails` e o campo `id`, consulte o [objeto runAutomationDetails](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) na documentação do OASIS. - -Observe que o resto dos campos compatíveis são ignorados. - -{% endif %} - -## Exemplos de arquivos de saída SARIF - -Estes exemplos de arquivos de saída SARIF mostram as propriedades compatíveis e os valores de exemplo. - -### Exemplo com as propriedades mínimas necessárias - -Este arquivo de saída SARIF tem exemplo de valores para mostrar as propriedades mínimas necessárias para que os resultados de {% data variables.product.prodname_code_scanning %} funcionem conforme esperado. Se você remover qualquer propriedade ou não incluir valores, esses dados não serão exibidos corretamente e não serão sincronizados em {% data variables.product.prodname_dotcom %}. - -```json -{ - "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", - "version": "2.1.0", - "runs": [ - { - "tool": { - "driver": { - "name": "Tool Name", - "rules": [ - { - "id": "R01" - ... - "properties" : { - "id" : "java/unsafe-deserialization", - "kind" : "path-problem", - "name" : "...", - "problem.severity" : "error", - "security-severity" : "9.8", - } - ] - } - }, - "results": [ - { - "ruleId": "R01", - "message": { - "text": "Result text. Este resultado não tem nenhuma regra associada." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "fileURI" - }, - "region": { - "startLine": 2, - "startColumn": 7, - "endColumn": 10 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "39fa2ee980eb94b0:1" - } - } - ] - } - ] -} -``` - -### Exemplo que mostra todas as propriedades compatíveis como SARIF - -Este arquivo de saída SARIF tem valores de exemplo para mostrar todas as propriedades do SARIF compatíveis com {% data variables.product.prodname_code_scanning %}. - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -```json -{ - "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", - "version": "2.1.0", - "runs": [ - { - "tool": { - "driver": { - "name": "Tool Name", - "semanticVersion": "2.0.0", - "rules": [ - { - "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad", - "name": "js/unused-local-variable", - "shortDescription": { - "text": "Unused variable, import, function or class" - }, - "fullDescription": { - "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully." - }, - "defaultConfiguration": { - "level": "note" - }, - "properties": { - "tags": [ - "maintainability" - ], - "precision": "very-high" - } - }, - { - "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0", - "name": "js/inconsistent-use-of-new", - "shortDescription": { - "text": "Inconsistent use of 'new'" - }, - "fullDescription": { - "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'." - }, - "properties": { - "tags": [ - "reliability", - "correctness", - "language-features" - ], - "precision": "very-high" - } - }, - { - "id": "R01" - } - ] - } - }, - "automationDetails": { - "id": "my-category/" - }, - "results": [ - { - "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad", - "ruleIndex": 0, - "message": { - "text": "Unused variable foo." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "main.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 2, - "startColumn": 7, - "endColumn": 10 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "39fa2ee980eb94b0:1", - "primaryLocationStartColumnFingerprint": "4" - } - }, - { - "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0", - "ruleIndex": 1, - "message": { - "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "src/promises.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 2 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "5061c3315a741b7d:1", - "primaryLocationStartColumnFingerprint": "7" - }, - "relatedLocations": [ - { - "id": 1, - "physicalLocation": { - "artifactLocation": { - "uri": "src/ParseObject.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 2281, - "startColumn": 33, - "endColumn": 55 - } - }, - "message": { - "text": "here" - } - }, - { - "id": 2, - "physicalLocation": { - "artifactLocation": { - "uri": "src/LiveQueryClient.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 166 - } - }, - "message": { - "text": "here" - } - } - ] - }, - { - "ruleId": "R01", - "message": { - "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies." - }, - "level": "error", - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 54, - "startColumn": 10, - "endLine": 55, - "endColumn": 25 - } - } - } - ], - "relatedLocations": [ - { - "id": 1, - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif" - }, - "region": { - "startLine": 81, - "startColumn": 10, - "endColumn": 18 - } - }, - "message": { - "text": "here" - } - }, - { - "id": 2, - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif" - }, - "region": { - "startLine": 82, - "startColumn": 10, - "endColumn": 21 - } - }, - "message": { - "text": "here" - } - } - ], - "codeFlows": [ - { - "threadFlows": [ - { - "locations": [ - { - "location": { - "physicalLocation": { - "region": { - "startLine": 11, - "endLine": 29, - "startColumn": 10, - "endColumn": 18 - }, - "artifactLocation": { - "uriBaseId": "%SRCROOT%", - "uri": "full.sarif" - } - }, - "message": { - "text": "Rule has index 0" - } - } - }, - { - "location": { - "physicalLocation": { - "region": { - "endColumn": 47, - "startColumn": 12, - "startLine": 12 - }, - "artifactLocation": { - "uriBaseId": "%SRCROOT%", - "uri": "full.sarif" - } - } - } - } - ] - } - ] - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "ABC:2" - } - } - ], - "columnKind": "utf16CodeUnits" - } - ] -} -``` -{% else %} -```json -{ - "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", - "version": "2.1.0", - "runs": [ - { - "tool": { - "driver": { - "name": "Tool Name", - "semanticVersion": "2.0.0", - "rules": [ - { - "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad", - "name": "js/unused-local-variable", - "shortDescription": { - "text": "Unused variable, import, function or class" - }, - "fullDescription": { - "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully." - }, - "defaultConfiguration": { - "level": "note" - }, - "properties": { - "tags": [ - "maintainability" - ], - "precision": "very-high" - } - }, - { - "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0", - "name": "js/inconsistent-use-of-new", - "shortDescription": { - "text": "Inconsistent use of 'new'" - }, - "fullDescription": { - "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'." - }, - "properties": { - "tags": [ - "reliability", - "correctness", - "language-features" - ], - "precision": "very-high" - } - }, - { - "id": "R01" - } - ] - } - }, - "results": [ - { - "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad", - "ruleIndex": 0, - "message": { - "text": "Unused variable foo." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "main.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 2, - "startColumn": 7, - "endColumn": 10 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "39fa2ee980eb94b0:1", - "primaryLocationStartColumnFingerprint": "4" - } - }, - { - "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0", - "ruleIndex": 1, - "message": { - "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "src/promises.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 2 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "5061c3315a741b7d:1", - "primaryLocationStartColumnFingerprint": "7" - }, - "relatedLocations": [ - { - "id": 1, - "physicalLocation": { - "artifactLocation": { - "uri": "src/ParseObject.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 2281, - "startColumn": 33, - "endColumn": 55 - } - }, - "message": { - "text": "here" - } - }, - { - "id": 2, - "physicalLocation": { - "artifactLocation": { - "uri": "src/LiveQueryClient.js", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 166 - } - }, - "message": { - "text": "here" - } - } - ] - }, - { - "ruleId": "R01", - "message": { - "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies." - }, - "level": "error", - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif", - "uriBaseId": "%SRCROOT%" - }, - "region": { - "startLine": 54, - "startColumn": 10, - "endLine": 55, - "endColumn": 25 - } - } - } - ], - "relatedLocations": [ - { - "id": 1, - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif" - }, - "region": { - "startLine": 81, - "startColumn": 10, - "endColumn": 18 - } - }, - "message": { - "text": "here" - } - }, - { - "id": 2, - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif" - }, - "region": { - "startLine": 82, - "startColumn": 10, - "endColumn": 21 - } - }, - "message": { - "text": "here" - } - } - ], - "codeFlows": [ - { - "threadFlows": [ - { - "locations": [ - { - "location": { - "physicalLocation": { - "region": { - "startLine": 11, - "endLine": 29, - "startColumn": 10, - "endColumn": 18 - }, - "artifactLocation": { - "uriBaseId": "%SRCROOT%", - "uri": "full.sarif" - } - }, - "message": { - "text": "Rule has index 0" - } - } - }, - { - "location": { - "physicalLocation": { - "region": { - "endColumn": 47, - "startColumn": 12, - "startLine": 12 - }, - "artifactLocation": { - "uriBaseId": "%SRCROOT%", - "uri": "full.sarif" - } - } - } - } - ] - } - ] - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "ABC:2" - } - } - ], - "columnKind": "utf16CodeUnits" - } - ] -} -``` -{% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md deleted file mode 100644 index 96f46df0ef..0000000000 --- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Fazer o upload de arquivo SARIF para o GitHub -shortTitle: Fazer o upload de um arquivo SARIF -intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}' -permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/managing-security-vulnerabilities/uploading-a-code-scanning-analysis-to-github - - /github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github - - /code-security/secure-coding/uploading-a-sarif-file-to-github - - /code-security/secure-coding/integrating-with-code-scanning/uploading-a-sarif-file-to-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: how_to -topics: - - Advanced Security - - Code scanning - - Integration - - Actions - - Repositories - - CI - - SARIF ---- - - - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} -{% data reusables.code-scanning.deprecation-codeql-runner %} - -## Sobre os uploads de arquivos SARIF para {% data variables.product.prodname_code_scanning %} - -O {% data variables.product.prodname_dotcom %} cria alertas de {% data variables.product.prodname_code_scanning %} em um repositório usando informações de arquivos de Formato Intercâmbio de Resultados de Análise Estática (SARIF). Os arquivos SARIF podem ser enviados para um repositório usando a API ou {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". - -Você pode gerar arquivos SARIF usando muitas ferramentas de teste de segurança de análise estática, incluindo {% data variables.product.prodname_codeql %}. Para fazer o upload dos resultados das ferramentas de terceiros, você deve usar o formato Intercâmbio de Resultados de Análise Estática (SARIF) 2.1.0. Para obter mais informações, consulte "[Suporte SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)". - -Você pode enviar os resultados usando {% data variables.product.prodname_actions %}, a API de {% data variables.product.prodname_code_scanning %} {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}ou {% data variables.product.prodname_codeql_runner %}. O melhor método de upload dependerá de como você gera o arquivo SARIF. Por exemplo, se você usar: - -- {% data variables.product.prodname_actions %} para executar a ação {% data variables.product.prodname_codeql %}, não haverá nenhuma ação adicional necessária. A ação {% data variables.product.prodname_codeql %} faz o upload do arquivo SARIF automaticamente quando ele conclui a análise. -- O arquivo SARIF pode ser gerado a partir de uma ferramenta de análise compatível com o SARIF, que você executa no mesmo fluxo de trabalho de {% data variables.product.prodname_actions %} usado para fazer o upload do arquivo. {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} - - O {% data variables.product.prodname_codeql_cli %} para executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI, você pode usar a CLI para fazer o upload de resultados para {% data variables.product.prodname_dotcom %} (para mais informações, consulte "[Instalar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% endif %} -- {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. Se você bloquear o upload automático, quando você estiver pronto para fazer o upload dos resultados, você poderá usar o comando `enviar` (para mais informações, ver "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"). -- Uma ferramenta que gera resultados como um artefato fora do seu repositório, você pode usar a API de {% data variables.product.prodname_code_scanning %} para fazer o upload do arquivo (para mais informações, consulte "[Enviar uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"). - -{% data reusables.code-scanning.not-available %} - -## Fazer o upload uma análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_actions %} - -Para fazer o upload de um arquivo SARIF de terceiros para {% data variables.product.prodname_dotcom %}, você precisará de um fluxo de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". - -O seu fluxo de trabalho precisará usar a ação `upload-sarif`, que tem parâmetros de entrada que você pode usar para configurar o upload. Ele tem parâmetros de entrada que você pode usar para configurar o upload. O parâmetro de entrada principal que você usará é `sarif-file`, que configura o arquivo ou diretório dos arquivos SARIF a serem carregados. O diretório ou caminho do arquivo é relativo à raiz do repositório. Para mais informações, consulte a ação [`upload-sarif`](https://github.com/github/codeql-action/tree/HEAD/upload-sarif). - -A ação `upload-sarif` pode ser configurada para ser executada quando ocorrem o evento `push` e `agendado`. Para obter mais informações sobre eventos do {% data variables.product.prodname_actions %}, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". - -Se o seu arquivo SARIF não incluir `partialFingerprints`, a ação `upload-sarif` calculará o campo `parcialFingerprints` para você e tentará evitar alertas duplicados. O {% data variables.product.prodname_dotcom %} só pode criar `partialFingerprints` quando o repositório contiver o arquivo SARIF e o código-fonte usado na análise estática. Para obter mais informações sobre a prevenção de alertas duplicados, consulte "[Sobre o suporte SARIF para a varredura de código](/code-security/secure-coding/sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)". - -{% data reusables.code-scanning.upload-sarif-alert-limit %} - -### Exemplo de fluxo de trabalho para arquivos SARIF gerados fora de um repositório - -Você pode criar um novo fluxo de trabalho que faz o upload de arquivos SARIF após fazer o commit deles no seu repositório. Isso é útil quando o arquivo SARIF é gerado como um artefato fora do seu repositório. - -Este exemplo de fluxo de trabalho é executado sempre que os commits são carregados no repositório. A ação usa a propriedade `partialFingerprints` para determinar se houve alterações. Além de executar quando os commits são carregados, o fluxo de trabalho está programado para ser executado uma vez por semana. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". - -Este fluxo de trabalho faz o upload do arquivo `results.sarif` localizado na raiz do repositório. Para obter mais informações sobre a criação de um arquivo de fluxo de trabalho, consulte "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". - -Como alternativa, você pode modificar este fluxo de trabalho para fazer upload de um diretório de arquivos SARIF. Por exemplo, você pode colocar todos os arquivos SARIF em um diretório na raiz do seu repositório denominado `sarif-output` e definir o parâmetro de entrada da ação `sarif_file` como `sarif-output`. - -```yaml -name: "Upload SARIF" - -# Run workflow each time code is pushed to your repository and on a schedule. -# The scheduled workflow runs every Thursday at 15:45 UTC. -on: - push: - schedule: - - cron: '45 15 * * 4' - -jobs: - build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - permissions: - security-events: write{% endif %} - steps: - # This step checks out a copy of your repository. - - name: Checkout repository - uses: actions/checkout@v2 - - name: Upload SARIF file - uses: github/codeql-action/upload-sarif@v1 - with: - # Path to SARIF file relative to the root of the repository - sarif_file: results.sarif -``` - -### Exemplo de fluxo de trabalho que executa a ferramenta de análise ESLint - -Se você gerar seu arquivo SARIF de terceiros como parte de um fluxo de trabalho de integração contínua (CI), você poderá adicionar a ação `upload-sarif` como um passo depois de executar seus testes de CI. Se você ainda não tiver um fluxo de trabalho de CI, você poderá criar um usando um modelo de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte o início rápido "[{% data variables.product.prodname_actions %}](/actions/quickstart)". - -Este exemplo de fluxo de trabalho é executado sempre que os commits são carregados no repositório. A ação usa a propriedade `partialFingerprints` para determinar se houve alterações. Além de executar quando os commits são carregados, o fluxo de trabalho está programado para ser executado uma vez por semana. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". - -O fluxo de trabalho mostra um exemplo de execução da ferramenta de análise estática ESLint como uma etapa de um fluxo de trabalho. A etapa `Executar ESLint` executa a ferramenta ESLint e produz o arquivo `results.sarif`. Em seguida, o fluxo de trabalho faz o upload do arquivo `results.sarif` para {% data variables.product.prodname_dotcom %} usando a ação `upload-sarif`. Para obter mais informações sobre a criação de um arquivo de fluxo de trabalho, consulte "[Introdução ao GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)". - -```yaml -name: "ESLint analysis" - -# Run workflow each time code is pushed to your repository and on a schedule. -# The scheduled workflow runs every Wednesday at 15:45 UTC. -on: - push: - schedule: - - cron: '45 15 * * 3' - -jobs: - build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - permissions: - security-events: write{% endif %} - steps: - - uses: actions/checkout@v2 - - name: Run npm install - run: npm install - # Runs the ESlint code analysis - - name: Run ESLint - # eslint exits 1 if it finds anything to report - run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true - # Uploads results.sarif to GitHub repository using the upload-sarif action - - uses: github/codeql-action/upload-sarif@v1 - with: - # Path to SARIF file relative to the root of the repository - sarif_file: results.sarif -``` - -## Leia mais - -- "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" -- "[Visualizando o seu histórico de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- ifversion fpt or ghes > 3.0 or ghae-next %} -- "[Cerca de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %} -- "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} -- "[Fazer o upload de uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)" diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 9f2cfa7400..8d71a5fd2e 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: Configurando a CLI do CodeQL no seu sistema de CI -shortTitle: Configurar a CLI do CodeQL -intro: 'Você pode configurar seu sistema de integração contínua para executar o {% data variables.product.prodname_codeql_cli %}, realizar análise de {% data variables.product.prodname_codeql %} e fazer o upload dos resultados para {% data variables.product.product_name %} para exibição como os alertas de {% data variables.product.prodname_code_scanning %}.' +title: Configuring CodeQL CLI in your CI system +shortTitle: Configure CodeQL CLI +intro: 'You can configure your continuous integration system to run the {% data variables.product.prodname_codeql_cli %}, perform {% data variables.product.prodname_codeql %} analysis, and upload the results to {% data variables.product.product_name %} for display as {% data variables.product.prodname_code_scanning %} alerts.' product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -22,39 +22,38 @@ topics: - CI - SARIF --- - {% data reusables.code-scanning.enterprise-enable-code-scanning %} -## Sobre como gerar resultados de varredura de código com {% data variables.product.prodname_codeql_cli %} +## About generating code scanning results with {% data variables.product.prodname_codeql_cli %} -Uma vez disponibilizado o {% data variables.product.prodname_codeql_cli %} para servidores o seu sistema de CI e após garantir ele possa ser autenticado com {% data variables.product.product_name %}, você estárá pronto para gerar dados. +Once you've made the {% data variables.product.prodname_codeql_cli %} available to servers in your CI system, and ensured that they can authenticate with {% data variables.product.product_name %}, you're ready to generate data. -Você usa três comandos diferentes para gerar resultados e fazer o upload deles para {% data variables.product.product_name %}: +You use three different commands to generate results and upload them to {% data variables.product.product_name %}: {% ifversion fpt or ghes > 3.1 or ghae or ghec %} -1. `criar um banco de dados` para criar um banco de dados de {% data variables.product.prodname_codeql %} para representar a estrutura hierárquica de cada linguagem de programação compatível no repositório. -2. `análise do banco de dados` para executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %} e resumir os resultados em um arquivo SARIF. -3. `github upload-results` para fazer o upload dos arquivos SARIF resultantes para {% data variables.product.product_name %} em que os resultados são correspondentes a um branch ou pull request e exibidos como alertas de {% data variables.product.prodname_code_scanning %}. +1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository. +2. ` database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. +3. `github upload-results` to upload the resulting SARIF files to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts. {% else %} -1. `database create` para criar um banco de dados {% data variables.product.prodname_codeql %} para representar a estrutura hierárquica de uma linguagem de programação compatível com o repositório. -2. `database analyze` para executar consultas a fim de analisar o banco de dados {% data variables.product.prodname_codeql %} e resumir os resultados em um arquivo SARIF. -3. `github upload-results` para fazer o upload do arquivo SARIF resultante para {% data variables.product.product_name %} em que os resultados são correspondentes a um branch ou pull request e exibidos como alertas de {% data variables.product.prodname_code_scanning %}. +1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of a supported programming language in the repository. +2. ` database analyze` to run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. +3. `github upload-results` to upload the resulting SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts. {% endif %} -Você pode mostrar a ajuda de linha de comando para qualquer comando usando `--help` opção. +You can display the command-line help for any command using the `--help` option. {% data reusables.code-scanning.upload-sarif-ghas %} -## Criando bancos de dados de {% data variables.product.prodname_codeql %} para analisar +## Creating {% data variables.product.prodname_codeql %} databases to analyze -1. Confira o código que você deseja analisar: - - Para um branch, confira o cabeçalho do branch que você deseja analisar. - - Para um pull request, faça o checkout do commit principal do pull request, ou confira um commit do pull request gerado por {% data variables.product.prodname_dotcom %}. -2. Defina o ambiente para a base de código, garantindo que quaisquer dependências estejam disponíveis. Para mais informações, consulte [Criando bancos de dados para linguagens não compiladas](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) e [Criando bancos de dados para linguagens compiladas](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) na documentação do {% data variables.product.prodname_codeql_cli %}. -3. Encontre o comando de criação, se houver, para a base de código. Normalmente, ele está disponível em um arquivo de configuração no sistema de CI. -4. Execute `codeql database creater` a partir da raiz de checkout do seu repositório e construa a base de código. +1. Check out the code that you want to analyze: + - For a branch, check out the head of the branch that you want to analyze. + - For a pull request, check out either the head commit of the pull request, or check out a {% data variables.product.prodname_dotcom %}-generated merge commit of the pull request. +2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}. +3. Find the build command, if any, for the codebase. Typically this is available in a configuration file in the CI system. +4. Run `codeql database create` from the checkout root of your repository and build the codebase. {% ifversion fpt or ghes > 3.1 or ghae or ghec %} ```shell # Single supported language - create one CodeQL databsae @@ -71,147 +70,24 @@ Você pode mostrar a ajuda de linha de comando para qualquer comando usando - - - Opção - - - - Obrigatório - - - - Uso - - - - - - <database> - - - - {% octicon "check-circle-fill" aria-label="Required" %} - - - - Especifique o nome e local de um diretório a ser criado para o banco de dados de {% data variables.product.prodname_codeql %}. O comando irá falhar se você tentar substituir um diretório existente. Se você também especificar --db-cluster, este será o diretório principal e um subdiretório será criado para cada linguagem analisada. - - - - - - `--language` - - - - {% octicon "check-circle-fill" aria-label="Required" %} - - - - Especifique o identificador para a linguagem para criar um banco de dados: {% data reusables.code-scanning.codeql-languages-keywords %} (use javascript para analisar o código TypeScript). - - - - - - {% ifversion fpt or ghes > 3.1 or ghae or ghec %}When used with `--db-cluster`, a opção aceita uma lista separada por vírgulas, ou pode ser especificada mais de uma vez.{% endif %} - - - - - - - - - - - - `--command` - - - - - - - Recomendado. Use para especificar o comando de criação ou o script que invoca o processo de criação para a base de código. Os comandos são executados a partir da pasta atual ou de onde são definidos, a partir de `--source-root`. Não é necessário para análise de Python e JavaScript/TypeScript. - - - - - - {% ifversion fpt or ghes > 3.1 or ghae or ghec %} - - - - - - - - - - - - `--db-cluster` - - - - - - - Opcional. Use em bases de código linguagem múltipla para gerar um banco de dados para cada linguagem especificada por `--language`. - - - - - - `--no-run-unnecessary-builds` - - - - - - - Recomendado. Use para suprimir o comando de compilação para linguagens em que {% data variables.product.prodname_codeql_cli %} não precisa monitorar a criação (por exemplo, Python e JavaScript/TypeScript). - - - - - - {% endif %} - - - - - - - - - - - - `--source-root` - - - - - - - Opcional. Use se você executar a CLI fora da raiz do check-out do repositório. Por padrão, o comando criação de banco de dados supõe que o diretório atual é o diretório raiz para os arquivos de origem, use esta opção para especificar uma localidade diferente. - - - +| Option | Required | Usage | +|--------|:--------:|-----| +| `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory. If you also specify `--db-cluster`, this is the parent directory and a subdirectory is created for each language analyzed.| +| `--language` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the identifier for the language to create a database for, one of: `{% data reusables.code-scanning.codeql-languages-keywords %}` (use `javascript` to analyze TypeScript code). {% ifversion fpt or ghes > 3.1 or ghae or ghec %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} +| `--command` | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from `--source-root`. Not needed for Python and JavaScript/TypeScript analysis. | {% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `--db-cluster` | | Optional. Use in multi-language codebases to generate one database for each language specified by `--language`. +| `--no-run-unnecessary-builds` | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript). {% endif %} +| `--source-root` | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. | -Para obter mais informações, consulte [Criar bancos de dados de {% data variables.product.prodname_codeql %} ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) na documentação para o {% data variables.product.prodname_codeql_cli %}. +For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. -### {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Exemplo de linguagem única{% else %}Exemplo básico{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Single language example{% else %}Basic example{% endif %} -Este exemplo cria um banco de dados de {% data variables.product.prodname_codeql %} para o repositório verificado em `/checkouts/example-repo`. Ele usa o extrator do JavaScript para criar uma representação hierárquica do código JavaScript e TypeScript no repositório. O banco de dados resultante é armazenado em `/codeql-dbs/example-repo`. +This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`. ``` $ codeql database create /codeql-dbs/example-repo --language=javascript \ @@ -228,16 +104,16 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ ``` {% ifversion fpt or ghes > 3.1 or ghae or ghec %} -### Exemplo de linguagem múltipla +### Multiple language example -Este exemplo cria dois bancos de dados de {% data variables.product.prodname_codeql %} para o repositório verificado em `/checkouts/example-repo-multi`. Ela usa: +This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses: -- `--db-cluster` para solicitar análise de mais de uma linguagem. -- `--language` para especificar para quais linguagens criar bancos de dados. -- `--command` para dizer a ferramenta que o comando de compilação para a base de código. Nesse caso, `make`. -- `--no-run-unnecessary-builds` para informar a ferramenta que ignore o comando de criação para linguagens em que não é necessário (como Python). +- `--db-cluster` to request analysis of more than one language. +- `--language` to specify which languages to create databases for. +- `--command` to tell the tool the build command for the codebase, here `make`. +- `--no-run-unnecessary-builds` to tell the tool to skip the build command for languages where it is not needed (like Python). -Os bancos de dados resultantes são armazenados em `python` e nos subdiretórios `cpp` e `/codeql-dbs/example-repo-multi`. +The resulting databases are stored in `python` and `cpp` subdirectories of `/codeql-dbs/example-repo-multi`. ``` $ codeql database create /codeql-dbs/example-repo-multi \ @@ -255,20 +131,20 @@ Running build command: [make] [build-stdout] [INFO] Processed 1 modules in 0.15s [build-stdout] Finalizing databases at /codeql-dbs/example-repo-multi. -Banco de dados criado com sucesso em /codeql-dbs/example-repo-multi. +Successfully created databases at /codeql-dbs/example-repo-multi. $ ``` {% endif %} -## Analisando um banco de dados de {% data variables.product.prodname_codeql %} +## Analyzing a {% data variables.product.prodname_codeql %} database -1. Criar um banco de dados de {% data variables.product.prodname_codeql %} (ver acima).{% if codeql-packs %} -2. Opcional, execute `codeql pack download` para fazer o download de quaisquer pacotes (beta) de {% data variables.product.prodname_codeql %} que você deseja executar durante a análise. Para obter mais informações, consulte "[Fazer o download e usando pacotes de consulta de {% data variables.product.prodname_codeql %} pacotes de consulta](#downloading-and-using-codeql-query-packs)" abaixo. +1. Create a {% data variables.product.prodname_codeql %} database (see above).{% if codeql-packs %} +2. Optional, run `codeql pack download` to download any {% data variables.product.prodname_codeql %} packs (beta) that you want to run during analysis. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} query packs](#downloading-and-using-codeql-query-packs)" below. ```shell codeql pack download <packs> ``` {% endif %} -3. Executar `codeql database analyze` no banco de dados e especifique quais {% if codeql-packs %}pacotes e/ou {% endif %}consultas devem ser usados. +3. Run `codeql database analyze` on the database and specify which {% if codeql-packs %}packs and/or {% endif %}queries to use. ```shell codeql database analyze <database> --format=<format> \ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} @@ -277,7 +153,7 @@ $ {% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% note %} -**Observação:** Se você analisar mais de um banco de dados de {% data variables.product.prodname_codeql %} para um único commit, você deverá especificar uma categoria SARIF para cada conjunto de resultados gerados por este comando. Ao fazer o upload dos resultados para {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} usa essa categoria para armazenar os resultados para cada linguagem separadamente. Se você esquecer de fazer isso, cada upload irá substituir os resultados anteriores. +**Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results. ```shell codeql database analyze <database> --format=<format> \ @@ -285,137 +161,26 @@ codeql database analyze <database> --format=<format> \ {% if codeql-packs %}<packs,queries>{% else %}<queries>{% endif %} ``` {% endnote %} - {% endif %} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - Opção - - Obrigatório - - Uso -
    - <database> - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o caminho para o diretório que contém o banco de dados de {% data variables.product.prodname_codeql %} a ser analisado. -
    - <packs,queries> - - - Especifique pacotes ou consultas de {% data variables.product.prodname_codeql %} para executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, omita este parâmetro. Para ver os outros itens de consultas incluídos no pacote de {% data variables.product.prodname_codeql_cli %}, procure em /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte Criando conjuntos de consultas de CodeQL na documentação do {% data variables.product.prodname_codeql_cli %}. -
    - `--format` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o formato para o arquivo de resultados gerado pelo comando. Para fazer upload para {% data variables.product.company_short %}, deverá ser: {% ifversion fpt or ghae or ghec %}sarif-latest{% else %}sarifv2.1.0{% endif %}. Para obter mais informações, consulte "Suporte SARIF para {% data variables.product.prodname_code_scanning %}". -
    - `--output` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique onde salvar o arquivo de resultados SARIF.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -
    - --sarif-category - - {% octicon "question" aria-label="Required with multiple results sets" %} - - Opcional para análise única do banco de dados. Necessário para definir a linguagem quando você analisa vários bancos de dados para um único commit em um repositório. Especifique uma categoria a incluir no arquivo de resultados SARIF para esta análise. Usa-e uma categoria para distinguir várias análises para a mesma ferramenta e commit, mas é realizada em diferentes linguagens ou diferentes partes do código.{% endif %}{% if codeql-packs %} -
    - <packs> - - - Opcional. Use se você fez o download dos pacotes de consulta CodeQL e desejar executar as consultas padrão ou os conjuntos de consulta especificados nos pacotes. Para obter mais informações, consulte "Fazer o download e usar pacotes de {% data variables.product.prodname_codeql %}."{% endif %} -
    - `--threads` - - - Opcional. Use se você quiser usar mais de um tópico para executar consultas. O valor padrão é 1. Você pode especificar mais threads para acelerar a execução da consulta. Para definir o número de threads para o número de processadores lógicos, especifique 0. -
    - `--verbose` - - - Opcional. Use para obter informações mais detalhadas sobre o processo de análise{% ifversion fpt or ghes > 3.1 or ghae or ghec %} e dados de diagnóstico do processo de criação do banco de dados{% endif %}. -
    -Para obter mais informações, consulte [Analisando bancos de dados com {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) na documentação do {% data variables.product.prodname_codeql_cli %}. +| Option | Required | Usage | +|--------|:--------:|-----| +| `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. | +| `` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `//codeql/qlpacks/codeql-/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. +| `--format` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)." +| `--output` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `--sarif-category` | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %} +| `--sarif-add-query-help` | | Optional. Use if you want to include any available markdown-rendered query help for custom queries used in your analysis. Any query help for custom queries included in the SARIF output will be displayed in the code scanning UI if the relevant query generates an alert. For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/#including-query-help-for-custom-codeql-queries-in-sarif-files) in the documentation for the {% data variables.product.prodname_codeql_cli %}.{% endif %}{% if codeql-packs %} +| `` | | Optional. Use if you have downloaded CodeQL query packs and want to run the default queries or query suites specified in the packs. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} packs](#downloading-and-using-codeql-query-packs)."{% endif %} +| `--threads` | | Optional. Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`. +| `--verbose` | | Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae or ghec %} and diagnostic data from the database creation process{% endif %}. -### Exemplo básico -Este exemplo analisa um banco de dados {% data variables.product.prodname_codeql %} armazenado em `/codeql-dbs/example-repo` e salva os resultados como um arquivo SARIF: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}}Ele usa `--sarif-category` para incluir informações extras no arquivo SARIF que identifica os resultados como JavaScript. Isto é essencial quando você tem mais de um banco de dados de {% data variables.product.prodname_codeql %} para analisar um único commit em um repositório.{% endif %} +For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. + +### Basic example + +This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ @@ -430,16 +195,16 @@ $ codeql database analyze /codeql-dbs/example-repo \ > Interpreting results. ``` -## Fazendo upload de resultados para {% data variables.product.product_name %} +## Uploading results to {% data variables.product.product_name %} {% data reusables.code-scanning.upload-sarif-alert-limit %} -Antes de poder fazer o upload dos resultados para {% data variables.product.product_name %}, você deverá determinar a melhor maneira de passar o token de acesso {% data variables.product.prodname_github_app %} ou pessoal que você criou anteriormente para o {% data variables.product.prodname_codeql_cli %} (consulte [Instalando {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). Recomendamos que você revise a orientação do seu sistema de CI sobre o uso seguro de um armazenamento de segredos. O {% data variables.product.prodname_codeql_cli %} é compatível com: +Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports: -- Passando o token para a CLI através da entrada padrão usando a opção `--github-auth-stdin` (recomendado). -- Salvando o segredo na variável de ambiente `GITHUB_TOKEN` e executando a CLI sem incluir a opção `--github-auth-stdin`. +- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended). +- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option. -Quando você decidir o método mais seguro e confiável para o seu servidor de CI, execute `codeql github upload-results` no arquivo de resultados SARIF e inclua `--github-auth-stdin`, a menos que o token esteja disponível na variável de ambiente `GITHUB_TOKEN`. +When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on each SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`. ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ @@ -447,110 +212,20 @@ Quando você decidir o método mais seguro e confiável para o seu servidor de C {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - Opção - - Obrigatório - - Uso -
    - `--repository` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o PROPRIETÁRIO/NOME do repositório para o qual será feito o upload dos dados. O proprietário deve ser uma organização dentro de uma empresa com uma licença para {% data variables.product.prodname_GH_advanced_security %} e {% data variables.product.prodname_GH_advanced_security %} deve estar habilitado para o repositório{% ifversion fpt or ghec %}, a menos que o repositório seja público{% endif %}. Para obter mais informações, consulte "Gerenciar configurações de segurança e análise do seu repositório". -
    - `--ref` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o nome do ref que você verificou e analisou para que os resultados possam ser correspondidos ao código correto. Para o uso de um branch: refs/heads/BRANCH-NAME, para o commit principal de um pull request, use refs/pulls/NUMBER/head ou para o commit de merge gerado por {% data variables.product.prodname_dotcom %} do uso de um pull request refs/pulls/NUMBER/merge. -
    - `--commit` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o SHA completo do commit que você analisou. -
    - `--sarif` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o arquivo SARIF a ser carregado.{% ifversion ghes > 3.0 or ghae %} -
    - `--github-url` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique a URL para {% data variables.product.product_name %}.{% endif %} -
    - `--github-auth-stdin` - - - Opcional. Use para passar a CLI, {% data variables.product.prodname_github_app %} ou o token de acesso pessoal criado para autenticação com a API REST de {% data variables.product.company_short %}por meio da entrada padrão. Isso não é necessário se o comando tiver acesso a uma variável de ambiente GITHUB_TOKEN definida com este token. -
    +| Option | Required | Usage | +|--------|:--------:|-----| +| `--repository` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the *OWNER/NAME* of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% ifversion fpt or ghec %}, unless the repository is public{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +| `--ref` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pulls/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pulls/NUMBER/merge`. +| `--commit` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed. +| `--sarif` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %} +| `--github-url` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %} +| `--github-auth-stdin` | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. -Para obter mais informações, consulte [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) na documentação para {% data variables.product.prodname_codeql_cli %}. +For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. -### Exemplo básico +### Basic example -Este exemplo faz o upload dos resultados do arquivo SARIF `temp/example-repo-js.sarif` para o repositório `meu-org/example-repo`. Ele informa à API de {% data variables.product.prodname_code_scanning %} que os resultados são para o commit `deb275d2d5fe9a522a0b7bd8b6b6a1c939552718` no branch `main`. +This example uploads results from the SARIF file `temp/example-repo-js.sarif` to the repository `my-org/example-repo`. It tells the {% data variables.product.prodname_code_scanning %} API that the results are for the commit `deb275d2d5fe9a522a0b7bd8b6b6a1c939552718` on the `main` branch. ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ @@ -559,67 +234,29 @@ $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example- {% endif %}--github-auth-stdin ``` -Não há saída deste comando a menos que o upload não tenha sido bem-sucedido. A instrução de comando retorna quando o upload foi concluído e o processamento de dados é iniciado. Em bases de código menores, você poderá explorar os alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} pouco tempo depois. É possível ver alertas diretamente no pull request ou na aba **Segurança** para branches, dependendo do código que você fizer checkout. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" e "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". +There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. You can see alerts directly in the pull request or on the **Security** tab for branches, depending on the code you checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." {% if codeql-packs %} -## Fazendo o download e usando pacotes de consulta de {% data variables.product.prodname_codeql %} +## Downloading and using {% data variables.product.prodname_codeql %} query packs {% data reusables.code-scanning.beta-codeql-packs-cli %} -O pacote de {% data variables.product.prodname_codeql_cli %} inclui consultas mantidas por especialistas de {% data variables.product.company_short %}, pesquisadores de segurança e contribuidores da comunidade. Se você quiser executar consultas desenvolvidas por outras organizações, os pacotes de consulta de {% data variables.product.prodname_codeql %} fornecem uma forma eficiente e confiável de fazer o download e executar consultas. Para obter mais informações, consulte "[Sobre digitalização de código com o CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)". +The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." -Antes de usar um pacote de {% data variables.product.prodname_codeql %} para analisar um banco de dados, você deve fazer o download de todos os pacotes que precisar a partir de {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} executando `codeql download` e especificando os pacotes que você deseja baixar. Se um pacote não estiver disponível publicamente, você precisará usar um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para efetuar a autenticação. Para obter mais informações e um exemplo, consulte "[o Fazer upload dos resultados para {% data variables.product.product_name %}](#uploading-results-to-github)" acima. +Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} by running `codeql pack download` and specifying the packages you want to download. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or personal access token to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. ```shell codeql pack download <scope/name@version>,... ``` - - - - - - - - - - - - - - - - - - - - - - - - -
    - Opção - - Obrigatório - - Uso -
    - `` - - {% octicon "check-circle-fill" aria-label="Required" %} - - Especifique o escopo e o nome de um ou mais pacotes de consulta CodeQL para fazer o download usando uma lista separada por vírgulas. Opcionalmente, inclua a versão para fazer o download e descompactar. Por padrão, a versão mais recente deste pacote foi baixada. -
    - `--github-auth-stdin` - - - Opcional. Passe o token de acesso {% data variables.product.prodname_github_app %} ou pessoal criado para autenticação com a API REST de {% data variables.product.company_short %}para a CLI por meio da entrada padrão. Isso não é necessário se o comando tiver acesso a uma variável de ambiente GITHUB_TOKEN definida com este token. -
    +| Option | Required | Usage | +|--------|:--------:|-----| +| `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. | +| `--github-auth-stdin` | | Optional. Pass the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. -### Exemplo básico +### Basic example -Este exemplo executa dois comandos para baixar a última versão do pacote `octo-org/security-queries` e, em seguida, analisar o banco de dados `/codeql-dbs/exemplo-repo`. +This example runs two commands to download the latest version of the `octo-org/security-queries` pack and then analyze the database `/codeql-dbs/example-repo`. ``` $ echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download octo-org/security-queries @@ -642,9 +279,9 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Exemplo de configuração de CI para análise de {% data variables.product.prodname_codeql %} +## Example CI configuration for {% data variables.product.prodname_codeql %} analysis -Este é um exemplo da série de comandos que você pode usar para analisar uma base de código com duas linguagens compatíveis e, em seguida, fazer o upload dos resultados para {% data variables.product.product_name %}. +This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}. ```shell # Create CodeQL databases for Java and Python in the 'codeql-dbs' directory @@ -678,25 +315,25 @@ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-re --sarif=python-results.sarif --github-auth-stdin ``` -## Solucionando o {% data variables.product.prodname_codeql_cli %} do seu sistema de CI +## Troubleshooting the {% data variables.product.prodname_codeql_cli %} in your CI system -### Visualizando o registro e as informações de diagnóstico +### Viewing log and diagnostic information -Ao analisar um banco de dados {% data variables.product.prodname_codeql %} usando um conjunto de consultas de {% data variables.product.prodname_code_scanning %}, além de gerar informações detalhadas sobre alertas, a CLI relata dados de diagnóstico da etapa de geração de banco de dados e resumo de métricas. Para repositórios com poucos alertas, você pode considerar úteis essas informações para determinar se realmente existem poucos problemas no código, ou se houve erros ao gerar o banco de dados {% data variables.product.prodname_codeql %}. Para obter saídas mais detalhadas de `codeql database analyze`, use a opção `--verbose`. +When you analyze a {% data variables.product.prodname_codeql %} database using a {% data variables.product.prodname_code_scanning %} query suite, in addition to generating detailed information about alerts, the CLI reports diagnostic data from the database generation step and summary metrics. For repositories with few alerts, you may find this information useful for determining if there are genuinely few problems in the code, or if there were errors generating the {% data variables.product.prodname_codeql %} database. For more detailed output from `codeql database analyze`, use the `--verbose` option. -Para obter mais informações sobre o tipo de informações de diagnóstico disponíveis, consulte "[Visualizar registros de {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#about-analysis-and-diagnostic-information)". +For more information about the type of diagnostic information available, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#about-analysis-and-diagnostic-information)". -### {% data variables.product.prodname_code_scanning_capc %} mostra apenas os resultados da análise de uma das linguagens analisadas +### {% data variables.product.prodname_code_scanning_capc %} only shows analysis results from one of the analyzed languages -Por padrão, {% data variables.product.prodname_code_scanning %} espera um arquivo de resultados SARIF por análise de um repositório. Consequentemente, quando se faz o upload de um segundo arquivo SARIF para um compromisso, ele é tratado como uma substituição do conjunto original de dados. +By default, {% data variables.product.prodname_code_scanning %} expects one SARIF results file per analysis for a repository. Consequently, when you upload a second SARIF results file for a commit, it is treated as a replacement for the original set of data. -Se desejar fazer o upload de mais de um conjunto de resultados para a API de {% data variables.product.prodname_code_scanning %} para um commit em um repositório, você deve identificar cada conjunto de resultados como um conjunto único. Para repositórios em que você cria mais de um banco de dados de {% data variables.product.prodname_codeql %} para analisar para cada commit, use a opção `--sarif-category` para especificar uma linguagem ou outra categoria exclusiva para cada arquivo SARIF que você gerar para esse repositório. +If you want to upload more than one set of results to the {% data variables.product.prodname_code_scanning %} API for a commit in a repository, you must identify each set of results as a unique set. For repositories where you create more than one {% data variables.product.prodname_codeql %} database to analyze for each commit, use the `--sarif-category` option to specify a language or other unique category for each SARIF file that you generate for that repository. -### Alternativa caso o seu sistema de CI não puder acionar {% data variables.product.prodname_codeql_cli %} +### Alternative if your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} -Se o seu sistema CI não puder habilitar o autobuild {% data variables.product.prodname_codeql_cli %} e você não puder especificar uma linha de comando para a compilação, você poderá usar o rastreamento de compilação indireto para criar bancos de dados de {% data variables.product.prodname_codeql %} para linguagens compiladas. Para obter mais informações, consulte [Usando o rastreamento indireto de compilação](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) na documentação de {% data variables.product.prodname_codeql_cli %}. +If your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} autobuild and you cannot specify a command line for the build, you can use indirect build tracing to create {% data variables.product.prodname_codeql %} databases for compiled languages. For more information, see [Using indirect build tracing](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) in the documentation for the {% data variables.product.prodname_codeql_cli %}. {% endif %} @@ -710,7 +347,7 @@ Se o seu sistema CI não puder habilitar o autobuild {% data variables.product.p {% endif %} -## Leia mais +## Further reading -- [Criando bancos de dados de CodeQL](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) -- [Analisando bancos de dados com a CLI do CodeQL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) +- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) +- [Analyzing databases with the CodeQL CLI](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md deleted file mode 100644 index 946ca7eb38..0000000000 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -title: Configurar o executor do CodeQL no seu sistema de CI -shortTitle: Configurar o executor do CodeQL -intro: 'Você pode configurar como o {% data variables.product.prodname_codeql_runner %} faz a varredura do código no seu projeto e faz o upload dos resultados para o {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system - - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system - - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system - - /code-security/secure-coding/configuring-codeql-runner-in-your-ci-system - - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: how_to -topics: - - Advanced Security - - Code scanning - - CodeQL - - Integration - - CI - - Repositories - - Pull requests - - C/C++ - - C# - - Java ---- - - - -{% data reusables.code-scanning.deprecation-codeql-runner %} -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -## Sobre a configuração de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI - -Para integrar {% data variables.product.prodname_code_scanning %} ao seu sistema de CI, você pode usar o {% data variables.product.prodname_codeql_runner %}. Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)". - -De modo geral, você invoca o {% data variables.product.prodname_codeql_runner %} da seguinte forma. - -```shell -$ /path/to-runner/codeql-runner-OS -``` - -`/path/to-runner/` depende do local onde você fez o download do {% data variables.product.prodname_codeql_runner %} no seu sistema de CI. `codeql-runner-OS` depende do sistema operacional que você usa. Existem três versões do {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos` e `codeql-runner-win`, para os sistemas Linux, macOS e Windows, respectivamente. - -Para personalizar a maneira como o {% data variables.product.prodname_codeql_runner %} faz a varredura do seu código, você pode usar sinalizadores, como `--languages` e `--queries`, ou você pode especificar configurações personalizadas em um arquivo de configuração separado. - -## Fazer a varredura de pull requests - -A varredura de código sempre que uma pull request é criada impede que os desenvolvedores introduzam novas vulnerabilidades e erros no código. - -Para fazer a varredura de um pull request, execute o comando `analyze` e use o sinalizador `--ref` para especificar o pull request. A referência é `refs/pull//head` ou `refs/pull//merge`, dependendo se você verificou o commit HEAD do branch do pull request ou um commit de merge com o branch de base. - -```shell -$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge -``` - -{% note %} - -**Observação**: Se você analisar o código com uma ferramenta de terceiros e desejar que os resultados apareçam como verificações de pull request, você deverá executar o comando `upload` e usar o sinalizador `--ref` para especificar o pull request em vez do branch. A referência é `refs/pull//head` ou `refs/pull//merge`. - -{% endnote %} - -## Sobrescrever a detecção automática de linguagem - -O {% data variables.product.prodname_codeql_runner %} detecta e faz a varredura automática do código escrito nas linguagens compatíveis. - -{% data reusables.code-scanning.codeql-languages-bullets %} - -{% data reusables.code-scanning.specify-language-to-analyze %} - -Para substituir a detecção automática de idioma, execute o comando `init` com o sinalizador `--languages`, seguido de uma lista de palavras-chave de linguagem separada por vírgulas. As palavras-chave para os idiomas compatíveis são {% data reusables.code-scanning.codeql-languages-keywords %}. - -```shell -$ /path/to-runner/codeql-runner-linux init --languages cpp,java -``` - -## Executar consultas adicionais - -{% data reusables.code-scanning.run-additional-queries %} - -{% data reusables.code-scanning.codeql-query-suites %} - -Para adicionar uma ou mais consultas, passe uma lista de caminhos separados por vírgulas para o sinalizador `--queries` do comando `init`. Você também pode especificar consultas adicionais em um arquivo de configuração. - -Se você também estiver usando um arquivo de configuração para configurações personalizadas, e você também estiver especificando consultas adicionais com o sinalizador `--queries`, o {% data variables.product.prodname_codeql_runner %} usará as consultas adicionais especificadas com o sinalizador `--queries` em vez de qualquer um no arquivo de configuração. Se você desejar executar o conjunto combinado de consultas adicionais especificadas com o sinalizador e no arquivo de configuração, determine previamente o valor passado para `--queries` com o símbolo `+`. Para obter exemplos de arquivos de configuração, consulte "[Exemplo de arquivos de configuração](#example-configuration-files)". - -No exemplo a seguir,. o símbolo `+` garante que o {% data variables.product.prodname_codeql_runner %} usará as consultas adicionais junto com quaisquer consultas especificadas no arquivo de configuração referenciado. - -```shell -$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml - --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main -``` - -## Usar uma ferramenta de varredura de código de terceiros - -Em vez de passar informações adicionais para os comandos de {% data variables.product.prodname_codeql_runner %}, você pode especificar configurações personalizadas em um arquivo de configuração separado. - -O arquivo de configuração é um arquivo YAML. Ele usa uma sintaxe semelhante à sintaxe do fluxo de trabalho do {% data variables.product.prodname_actions %}, conforme ilustrado nos exemplos abaixo. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)". - -Use o sinalizador `--config-file` do comando `init` para especificar o arquivo de configuração. O valor de `--config-file` é o caminho para o arquivo de configuração que você deseja usar. Este exemplo carrega o arquivo de configuração _.github/codeql/codeql-config.yml_. - -```shell -$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml -``` - -{% data reusables.code-scanning.custom-configuration-file %} - -### Exemplo de arquivo de configuração - -{% data reusables.code-scanning.example-configuration-files %} - -## Configurar o {% data variables.product.prodname_code_scanning %} para linguagens compiladas - -Para as linguagens compiladas C/C++, C#, e Java, o {% data variables.product.prodname_codeql %} constrói o código antes de analisá-lo. {% data reusables.code-scanning.analyze-go %} - -Para muitos sistemas de criação comuns, o {% data variables.product.prodname_codeql_runner %} pode construir o código automaticamente. Para tentar construir o código automaticamente, execute `autobuild` entre `init` e `analise` as etapas. Observe que, se seu repositório precisar de uma versão específica de uma ferramenta de criação, primeiro você precisará instalar a ferramenta de criação manualmente. - -O processo `autobuild` sempre tenta criar _uma_ linguagem compilada para um repositório. A linguagem selecionada automaticamente para análise é a linguagem com mais arquivos. Se você quiser escolher um idioma explicitamente, use o sinalizador `--language` do comando `autobuild`. - -```shell -$ /path/to-runner/codeql-runner-linux autobuild --language csharp -``` - -Se o comando `autobuild` não puder criar o seu código, você poderá executar as etapas de compilação, entre as etapas de `init` e de `análise`. Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)". - -## {% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}. - -Por padrão, o {% data variables.product.prodname_codeql_runner %} faz o upload dos resultados a partir de {% data variables.product.prodname_code_scanning %} quando você executa o comando de `análise`. Você também pode carregar arquivos do SARIF separadamente, usando o comando `upload`. - -Depois de enviar os dados, o {% data variables.product.prodname_dotcom %} exibirá os alertas no seu repositório. -- Se você fez o upload de um pull request como, por exemplo, `--ref refs/pull/42/merge` ou `--ref refs/pull/42/head`, os resultados aparecerão como alertas em uma verificação de pull request. Para obter mais informações, consulte "[Alertas de varredura de código de triagem em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". -- Se você fez upload de um branch como, por exemplo `--ref refs/heads/my-branch`, os resultados aparecerão na aba **Segurança** do seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). " - -## Comando de referência de {% data variables.product.prodname_codeql_runner %} - -O {% data variables.product.prodname_codeql_runner %} é compatível os seguintes comandos e sinalizadores. - -### `init` - -Inicializa o {% data variables.product.prodname_codeql_runner %} e cria um banco de dados de {% data variables.product.prodname_codeql %} para cada linguagem a ser analisada. - -| Sinalizador | Obrigatório | Valor de entrada | -| -------------------------------------- |:-----------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | Nome do repositório a ser inicializado. | -| `--github-url` | ✓ | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado. |{% ifversion ghes < 3.1 %} -| `--github-auth` | ✓ | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal. |{% else %} -| `--github-auth-stdin` | ✓ | Leia o token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal da entrada padrão. -{% endif %} -| `--languages` | | Lista de linguagens para análise separada por vírgulas. Por padrão, o {% data variables.product.prodname_codeql_runner %} detecta e analisa todas as linguagens compatíveis no repositório. | -| `--queries` | | Lista separada por vírgulas de consultas adicionais a serem executadas, além do conjunto-padrão de consultas de segurança. Isso substitui a configuração de `consultas` no arquivo de configuração personalizada. | -| `--config-file` | | Caminho para o arquivo de configuração personalizado. | -| `--codeql-path` | | Caminho para uma cópia do CLI de {% data variables.product.prodname_codeql %} executável a ser usado. Por padrão, o {% data variables.product.prodname_codeql_runner %} faz o download de uma cópia. | -| `--temp-dir` | | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`. | -| `--tools-dir` | | Diretório onde as ferramentas de {% data variables.product.prodname_codeql %} e outros arquivos são armazenados entre as execuções. O padrão é um subdiretório do diretório home. | -| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `--trace-process-name` | | Avançado, apenas para Windows. Nome do processo em que um rastreador do Windows deste processo é injetado. | -| `--trace-process-level` | | Avançado, apenas para Windows. Número de níveis acima do processo principal em que um rastreador do Windows deste processo é injetado. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | - -### `autobuild` - -Tenta construir o código para as linguagens compiladas C/C++, C# e Java. Para essas linguagens, {% data variables.product.prodname_codeql %} cria o código antes de analisá-lo. Executar `autobuild` entre as etapas de `init` e `analise`. - -| Sinalizador | Obrigatório | Valor de entrada | -| -------------------------------- |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------- | -| `--language` | | A linguagem a ser criada. Por padrão, o {% data variables.product.prodname_codeql_runner %} cria a linguagem compilada com mais arquivos. | -| `--temp-dir` | | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | - -### `analyze` - -Analisa o código nos bancos de dados do {% data variables.product.prodname_codeql %} e faz o upload dos resultados para o {% data variables.product.product_name %}. - -| Sinalizador | Obrigatório | Valor de entrada | -| ------------------------------------ |:-----------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | Nome do repositório a ser analisado. | -| `--commit` | ✓ | SHA do commit a ser analisado. No Git e no Azure DevOps, isso corresponde ao valor de `git rev-parse HEAD`. No Jenkins, isso corresponde a `$GIT_COMMIT`. | -| `--ref` | ✓ | Nome da referência para análise, por exemplo `refs/heads/main` ou `refs/pull/42/merge`. No Git ou no Jenkins, isso corresponde ao valor de `git simbolic-ref HEAD`. No Azure DevOps, isso corresponde a `$(Build.SourceBranch)`. | -| `--github-url` | ✓ | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado. |{% ifversion ghes < 3.1 %} -| `--github-auth` | ✓ | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal. |{% else %} -| `--github-auth-stdin` | ✓ | Leia o token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal da entrada padrão. -{% endif %} -| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | -| `--no-upload` | | Nenhum. Impede que o {% data variables.product.prodname_codeql_runner %} faça o upload dos resultados para {% data variables.product.product_name %}. | -| `--output-dir` | | Diretório onde os arquivos SARIF de saída são armazenados. O padrão está no diretório de arquivos temporários. | -| `--ram` | | A quantidade de memória a ser usada ao executar consultas. O padrão é usar toda a memória disponível. | -| `--no-add-snippets` | | Nenhum. Exclui snippets de código da saída de SARIF. |{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -| `--category` | | A categoria a incluir no arquivo de resultados SARIF para esta análise. Uma categoria pode ser usada para distinguir várias análises para a mesma ferramenta e commit, mas executado em diferentes linguagens ou diferentes partes do código. Este valor aparecerá na propriedade `.automationDetails.id` no SARIF v2.1.0. -{% endif %} -| `--threads` | | Número de threads a serem usados ao executar consultas. O padrão é usar todos os núcleos disponíveis. | -| `--temp-dir` | | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | - -### `fazer upload` - -Faz o upload dos arquivos SARIF para {% data variables.product.product_name %}. - -{% note %} - -**Observação**: Se você analisar o código com o executor do CodeQL, o comando `analyze` irá carregar os resultados SARIF, por padrão. Você pode usar o comando `upload` para carregar os resultados SARIF que foram gerados por outras ferramentas. - -{% endnote %} - -| Sinalizador | Obrigatório | Valor de entrada | -| ------------------------------------ |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--sarif-file` | ✓ | O arquivo SARIF a ser subido ou um diretório que contém vários arquivos SARIF. | -| `--repository` | ✓ | Nome do repositório que foi analisado. | -| `--commit` | ✓ | SHA do commit que foi analisado. No Git e no Azure DevOps, isso corresponde ao valor de `git rev-parse HEAD`. No Jenkins, isso corresponde a `$GIT_COMMIT`. | -| `--ref` | ✓ | Nome da referência que foi analisada, por exemplo `refs/heads/main` ou `refs/pull/42/merge`. No Git ou no Jenkins, isso corresponde ao valor de `git simbolic-ref HEAD`. No Azure DevOps, isso corresponde a `$(Build.SourceBranch)`. | -| `--github-url` | ✓ | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado. |{% ifversion ghes < 3.1 %} -| `--github-auth` | ✓ | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal. |{% else %} -| `--github-auth-stdin` | ✓ | Leia o token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal da entrada padrão. -{% endif %} -| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | diff --git a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index ab2537d404..e4cde2b237 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -1,7 +1,7 @@ --- -title: Definindo padrões personalizados para varredura de segredo -shortTitle: Defina padrões personalizados -intro: 'Você pode definir padrões personalizados para {% data variables.product.prodname_secret_scanning %} em organizações e repositórios privados.' +title: Defining custom patterns for secret scanning +shortTitle: Define custom patterns +intro: 'You can define custom patterns for {% data variables.product.prodname_secret_scanning %} in organizations and private repositories.' product: '{% data reusables.gated-features.secret-scanning %}' redirect_from: - /code-security/secret-security/defining-custom-patterns-for-secret-scanning @@ -17,36 +17,40 @@ topics: {% ifversion ghes < 3.3 or ghae %} {% note %} -**Observação:** Os padrões personalizados para {% data variables.product.prodname_secret_scanning %} estão atualmente em fase beta e sujeitos a alterações. +**Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change. {% endnote %} {% endif %} -## Sobre padrões personalizados para {% data variables.product.prodname_secret_scanning %} +## About custom patterns for {% data variables.product.prodname_secret_scanning %} -{% data variables.product.company_short %} executa {% data variables.product.prodname_secret_scanning %} nos repositórios {% ifversion fpt or ghec %}públicos e privados{% endif %} para padrões de segredo fornecidos por parceiros de {% data variables.product.company_short %} e {% data variables.product.company_short %}. Para obter mais informações sobre o programa de parceria de {% data variables.product.prodname_secret_scanning %}, consulte "Programa de varredura de segredo de parceiros". +{% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt or ghec %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "Secret scanning partner program." -No entanto, pode haver situações em que você deverá pesquisar outros padrões secretos nos seus repositórios {% ifversion fpt or ghec %}privados{% endif %}. Por exemplo, você pode ter um padrão de segredo que é interno da sua organização. Para esses casos, você pode definir padrões personalizados de {% data variables.product.prodname_secret_scanning %} na sua empresa, organização ou {% ifversion fpt or ghec %}repositório{% endif %} privado em {% data variables.product.product_name %}. É possível definir até 500 padrões personalizados para cada conta da organização ou empresa e até 100 padrões personalizados por repositório {% ifversion fpt or ghec %}privado{% endif %}. +However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt or ghec %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt or ghec %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to +{%- ifversion fpt or ghec or ghes > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per {% ifversion fpt or ghec %}private{% endif %} repository. +{%- elsif ghes = 3.3 %} 100 custom patterns for each organization or enterprise account, and per repository. +{%- else %} 20 custom patterns for each organization or enterprise account, and per repository. +{%- endif %} {% ifversion ghes < 3.3 or ghae %} {% note %} -**Observação:** No beta, existem algumas limitações ao usar padrões personalizados para {% data variables.product.prodname_secret_scanning %}: +**Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}: -* Não há nenhuma funcionalidade de exercício de simulação. -* Você não pode editar padrões personalizados depois que forem criados. Para alterar um padrão, você deve excluí-lo e recriá-lo. -* Não há API para criar, editar ou excluir padrões personalizados. No entanto, os resultados de padrões personalizados são retornados na [API de alertas de segredos](/rest/reference/secret-scanning). +* There is no dry-run functionality. +* You cannot edit custom patterns after they're created. To change a pattern, you must delete it and recreate it. +* There is no API for creating, editing, or deleting custom patterns. However, results for custom patterns are returned in the [secret scanning alerts API](/rest/reference/secret-scanning). {% endnote %} {% endif %} -## Sintaxe de expressão regular para padrões personalizados +## Regular expression syntax for custom patterns -Os padrões personalizados para {% data variables.product.prodname_secret_scanning %} são especificados como expressões regulares. {% data variables.product.prodname_secret_scanning_caps %} usa a [biblioteca Hyperscan](https://github.com/intel/hyperscan) e é compatível apenas os construtores regex do Hyperscan, que são um subconjunto da sintaxe PCRE. Os modificadores de opções de huperscan não são compatíveis. Para obter mais informações sobre construções de padrões do Hyperscan, consulte "[suporte do padrão](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)na documentação do Hyperscan. +Custom patterns for {% data variables.product.prodname_secret_scanning %} are specified as regular expressions. {% data variables.product.prodname_secret_scanning_caps %} uses the [Hyperscan library](https://github.com/intel/hyperscan) and only supports Hyperscan regex constructs, which are a subset of PCRE syntax. Hyperscan option modifiers are not supported. For more information on Hyperscan pattern constructs, see "[Pattern support](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" in the Hyperscan documentation. -## Definindo um padrão personalizado para um repositório +## Defining a custom pattern for a repository -Antes de definir um padrão personalizado, você deve garantir que {% data variables.product.prodname_secret_scanning %} está habilitado no seu repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_secret_scanning %} para os seus repositórios](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)". +Before defining a custom pattern, you must ensure that {% data variables.product.prodname_secret_scanning %} is enabled on your repository. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your repositories](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -55,15 +59,15 @@ Antes de definir um padrão personalizado, você deve garantir que {% data varia {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -Após a criação do seu padrão, {% data reusables.secret-scanning.secret-scanning-process %} Para mais informações sobre visualização de alertas {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -## Definindo um padrão personalizado para uma organização +## Defining a custom pattern for an organization -Antes de definir um padrão personalizado, você deverá habilitar {% data variables.product.prodname_secret_scanning %} para os repositórios {% ifversion fpt or ghec %}privaivados{% endif %} que você deseja fazer a varredura na organização. Para habilitar {% data variables.product.prodname_secret_scanning %} em todos os repositórios {% ifversion fpt or ghec %}privados {% endif %} na sua organização, consulte "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +Before defining a custom pattern, you must ensure that you enable {% data variables.product.prodname_secret_scanning %} for the {% ifversion fpt or ghec %}private{% endif %} repositories that you want to scan in your organization. To enable {% data variables.product.prodname_secret_scanning %} on all {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% note %} -**Observação:** Como não há nenhuma funcionalidade de teste, recomendamos que você teste seus padrões personalizados em um repositório antes de defini-los para toda a organização. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}. +**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire organization. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. {% endnote %} @@ -74,19 +78,15 @@ Antes de definir um padrão personalizado, você deverá habilitar {% data varia {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -Depois que o padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar todos os segredos nos repositórios {% ifversion fpt or ghec %}privados {% endif %} na sua organização, incluindo todo seu histórico do Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -## Definir um padrão personalizado para uma conta corporativa +## Defining a custom pattern for an enterprise account -{% ifversion fpt or ghec or ghes %} - -Antes de definir um padrão personalizado, você deverá garantir que você habilite a digitalização de segredo para a sua conta corporativa. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." - -{% endif %} +Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." {% note %} -**Observação:** Como não há nenhuma funcionalidade de teste, recomendamos que você teste seus padrões personalizados em um repositório antes de defini-los para toda sua empresa. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}. +**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. {% endnote %} @@ -94,35 +94,35 @@ Antes de definir um padrão personalizado, você deverá garantir que você habi {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.advanced-security-policies %} {% data reusables.enterprise-accounts.advanced-security-security-features %} -1. Em "Padrões personalizados de digitalização de segredos", clique em {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**Novo padrão**{% elsif ghes = 3.2 %}**Novo padrão personalizado**{% endif %}. +1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -Depois que seu padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar se há segredos em repositórios {% ifversion fpt or ghec %}privados{% endif %} dentro das organizações da sua empresa com {% data variables.product.prodname_GH_advanced_security %} habilitado, incluindo toda a sua história de Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghes > 3.2 or ghec %} -## Editando um padrão personalizado +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} +## Editing a custom pattern -Ao salvar uma alteração em um padrão personalizado, isso irá fechar todos os alertas de {% data variables.product.prodname_secret_scanning %} que foram criados usando a versão anterior do padrão. -1. Acesse o local onde o padrão personalizado foi criado. Um padrão personalizado pode ser criado na conta de um repositório, organização ou empresa. - * Para um repositório ou organização, exiba as configurações "Segurança & análise" do repositório ou organização onde o padrão personalizado foi criado. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima. - * Para uma empresa, em "Políticas" exiba a área "Segurança Avançada" e, em seguida, clique em **Funcionalidades de segurança**. Para obter mais informações, consulte "[Definindo um padrão personalizado para uma conta corporativa](#defining-a-custom-pattern-for-an-enterprise-account)" acima. -2. Em "{% data variables.product.prodname_secret_scanning_caps %}", à direita do padrão personalizado que você deseja editar, clique em {% octicon "pencil" aria-label="The edit icon" %}. -3. Ao revisar e testar suas alterações, clique em **Salvar alterações**. +When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern. +1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. + * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above. + * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. +2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. +3. When you have reviewed and tested your changes, click **Save changes**. {% endif %} -## Removendo um padrão personalizado +## Removing a custom pattern -1. Acesse o local onde o padrão personalizado foi criado. Um padrão personalizado pode ser criado na conta de um repositório, organização ou empresa. +1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. - * Para um repositório ou organização, exiba as configurações "Segurança & análise" do repositório ou organização onde o padrão personalizado foi criado. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima. - * Para uma empresa, em "Políticas" exiba a área "Segurança Avançada" e, em seguida, clique em **Funcionalidades de segurança**. Para obter mais informações, consulte "[Definindo um padrão personalizado para uma conta corporativa](#defining-a-custom-pattern-for-an-enterprise-account)" acima. -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -1. À direita do padrão personalizado que você deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}. -1. Revise a confirmação e selecione um método para lidar com todos os alertas abertos relacionados ao padrão personalizado. -1. Clique em **Sim, excluir este padrão**. + * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above. + * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. +{%- ifversion fpt or ghes > 3.2 or ghae %} +1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. +1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern. +1. Click **Yes, delete this pattern**. - ![Confirmando a exclusão de um padrão {% data variables.product.prodname_secret_scanning %} personalizado ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) + ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) {%- elsif ghes = 3.2 %} -1. À direita do padrão personalizado que você deseja remover, clique em **Remover**. -1. Revise a confirmação e clique em **Remover padrão personalizado**. +1. To the right of the custom pattern you want to remove, click **Remove**. +1. Review the confirmation, and click **Remove custom pattern**. {%- endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index 87a4865d7d..b62275e4e3 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -1,6 +1,6 @@ --- -title: Automatizando o Dependabot com GitHub Actions -intro: 'Exemplos de como você pode usar {% data variables.product.prodname_actions %} para automatizar tarefas comuns de {% data variables.product.prodname_dependabot %} relacionadas.' +title: Automating Dependabot with GitHub Actions +intro: 'Examples of how you can use {% data variables.product.prodname_actions %} to automate common {% data variables.product.prodname_dependabot %} related tasks.' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_actions %} to respond to {% data variables.product.prodname_dependabot %}-created pull requests.' miniTocMaxHeadingLevel: 3 versions: @@ -16,42 +16,42 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Usar o Dependabot com ações +shortTitle: Use Dependabot with actions --- {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -## Sobre {% data variables.product.prodname_dependabot %} e {% data variables.product.prodname_actions %} +## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %} -{% data variables.product.prodname_dependabot %} cria pull requests para manter suas dependências atualizadas, e você pode usar {% data variables.product.prodname_actions %} para executar tarefas automatizadas quando estes pull requests forem criados. Por exemplo, busque artefatos adicionais, adicione etiquetas, execute testes ou modifique o pull request. +{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date, and you can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modifying the pull request. -## Respondendo aos eventos +## Responding to events -{% data variables.product.prodname_dependabot %} pode acionar fluxos de trabalho de {% data variables.product.prodname_actions %} nos seus pull requests e comentários. No entanto, devido ao ["GitHub Ações: Os fluxos de trabalho acionados pelos PRs do Dependabot serão executados com permissões somente de leitura"](https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/), alguns eventos são tratados de forma diferente. +{% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, due to ["GitHub Actions: Workflows triggered by Dependabot PRs will run with read-only permissions"](https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/), certain events are treated differently. -Para fluxos de trabalho iniciados por eventos de {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment` e `push`, aplicam-se as restrições a seguir: +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply: -- `GITHUB_TOKEN` tem permissões somente para leitura. -- Os segredos não podem ser acessados. +- `GITHUB_TOKEN` has read-only permissions. +- Secrets are inaccessible. -Para obter mais informações, consulte ["Manter seus GitHub Actions e fluxos de trabalho seguro: Evitando solicitações de pwn"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). +For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). {% ifversion ghes > 3.2 %} {% note %} -**Observação:** O administrador do seu site pode substituir essas restrições para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Solucionar problemas de {% data variables.product.prodname_actions %} para a sua empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." +**Note:** Your site administrator can override these restrictions for {% data variables.product.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." -Se as restrições forem removidas, quando um fluxo de trabalho for acionado por {% data variables.product.prodname_dependabot %}, ele terá acesso a todos os segredos que estão normalmente disponíveis. Além disso fluxos de trabalho acionados por {% data variables.product.prodname_dependabot %} podem usar as o termo `permissões` para aumentar o escopo padrão do `GITHUB_TOKEN` de acesso somente leitura. +If the restrictions are removed, when a workflow is triggered by {% data variables.product.prodname_dependabot %} it will have access to any secrets that are normally available. In addition, workflows triggered by {% data variables.product.prodname_dependabot %} can use the `permissions` term to increase the default scope of the `GITHUB_TOKEN` from read-only access. {% endnote %} {% endif %} -### Manipulando eventos de `pull_request` +### Handling `pull_request` events -Se o fluxo de trabalho precisar de acesso a segredos ou um `GITHUB_TOKEN` com permissões de gravação, você tem duas opções: usar `pull_request_target` ou usar dois fluxos de trabalho separados. Nós iremos detalhar o uso de `pull_request_target` nesta seção e o uso de dois fluxos de trabalho abaixo em "[Gerenciar `eventos`de push](#handling-push-events)". +If your workflow needs access to secrets or a `GITHUB_TOKEN` with write permissions, you have two options: using `pull_request_target`, or using two separate workflows. We will detail using `pull_request_target` in this section, and using two workflows below in "[Handling `push` events](#handling-push-events)." -Abaixo está um exemplo simples de um fluxo de trabalho `pull_request` que agora pode ter falha: +Below is a simple example of a `pull_request` workflow that might now be failing: {% raw %} ```yaml @@ -70,11 +70,11 @@ jobs: ``` {% endraw %} -Você pode substituir `pull_request` com `pull_request_target`, que é usado para pull requests a partir da bifurcação e fazer checkout explicitamente do `HEAD` do o pull request. +You can replace `pull_request` with `pull_request_target`, which is used for pull requests from forks, and explicitly check out the pull request `HEAD`. {% warning %} -**Aviso:** Usar `pull_request_target` como um substituto para `pull_request` expõe você a um comportamento inseguro. Recomendamos que você use o método de fluxo de trabalho, conforme descrito abaixo em "[Gerenciar `eventos` de push](#handling-push-events). +**Warning:** Using `pull_request_target` as a substitute for `pull_request` exposes you to insecure behavior. We recommend you use the two workflow method, as described below in "[Handling `push` events](#handling-push-events)." {% endwarning %} @@ -101,13 +101,13 @@ jobs: ``` {% endraw %} -Também é altamente recomendável que você reduza o escopo das permissões concedidas ao `GITHUB_TOKEN` para evitar vazamento de um token com mais privilégios do que o necessário. Para obter mais informações, consulte "[Permissões para o `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +It is also strongly recommended that you downscope the permissions granted to the `GITHUB_TOKEN` in order to avoid leaking a token with more privilege than necessary. For more information, see "[Permissions for the `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." -### Gerenciar `eventos` de push +### Handling `push` events -Como não há nenhum `pull_request_target` equivalente para eventos `push`, você terá que usar dois fluxos de trabalho: um fluxo de trabalho não confiável que termina fazendo o upload de artefatos, que aciona um segundo fluxo de trabalho confiável que faz o download de artefatos e continua processando. +As there is no `pull_request_target` equivalent for `push` events, you will have to use two workflows: one untrusted workflow that ends by uploading artifacts, which triggers a second trusted workflow that downloads artifacts and continues processing. -O primeiro fluxo de trabalho executa qualquer trabalho não confiável: +The first workflow performs any untrusted work: {% raw %} ```yaml @@ -125,7 +125,7 @@ jobs: ``` {% endraw %} -O segundo fluxo de trabalho executa trabalho confiável após a conclusão do primeiro fluxo de trabalho com sucesso: +The second workflow performs trusted work after the first workflow completes successfully: {% raw %} ```yaml @@ -149,19 +149,19 @@ jobs: ``` {% endraw %} -### Reexecutando manualmente um fluxo de trabalho +### Manually re-running a workflow -Você também pode executar novamente um fluxo de trabalho pendente no Dependabot, e ele será executado com um token de leitura-gravação e acesso a segredos. Antes de executar manualmente um fluxo de trabalho com falha, você deve sempre verificar se a dependência está sendo atualizada para garantir que a mudança não introduza qualquer comportamento malicioso ou não intencional. +You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior. -## Automações comuns de dependência +## Common Dependabot automations -Aqui estão vários cenários comuns que podem ser automatizados usando {% data variables.product.prodname_actions %}. +Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}. -### Obter metadados sobre um pull request +### Fetch metadata about a pull request -Uma grande quantidade de automação supõe o conhecimento do conteúdo do pull request: qual era o nome da dependência, se for uma dependência de produção, e se for uma atualização maior, menor ou de patch. +A large amount of automation requires knowing information about the contents of the pull request: what the dependency name was, if it's a production dependency, and if it's a major, minor, or patch update. -A ação `dependabot/fetch-metadata` fornece todas as informações para você: +The `dependabot/fetch-metadata` action provides all that information for you: {% raw %} ```yaml @@ -179,24 +179,24 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" # The following properties are now available: - # - steps.metadata.outputs.dependency-names - # - steps.metadata.outputs.dependency-type - # - steps.metadata.outputs.update-type + # - steps.dependabot-metadata.outputs.dependency-names + # - steps.dependabot-metadata.outputs.dependency-type + # - steps.dependabot-metadata.outputs.update-type ``` {% endraw %} -Para obter mais informações, consulte o repositório [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata). +For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository. -### Etiquetar um pull request +### Label a pull request -Se você tiver outras automações ou fluxos de trabalho de triagem com base nas etiquetas de {% data variables.product.prodname_dotcom %}, poderá configurar uma ação para atribuir etiquetas com base nos metadados fornecidos. +If you have other automation or triage workflows based on {% data variables.product.prodname_dotcom %} labels, you can configure an action to assign labels based on the metadata provided. -Por exemplo, se você quiser sinalizar todas as atualizações de dependências de produção com uma etiqueta: +For example, if you want to flag all production dependency updates with a label: {% raw %} ```yaml @@ -214,21 +214,21 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata - uses: dependabot/fetch-metadata@v1.1.0 + id: dependabot-metadata + uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Add a label for all production dependencies - if: ${{ steps.metadata.outputs.dependency-type == 'direct:production' }} + if: ${{ steps.dependabot-metadata.outputs.dependency-type == 'direct:production' }} run: gh pr edit "$PR_URL" --add-label "production" env: PR_URL: ${{github.event.pull_request.html_url}} ``` {% endraw %} -### Aprovar um pull request +### Approve a pull request -Se você quiser aprovar automaticamente os pull requests do Dependabot, você poderá usar o {% data variables.product.prodname_cli %} em um fluxo de trabalho: +If you want to automatically approve Dependabot pull requests, you can use the {% data variables.product.prodname_cli %} in a workflow: {% raw %} ```yaml @@ -244,7 +244,7 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" @@ -256,11 +256,11 @@ jobs: ``` {% endraw %} -### Habilitar o merge automático em um pull request +### Enable auto-merge on a pull request -Se você quiser fazer merge automático dos seus pull requests, você poderá usar a funcionalidade de merge automático de {% data variables.product.prodname_dotcom %}. Isto permite que o pull request seja mesclado quando todos os testes e aprovações forem cumpridos com sucesso. Para obter mais informações sobre merge automático, consulte "[Fazer merge automático de um pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)". +If you want to auto-merge your pull requests, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." -Aqui está um exemplo de como habilitar o merge automático para todas as atualizações de patch para `my-dependency`: +Here is an example of enabling auto-merge for all patch updates to `my-dependency`: {% raw %} ```yaml @@ -277,12 +277,12 @@ jobs: if: ${{ github.actor == 'dependabot[bot]' }} steps: - name: Dependabot metadata - id: metadata + id: dependabot-metadata uses: dependabot/fetch-metadata@v1.1.1 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Enable auto-merge for Dependabot PRs - if: ${{contains(steps.metadata.outputs.dependency-names, 'my-dependency') && steps.metadata.outputs.update-type == 'version-update:semver-patch'}} + if: ${{contains(steps.dependabot-metadata.outputs.dependency-names, 'my-dependency') && steps.dependabot-metadata.outputs.update-type == 'version-update:semver-patch'}} run: gh pr merge --auto --merge "$PR_URL" env: PR_URL: ${{github.event.pull_request.html_url}} @@ -290,13 +290,13 @@ jobs: ``` {% endraw %} -## Ocorreu uma falha na solução de problemas de execução do fluxo de trabalho +## Troubleshooting failed workflow runs -Se a execução do fluxo de trabalho falhar, verifique o seguinte: +If your workflow run fails, check the following: -- Você só está executando o fluxo de trabalho quando o ator correto o acionar. -- Você está fazendo o checkout do `ref` correto para o seu `pull_request`. -- Você não está tentando acessar segredos de dentro de um evento acionado por Dependabot `pull_request`, `pull_request_review`, `pull_request_review_comment` ou `push`. -- Você não está tentando executar qualquer ação de `gravar` de dentro de um evento acionado pelo Dependabot `pull_request`, `pull_request_review`, `pull_request_review_comment` ou `push`. +- You are running the workflow only when the correct actor triggers it. +- You are checking out the correct `ref` for your `pull_request`. +- You aren't trying to access secrets from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event. +- You aren't trying to perform any `write` actions from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event. -Para obter informações sobre gravação e depuração de {% data variables.product.prodname_actions %}, consulte "[Conhecendo o GitHub Actions](/actions/learn-github-actions)". +For information on writing and debugging {% data variables.product.prodname_actions %}, see "[Learning GitHub Actions](/actions/learn-github-actions)." diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 407afdb258..14ea4e4b20 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -1,6 +1,6 @@ --- -title: Sobre o gráfico de dependências -intro: Você pode usar o gráfico de dependências para identificar todas as dependências do seu projeto. O gráfico de dependências é compatível com uma série de ecossistemas de pacotes populares. +title: About the dependency graph +intro: You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems. redirect_from: - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph - /code-security/supply-chain-security/about-the-dependency-graph @@ -14,89 +14,92 @@ topics: - Dependency graph - Dependencies - Repositories -shortTitle: Gráfico de dependências +shortTitle: Dependency graph --- - -## Disponibilidade do gráfico de dependências +## Dependency graph availability -{% ifversion fpt or ghec %}O gráfico de dependências está disponível para cada repositório público que define as dependências em um ecossistema de pacote compatível usando um formato de arquivo compatível. Os administradores de repositórios também podem configurar o gráfico de dependências para repositórios privados.{% endif %} +{% ifversion fpt or ghec %}The dependency graph is available for every public repository that defines dependencies in a supported package ecosystem using a supported file format. Repository administrators can also set up the dependency graph for private repositories.{% endif %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -## Sobre o gráfico de dependências +## About the dependency graph -O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, ele mostra{% ifversion fpt or ghec %}: +The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% ifversion fpt or ghec %}: -- As dependências, os ecossistemas e os pacotes do qual depende -- Dependentes, os repositórios e pacotes que dependem dele{% else %} dependências, isto é, os ecossistemas e pacotes de que ele depende. O {% data variables.product.product_name %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.{% endif %} +- Dependencies, the ecosystems and packages it depends on +- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.product_name %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} -Ao fazer push de um commit para o {% data variables.product.product_name %}, que muda ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch-padrão, o gráfico de dependências será atualizado automaticamente.{% ifversion fpt or ghec %} Além disso, o gráfico é atualizado quando alguém faz push de uma alteração no repositório de uma de suas dependências.{% endif %} Para obter informações sobre os ecossistemas compatíveis e arquivos de manifesto, consulte "[ecossistemas de pacotes compatíveis](#supported-package-ecosystems)" abaixo. +When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% ifversion fpt or ghec %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. {% ifversion fpt or ghes > 3.1 or ghae or ghec %} -Ao criar um pull request que contém alterações para dependências direcionadas ao branch padrão, {% data variables.product.prodname_dotcom %} usará o gráfico de dependências para adicionar revisões de dependências ao pull request. Eles indicam se as dependências contêm vulnerabilidades e, em caso afirmativo, a versão da dependência na qual a vulnerabilidade foi corrigida. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". +When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -## Dependências incluídas +## Dependencies included -O gráfico de dependências inclui todas as dependências de um repositório detalhadas nos arquivos de manifesto e de bloqueio ou seu equivalente para ecossistemas compatíveis. Isto inclui: +The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: -- Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio -- Dependências indiretas dessas dependências diretas, também conhecidas como dependências transitórias ou subdependências +- Direct dependencies, that are explicitly defined in a manifest or lock file +- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies -O gráfico de dependências identifica as dependências indiretas{% ifversion fpt or ghec %} explicitamente a partir de um arquivo de bloqueio ou verificando as dependências das suas dependências diretas. Para o gráfico mais confiável, você deve usar os arquivos de bloqueio (ou o equivalente deles), pois definem exatamente quais versões das dependências diretas e indiretas você usa atualmente. Se você usar arquivos de bloqueio, você também terá certeza de que todos os contribuidores do repositório usarão as mesmas versões, o que facilitará para você testar e depurar o código{% else %} dos arquivos de bloqueio{% endif %}. +The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. {% ifversion fpt or ghec %} -## Dependentes incluídos +## Dependents included -Para repositórios públicos, apenas repositórios públicos que dependem dele ou de pacotes que publica são relatados. Essas informações não foram relatadas para repositórios privados.{% endif %} +For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} -## Usar o gráfico de dependências +## Using the dependency graph -Você pode usar o gráfico de dependências para: +You can use the dependency graph to: -- Explorar os repositórios dos quais o seu código depende{% ifversion fpt or ghec %} e aqueles que dependem dele{% endif %}. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% ifversion fpt or ghec %} -- Visualizar um resumo das dependências usadas nos repositórios da sua organização em um único painel. Para obter mais informações, consulte "[Visualizar informações na organização](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %} -- Ver e atualizar dependências vulneráveis no seu repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". {% ifversion fpt or ghes > 3.1 or ghec %} -- Veja as informações sobre dependências vulneráveis em pull requests. Para obter mais informações, consulte "[Revisar as alterações de dependências em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)".{% endif %} +- Explore the repositories your code depends on{% ifversion fpt or ghec %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% ifversion fpt or ghec %} +- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} +- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes > 3.1 or ghec %} +- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %} -## Habilitar o gráfico de dependências +## Enabling the dependency graph -{% ifversion fpt or ghec %}Para gerar um gráfico de dependência, o {% data variables.product.product_name %} precisa de acesso somente leitura ao manifesto dependência e aos arquivos de bloqueio em um repositório. O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% ifversion fpt or ghec %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% ifversion ghes or ghae %}Se o gráfico de dependências não estiver disponível no seu sistema, o proprietário da empresa poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} na sua conta corporativa](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} +{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} -Quando o gráfico de dependências é ativado pela primeira vez, todos manifesto e arquivos de bloqueio para ecossistemas suportados são analisados imediatamente. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Uma vez habilitado, o gráfico é atualizado automaticamente a cada push no repositório{% ifversion fpt or ghec %} e a cada push para outros repositórios no gráfico{% endif %}. +When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}. -## Ecossistemas de pacote compatíveis +## Supported package ecosystems -Os formatos recomendados definem explicitamente quais versões são usadas para todas as dependências diretas e indiretas. Se você usar esses formatos, seu gráfico de dependências será mais preciso. Ele também reflete a configuração da criação atual e permite que o gráfico de dependências relate vulnerabilidades em dependências diretas e indiretas.{% ifversion fpt or ghec %} As dependências indiretas, inferidas a partir de um arquivo de manifesto (ou equivalente), são excluídas das verificações de dependências vulneráveis.{% endif %} +The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% ifversion fpt or ghec %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} -| Gerenciador de pacotes | Idiomas | Formatos recomendados | Todos os formatos compatíveis | -| ---------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | +| Package manager | Languages | Recommended formats | All supported formats | +| --- | --- | --- | ---| +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | {%- ifversion fpt or ghes > 3.2 or ghae %} | Go modules | Go | `go.sum` | `go.mod`, `go.sum` | {%- elsif ghes = 3.2 %} | Go modules | Go | `go.mod` | `go.mod` | {%- endif %} -| Maven | Java, Scala | `pom.xml` | `pom.xml` | | npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| | Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | +| Maven | Java, Scala | `pom.xml` | `pom.xml` | +| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | {%- ifversion fpt or ghes > 3.3 %} -| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} | RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} -**Observação:** se você listar suas dependências de Python em um arquivo `setup.py`, será provável que não possamos analisar e listar cada dependência no seu projeto. +**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. {% endnote %} -## Leia mais +## Further reading -- "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia -- "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} -- "[Visualizar informações da sua organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} -- "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" +- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia +- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} +- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md index ddc4b14eb5..59a3cb1418 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md @@ -1,6 +1,6 @@ --- title: Codespaces lifecycle -intro: 'Você pode desenvolver em um ambiente {% data variables.product.prodname_codespaces %} e manter seus dados ao longo de todo o ciclo de vida do codespace.' +intro: 'You can develop in a {% data variables.product.prodname_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.' versions: fpt: '*' ghec: '*' @@ -11,37 +11,37 @@ topics: product: '{% data reusables.gated-features.codespaces %}' --- -## Sobre o ciclo de vida de um codespace +## About the lifecycle of a codespace -O ciclo de vida de um codespace começa quando você cria um código e termina quando você o exclui. Você pode desconectar-se e reconectar-se a um codespace ativo sem afetar seus processos em execução. Você pode parar e reiniciar o processo sem perder as alterações feitas no seu projeto. +The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project. -## Criar um codespace +## Creating a codespace -Quando você deseja trabalhar em um projeto, você pode optar por criar um novo codespaceou abrir um codespace já existente. Você deverá criar um novo codespace a partir de um branch do seu projeto toda vez que você desenvolver em {% data variables.product.prodname_codespaces %} ou mantiver um codespace de longo prazo para um recurso. +When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your project each time you develop in {% data variables.product.prodname_codespaces %} or keep a long-running codespace for a feature. -Se você escolher criar um novo codespace, sempre que você trabalhar em um projeto, você deverá fazer push das alterações regularmente para que todos os novos commits estejam em {% data variables.product.prodname_dotcom %}. Você pode ter até 10 codespaces por vez. Depois de ter 10 codespaces, você deverá excluir um codespace antes de criar um novo. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". +If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. You can have up to 10 codespaces at a time. Once you have 10 codespaces, you must delete a codespace before you can create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -Se você optar por usar um codespace de longo prazo para o seu projeto, você deverá retirá-lo do branch padrão do repositório cada vez que começar a trabalhar no seu codespace para que seu ambiente tenha os commits mais recentes. Esse fluxo de trabalho é muito parecido como se você estivesse trabalhando com um projeto na sua máquina local. +If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine. -## Salvar alterações em um codespace +## Saving changes in a codespace -Ao conectar-se a um código através da web, a gravação automática é habilitada automaticamente para o editor da web e configurada para salvar as alterações após um atraso. Ao conectar-se a um codespace por meio de {% data variables.product.prodname_vscode %} em execução no seu computador, você deverá habilitar o salvamento automático. Para obter mais informações, consulte [Salvar/Salvar Automaticamente](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) na documentação de {% data variables.product.prodname_vscode %}. +When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation. -Se você desejar salvar suas alterações no repositório do git no sistema de arquivos do codespace, faça commit e envio por push para um branch remoto. +If you want to save your changes in the git repository on the codespace's file system, commit them and push them to a remote branch. -Se você tiver alterações não salvas, seu editor solicitará que você as salve antes de sair. +If you have unsaved changes, your editor will prompt you to save them before exiting. -## Tempo limite de codespaces +## Codespaces timeouts -Se você não interagir com o seu codespace em execução ou se vocÊ sair do seu codespace sem pará-lo explicitamente, ele irá expirar após 30 minutos de inatividade e irá parar de executar. Para obter mais informações, consulte "[Parando um codespace](#stopping-a-codespace)". +If you leave your codespace running without interaction or if you exit your codespace without explicitly stopping it, the codespace will timeout after 30 minutes of inactivity and stop running. For more information, see "[Stopping a codespace](#stopping-a-codespace)." -Quando o tempo de um codespace chega ao limite, os seus dados são preservados da última vez que suas alterações foram salvas. Para obter mais informações, consulte "[Salvando alterações em um codespace](#saving-changes-in-a-codespace)". +When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)." -## Reconstruindo um codespace +## Rebuilding a codespace -Você pode recriar o seu codespace para restaurar um estado limpo, como se tivesse criado um novo codespace. Para a maioria dos usos, você pode criar um novo codespace como uma alternativa à reconstrução de um codespace. É muito provável que você reconstrua um codespace para implementar alterações no seu contêiner de desenvolvimento. Ao reconstruir um codespace, qualquer contêiner, imagens, volumes e caches serão limpos e o codespace será reconstruído. +You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt. -Se você precisar de algum desses dados para persistir em uma recriação, você poderá criar, no local desejado do contêiner, um link simbólico (symlink) para o diretório persistente. Por exemplo, no seu diretório `.devcontainer`, você poderá criar uma pasta `config` que será preservada durante uma recriação. Você pode vincular simbolicamente o diretório `config` e seu conteúdo como um `postCreateCommand` no seu arquivo de `devcontainer.json`. +If you need any of this data to persist over a rebuild, you can create, at the desired location in the container, a symbolic link (symlink) to the persistent directory. For example, in your `.devcontainer` directory, you can create a `config` directory that will be preserved across a rebuild. You can then symlink the `config` directory and its contents as a `postCreateCommand` in your `devcontainer.json` file. ```json { @@ -50,33 +50,33 @@ Se você precisar de algum desses dados para persistir em uma recriação, você } ``` -No exemplo do arquivo `postCreate.sh`abaixo, o conteúdo do diretório `config` são está simbolicamente vinculado ao diretório principal. +In the example `postCreate.sh` file below, the contents of the `config` directory are symbolically linked to the home directory. ```bash #!/bin/bash ln -sf $PWD/.devcontainer/config $HOME/config && set +x ``` -## Interrompendo um codespace +## Stopping a codespace -Você pode interromper um codespace a qualquer momento. Ao interromper um codespace, todos os processos em execução são interrompidos e o histórico de terminais é limpo. Qualquer alteração salva no seu codespace ainda estará disponível na próxima vez que você iniciá-lo. Se você não interromper explicitamente um codespace, ele continuará sendo executado até que o tempo seja esgotado em razão de inatividade. Para obter mais informações, consulte "[Tempo esgotado de codespaces](#codespaces-timeouts)". +You can stop a codespace at any time. When you stop a codespace, any running processes are stopped and the terminal history is cleared. Any saved changes in your codespace will still be available when you next start it. If you do not explicitly stop a codespace, it will continue to run until it times out from inactivity. For more information, see "[Codespaces timeouts](#codespaces-timeouts)." -Apenas os codespaces em execução implicam cobranças de CPU. Um codespace interrompido implica apenas custos de armazenamento. +Only running codespaces incur CPU charges; a stopped codespace incurs only storage costs. -Você deverá interromper e reiniciar um codespace para aplicar as alterações nele. Por exemplo, se você mudar o tipo de máquina usado no seu codespace, você deverá interromper e reiniciá-la para que a alteração seja implementada. Você também pode interromper o seu codespace e optar por reiniciá-lo ou excluí-lo se você encontrar um erro ou algo inesperado. Para obter mais informações, consulte "[Suspender ou interromper um codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)". +You may want to stop and restart a codespace to apply changes to it. For example, if you change the machine type used for your codespace, you will need to stop and restart it for the change to take effect. You can also stop your codespace and choose to restart or delete it if you encounter an error or something unexpected. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)." -## Excluir um codespace +## Deleting a codespace -Você pode criar um codespace para uma tarefa específica e, em seguida, excluir com segurança o codespace depois que você fizer push das alterações em um branch remoto. +You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch. -Se você tentar excluir um codespace com commits git que não foram enviados por push, o seu editor irá notificar você de que você tem alterações que não foram enviadas por push para um branch remoto. Você pode fazer push de todas as alterações desejadas e, em seguida, excluir o seu codespace ou continuar excluindo o seu codespace e todas as alterações que não foram enviadas por commit. Você também pode exportar seu codespace para um novo branch sem criar um novo codespace. Para obter mais informações, consulte "[ Exportando alterações para um branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)." +If you try to delete a codespace with unpushed git commits, your editor will notify you that you have changes that have not been pushed to a remote branch. You can push any desired changes and then delete your codespace, or continue to delete your codespace and any uncommitted changes. You can also export your code to a new branch without creating a new codespace. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)." -Você será cobrado pelo armazenamento de todos os seus codespaces. Ao excluir um codespace, você não será mais cobrado. +You will be charged for the storage of all your codespaces. When you delete a codespace, you will no longer be charged. -Para obter mais informações sobre exclusão de um codespace, consulte "[Excluindo um codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)". +For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)." -## Perdendo a conexão durante o uso de codespaces +## Losing the connection while using Codespaces -O {% data variables.product.prodname_codespaces %} é um ambiente de desenvolvimento baseado na nuvem e requer uma conexão à internet. Se você perder a conexão à internet enquanto trabalha em um codespace, você não poderá acessar seu codespace. No entanto, todas as alterações não comprometidas serão salvas. Quando você tiver acesso a uma conexão à internet novamente, você poderá conectar-se ao seu codespace no mesmo estado em que ele foi deixado. Se você tiver uma conexão instável, você deverá se fazer envio por commit e push das suas alterações com frequência. +{% data variables.product.prodname_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often. If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["{% data variables.product.prodname_vscode %} Remote - Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation. diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 00e037a555..6ee69270ff 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Excluir um codespace -intro: Você pode excluir um codespace de que você não precisa mais. +title: Deleting a codespace +intro: You can delete a codespace you no longer need. product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-github-codespaces/deleting-a-codespace @@ -21,44 +21,44 @@ topics: {% note %} -**Observação:** Somente a pessoa que criou um codespace pode excluí-lo. Atualmente, não há forma de os proprietários da organização excluírem os codespaces criados dentro de sua organização. +**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization. {% endnote %} {% include tool-switcher %} - + {% webui %} -1. Acesse a página "Seus codespaces" em [github.com/codespaces](https://github.com/codespaces). +1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces). -2. À direita do código que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, depois em **{% octicon "trash" aria-label="The trash icon" %} Apagar** +2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** - ![Botão excluir](/assets/images/help/codespaces/delete-codespace.png) + ![Delete button](/assets/images/help/codespaces/delete-codespace.png) {% endwebui %} - + {% vscode %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} {% endvscode %} - + {% cli %} {% data reusables.cli.cli-learn-more %} -Para excluir um codespace, use o comando `gh codespace delete` e, em seguida, escolha um codespace na lista que for exibida. +To delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed. ```shell gh codespace delete ``` -Se você tiver alterações não salvas, será solicitado que você confirme a exclusão. Você pode usar o sinalizador `-f` para forçar a exclusão, evitando a instrução. +If you have unsaved changes, you'll be prompted to confirm deletion. You can use the `-f` flag to force deletion, avoiding this prompt. -Para obter mais informações sobre esse comando, consulte [o manual de{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_delete). +For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete). {% endcli %} -## Leia mais +## Further reading - [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle) diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index e25223f842..2f9f4c0cdc 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,6 +1,6 @@ --- -title: Usar espaços de código no Visual Studio Code -intro: 'Você pode desenvolver seu codespace diretamente em {% data variables.product.prodname_vscode %}, conectando a extensão de {% data variables.product.prodname_github_codespaces %} à sua conta no {% data variables.product.product_name %}.' +title: Using Codespaces in Visual Studio Code +intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code @@ -18,81 +18,81 @@ shortTitle: Visual Studio Code --- -## Sobre {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %} +## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} -Você pode usar sua instalação local de {% data variables.product.prodname_vscode %} para criar, gerenciar, trabalhar e excluir codespaces. Para usar {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}, você deverá instalar a extensão de {% data variables.product.prodname_github_codespaces %}. Para obter mais informações sobre a configuração de codespaces em {% data variables.product.prodname_vscode %}, consulte "[pré-requisitos](#prerequisites)". +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)." -Por padrão, se você criar um novo codespace em {% data variables.product.prodname_dotcom_the_website %}, ele será aberto no navegador. Se você preferir abrir qualquer codespace novo em {% data variables.product.prodname_vscode %} automaticamente, você pode definir seu editor padrão como {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Definindo seu editor padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)". +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -Se você preferir trabalhar no navegador, mas deseja continuar usando suas extensões de {% data variables.product.prodname_vscode %} temas e atalhos existentes, você poderá ativar as Configurações Sincronizadas. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." -## Pré-requisitos +## Prerequisites -Para desenvolver-se em uma plataforma de codespace diretamente em {% data variables.product.prodname_vscode %}, você deverá instalar e efetuar o login na extensão {% data variables.product.prodname_github_codespaces %} com as suas credenciais de {% data variables.product.product_name %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode %}. +To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. -Use o {% data variables.product.prodname_vs %} Marketplace para instalar a extensão [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}. +Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. {% mac %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_dotcom %}...**. +2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. - ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) + ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. -4. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. +3. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +4. Sign in to {% data variables.product.product_name %} to approve the extension. {% endmac %} {% windows %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Utilize o menu suspenso "EXPLORADOR REMOTO" e clique em **{% data variables.product.prodname_github_codespaces %}**. +2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. - ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) + ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_codespaces %}...**. +3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. - ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) + ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. -5. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. +4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +5. Sign in to {% data variables.product.product_name %} to approve the extension. {% endwindows %} -## Criar um codespace em {% data variables.product.prodname_vscode %} +## Creating a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Abrir um codespace em {% data variables.product.prodname_vscode %} +## Opening a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Em "Codedespaces", clique no código que você deseja desenvolver. -3. Clique no ícone Conectar-se ao Codespace. +2. Under "Codespaces", click the codespace you want to develop in. +3. Click the Connect to Codespace icon. - ![Ícone de conectar-se a um Codespace em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Alterar o tipo da máquina em {% data variables.product.prodname_vscode %} +## Changing the machine type in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.codespaces-machine-types %} -Você pode alterar o tipo de máquina do seu codespace a qualquer momento. +You can change the machine type of your codespace at any time. -1. Em {% data variables.product.prodname_vscode %}, abra a Paleta de Comando (`shift comando P` / `shift control P`). -2. Pesquise e selecione "Codespaces: Alterar tipo de máquina." +1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). +2. Search for and select "Codespaces: Change Machine Type." - ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) + ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Clique no codespace que você deseja alterar. +3. Click the codespace that you want to change. - ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) + ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Escolha o tipo de máquina que você quer usar. +4. Choose the machine type you want to use. -Se o codespace estiver sendo executado, será exibida uma mensagem perguntando se você deseja reiniciar e reconectar-se ao seu codespace agora. Clique em **Sim** se desejar mudar o tipo de máquina utilizado para este codespace imediatamente. Se você clicar em **Não**, ou se o código não estiver em execução, a alteração entrará em vigor na próxima vez que o codespace for reiniciado. +If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. -## Excluir um codespace em {% data variables.product.prodname_vscode %} +## Deleting a codespace in {% data variables.product.prodname_vscode %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} @@ -100,8 +100,8 @@ Se o codespace estiver sendo executado, será exibida uma mensagem perguntando s You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. -1. Na parte inferior esquerda da sua janela {% data variables.product.prodname_codespaces %}, selecione **Configurações de {% octicon "gear" aria-label="The settings icon" %}**. -2. Na lista, selecione "Alternar para Versão de Insiders". +1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**. +2. From the list, select "Switch to Insiders Version". ![Clicking on "Insiders Build" in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-insiders-vscode.png) 3. Once selected, {% data variables.product.prodname_codespaces %} will continue to open in Insiders Version. diff --git a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md index c9c1e1ba9e..341f4d1d3d 100644 --- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md +++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md @@ -1,6 +1,6 @@ --- -title: Aprofundamento nos codespaces -intro: 'Entender o funcionamento do {% data variables.product.prodname_codespaces %};' +title: Deep dive into Codespaces +intro: 'Understand how {% data variables.product.prodname_codespaces %} works.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -11,30 +11,30 @@ topics: - Codespaces --- -{% data variables.product.prodname_codespaces %} é um ambiente de desenvolvimento instantâneo e baseado na nuvem que usa um recipiente para fornecer linguagens, ferramentas e utilitários de desenvolvimento comuns. {% data variables.product.prodname_codespaces %} também é configurável, o que permite que você crie um ambiente de desenvolvimento personalizado para o seu projeto. Ao configurar um ambiente de desenvolvimento personalizado para seu projeto, você pode ter uma configuração de código reproduzível para todos os usuários do seu projeto. +{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. -## Criando seu codespace +## Creating your codespace -Há uma série de pontos de entrada para criar um codespace. +There are a number of entry points to create a codespace. -- Do seu repositório para um novo recurso funcionar. -- De um pull request aberto para explorar o trabalho em andamento. -- De um commit no histórico do repositório para investigar um erro em um momento específico. -- De {% data variables.product.prodname_vscode %}. +- From your repository for new feature work. +- From an open pull request to explore work-in-progress. +- From a commit in the repository's history to investigate a bug at a specific point in time. +- From {% data variables.product.prodname_vscode %}. + +Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -Seu codespace pode ser efêmero se você tiver de fazer algum teste ou você pode retornar ao mesmo codespace para fazer um trabalho de recurso de longo prazo. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". +Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you. -Depois de selecionar a opção de criar um novo codespace, algumas etapas são executadas em segundo plano antes que o codespace esteja disponível para você. +![Open with Codespaces button](/assets/images/help/codespaces/new-codespace-button.png) -![Botão de abrir com codespaces](/assets/images/help/codespaces/new-codespace-button.png) +### Step 1: VM and storage are assigned to your codespace -### Etapa 1: A VM e o armazenamento são atribuídos ao seu codespace +When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. -Ao criar um codespace, cria-se [clone superficial](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) do seu repositório em uma máquina virtual Linux dedicada e exclusiva para você. Ter uma VM dedicada garante que você tenha todo o conjunto de recursos de computação daquela máquina disponível para você. Se necessário, isso também permite que você tenha acesso total à raiz do seu contêiner. +### Step 2: Container is created -### Etapa 2: O contêiner foi criado - -{% data variables.product.prodname_codespaces %} usa um contêiner como ambiente de desenvolvimento. Este contêiner foi criado com base nas configurações que você pode definir em um arquivo `devcontainer.json` e/ou arquivo Docker no seu repositório. Se você não [configurar um contêiner](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} usará uma [imagem padrão](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), que tem muitas linguages e tempos de execução disponíveis. Para obter informações sobre o que a imagem padrão contém, consulte o repositório [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux). +{% data variables.product.prodname_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't [configure a container](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} uses a [default image](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), which has many languages and runtimes available. For information on what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. {% note %} @@ -44,76 +44,76 @@ Since your repository is cloned onto the host VM before the container is created {% endnote %} -### Etapa 3: Conectando-se ao codespace +### Step 3: Connecting to the codespace -Quando seu contêiner for criado e qualquer outra inicialização for executada, você estará conectado ao seu codespace. Você pode conectar-se por meio da web ou via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), ou ambos, se necessário. +When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. -### Passo 4: Configuração de pós-criação +### Step 4: Post-creation setup Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. -If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)". +If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)." -Por fim, toda a história do repositório é copiada com um clone completo. +Finally, the entire history of the repository is copied down with a full clone. -Durante a configuração de pós-criação, você ainda poderá usar o terminal integrado e fazer edições nos seus arquivos, mas tenha cuidado para evitar quaisquer condições de corrida entre seu trabalho e os comandos que estão sendo executados. -## Ciclo de vida de {% data variables.product.prodname_codespaces %} +During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running. +## {% data variables.product.prodname_codespaces %} lifecycle -### Salvando arquivos no seu codespace +### Saving files in your codespace -À medida que você desenvolve no seu codespace, ele salvará todas as alterações nos seus arquivos a cada poucos segundos. Seu codespace continuará em execução por 30 minutos após a última atividade. Depois desse tempo ele irá parar de executar, mas você poderá reiniciá-lo a partir da aba do navegador existente ou da lista de codespaces existentes. As mudanças de arquivo do editor e saída terminal são contadas como atividade. Portanto, o seu código não parará se a saída do terminal continuar. +As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing. {% note %} -**Observação:** As mudanças em um codespace em {% data variables.product.prodname_vscode %} não são salvas automaticamente, a menos que você tenha habilitado o [Salvamento automático](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). {% endnote %} -### Fechando ou interrompendo seu codespace +### Closing or stopping your codespace -To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). Se você sair do seu codespace sem executar o comando de interrupção (por exemplo, fechando a aba do navegador), ou se você sair do codespace em execução sem interação, o codespace e os seus processos em execução continuarão até que ocorra uma janela de inatividade, após a qual o código será interrompido. Por padrão, a janela de inatividade é de 30 minutos. +To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop. By default, the window of inactivity is 30 minutes. -Ao fechar ou interromper o seu codespace, todas as alterações não autorizadas são preservadas até você conectar-se ao codespace novamente. +When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again. -## Executando seu aplicativo +## Running your application -O redirecionamento de porta dá acesso a portas TCP que estão em execução no seu codespace. Por exemplo, se você estiver executando um aplicativo web na porta 4000 dentro do seu codespace, você poderá encaminhar automaticamente a porta para tornar o aplicativo acessível a partir do seu navegador. +Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser. -O encaminhamento de portas determina quais portas podem ser acessadas por você a partir da máquina remota. Mesmo que você não encaminhe uma porta, esse porta ainda poderá ser acessada para outros processos em execução dentro do próprio codespace. +Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself. -![Diagrama que mostra como funciona o encaminhamento de porta em um codespace](/assets/images/help/codespaces/port-forwarding.png) +![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png) -Quando um aplicativo em execução dentro de {% data variables.product.prodname_codespaces %} produz uma porta para o console, {% data variables.product.prodname_codespaces %} detecta o padrão da URL do host local e encaminha a porta automaticamente. Você pode clicar na URL no terminal ou na mensagem de alerta para abrir a porta em um navegador. By default, {% data variables.product.prodname_codespaces %} forwards the port using HTTP. Para obter mais informações sobre o encaminhamento de portas, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". +When an application running inside {% data variables.product.prodname_codespaces %} outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal or in the toast message to open the port in a browser. By default, {% data variables.product.prodname_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." -Embora as portas possam ser encaminhadas automaticamente, elas não podem ser acessadas pelo público na internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)." +While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)." -A execução do seu aplicativo ao chegar pela primeira vez no seu codespace pode fazer um loop de desenvolvimento rápido interno. À medida que você edita, as alterações são salvas automaticamente e ficam disponíveis na sua porta encaminhada. Para visualizar as alterações, volte para a aba do aplicativo em execução no seu navegador e atualize-as. +Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it. -## Enviando e fazendo push das suas alterações +## Committing and pushing your changes -O Git está disponível por padrão no seu codespace. Portanto, você pode confiar no fluxo de trabalho do Git existente. Você pode trabalhar com o Git no seu codespace por meio do Terminal ou usando a interface de usuário do controle de origem do [do Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol). Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" -![Executando o status do git no terminal do codespaces](/assets/images/help/codespaces/git-status.png) +![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) -Você pode criar um codespace a partir de qualquer branch, commit ou pull request no seu projeto, ou você pode mudar para branch novo branch ou branch existente de dentro do seu codespace ativo. Uma vez que {% data variables.product.prodname_codespaces %} foi projetado para ser efêmero, você pode usá-lo como um ambiente isolado para experimentar, verificar o pull request de um amigo de equipe ou corrigir os conflitos de merge. Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. No entanto, cada conta de usuário tem um limite de 10 codespaces. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código. +You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. You can create more than one codespace per repository or even per branch. However, each user account has a limit of 10 codespaces. If you've reached the limit and want to create a new codespace, you must delete a codespace first. {% note %} -**Observação:** Os commits do seu codespace serão atribuídos ao nome e ao e-mail público configurado em https://github.com/settings/profile. Um token com escopo no repositório, incluído no ambiente como `GITHUB_TOKEN`, e as suas credenciais do GitHub serão usadas para efetuar a autenticação. +**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate. {% endnote %} -## Personalizando seu codespace com extensões +## Personalizing your codespace with extensions -Usar {% data variables.product.prodname_vscode %} no seu codespace dá acesso ao Marketplace de {% data variables.product.prodname_vscode %} para que você possa adicionar todas as extensões de que precisar. Para obter informações de como as extensões são executadas em {% data variables.product.prodname_codespaces %}, consulte [Suporte ao Desenvolvimento Remoto e aos codespaces do GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) na documentação de {% data variables.product.prodname_vscode %}. +Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. -Se você já usa o {% data variables.product.prodname_vscode %}, você pode usar as [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automaticamente as extensões, configurações, temas, e atalhos de teclado entre sua instância local e todos {% data variables.product.prodname_codespaces %} que você criar. +If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. -## Leia mais +## Further reading -- [Habilitando {% data variables.product.prodname_codespaces %} para a sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Gerenciando a cobrança para {% data variables.product.prodname_codespaces %} na sua organização](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) -- [Configurando seu projeto para os codespaces](/codespaces/setting-up-your-project-for-codespaces) +- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [Setting up your project for Codespaces](/codespaces/setting-up-your-project-for-codespaces) - [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle) diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index 204b25b812..10088f39bd 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -1,7 +1,7 @@ --- -title: Gerenciando o acesso ao repositório para os codespaces da sua organização -shortTitle: Acesso ao repositório -intro: 'Você pode gerenciar os repositórios na sua organização que {% data variables.product.prodname_codespaces %} pode acessar.' +title: Managing repository access for your organization's codespaces +shortTitle: Repository access +intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' versions: @@ -18,16 +18,18 @@ redirect_from: - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces --- -Por padrão, um codespace só pode acessar o repositório onde foi criado. Ao habilitar o acesso e a segurança de um repositório pertencente à sua organização, todos os codespaces que forem criados para esse repositório também terão permissões de leitura e gravação para todos os outros repositórios que a organização possui e o criador de codespace terá permissões para acessar. Se você deseja restringir os repositórios que um codespace pode acessar, você pode limitá-lo ao repositório em que o codespace foi criado ou a repositórios específicos. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia. +By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. -Para gerenciar quais usuários na sua organização podem usar {% data variables.product.prodname_codespaces %}, consulte "[Gerenciar permissões de usuário para a sua organização](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)". +To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} -1. Em "Acesso e segurança", selecione a configuração que você deseja para a sua organização. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para permitir que os codespaces do repositório acessem outros repositórios pertencentes à sua organização. Repita isso para todos os repositórios cujos códigos você deseja que acessem outros repositórios. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) +1. Under "Access and security", select the setting you want for your organization. + ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. + !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) -## Leia mais +## Further Reading -- "[Gerenciando acesso ao repositório para seus codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md index 58cba03194..9d91fc58fd 100644 --- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md +++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md @@ -1,6 +1,6 @@ --- -title: Desbloquear usuários da organização -intro: 'Os proprietários da organização podem desbloquear um usuário que tenha sido bloqueado anteriormente, restaurando o acesso dele aos repositórios da organização.' +title: Unblocking a user from your organization +intro: 'Organization owners can unblock a user who was previously blocked, restoring their access to the organization''s repositories.' redirect_from: - /articles/unblocking-a-user-from-your-organization - /github/building-a-strong-community/unblocking-a-user-from-your-organization @@ -9,36 +9,38 @@ versions: ghec: '*' topics: - Community -shortTitle: Desbloquear a partir do seu org +shortTitle: Unblock from your org --- -O desbloqueio de um usuário da organização permite que ele continue contribuindo para os repositórios da organização. +After unblocking a user from your organization, they'll be able to contribute to your organization's repositories. -Se você tiver selecionado uma duração para o bloqueio do usuário, ele será automaticamente desbloqueado quando esse tempo acabar. Para obter mais informações, consulte "[Bloquear um usuário em sua organização](/articles/blocking-a-user-from-your-organization)". +If you selected a specific amount of time to block the user, they will be automatically unblocked when that period of time ends. For more information, see "[Blocking a user from your organization](/articles/blocking-a-user-from-your-organization)." {% tip %} -**Dica**: as configurações que tenham sido removidas durante o bloqueio do usuário na organização (como status de colaborador, estrelas e inspeções) não são restauradas quando você desbloqueia o usuário. +**Tip**: Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user. {% endtip %} -## Desbloquear usuários em um comentário +## Unblocking a user in a comment -1. Navegue até o comentário cujo autor você deseja desbloquear. -2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e depois em **Unblock user** (Desbloquear usuário). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando a opção unblock user (desbloquear usuário)](/assets/images/help/repository/comment-menu-unblock-user.png) -3. Para confirmar que você deseja desbloquear o usuário, clique em **OK**. +1. Navigate to the comment whose author you would like to unblock. +2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock user**. +![The horizontal kebab icon and comment moderation menu showing the unblock user option](/assets/images/help/repository/comment-menu-unblock-user.png) +3. To confirm you would like to unblock the user, click **Okay**. -## Desbloquear usuários nas configurações da organização +## Unblocking a user in the organization settings {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -{% data reusables.organizations.block_users %} -5. Em "Blocked users" (Usuários bloqueados), clique em **Unblock** (Desbloquear) próximo ao usuário que deseja desbloquear. ![Botão Unblock user (Desbloquear usuário)](/assets/images/help/organizations/org-unblock-user-button.png) +{% data reusables.organizations.moderation-settings %} +5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**. +![Unblock user button](/assets/images/help/organizations/org-unblock-user-button.png) -## Leia mais +## Further reading -- "[Bloquear usuários da organização](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)" -- "[Bloquear usuários da sua conta pessoal](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)" -- "[Desbloquear usuários da sua conta pessoal](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)" -- "[Denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)" +- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)" +- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)" +- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)" +- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)" diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md deleted file mode 100644 index fd381c3966..0000000000 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md +++ /dev/null @@ -1,281 +0,0 @@ ---- -title: Sintaxe para o esquema de formulário do GitHub -intro: 'Você pode usar o esquema de formulário de {% data variables.product.company_short %} para configurar formulários para funcionalidades compatíveis.' -versions: - fpt: '*' - ghec: '*' -miniTocMaxHeadingLevel: 3 -topics: - - Community ---- - -{% note %} - -**Observação:** O esquema de formulário de {% data variables.product.company_short %} encontra-se atualmente na versão beta e está sujeito a alterações. - -{% endnote %} - -## Sobre o esquema de formulário de {% data variables.product.company_short %} - -Você pode usar o esquema de formulário de {% data variables.product.company_short %} para configurar formulários para funcionalidades compatíveis. Para obter mais informações, consulte "[Configurando modelos de problema para seu repositório](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)." - -Um formulário é um conjunto de elementos que solicita a entrada do usuário. Você pode configurar um formulário criando uma definição de formulário YAML, que é uma matriz de elementos de formulário. Cada elemento de formulário é um conjunto de par chave-valor que determina o tipo do elemento, as propriedades do elemento e as restrições que você deseja aplicar ao elemento. Para algumas chaves, o valor é outro conjunto de pares de chave-valor. - -Por exemplo, a definição de formulário a seguir inclui quatro elementos de formulário: uma área de texto para fornecer o sistema operacional do usuário, um menu suspenso para escolher a versão de software que o usuário está executando, uma caixa de seleção para reconhecer o Código de Conduta e Markdown que agradece ao usuário por ter preenchido o formulário. - -```yaml{:copy} -- type: textarea - attributes: - label: Operating System - description: What operating system are you using? - placeholder: Example: macOS Big Sur - value: operating system - validations: - required: true -- type: dropdown - attributes: - label: Version - description: What version of our software are you running? - multiple: false - options: - - label: 1.0.2 (Default) - - label: 1.0.3 (Edge) - validations: - required: true -- type: checkboxes - attributes: - label: Code of Conduct - description: The Code of Conduct helps create a safe space for everyone. Nós exigimos - que todos concordem com isso. - options: - - label: I agree to follow this project's [Code of Conduct](link/to/coc) - required: true -- type: markdown - attributes: - value: "Thanks for completing our form!" -``` - -## Chaves - -Para cada elemento de formulário, você pode definir as seguintes chaves. - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------ | ----------------------------------------------- | ----------------------------------------------- | -| `tipo` | O tipo de elemento que você deseja definir. | Obrigatório | string | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | -| `id` | O identificador para o elemento, exceto quando `tipo` é definido como `markdown`. {% data reusables.form-schema.id-must-be-unique %} Se fornecido, o `ID` é o identificador canônico para o campo no parâmetro de consulta da URL. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `attributes` | Um conjunto de pares chave-valor que definem as propriedades do elemento. | Obrigatório | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `validações` | Um conjunto de pares chave-valor que define restrições sobre o elemento. | Opcional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} - -Você pode escolher entre os seguintes tipos de elementos de formulário. Cada tipo tem atributos e validações exclusivos. - -| Tipo | Descrição | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -| [`markdown`](#markdown) | O texto do markdown exibido no formulário para fornecer um contexto adicional ao usuário, mas **não é enviado**. | -| [`textarea`](#textarea) | Um campo de texto linha múltipla. | -| [`entrada`](#input) | Um campo de texto de linha única. | -| [`suspenso`](#dropdown) | Um menu suspenso. | -| [`caixas de seleção`](#checkboxes) | Um conjunto de caixas de seleção. | - -### `markdown` - -Você pode usar um elemento    markdown` para exibir o markdown no seu formulário que fornece contexto extra para o usuário, mas não é enviado.

    - -

    Atributos

    - -

    {% data reusables.form-schema.attributes-intro %}

    - - - - - - - - - - - - - - - - -
    TeclaDescriçãoObrigatórioTipoPadrãoValores válidos
    valor`
    - -{% tip %} - -**Dicas:** O processamento do YAML tratará o símbolo hash como um comentário. Para inserir cabeçalhos do Markdown, coloque seu texto entre aspas. - -Para texto de linhas múltiplas, você pode usar o operador de pipe. - -{% endtip %} - -#### Exemplo - -```YAML{:copy} -body: -- type: markdown - value: "## Thank you for contributing to our project!" -- type: markdown - attributes: - value: | - Thanks for taking the time to fill out this bug report. -``` - -### `textarea` - -Você pode usar um elemento `textarea` para adicionar um campo de texto de linha múltipla ao seu formulário. Os colaboradores também podem anexar arquivos aos campos `textarea`. - -#### Atributos - -{% data reusables.form-schema.attributes-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------ | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `etiqueta` | Uma breve descrição da entrada esperada do usuário, que também é exibida no formulário. | Obrigatório | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descrição` | Uma descrição da área de texto para fornecer contexto ou orientação, que é exibida no formulário. | Opcional | string | String vazia | {% octicon "dash" aria-label="The dash icon" %} -| `espaço reservado` | Um marcador semi-opaco interpretado na área de texto quando vazio. | Opcional | string | String vazia | {% octicon "dash" aria-label="The dash icon" %} -| `valor` | Texto pré-preenchido na área de texto. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `render` | Se um valor for fornecido, o texto enviado será formatado de bloco de código. Quando esta chave é fornecida, a área de texto não será expandida para anexos de arquivos ou edição de markdown. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | Linguagens conhecidas para {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte [o arquivo de linguagens do YAML](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | - -#### Validações - -{% data reusables.form-schema.validations-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ----- | --------- | ----------- | ---- | ------ | --------------- | -| | | | | | | -{% data reusables.form-schema.required-key %} - -#### Exemplo - -```YAML{:copy} -body: -- type: textarea - id: repro - attributes: - label: Reproduction steps - description: "How do you trigger this bug? Apresente-nos o passo a passo." - value: | - 1. - 2. - 3. - ... - render: bash - validations: - required: true -``` - -### `entrada` - -Você pode usar um elemento de `entrada` para adicionar um campo de texto de linha única ao seu formulário. - -#### Atributos - -{% data reusables.form-schema.attributes-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ------------------ | ----------------------------------------------------------------------------------------- | ----------- | ------ | ----------------------------------------------- | ----------------------------------------------- | -| `etiqueta` | Uma breve descrição da entrada esperada do usuário, que também é exibida no formulário. | Obrigatório | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descrição` | Uma descrição do campo para fornecer contexto ou orientação, que é exibida no formulário. | Opcional | string | String vazia | {% octicon "dash" aria-label="The dash icon" %} -| `espaço reservado` | Um espaço reservado semitransparente interpretado no campo quando vazio. | Opcional | string | String vazia | {% octicon "dash" aria-label="The dash icon" %} -| `valor` | Texto pré-preenchido no campo. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} - -#### Validações - -{% data reusables.form-schema.validations-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ----- | --------- | ----------- | ---- | ------ | --------------- | -| | | | | | | -{% data reusables.form-schema.required-key %} - -#### Exemplo - -```YAML{:copy} -body: -- type: input - id: prevalence - attributes: - label: Bug prevalence - description: "How often do you or others encounter this bug?" - placeholder: "Example: Whenever I visit the user account page (1-2 times a week)" - validations: - required: true -``` - -### `suspenso` - -Você pode usar um elemento de `dropdown` para adicionar um menu suspenso ao seu formulário. - -#### Atributos - -{% data reusables.form-schema.attributes-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ----------- | --------------------------------------------------------------------------------------------------------------- | ----------- | ---------------- | ----------------------------------------------- | ----------------------------------------------- | -| `etiqueta` | Uma breve descrição da entrada esperada do usuário, que é exibida no formulário. | Obrigatório | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descrição` | Uma descrição do menu suspenso para fornecer contexto ou orientação extra, que é exibida no formulário. | Opcional | string | String vazia | {% octicon "dash" aria-label="The dash icon" %} -| `múltiplo` | Determina se o usuário pode selecionar mais de uma opção. | Opcional | Booleano | falso | {% octicon "dash" aria-label="The dash icon" %} -| `options` | Uma matriz de opções que o usuário pode escolher. Não pode estar vazio e todas as escolhas devem ser distintas. | Obrigatório | String da matriz | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} - -#### Validações - -{% data reusables.form-schema.validations-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ----- | --------- | ----------- | ---- | ------ | --------------- | -| | | | | | | -{% data reusables.form-schema.required-key %} - -#### Exemplo - -```YAML{:copy} -body: -- type: dropdown - id: download - attributes: - label: How did you download the software? - options: - - Homebrew - - MacPorts - - apt-get - - Built from source - validations: - required: true -``` - -### `caixas de seleção` - -Você pode usar o elemento `checkboxes` para adicionar um conjunto de caixas de seleção ao seu formulário. - -#### Atributos - -{% data reusables.form-schema.attributes-intro %} - -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ----------- | ----------------------------------------------------------------------------------------------------------------------- | ----------- | ------ | ----------------------------------------------- | ----------------------------------------------- | -| `etiqueta` | Uma breve descrição da entrada esperada do usuário, que é exibida no formulário. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descrição` | Uma descrição do conjunto de caixas de seleção, que é exibida no formulário. É compatível com a formatação de markdown. | Opcional | string | String vazia | {% octicon "dash" aria-label="The dash icon" %} -| `options` | Uma matriz de caixas de seleção que o usuário pode selecionar. Para a sintaxe, veja abaixo. | Obrigatório | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} - -{% data reusables.form-schema.options-syntax %} -{% data reusables.form-schema.required-key %} - -#### Exemplo - -```YAML{:copy} -body: -- type: checkboxes - id: operating-systems - attributes: - label: Which operating systems have you used? - description: You may select more than one. - options: - - label: macOS - - label: Windows - - label: Linux -``` - -## Leia mais - -- [YAML](https://yaml.org) diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md index 61a12cf696..e2f50add97 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md @@ -1,6 +1,6 @@ --- -title: Gerenciar branches -intro: Você pode criar um branch fora do branch-padrão de um repositório para poder experimentar as alterações com segurança. +title: Managing branches +intro: You can create a branch off of a repository's default branch so you can safely experiment with changes. redirect_from: - /desktop/contributing-to-projects/creating-a-branch-for-your-work - /desktop/contributing-to-projects/switching-between-branches @@ -9,112 +9,115 @@ redirect_from: versions: fpt: '*' --- +## About managing branches +You can use branches to safely experiment with changes to your project. Branches isolate your development work from other branches in the repository. For example, you could use a branch to develop a new feature or fix a bug. -## Sobre o gerenciamento de branches -Você pode usar os branches para experimentar com segurança as alterações no seu projeto. Os branches isolam seu trabalho de desenvolvimento de outros branches do repositório. Por exemplo, você poderia usar um branch para desenvolver um novo recurso ou corrigir um erro. +You always create a branch from an existing branch. Typically, you might create a branch from the default branch of your repository. You can then work on this new branch in isolation from changes that other people are making to the repository. -Você sempre cria um branch a partir de um branch existente. Normalmente, você pode criar um branch a partir do branch-padrão do seu repositório. Você então poderá trabalhar nesse novo branch isolado das mudanças que outras pessoas estão fazendo no repositório. +You can also create a branch starting from a previous commit in a branch's history. This can be helpful if you need to return to an earlier view of the repository to investigate a bug, or to create a hot fix on top of your latest release. -Você também pode criar um branch a partir de um commit anterior no histórico de um branch. Isso pode ser útil se você precisar retornar a uma visão anterior do repositório para investigar um erro ou para criar uma correção em cima de sua versão mais recente. +Once you're satisfied with your work, you can create a pull request to merge your changes in the current branch into another branch. For more information, see "[Creating an issue or pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" and "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Quando estiver satisfeito com seu trabalho, você poderá criar um pull request para fazer merge nas suas alterações no branch atual em outro branch. For more information, see "[Creating an issue or pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" and "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." - -É sempre possível criar um branch no {% data variables.product.prodname_desktop %}, se tiver acesso de leitura a um repositório, mas você só pode fazer push do branch para o {% data variables.product.prodname_dotcom %} se você tiver acesso de gravação no repositório. +You can always create a branch in {% data variables.product.prodname_desktop %} if you have read access to a repository, but you can only push the branch to {% data variables.product.prodname_dotcom %} if you have write access to the repository. {% data reusables.desktop.protected-branches %} -## Criar um branch +## Creating a branch {% tip %} -**Dica:** O primeiro branch que você criar será baseado no branch-padrão. Se você tiver mais de um branch, você pode escolher basear o novo branch no branch atualmente verificado ou no branch-padrão. +**Tip:** The first new branch you create will be based on the default branch. If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch. {% endtip %} {% mac %} {% data reusables.desktop.click-base-branch-in-drop-down %} - ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/select-branch-from-dropdown.png) + ![Drop-down menu to switch your current branch](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.create-new-branch %} - ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-mac.png) + ![New Branch option in the Branch menu](/assets/images/help/desktop/new-branch-button-mac.png) {% data reusables.desktop.name-branch %} - ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-mac.png) + ![Field for creating a name for the new branch](/assets/images/help/desktop/create-branch-name-mac.png) {% data reusables.desktop.select-base-branch %} - ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-mac.png) + ![Base branch options](/assets/images/help/desktop/create-branch-choose-branch-mac.png) {% data reusables.desktop.confirm-new-branch-button %} - ![Botão Create Branch (Criar branch)](/assets/images/help/desktop/create-branch-button-mac.png) + ![Create Branch button](/assets/images/help/desktop/create-branch-button-mac.png) {% endmac %} {% windows %} {% data reusables.desktop.click-base-branch-in-drop-down %} - ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down-win.png) + ![Drop-down menu to switch your current branch](/assets/images/help/desktop/click-branch-in-drop-down-win.png) {% data reusables.desktop.create-new-branch %} - ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-win.png) + ![New Branch option in the Branch menu](/assets/images/help/desktop/new-branch-button-win.png) {% data reusables.desktop.name-branch %} - ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-win.png) + ![Field for creating a name for the new branch](/assets/images/help/desktop/create-branch-name-win.png) {% data reusables.desktop.select-base-branch %} - ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-win.png) + ![Base branch options](/assets/images/help/desktop/create-branch-choose-branch-win.png) {% data reusables.desktop.confirm-new-branch-button %} - ![Botão Create branch (Criar branch)](/assets/images/help/desktop/create-branch-button-win.png) + ![Create branch button](/assets/images/help/desktop/create-branch-button-win.png) {% endwindows %} -## Criando um branch de um commit anterior +## Creating a branch from a previous commit {% data reusables.desktop.history-tab %} -2. Clique com o botão direito no commit a partir do qual você gostaria de criar um novo branch e selecione **Criar Branch a partir de Commit**. ![Criar branch a partir do menu de contexto de commit](/assets/images/help/desktop/create-branch-from-commit-context-menu.png) +2. Right-click on the commit you would like to create a new branch from and select **Create Branch from Commit**. + ![Create branch from commit context menu](/assets/images/help/desktop/create-branch-from-commit-context-menu.png) {% data reusables.desktop.name-branch %} {% data reusables.desktop.confirm-new-branch-button %} - ![Criar branch a partir do commit](/assets/images/help/desktop/create-branch-from-commit-overview.png) + ![Create branch from commit](/assets/images/help/desktop/create-branch-from-commit-overview.png) -## Publicar um branch +## Publishing a branch -Se você criar um branch no {% data variables.product.product_name %}, você deverá publicá-lo para disponibilizá-lo para colaboração no {% data variables.product.prodname_dotcom %}. +If you create a branch on {% data variables.product.product_name %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.prodname_dotcom %}. -1. Na parte superior do aplicativo, clique em {% octicon "git-branch" aria-label="The branch icon" %} **Branch atual** e, em seguida, clique no branch que você deseja publicar. ![Menu suspenso para selecionar qual branch publicar](/assets/images/help/desktop/select-branch-from-dropdown.png) -2. Clique em **Publicar branch**. ![Botão de publicar branch](/assets/images/help/desktop/publish-branch-button.png) +1. At the top of the app, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to publish. + ![Drop-down menu to select which branch to publish](/assets/images/help/desktop/select-branch-from-dropdown.png) +2. Click **Publish branch**. + ![The Publish branch button](/assets/images/help/desktop/publish-branch-button.png) -## Alternar entre branches -É possível exibir e fazer commits em qualquer branch do seu repositório. Se houver alterações salvas sem commit, você terá que decidir o que fazer com elas antes de poder alternar entre os branches. Você pode fazer o commit das alterações no branch atual, ocultar as suas alterações para salvá-las temporariamente no branch atual ou trazer as mudanças para seu novo branch. Se você deseja confirmar suas alterações antes de alternar os branches, consulte "[Fazer commit e revisar as alterações do seu projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)." +## Switching between branches +You can view and make commits to any of your repository's branches. If you have uncommitted, saved changes, you'll need to decide what to do with your changes before you can switch branches. You can commit your changes on the current branch, stash your changes to temporarily save them on the current branch, or bring the changes to your new branch. If you want to commit your changes before switching branches, see "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)." {% tip %} -**Dica**: Você pode definir um comportamento-padrão para alternar branches nas configurações **Avançadas**. Para obter mais informações, consulte "[Definindo as configurações básicas](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". +**Tip**: You can set a default behavior for switching branches in the **Advanced** settings. For more information, see "[Configuring basic settings](/desktop/getting-started-with-github-desktop/configuring-basic-settings)." {% endtip %} {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.switching-between-branches %} - ![Lista de branches no repositório](/assets/images/help/desktop/select-branch-from-dropdown.png) -3. Se você tiver alterações salvas sem commit, escolha entre **Leave my changes** (Deixar as alterações) ou **Bring my changes** (Levar as alterações) e clique em **Switch Branch** (Alternar branch). ![Alternar branch com opções de alteração](/assets/images/help/desktop/stash-changes-options.png) + ![List of branches in the repository](/assets/images/help/desktop/select-branch-from-dropdown.png) +3. If you have saved, uncommitted changes, choose **Leave my changes** or **Bring my changes**, then click **Switch Branch**. + ![Switch branch with changes options](/assets/images/help/desktop/stash-changes-options.png) -## Excluir um branch +## Deleting a branch -Não é possível excluir um branch se ele estiver atualmente associado a uma pull request aberta. Não é possível desfazer a exclusão de um branch. +You can't delete a branch if it's currently associated with an open pull request. You cannot undo deleting a branch. {% mac %} {% data reusables.desktop.select-branch-to-delete %} - ![Menu suspenso para selecionar qual branch deseja excluir](/assets/images/help/desktop/select-branch-from-dropdown.png) + ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.delete-branch-mac %} - ![Excluir... opção no menu do branch](/assets/images/help/desktop/delete-branch-mac.png) + ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-mac.png) {% endmac %} {% windows %} {% data reusables.desktop.select-branch-to-delete %} - ![Menu suspenso para selecionar qual branch deseja excluir](/assets/images/help/desktop/select-branch-from-dropdown.png) + ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.delete-branch-win %} - ![Excluir... opção no menu do branch](/assets/images/help/desktop/delete-branch-win.png) + ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-win.png) {% endwindows %} -## Leia mais +## Further reading -- "[Clonar um repositório no {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)" -- "[Branch](/articles/github-glossary/#branch)" no glossário do {% data variables.product.prodname_dotcom %} +- "[Cloning a repository from {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)" +- "[Branch](/articles/github-glossary/#branch)" in the {% data variables.product.prodname_dotcom %} glossary - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)" -- "[Branches em um Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" na documentação do Git -- "[Ocultar as alterações](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes) +- "[Branches in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" in the Git documentation +- "[Stashing changes](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes)" diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md deleted file mode 100644 index 9561f11594..0000000000 --- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Criar o primeiro repositório usando o GitHub Desktop -shortTitle: Criar o seu primeiro repositório -intro: 'Você pode usar o {% data variables.product.prodname_desktop %} para criar e gerenciar um repositório do Git sem usar a linha de comando.' -redirect_from: - - /desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop - - /desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop -versions: - fpt: '*' ---- - -## Introdução -O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Ao fim da leitura deste guia, você usará o {% data variables.product.prodname_desktop %} para criar um repositório, alterá-lo e publicar as alterações no {% data variables.product.product_name %}. - -Depois de instalar o {% data variables.product.prodname_desktop %} e entrar no {% data variables.product.prodname_dotcom %} ou {% data variables.product.prodname_enterprise %}, você pode criar e clonar um repositório de tutorial. O tutorial apresentará os conceitos básicos de trabalho com o Git e o {% data variables.product.prodname_dotcom %}, incluindo a instalação de um editor de texto, criando um branch, fazendo um commit, fazendo push para {% data variables.product.prodname_dotcom_the_website %} e abrindo um pull request. O tutorial está disponível caso você ainda não tenha nenhum repositório no {% data variables.product.prodname_desktop %}. - -Recomendamos concluir o tutorial, mas se você desejar explorar o {% data variables.product.prodname_desktop %} criando um novo repositório, este guia irá orientar você a usar o {% data variables.product.prodname_desktop %} para funcionar em um repositório do Git. - -## Parte 1: Instalando {% data variables.product.prodname_desktop %} e autenticando sua conta -Você pode instalar o {% data variables.product.prodname_desktop %} em qualquer sistema operacional compatível. Depois de instalar o app, você deverá entrar e autenticar sua conta no {% data variables.product.prodname_dotcom %} ou no {% data variables.product.prodname_enterprise %} antes de criar e clonar um repositório de tutorial. - -Para obter mais informações sobre instalação e autenticação, consulte "[Configurando o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop)". - -## Parte 2: Criando um novo repositório -Se você não tiver nenhum repositório associado ao {% data variables.product.prodname_desktop %}, você verá a frase "Vamos começar!", em que você pode optar por criar e clonar um repositório de tutorial, clonar um repositório da Internet existente, criar um novo repositório ou adicionar um repositório existente a partir do seu disco rígido. ![Vamos começar! screen](/assets/images/help/desktop/lets-get-started.png) - -### Criar e clonar um repositório de tutorial -Recomendamos que você crie e clone um repositório de tutorial como seu primeiro projeto a ser praticado usando o {% data variables.product.prodname_desktop %}. - -1. Clique em **Create a tutorial repository and clone it** (Criar um repositório de tutorial e cloná-lo). ![Botão Create and clone a tutorial repository (Criar e clonar um repositório de tutorial)](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png) -2. Siga as instruções no tutorial para instalar um editor de texto, criar um branch, editar um arquivo, fazer um commit, publicar em {% data variables.product.prodname_dotcom %} e abrir um pull request. - -### Criar um repositório -Se você não desejar criar e clonar um repositório de tutorial, é possível criar um novo repositório. - -1. Clique em **Create a New Repository on your hard drive** (Criar um repositório no disco rígido). ![Criar um repositório](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png) -2. Preencha os campos e selecione as suas opções preferidas. ![Opções de criar um repositório](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png) - - "Name" (Nome) define o nome do repositório no local e no {% data variables.product.product_name %}. - - "Description" (Descrição) é um campo opcional com mais informações sobre o propósito do repositório. - - "Local path" (Caminho local) define o local do repositório no computador. Por padrão, o {% data variables.product.prodname_desktop %} cria uma pasta _GitHub_ dentro da pasta _Documents_ (Documentos) para armazenar seus repositórios, mas é possível escolher qualquer local no computador. O novo repositório será uma pasta dentro do local escolhido. Por exemplo, se você nomear o repositório como `Tutorial`, será criada uma pasta de nome _Tutorial_ dentro da pasta no caminho selecionado. O {% data variables.product.prodname_desktop %} registra o local escolhido para as próximas vezes que você criar ou clonar repositórios. - - A opção **Initialize this repository with a README** (Inicializar este repositório com um README) cria o commit com um arquivo _README.md_. Arquivos README ajudam as pessoas a entenderem o objetivo do seu projeto. Portanto, é recomendável usar esse item e adicionar informações úteis a ele. Quando alguém acessar seu repositório no {% data variables.product.product_name %}, a primeira informação exibida será o README. Para obter mais informações, consulte "[Sobre README](/articles/about-readmes)". - - O menu suspenso **Git ignore** (Git para ignorar) permite incluir um arquivo personalizado para ignorar determinados arquivos no repositório local, isto é, informações que você não quer armazenar no controle de versão. Se houver uma linguagem ou framework específico para uso, você poderá selecionar uma opção na lista disponível. Se você estiver começando agora, fique à vontade para ignorar essa opção. Para obter mais informações, consulte "[Ignorar arquivos](/github/getting-started-with-github/ignoring-files)". - - O menu suspenso **License** (Licença) permite adicionar uma licença de código aberto a um arquivo _LICENSE_ no repositório. Não se preocupe em adicionar uma licença de imediato. Para obter mais informações sobre as licenças de código aberto disponíveis e sobre como adicioná-las ao repositório, consulte "[Criar a licença de um repositório](/articles/licensing-a-repository)." -3. Clique em **Create Repository** (Criar repositório). - -## Parte 3: Explorando o {% data variables.product.prodname_desktop %} -No menu de arquivos na parte superior da tela, você pode acessar as configurações e ações que pode executar no {% data variables.product.prodname_desktop %}. A maioria das ações tem atalhos de teclado para aumentar a eficiência do seu trabalho. Para obter uma lista completa de atalhos de teclado, consulte "[Atalhos de teclado](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)". - -### A barra de menu do {% data variables.product.prodname_desktop %} -Na parte superior do aplicativo {% data variables.product.prodname_desktop %}, você verá uma barra que mostra o estado atual do seu repositório. - - **Current repository** (Repositório atual) mostra o nome do repositório em que você está trabalhando. Você pode clicar em **Current repository** (Repositório atual) para alternar entre repositórios no {% data variables.product.prodname_desktop %}. - - **Current branch** (Branch atual) mostra o nome do branch em que você está trabalhando. Você pode clicar em **Current branch** (Branch atual) para exibir todos os branches do repositório, alternar entre branches ou criar um branch. Depois de criar pull requests no repositório, você também poderá exibi-las clicando em **Current branch** (Branch atual). - - A opção **Publish repository** (Publicar repositório) aparece porque você ainda não publicou o repositório no {% data variables.product.product_name %}. A publicação será feita depois, em outra etapa. Esta seção da barra mudará com base no status de seu branch atual e repositório. Diferentes ações dependentes de contextos estarão disponíveis para o intercâmbio de dados entre repositórios locais e remotos. - - ![Explorar o GitHub Desktop](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png) - -### Alterações e histórico -Na barra lateral à esquerda, você verá **Changes** (Alterações) e **History** (Histórico). ![Abas Alterações e Histórico](/assets/images/help/desktop/changes-and-history.png) - - - A opção **Changes** (Alterações) mostra as mudanças que você fez nos arquivos do branch atual, mas que ainda estão sem commit no repositório local. Na parte inferior, há uma caixa com caixas de texto "Resumo" e "Descrição" e um botão **Commit para BRANCH**. É nessa área que você fará o commit das novas alterações. O botão **Commit para BRANCH** é dinâmico e irá exibir em qual branch você está fazendo o commit das suas alterações. ![Área do commit](/assets/images/help/desktop/getting-started-guide/commit-area.png) - - - A opção **History** (Histórico) mostra os commits anteriores no branch atual do repositório. Provavelmente você verá um "Initial commit" (Commit inicial) criado pelo {% data variables.product.prodname_desktop %} quando você criou o repositório. À direita do commit, dependendo das opções escolhidas durante a criação do repositório, você poderá ver arquivos _.gitattributes_, _.gitignore_, _LICENÇA_ ou _README_. Ao clicar em cada arquivo você verá o diff, que consiste no registro das alterações feitas no arquivo do commit em questão. O diff não mostra todo o conteúdo do arquivo, mas somente as partes que foram alteradas. ![Exibição de histórico](/assets/images/help/desktop/getting-started-guide/history-view.png) - -## Parte 4: Publicando seu repositório no {% data variables.product.product_name %} -Ao criar um novo repositório, ele existe apenas no seu computador e você é o único que pode acessar o repositório. Você pode publicar seu repositório no {% data variables.product.product_name %} para mantê-lo sincronizado em vários computadores e permitir que outras pessoas o acessem. Para publicar seu repositório, faça push de suas alterações locais no {% data variables.product.product_name %}. - -1. Clique em **Publicar repositório** na barra de menu. ![Publicar repositório](/assets/images/help/desktop/getting-started-guide/publish-repository.png) - - O {% data variables.product.prodname_desktop %} preenche automaticamente os campos "Nome" e "Descrição" com as informações inseridas quando você criou o repositório. - - A opção de **Manter este código privado** permite que você controle quem pode visualizar o seu projeto. Se você deixar esta opção desmarcada, outros usuários em {% data variables.product.product_name %} poderão visualizar o seu código. Se você selecionar esta opção, o seu código não ficará disponível publicamente. - - Se estiver presente, o menu suspenso da **Organização** permite que você publique o seu repositório em uma organização específica à qual você pertence no {% data variables.product.product_name %}. - - ![Etapas para publicar repositório](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png) - 2. Clique no botão **Publish Repository** (Publicar repositório). - 3. É possível acessar o repositório no {% data variables.product.prodname_dotcom %} pelo {% data variables.product.prodname_desktop %}. No menu do arquivo, clique em **Repository** (Repositório) e em **View on GitHub** (Exibir no GitHub). Fazer isso levará você diretamente para o repositório no seu navegador padrão. - -## Parte 5: Fazer commit e carregar as alterações -Agora que você criou e publicou seu repositório, você está pronto para fazer alterações no seu projeto e começar a criar seu primeiro commit no seu repositório. - -1. Para abrir o editor externo dentro de {% data variables.product.prodname_desktop %}, clique em **Repositório** e, em seguida, clique em **Abrir no EDITOR**. Para obter mais informações, consulte "[Configurar um editor padrão](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)". ![Abrir no editor](/assets/images/help/desktop/getting-started-guide/open-in-editor.png) - -2. Faça algumas alterações no arquivo _README.md_ que você criou anteriormente. Você pode adicionar informações que descrevem o seu projeto, como o que ele faz e por que ele é útil. Quando estiver satisfeito com suas alterações, salve-as no editor de texto. -3. Em {% data variables.product.prodname_desktop %}, acesse a vista **Alterações**. Na lista de arquivos, você verá o _README.md_ alterado. A marca de verificação à esquerda do arquivo _README.md_ indica que as alterações feitas no arquivo serão parte do commit que você fez. Talvez você queira fazer alterações em vários arquivos no futuro, mas sem fazer o commit das alterações de todos eles. Se você clicar na marca de seleção ao lado de um arquivo, esse arquivo não será incluído no commit. ![Exibir alterações](/assets/images/help/desktop/getting-started-guide/viewing-changes.png) - -4. Na parte inferior da lista **Changes** (Alterações), adicione uma mensagem ao commit. À direita da sua foto de perfil, digite uma breve descrição do commit. Já que estamos alterando o arquivo _README.md_, algo como "Adicionar informações sobre o propósito do projeto" seria um bom resumo. Abaixo do resumo, o campo de texto "Descrição" permite digitar uma descrição mais longa das alterações feitas no commit. Essa descrição pode ser útil para analisar o histórico de um projeto e entender o motivo das alterações. Como estamos fazendo uma atualização básica do arquivo _README.md_, fique à vontade para ignorar a descrição. ![Mensagem do commit](/assets/images/help/desktop/getting-started-guide/commit-message.png) -5. Clique em **Fazer commit do NOME DO BRANCH**. O botão do commit mostra o seu branch atual. Dessa forma, você pode ter certeza de que deseja fazer o commit no branch desejado. ![Fazer commit de um branch](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) -6. Para fazer push das alterações no repositório remote no {% data variables.product.product_name %}, clique em **Push origin** (Fazer push da origem). ![Fazer push de origem](/assets/images/help/desktop/getting-started-guide/push-to-origin.png) - - O botão **Subir origem** é o mesmo que você clicou para publicar o seu repositório no {% data variables.product.product_name %}. Este botão muda contextualmente de acordo com o local em que você está no fluxo de trabalho do Git. Agora, ele deve mostrar `Fazer push da origem` com um número `1` ao lado, indicando que ainda não foi feito o push de um commit para o {% data variables.product.product_name %}. - - O termo "origem" na opção **Fazer push da origem** indica que estamos fazendo push das alterações para o repositório remoto denominado `origem` que, neste caso, é o repositório do seu projeto no {% data variables.product.prodname_dotcom_the_website %}. Até você fazer o push de qualquer commit para o {% data variables.product.product_name %}, haverá diferenças entre o repositório do seu projeto no computador e o repositório do seu projeto no {% data variables.product.prodname_dotcom_the_website %}. Assim, você pode trabalhar no local e deixar para fazer push das suas alterações no {% data variables.product.prodname_dotcom_the_website %} quando estiver tudo pronto. -7. Na janela à direita da vista de **Alterações**, você verá sugestões de ações que podem ser feitas a seguir. Para abrir o repositório no {% data variables.product.product_name %} no seu navegador, clique em **Visualizar no {% data variables.product.product_name %}**. ![Ações disponíveis](/assets/images/help/desktop/available-actions.png) -8. No navegador, clique em **2 commits**. Você verá uma lista dos commits neste repositório no {% data variables.product.product_name %}. O primeiro commit deve ser o que você acabou de fazer no {% data variables.product.prodname_desktop %}. ![Clicar em dois commits](/assets/images/help/desktop/getting-started-guide/click-two-commits.png) - -## Conclusão -Agora você criou um repositório, publicou o repositório no {% data variables.product.product_name %}, fez um commit e fez push das suas alterações no {% data variables.product.product_name %}. Você pode seguir esse mesmo fluxo de trabalho ao contribuir para outros projetos os quais você cria ou nos quais você colabora. - -## Leia mais -- "[Primeiros passos com o Git](/github/getting-started-with-github/getting-started-with-git)" -- "[Aprender sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" -- "[Começar com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index 38945cf666..75409ef3ff 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -1,5 +1,5 @@ --- -title: Autenticar com os aplicativos GitHub +title: Authenticating with GitHub Apps intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/ @@ -13,59 +13,61 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Autenticação +shortTitle: Authentication --- -## Gerar uma chave privada +## Generating a private key -Após criar um aplicativo GitHub, você deverá gerar uma ou mais chaves privadas. Você usará a chave privada para assinar solicitações de token de acesso. +After you create a GitHub App, you'll need to generate one or more private keys. You'll use the private key to sign access token requests. -Você pode criar várias chaves privadas e girá-las para evitar período de inatividade se uma chave for comprometida ou perdida. Para verificar se uma chave privada corresponde a uma chave pública, consulte [Verificando chaves privadas](#verifying-private-keys). +You can create multiple private keys and rotate them to prevent downtime if a key is compromised or lost. To verify that a private key matches a public key, see [Verifying private keys](#verifying-private-keys). -Para gerar uma chave privada: +To generate a private key: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. Em "Chaves Privadas", clique em **Gerar uma chave privada**. ![Gerar chave privada](/assets/images/github-apps/github_apps_generate_private_keys.png) -6. Você verá uma chave privada no formato PEM baixado no seu computador. Certifique-se de armazenar este arquivo porque o GitHub armazena apenas a parte pública da chave. +5. In "Private keys", click **Generate a private key**. +![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) +6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key. {% note %} -**Observação:** Se você estiver usando uma biblioteca que exige um formato de arquivo específico, o arquivo PEM que você baixar será no formato `PKCS#1 RSAPrivateKey`. +**Note:** If you're using a library that requires a specific file format, the PEM file you download will be in `PKCS#1 RSAPrivateKey` format. {% endnote %} -## Verificar chaves privadas -{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. Você pode verificar se a sua chave privada corresponde à chave pública armazenada no {% data variables.product.product_name %}, gerando a impressão digital da sua chave privada e comparando-a com a impressão digital exibida no {% data variables.product.product_name %}. +## Verifying private keys +{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. You can verify that your private key matches the public key stored on {% data variables.product.product_name %} by generating the fingerprint of your private key and comparing it to the fingerprint shown on {% data variables.product.product_name %}. -Para verificar uma chave privada: +To verify a private key: -1. Encontre a impressão digital para o par de chaves privada e pública que deseja verificar na seção "Chaves privadas" da página de configurações de desenvolvedor do seu {% data variables.product.prodname_github_app %}. Para obter mais informações, consulte [Gerar uma chave privada](#generating-a-private-key). ![Impressão digital de chave privada](/assets/images/github-apps/github_apps_private_key_fingerprint.png) -2. Gere a impressão digital da sua chave privada (PEM) localmente usando o comando a seguir: +1. Find the fingerprint for the private and public key pair you want to verify in the "Private keys" section of your {% data variables.product.prodname_github_app %}'s developer settings page. For more information, see [Generating a private key](#generating-a-private-key). +![Private key fingerprint](/assets/images/github-apps/github_apps_private_key_fingerprint.png) +2. Generate the fingerprint of your private key (PEM) locally by using the following command: ```shell $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl sha256 -binary | openssl base64 ``` -3. Compare os resultados da impressão digital gerada localmente com a impressão digital que você vê no {% data variables.product.product_name %}. +3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}. -## Apagar chaves privadas -Você pode remover uma chave privada perdida ou comprometida excluindo-a. No entanto, você deve ter pelo menos uma chave privada. Quando você tem apenas uma chave, você deverá gerar uma nova antes de excluir a antiga. ![Excluir a última chave privada](/assets/images/github-apps/github_apps_delete_key.png) +## Deleting private keys +You can remove a lost or compromised private key by deleting it, but you must have at least one private key. When you only have one key, you will need to generate a new one before deleting the old one. +![Deleting last private key](/assets/images/github-apps/github_apps_delete_key.png) -## Efetuar a autenticação um {% data variables.product.prodname_github_app %} +## Authenticating as a {% data variables.product.prodname_github_app %} -Efetuar a autenticação como um {% data variables.product.prodname_github_app %} permite que você faça algumas coisas: +Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things: -* Você pode recuperar informações de gerenciamento de alto nível sobre seu {% data variables.product.prodname_github_app %}. -* Você pode solicitar tokens de acesso para uma instalação do aplicativo. +* You can retrieve high-level management information about your {% data variables.product.prodname_github_app %}. +* You can request access tokens for an installation of the app. -Para efetuar a autenticação como um {% data variables.product.prodname_github_app %}, [gere uma chave privada](#generating-a-private-key) no formato PEM e baixe-a para na sua máquina local. Você usará essa chave para assinar um [JSON Web Token (JWT)](https://jwt.io/introduction) e codificá-lo usando o algoritmo `RS256`. O {% data variables.product.product_name %} verifica se a solicitação foi autenticada, fazendo a verificação do token com a chave pública armazenada pelo aplicativo. +To authenticate as a {% data variables.product.prodname_github_app %}, [generate a private key](#generating-a-private-key) in PEM format and download it to your local machine. You'll use this key to sign a [JSON Web Token (JWT)](https://jwt.io/introduction) and encode it using the `RS256` algorithm. {% data variables.product.product_name %} checks that the request is authenticated by verifying the token with the app's stored public key. -Aqui está um script Ruby rápido que você pode usar para gerar um JWT. Observe que você deve executar o `gem install jwt` antes de usá-lo. +Here's a quick Ruby script you can use to generate a JWT. Note you'll have to run `gem install jwt` before using it. - ```ruby require 'openssl' require 'jwt' # https://rubygems.org/gems/jwt @@ -88,19 +90,19 @@ jwt = JWT.encode(payload, private_key, "RS256") puts jwt ``` -`YOUR_PATH_TO_PEM` e `YOUR_APP_ID` são os valores que você deve substituir. Certifique-se de incluir os valores entre aspas duplas. +`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes. -Use o seu identificador de {% data variables.product.prodname_github_app %}(`YOUR_APP_ID`) como o valor para a reivindicação do JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (emissor). Você pode obter o identificador {% data variables.product.prodname_github_app %} por meio do ping inicial do webhook, após [criar o aplicativo](/apps/building-github-apps/creating-a-github-app/), ou a qualquer momento na da página de configurações do aplicativo na UI do GitHub.com. +Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI. -Após criar o JWT, defina-o no `Cabeçalho` da solicitação de API: +After creating the JWT, set it in the `Header` of the API request: ```shell $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app ``` -`YOUR_JWT` é o valor que você deve substituir. +`YOUR_JWT` is the value you must replace. -O exemplo acima usa o tempo máximo de expiração de 10 minutos, após o qual a API começará a retornar o erro `401`: +The example above uses the maximum expiration time of 10 minutes, after which the API will start returning a `401` error: ```json { @@ -109,19 +111,19 @@ O exemplo acima usa o tempo máximo de expiração de 10 minutos, após o qual a } ``` -Você deverá criar um novo JWT após o tempo expirar. +You'll need to create a new JWT after the time expires. -## Acessar os pontos finais da API como um {% data variables.product.prodname_github_app %} +## Accessing API endpoints as a {% data variables.product.prodname_github_app %} -Para obter uma lista dos pontos finais da API REST que você pode usar para obter informações de alto nível sobre um {% data variables.product.prodname_github_app %}, consulte "[aplicativos GitHub](/rest/reference/apps)". +For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)." -## Autenticar como uma instalação +## Authenticating as an installation -Autenticar como uma instalação permite que você execute ações na API para essa instalação. Antes de autenticar como uma instalação, você deverá criar um token de acesso de instalação. Certifique-se de que você já instalou o aplicativo GitHub em pelo menos um repositório; é impossível criar um token de instalação sem uma única instalação. Estes tokens de acesso de instalação são usados por {% data variables.product.prodname_github_apps %} para efetuar a autenticação. Para obter mais informações, consulte "[Instalando aplicativos GitHub](/developers/apps/managing-github-apps/installing-github-apps)". +Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. Ensure that you have already installed your GitHub App to at least one repository; it is impossible to create an installation token without a single installation. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)." -Por padrão, os tokens de acesso de instalação são limitados em todos os repositórios que uma instalação pode acessar. É possível limitar o escopo do token de acesso de instalação a repositórios específicos usando o parâmetro `repository_ids`. Consulte [Criar um token de acesso de instalação para um ponto final de um aplicativo](/rest/reference/apps#create-an-installation-access-token-for-an-app) para obter mais informações. Os tokens de acesso de instalação têm as permissões configuradas pelo {% data variables.product.prodname_github_app %} e expiram após uma hora. +By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour. -Para listar as instalações para um aplicativo autenticado, inclua o JWT [gerado acima](#jwt-payload) no cabeçalho de autorização no pedido da API: +To list the installations for an authenticated app, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request: ```shell $ curl -i -X GET \ @@ -130,9 +132,9 @@ $ curl -i -X GET \ {% data variables.product.api_url_pre %}/app/installations ``` -A resposta incluirá uma lista de instalações em que o `id` de cada instalação pode ser usado para criar um token de acesso de instalação. Para obter mais informações sobre o formato de resposta, consulte "[Instalações de lista para o aplicativo autenticado](/rest/reference/apps#list-installations-for-the-authenticated-app)". +The response will include a list of installations where each installation's `id` can be used for creating an installation access token. For more information about the response format, see "[List installations for the authenticated app](/rest/reference/apps#list-installations-for-the-authenticated-app)." -Para criar um token de acesso de instalação, inclua o JWT [gerado acima](#jwt-payload) no cabeçalho Autorização no pedido de API e substitua `:installation_id` pelo `id` da instalação da instalação: +To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request and replace `:installation_id` with the installation's `id`: ```shell $ curl -i -X POST \ @@ -141,9 +143,9 @@ $ curl -i -X POST \ {% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens ``` -A resposta incluirá seu token de acesso de instalação, a data de validade, as permissões do token e os repositórios que o token pode acessar. Para obter mais informações sobre o formato de resposta, consulte [Criar um token de acesso de instalação para um ponto de final do](/rest/reference/apps#create-an-installation-access-token-for-an-app)aplicativo. +The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint. -Para efetuar a autenticação com um token de acesso de instalação, inclua-o no cabeçalho de autorização na solicitação de API: +To authenticate with an installation access token, include it in the Authorization header in the API request: ```shell $ curl -i \ @@ -152,17 +154,17 @@ $ curl -i \ {% data variables.product.api_url_pre %}/installation/repositories ``` -`YOUR_INSTALLATION_ACCESS_TOKEN` é o valor que você deve substituir. +`YOUR_INSTALLATION_ACCESS_TOKEN` is the value you must replace. -## Acessar pontos finais da API como uma instalação +## Accessing API endpoints as an installation -Para obter uma lista de pontos de extremidade da API REST disponíveis para uso por {% data variables.product.prodname_github_apps %} usando um token de acesso de instalação, consulte "[pontos de extremidade disponíveis](/rest/overview/endpoints-available-for-github-apps)." +For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)." -Para obter uma lista de pontos finais relacionados a instalações, consulte "[Instalações](/rest/reference/apps#installations)". +For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)." -## Acesso Git baseado em HTTP por uma instalação +## HTTP-based Git access by an installation -As instalações com [permissões](/apps/building-github-apps/setting-permissions-for-github-apps/) no conteúdo `` de um repositório, podem usar seus tokens de acesso de instalação para efetuar autenticação para acesso ao Git. Use o token de acesso da instalação como a senha HTTP: +Installations with [permissions](/apps/building-github-apps/setting-permissions-for-github-apps/) on `contents` of a repository, can use their installation access tokens to authenticate for Git access. Use the installation access token as the HTTP password: ```shell git clone https://x-access-token:<token>@github.com/owner/repo.git diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 230359e7b7..5d3b70e9d9 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -1,6 +1,6 @@ --- -title: Criar um aplicativo GitHub usando parâmetros de URL -intro: 'Você pode pré-selecionar as configurações de um novo {% data variables.product.prodname_github_app %} usando URL [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para definir rapidamente a configuração do novo {% data variables.product.prodname_github_app %}.' +title: Creating a GitHub App using URL parameters +intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.' redirect_from: - /apps/building-github-apps/creating-github-apps-using-url-parameters - /developers/apps/creating-a-github-app-using-url-parameters @@ -11,23 +11,22 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Parâmetros de consulta de criação de aplicativo +shortTitle: App creation query parameters --- +## About {% data variables.product.prodname_github_app %} URL parameters -## Sobre parâmetros de URL do {% data variables.product.prodname_github_app %}. +You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account: -Você pode adicionar parâmetros de consulta a essas URLs para pré-selecionar a configuração de um {% data variables.product.prodname_github_app %} em uma conta pessoal ou de organização: +* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new` +* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new` -* **Conta de usuário:** `{% data variables.product.oauth_host_code %}/settings/apps/new` -* **Conta da organização:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new` - -A pessoa que está criando o aplicativo pode editar os valores pré-selecionados a partir da página de registro do {% data variables.product.prodname_github_app %}, antes de enviar o aplicativo. Se você não incluir os parâmetros necessários na string de consulta da URL, como, por exemplo, o `nome`, a pessoa que criar o aplicativo deverá inserir um valor antes de enviar o aplicativo. +The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app. {% ifversion ghes > 3.1 or fpt or ghae-next or ghec %} -Para aplicativos que exigem que um segredo proteja seu webhook, o valor do segredo deve ser definido no formulário pela pessoa que criou o aplicativo, não pelo uso de parâmetros de consulta. Para obter mais informações, consulte "[Protegendo seus webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)". +For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)." {% endif %} -A URL a seguir cria um novo aplicativo pública denominado `octocat-github-app` com uma descrição pré-configurada e URL de chamada de retorno. Esta URL também seleciona permissões de leitura e gravação para `verificações`, inscreve-se nos eventos webhook de check_run` e check_suite` e seleciona a opção de solicitar autorização do usuário (OAuth) durante a instalação: +The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: {% ifversion fpt or ghae-next or ghes > 3.0 or ghec %} @@ -43,101 +42,102 @@ A URL a seguir cria um novo aplicativo pública denominado `octocat-github-app` {% endif %} -Lista completa de parâmetros de consulta, permissões e eventos disponíveis encontra-se nas seções abaixo. +The complete list of available query parameters, permissions, and events is listed in the sections below. -## Parâmetros de configuração do {% data variables.product.prodname_github_app %} +## {% data variables.product.prodname_github_app %} configuration parameters - | Nome | Tipo | Descrição | - | -------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `string` | O nome do {% data variables.product.prodname_github_app %}. Dê um nome claro e sucinto ao seu aplicativo. Seu aplicativo não pode ter o mesmo nome de um usuário existente no GitHub, a menos que seja o seu próprio nome de usuário ou da sua organização. Uma versão movida do nome do seu aplicativo será exibida na interface do usuário quando sua integração realizar uma ação. | - | `descrição` | `string` | Uma descrição do {% data variables.product.prodname_github_app %}. | - | `url` | `string` | A URL completa da página inicial do site do {% data variables.product.prodname_github_app %}. {% ifversion fpt or ghae-next or ghes > 3.0 or ghec %} - | `callback_urls` | `array de strigns` | Uma URL completa para a qual redirecionar após alguém autorizar uma instalação. Você pode fornecer até 10 URLs de retorno de chamada. Essas URLs são usadas se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. Por exemplo, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} - | `callback_url` | `string` | A URL completa para onde redirecionar após alguém autorizar uma instalação. Este URL é usada se o seu aplicativo precisar identificar e autorizar solicitações de usuário para servidor.{% endif %} - | `request_oauth_on_install` | `boolean` | Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você poderá definir essa opção como `verdadeiro` para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando um passo. Se você selecionar esta opção, `setup_url` irá tornar-se indisponível e os usuários serão redirecionados para sua `callback_url` após instalar o aplicativo. | - | `setup_url` | `string` | A URL completa para redirecionamento após alguém instalar o {% data variables.product.prodname_github_app %}, se o aplicativo precisar de configuração adicional após a instalação. | - | `setup_on_update` | `boolean` | Defina como `verdadeiro` para redirecionar as pessoas para a URL de configuração quando as instalações forem atualizadas, por exemplo, após os repositórios serem adicionados ou removidos. | - | `público` | `boolean` | Defina `verdadeiro` quando seu {% data variables.product.prodname_github_app %} estiver disponível para o público ou como `falso` quando só for acessível pelo proprietário do aplicativo. | - | `webhook_url` | `string` | A URL completa para a qual você deseja enviar as cargas do evento de webhook. | - | {% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string` | Você pode especificar um segredo para proteger seus webhooks. Consulte "[Protegendo seus webhooks](/webhooks/securing/)" para obter mais detalhes. | - | {% endif %}`events` | `array de strigns` | Eventos webhook. Alguns eventos de webhook exigem permissões de `leitura` ou `gravação` para um recurso antes de poder selecionar o evento ao registrar um novo {% data variables.product.prodname_github_app %}, . Consulte a seção "[{% data variables.product.prodname_github_app %} eventos de webhook](#github-app-webhook-events)" para eventos disponíveis e suas permissões necessárias. Você pode selecionar vários eventos em uma string de consulta. Por exemplo, `eventos[]=public&eventos[]=label`. | - | `domínio` | `string` | A URL de uma referência de conteúdo. | - | `single_file_name` | `string` | Esta é uma permissão de escopo limitado que permite que o aplicativo acesse um único arquivo em qualquer repositório. Quando você define a permissão `single_file` para `read` ou `write`, este campo fornece o caminho para o único arquivo que o {% data variables.product.prodname_github_app %} gerenciará. {% ifversion fpt or ghes or ghec %} Se você precisar gerenciar vários arquivos, veja `single_file_paths` abaixo. {% endif %}{% ifversion fpt or ghes or ghec %} - | `single_file_paths` | `array de strigns` | Isso permite que o aplicativo acesse até dez arquivos especificados em um repositório. Quando você define a permissão `single_file` para `read` ou `write`, este array pode armazenar os caminhos de até dez arquivos que seu {% data variables.product.prodname_github_app %} gerenciará. Todos esses arquivos recebem a mesma permissão definida por `single_file`, e não têm permissões individuais separadas. Quando dois ou mais arquivos estão configurados, a API retorna `multiple_single_files=true`, caso contrário retorna `multiple_single_files=false`.{% endif %} + Name | Type | Description +-----|------|------------- +`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. +`description` | `string` | A description of the {% data variables.product.prodname_github_app %}. +`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae-next or ghes > 3.0 or ghec %} +`callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} +`callback_url` | `string` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} +`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. +`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. +`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. +`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app. +`webhook_active` | `boolean` | Set to `false` to disable webhook. Webhook is enabled by default. +`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to. +{% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details. +{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`. +`domain` | `string` | The URL of a content reference. +`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% ifversion fpt or ghes or ghec %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% ifversion fpt or ghes or ghec %} +`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %} -## Permissões do {% data variables.product.prodname_github_app %} +## {% data variables.product.prodname_github_app %} permissions -Você pode selecionar permissões em uma string de consultas usando o nome da permissão na tabela a seguir como o nome do parâmetro de consulta e o tipo de permissão como valor da consulta. Por exemplo, para selecionar permissões de `Leitura & gravação` na interface de usuário para `conteúdo`, sua string de consulta incluiria `&contents=write`. Para selecionar as permissões `Somente leitura` na interface de usuário para `bloquear`, sua string de consulta incluiria `&blocking=read`. Para selecionar `sem acesso` na interface do usuário para `verificações`, sua string de consulta não incluiria a permissão `verificações`. +You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. -| Permissão | Descrição | -| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`administração`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Concede acesso a vários pontos finais para administração de organização e repositório. Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghec %} -| [`bloqueio`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Concede acesso à [API de usuários de bloqueio](/rest/reference/users#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`Verificações`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Concede acesso à [API de verificação](/rest/reference/checks). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| `content_references` | Concede acesso ao ponto final "[Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`Conteúdo`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Concede acesso a vários pontos finais que permitem modificar o conteúdo do repositório. Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`Implantações`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Concede acesso à [API de implementação](/rest/reference/repos#deployments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghec %} -| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Concede acesso à [API de e-mails](/rest/reference/users#emails). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`seguidores`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Concede acesso à [API de seguidores](/rest/reference/users#followers). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Concede acesso à [API de chaves de GPG](/rest/reference/users#gpg-keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`Problemas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Concede acesso à [API de problemas](/rest/reference/issues). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`chaves`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Concede acesso à [API de chaves públicas](/rest/reference/users#keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Concede acesso para gerenciar os membros de uma organização. Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghec %} -| [`metadados`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Concede acesso a pontos finais somente leitura que não vazam dados confidenciais. Pode ser `leitura ` ou `nenhum`. O padrão é `leitura`, ao definir qualquer permissão, ou `nenhum` quando você não especificar nenhuma permissão para o {% data variables.product.prodname_github_app %}. | -| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Concede acesso ao ponto final "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" ponto final e Pa [API de restrições de interação da organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Concede acesso à [API de webhooks da organização](/rest/reference/orgs#webhooks/). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| `organization_plan` | Concede acesso para obter informações sobre o plano de uma organização usando o ponto final "[Obter uma organização](/rest/reference/orgs#get-an-organization)". Pode ser: `nenhum` ou `leitura`. | -| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `administrador`.{% ifversion fpt or ghec %} -| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Concede acesso à [API de usuários de bloqueio da organização](/rest/reference/orgs#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`Páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Concede acesso à [API de páginas](/rest/reference/repos#pages). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| `plano` | Concede acesso para obter informações sobre o plano de um usuário do GitHub que usa o ponto final "[Obter um usuário](/rest/reference/users#get-a-user)". Pode ser: `nenhum` ou `leitura`. | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Concede acesso a vários pontos finais do pull request. Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Concede acesso à [API de webhooks do repositório](/rest/reference/repos#hooks). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `administrador`.{% ifversion fpt or ghes > 3.0 or ghec %} -| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Concede acesso à [API de varredura de segredo](/rest/reference/secret-scanning). Pode ser: `none`, `read` ou `write`.{% endif %}{% ifversion fpt or ghes or ghec %} -| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Concede acesso à [API de varredura de código](/rest/reference/code-scanning/). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Concede acesso à [API de status](/rest/reference/repos#statuses). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Concede acesso à [API de discussões de equipe](/rest/reference/teams#discussions) e à [API de comentários de discussão de equipe](/rest/reference/teams#discussion-comments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| `vulnerability_alerts` | Concede acesso a alertas de segurança para dependências vulneráveis em um repositório. Consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" para saber mais. Pode ser: `none` ou `read`.{% endif %} -| `inspecionando` | Concede acesso à lista e alterações de repositórios que um usuário assinou. Pode ser: `nenhum`, `leitura` ou `gravação`. | +Permission | Description +---------- | ----------- +[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %} +[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`. +`content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. +[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. +[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghec %} +[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %} +[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`. +[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`. +[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`. +[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`. +[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %} +[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. +[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} +[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`. +`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`. +[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghec %} +[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %} +[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`. +`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. +[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. +[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. +[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghes > 3.0 or ghec %} +[`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% ifversion fpt or ghes or ghec %} +[`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %} +[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. +[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. +[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. +[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %} +`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. -## Eventos webhook do {% data variables.product.prodname_github_app %} +## {% data variables.product.prodname_github_app %} webhook events -| Nome do evento webhook | Permissão necessária | Descrição | -| -------------------------------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------------------- | -| [`check_run`](/webhooks/event-payloads/#check_run) | `Verificações` | {% data reusables.webhooks.check_run_short_desc %} -| [`check_suite`](/webhooks/event-payloads/#check_suite) | `Verificações` | {% data reusables.webhooks.check_suite_short_desc %} -| [`commit_comment`](/webhooks/event-payloads/#commit_comment) | `Conteúdo` | {% data reusables.webhooks.commit_comment_short_desc %} -| [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} -| [`create`](/webhooks/event-payloads/#create) | `Conteúdo` | {% data reusables.webhooks.create_short_desc %} -| [`delete`](/webhooks/event-payloads/#delete) | `Conteúdo` | {% data reusables.webhooks.delete_short_desc %} -| [`implantação`](/webhooks/event-payloads/#deployment) | `Implantações` | {% data reusables.webhooks.deployment_short_desc %} -| [`implantação_status`](/webhooks/event-payloads/#deployment_status) | `Implantações` | {% data reusables.webhooks.deployment_status_short_desc %} -| [`bifurcação`](/webhooks/event-payloads/#fork) | `Conteúdo` | {% data reusables.webhooks.fork_short_desc %} -| [`gollum`](/webhooks/event-payloads/#gollum) | `Conteúdo` | {% data reusables.webhooks.gollum_short_desc %} -| [`Problemas`](/webhooks/event-payloads/#issues) | `Problemas` | {% data reusables.webhooks.issues_short_desc %} -| [`issue_comment`](/webhooks/event-payloads/#issue_comment) | `Problemas` | {% data reusables.webhooks.issue_comment_short_desc %} -| [`etiqueta`](/webhooks/event-payloads/#label) | `metadados` | {% data reusables.webhooks.label_short_desc %} -| [`integrante`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} -| [`filiação`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} -| [`marco`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %} -| [`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} -| [`organização`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} -| [`page_build`](/webhooks/event-payloads/#page_build) | `Páginas` | {% data reusables.webhooks.page_build_short_desc %} -| [`project`](/webhooks/event-payloads/#project) | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_short_desc %} -| [`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} -| [`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} -| [`público`](/webhooks/event-payloads/#public) | `metadados` | {% data reusables.webhooks.public_short_desc %} -| [`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} -| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} -| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} -| [`push`](/webhooks/event-payloads/#push) | `Conteúdo` | {% data reusables.webhooks.push_short_desc %} -| [`versão`](/webhooks/event-payloads/#release) | `Conteúdo` | {% data reusables.webhooks.release_short_desc %} -| [`repositório`](/webhooks/event-payloads/#repository) | `metadados` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %} -| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `Conteúdo` | Permite aos integradores que usam o GitHub Actions acionar eventos personalizados.{% endif %} -| [`status`](/webhooks/event-payloads/#status) | `Status` | {% data reusables.webhooks.status_short_desc %} -| [`equipe`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} -| [`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} -| [`inspecionar`](/webhooks/event-payloads/#watch) | `metadados` | {% data reusables.webhooks.watch_short_desc %} +Webhook event name | Required permission | Description +------------------ | ------------------- | ----------- +[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %} +[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %} +[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %} +[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %} +[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %} +[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %} +[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %} +[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %} +[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %} +[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %} +[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %} +[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %} +[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %} +[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} +[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} +[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %} +[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} +[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} +[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %} +[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %} +[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} +[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} +[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %} +[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} +[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} +[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} +[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %} +[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %} +[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %} +[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %} +[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} +[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} +[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} +[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 210ae826a2..f7fea30a12 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Identificar e autorizar usuários para aplicativos GitHub +title: Identifying and authorizing users for GitHub Apps intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}' redirect_from: - /early-access/integrations/user-identification-authorization/ @@ -13,89 +13,88 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Identificar & autorizar usuários +shortTitle: Identify & authorize users --- - {% data reusables.pre-release-program.expiring-user-access-tokens %} -Quando o seu aplicativo GitHub age em nome de um usuário, ele realiza solicitações de usuário para servidor. Essas solicitações devem ser autorizadas com o token de acesso de um usuário. As solicitações de usuário para servidor incluem a solicitação de dados para um usuário, como determinar quais repositórios devem ser exibidos para um determinado usuário. Essas solicitações também incluem ações acionadas por um usuário, como executar uma criação. +When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build. {% data reusables.apps.expiring_user_authorization_tokens %} -## Identificando usuários no seu site +## Identifying users on your site -Para autorizar usuários para aplicativos-padrão executados no navegador, use o [fluxo de aplicativo web](#web-application-flow). +To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow). {% ifversion fpt or ghae or ghes > 3.0 or ghec %} -Para autorizar usuários para aplicativos sem acesso direto ao navegador, como ferramentas de CLI ou gerentes de credenciais do Git, use o [fluxo de dispositivos](#device-flow). O fluxo de dispositivo usa o OAuth 2.0 [Concessão de autorização do dispositivo](https://tools.ietf.org/html/rfc8628). +To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628). {% endif %} -## Fluxo do aplicativo web +## Web application flow -Ao usar o fluxo de aplicativo web, o processo para identificar usuários no seu site é: +Using the web application flow, the process to identify users on your site is: -1. Os usuários são redirecionados para solicitar sua identidade do GitHub -2. Os usuários são redirecionados de volta para o seu site pelo GitHub -3. Seu aplicativo GitHub acessa a API com o token de acesso do usuário +1. Users are redirected to request their GitHub identity +2. Users are redirected back to your site by GitHub +3. Your GitHub App accesses the API with the user's access token -Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, a etapa 1 será concluída durante a instalação do aplicativo. Para obter mais informações, consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)". +If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)." -### 1. Solicitar identidade do GitHub de um usuário -Direcione o usuário para a seguinte URL em seu navegador: +### 1. Request a user's GitHub identity +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -Quando seu aplicativo GitHub especifica um parâmetro do `login`, ele solicita aos usuários com uma conta específica que podem usar para iniciar sessão e autorizar seu aplicativo. +When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. -#### Parâmetros +#### Parameters -| Nome | Tipo | Descrição | -| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `string` | **Obrigatório.** O ID do cliente para o seu aplicativo GitHub. Você pode encontrá-lo em suas [configurações do aplicativo GitHub](https://github.com/settings/apps) quando você selecionar seu aplicativo. **Observação:** O ID do aplicativo e o ID do cliente não são iguais e não são intercambiáveis. | -| `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Este deve ser um match exato para {% ifversion fpt or ghes > 3.0 or ghec %} um dos URLs fornecidos como uma **URL de Callback**{% else %} a URL fornecida no campo de **URL de callback de autorização do usuário**{% endif %} ao configurar o aplicativo GitHub e não pode conter nenhum parâmetro adicional. | -| `estado` | `string` | Isso deve conter uma string aleatória para proteger contra ataques falsificados e pode conter quaisquer outros dados arbitrários. | -| `login` | `string` | Sugere uma conta específica para iniciar a sessão e autorizar o aplicativo. | -| `allow_signup` | `string` | Independentemente de os usuários autenticados ou não atenticados terem a opção de iscrever-se em {% data variables.product.prodname_dotcom %} durante o fluxo do OAuth. O padrão é `verdadeiro`. Use `falso` quando uma política proibir inscrições. | +Name | Type | Description +-----|------|------------ +`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. **Note:** The app ID and client ID are not the same, and are not interchangeable. +`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters. +`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data. +`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. +`allow_signup` | `string` | Whether or not unauthenticated users will be offered an option to sign up for {% data variables.product.prodname_dotcom %} during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. {% note %} -**Observação:** Você não precisa fornecer escopos na sua solicitação de autorização. Ao contrário do OAuth tradicional, o token de autorização é limitado às permissões associadas ao seu aplicativo GitHub e às do usuário. +**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user. {% endnote %} -### 2. Os usuários são redirecionados de volta para o seu site pelo GitHub +### 2. Users are redirected back to your site by GitHub -Se o usuário aceitar o seu pedido, O GitHub irá fazer o redirecionamento para seu site com um `código temporário` em um parâmetro de código, bem como o estado que você forneceu na etapa anterior em um parâmetro do `estado`. Se os estados não corresponderem, o pedido foi criado por terceiros e o processo deve ser abortado. +If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted. {% note %} -**Observação:** Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, o GitHub irá retornar um `código temporário` que você precisará trocar por um token de acesso. O parâmetro `estado` não é retornado quando o GitHub inicia o fluxo OAuth durante a instalação do aplicativo. +**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation. {% endnote %} -Troque este `código` por um token de acesso. Quando os tokens vencidos estiverem habilitados, token de acesso irá expirar em 8 horas e o token de atualização irá expirar em 6 meses. Toda vez que você atualizar o token, você receberá um novo token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)." +Exchange this `code` for an access token. When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)." -Os tokens de usuário expirados são atualmente um recurso opcional e estão sujeitos a alterações. Para optar por participar do recurso de expiração de token de usuário para servidor, consulte "[Habilitar funcionalidades opcionais para aplicativos](/developers/apps/activating-optional-features-for-apps)." +Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)." -Faça um pedido para o seguinte ponto de extremidade para receber um token de acesso: +Make a request to the following endpoint to receive an access token: POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -#### Parâmetros +#### Parameters -| Nome | Tipo | Descrição | -| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `string` | **Obrigatório.** O ID do cliente para o seu aplicativo GitHub. | -| `client_secret` | `string` | **Obrigatório.** O segredo do cliente do seu aplicativo GitHub. | -| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | -| `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Este deve ser um match exato para {% ifversion fpt or ghes > 3.0 or ghec %} um dos URLs fornecidos como uma **URL de Callback**{% else %} a URL fornecida no campo de **URL de callback de autorização do usuário**{% endif %} ao configurar o aplicativo GitHub e não pode conter nenhum parâmetro adicional. | -| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | +Name | Type | Description +-----|------|------------ +`client_id` | `string` | **Required.** The client ID for your GitHub App. +`client_secret` | `string` | **Required.** The client secret for your GitHub App. +`code` | `string` | **Required.** The code you received as a response to Step 1. +`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters. +`state` | `string` | The unguessable random string you provided in Step 1. -#### Resposta +#### Response -Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `expires_in`, `refresh_token`, e `refresh_token_expires_in` só são retornados quando você habilita os token de acesso de usuário para servidor vencidos. +By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`, and `refresh_token_expires_in` are only returned when you enable expiring user-to-server access tokens. ```json { @@ -108,14 +107,14 @@ Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `e } ``` -### 3. Seu aplicativo GitHub acessa a API com o token de acesso do usuário +### 3. Your GitHub App accesses the API with the user's access token -O token de acesso do usuário permite que o aplicativo GitHub faça solicitações para a API em nome de um usuário. +The user's access token allows the GitHub App to make requests to the API on behalf of a user. - Autorização: token OUTH-TOKEN + Authorization: token OAUTH-TOKEN GET {% data variables.product.api_url_code %}/user -Por exemplo, no cURL você pode definir o cabeçalho de autorização da seguinte forma: +For example, in curl you can set the Authorization header like this: ```shell curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user @@ -123,812 +122,812 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre {% ifversion fpt or ghae or ghes > 3.0 or ghec %} -## Fluxo de dispositivo +## Device flow {% note %} -**Nota:** O fluxo do dispositivo está na versão beta pública e sujeito a alterações. +**Note:** The device flow is in public beta and subject to change. {% endnote %} -O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git. +The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. -Para obter mais informações sobre autorização de usuários que usam o fluxo do dispositivo, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". +For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)". {% endif %} -## Verifique quais recursos de instalação um usuário pode acessar +## Check which installation's resources a user can access -Depois de ter um token OAuth para um usuário, você pode verificar quais instalações o usuário poderá acessar. +Once you have an OAuth token for a user, you can check which installations that user can access. Authorization: token OAUTH-TOKEN GET /user/installations -Você também pode verificar quais repositórios são acessíveis a um usuário para uma instalação. +You can also check which repositories are accessible to a user for an installation. Authorization: token OAUTH-TOKEN GET /user/installations/:installation_id/repositories -Você pode encontrar mais informações em: [Listar instalações de aplicativos acessíveis para o token de acesso do usuário](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) e [Listar repositórios acessíveis para o token de acesso do usuário](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). +More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). -## Tratar uma autorização revogada do aplicativo GitHub +## Handling a revoked GitHub App authorization -Se um usuário revogar sua autorização de um aplicativo GitHub, o aplicativo receberá o webhook [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) por padrão. Os aplicativos GitHub não podem cancelar a assinatura deste evento. {% data reusables.webhooks.authorization_event %} +If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %} -## Permissões no nível do usuário +## User-level permissions -Você pode adicionar permissões de nível de usuário ao seu aplicativo GitHub para acessar os recursos de usuários, como, por exemplo, e-mails de usuários, concedidos por usuários individuais como parte do fluxo de autorização do usuário [](#identifying-users-on-your-site). As permissões de nível de usuário diferem das [permissões do repositório do nível de organização](/rest/reference/permissions-required-for-github-apps), que são concedidas no momento da instalação em uma conta de organização ou usuário. +You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account. -Você pode selecionar permissões de nível de usuário nas configurações do seu aplicativo GitHub na seção **Permissões de usuário** na página **Permissões & webhooks**. Para obter mais informações sobre como selecionar permissões, consulte "[Editando permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". +You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." -Quando um usuário instala seu aplicativo em sua conta, o prompt de instalação listará as permissões de nível de usuário que seu aplicativo solicita e explicará que o aplicativo pode pedir essas permissões a usuários individuais. +When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions. -Como as permissões de nível de usuário são concedidas em uma base de usuário individual, você poderá adicioná-las ao aplicativo existente sem pedir que os usuários façam a atualização. No entanto, você precisa enviar usuários existentes através do fluxo de autorização do usuário para autorizar a nova permissão e obter um novo token de usuário para servidor para essas solicitações. +Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests. -## Solicitações de usuário para servidor +## User-to-server requests -Embora a maior parte da interação da sua API deva ocorrer usando os tokens de acesso de servidor para servidor, certos pontos de extremidade permitem que você execute ações por meio da API usando um token de acesso do usuário. Your app can make the following requests using [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) or [REST v3](/rest) endpoints. +While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) or [REST v3](/rest) endpoints. -### Pontos de extremidade compatíveis +### Supported endpoints {% ifversion fpt or ghec %} -#### Executores de ações +#### Actions Runners -* [Listar aplicativos executores para um repositório](/rest/reference/actions#list-runner-applications-for-a-repository) -* [Listar executores auto-hospedados para um repositório](/rest/reference/actions#list-self-hosted-runners-for-a-repository) -* [Obter um executor auto-hospedado para um repositório](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) -* [Excluir um executor auto-hospedado de um repositório](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) -* [Criar um token de registro para um repositório](/rest/reference/actions#create-a-registration-token-for-a-repository) -* [Criar um token de remoção para um repositório](/rest/reference/actions#create-a-remove-token-for-a-repository) -* [Listar aplicativos executores para uma organização](/rest/reference/actions#list-runner-applications-for-an-organization) -* [Listar executores auto-hospedados para uma organização](/rest/reference/actions#list-self-hosted-runners-for-an-organization) -* [Obter um executor auto-hospedado para uma organização](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) -* [Excluir um executor auto-hospedado de uma organização](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) -* [Criar um token de registro para uma organização](/rest/reference/actions#create-a-registration-token-for-an-organization) -* [Criar um token de remoção para uma organização](/rest/reference/actions#create-a-remove-token-for-an-organization) +* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository) +* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization) +* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization) -#### Segredos de ações +#### Actions Secrets -* [Obter uma chave pública do repositório](/rest/reference/actions#get-a-repository-public-key) -* [Listar segredos do repositório](/rest/reference/actions#list-repository-secrets) -* [Obter um segredo do repositório](/rest/reference/actions#get-a-repository-secret) -* [Criar ou atualizar o segredo de um repositório](/rest/reference/actions#create-or-update-a-repository-secret) -* [Excluir o segredo de um repositório](/rest/reference/actions#delete-a-repository-secret) -* [Obter chave pública de uma organização](/rest/reference/actions#get-an-organization-public-key) -* [Listar segredos da organização](/rest/reference/actions#list-organization-secrets) -* [Obter segredo de uma organização](/rest/reference/actions#get-an-organization-secret) -* [Criar ou atualizar o segredo de uma organização](/rest/reference/actions#create-or-update-an-organization-secret) -* [Listar repositórios selecionados para o segredo de uma organização](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) -* [Definir repositórios selecionados para o segredo de uma organização](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) -* [Adicionar o repositório selecionado ao segredo de uma organização](/rest/reference/actions#add-selected-repository-to-an-organization-secret) -* [Remover o repositório selecionado do segredo de uma organização](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) -* [Excluir o segredo de uma organização](/rest/reference/actions#delete-an-organization-secret) +* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key) +* [List repository secrets](/rest/reference/actions#list-repository-secrets) +* [Get a repository secret](/rest/reference/actions#get-a-repository-secret) +* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret) +* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret) +* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key) +* [List organization secrets](/rest/reference/actions#list-organization-secrets) +* [Get an organization secret](/rest/reference/actions#get-an-organization-secret) +* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret) +* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret) {% endif %} {% ifversion fpt or ghec %} -#### Artefatos +#### Artifacts -* [Listar artefatos para um repositório](/rest/reference/actions#list-artifacts-for-a-repository) -* [Listar artefatos executados por fluxo de trabalho](/rest/reference/actions#list-workflow-run-artifacts) -* [Obter um artefato](/rest/reference/actions#get-an-artifact) -* [Excluir um artefato](/rest/reference/actions#delete-an-artifact) -* [Fazer o download de um artefato](/rest/reference/actions#download-an-artifact) +* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository) +* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts) +* [Get an artifact](/rest/reference/actions#get-an-artifact) +* [Delete an artifact](/rest/reference/actions#delete-an-artifact) +* [Download an artifact](/rest/reference/actions#download-an-artifact) {% endif %} -#### Execuções de verificação +#### Check Runs -* [Criar uma verificação de execução](/rest/reference/checks#create-a-check-run) -* [Obter uma verificação de execução](/rest/reference/checks#get-a-check-run) -* [Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run) -* [Listar anotações de execução de verificação](/rest/reference/checks#list-check-run-annotations) -* [Listar execuções de verificações em um conjunto de verificações](/rest/reference/checks#list-check-runs-in-a-check-suite) -* [Listar execuções de verificação para uma referência do GIt](/rest/reference/checks#list-check-runs-for-a-git-reference) +* [Create a check run](/rest/reference/checks#create-a-check-run) +* [Get a check run](/rest/reference/checks#get-a-check-run) +* [Update a check run](/rest/reference/checks#update-a-check-run) +* [List check run annotations](/rest/reference/checks#list-check-run-annotations) +* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference) -#### conjuntos de verificações +#### Check Suites -* [Criar um conjunto de verificações](/rest/reference/checks#create-a-check-suite) -* [Obter um conjunto de verificações](/rest/reference/checks#get-a-check-suite) -* [Ressolicitar um conjunto de verificação](/rest/reference/checks#rerequest-a-check-suite) -* [Atualizar preferências do repositório para conjuntos de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites) -* [Listar os conjuntos de verificação para uma referência do Git](/rest/reference/checks#list-check-suites-for-a-git-reference) +* [Create a check suite](/rest/reference/checks#create-a-check-suite) +* [Get a check suite](/rest/reference/checks#get-a-check-suite) +* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite) +* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference) -#### Códigos de conduta +#### Codes Of Conduct -* [Obter todos os códigos de conduta](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) -* [Obter um código de conduta](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct) -#### Status da implementação +#### Deployment Statuses -* [Listar status de implementação](/rest/reference/repos#list-deployment-statuses) -* [Criar um status de implementação](/rest/reference/repos#create-a-deployment-status) -* [Obter um status de implementação](/rest/reference/repos#get-a-deployment-status) +* [List deployment statuses](/rest/reference/repos#list-deployment-statuses) +* [Create a deployment status](/rest/reference/repos#create-a-deployment-status) +* [Get a deployment status](/rest/reference/repos#get-a-deployment-status) -#### Implantações +#### Deployments -* [Listar implementações](/rest/reference/repos#list-deployments) -* [Criar uma implementação](/rest/reference/repos#create-a-deployment) +* [List deployments](/rest/reference/repos#list-deployments) +* [Create a deployment](/rest/reference/repos#create-a-deployment) * [Get a deployment](/rest/reference/repos#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [Excluir um deploy](/rest/reference/repos#delete-a-deployment){% endif %} +* [Delete a deployment](/rest/reference/repos#delete-a-deployment){% endif %} -#### Eventos +#### Events -* [Listar eventos públicos de uma rede de repositórios](/rest/reference/activity#list-public-events-for-a-network-of-repositories) -* [Listar eventos públicos da organização](/rest/reference/activity#list-public-organization-events) +* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories) +* [List public organization events](/rest/reference/activity#list-public-organization-events) #### Feeds -* [Obter feeds](/rest/reference/activity#get-feeds) +* [Get feeds](/rest/reference/activity#get-feeds) -#### Blobs do Git +#### Git Blobs -* [Criar um blob](/rest/reference/git#create-a-blob) -* [Obter um blob](/rest/reference/git#get-a-blob) +* [Create a blob](/rest/reference/git#create-a-blob) +* [Get a blob](/rest/reference/git#get-a-blob) -#### Commits do Git +#### Git Commits -* [Criar um commit](/rest/reference/git#create-a-commit) -* [Obter um commit](/rest/reference/git#get-a-commit) +* [Create a commit](/rest/reference/git#create-a-commit) +* [Get a commit](/rest/reference/git#get-a-commit) -#### Refs do Git +#### Git Refs -* [Criar uma referência](/rest/reference/git#create-a-reference)* [Obter uma referência](/rest/reference/git#get-a-reference) -* [Lista de referências correspondentes](/rest/reference/git#list-matching-references) -* [Atualizar uma referência](/rest/reference/git#update-a-reference) -* [Excluir uma referência](/rest/reference/git#delete-a-reference) +* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference) +* [List matching references](/rest/reference/git#list-matching-references) +* [Update a reference](/rest/reference/git#update-a-reference) +* [Delete a reference](/rest/reference/git#delete-a-reference) -#### Tags do Git +#### Git Tags -* [Criar um objeto de tag](/rest/reference/git#create-a-tag-object) -* [Obter uma tag](/rest/reference/git#get-a-tag) +* [Create a tag object](/rest/reference/git#create-a-tag-object) +* [Get a tag](/rest/reference/git#get-a-tag) -#### Árvores do Git +#### Git Trees -* [Criar uma árvore](/rest/reference/git#create-a-tree) -* [Obter uma árvore](/rest/reference/git#get-a-tree) +* [Create a tree](/rest/reference/git#create-a-tree) +* [Get a tree](/rest/reference/git#get-a-tree) -#### Modelos do Gitignore +#### Gitignore Templates -* [Obter todos os modelos do gitignore](/rest/reference/gitignore#get-all-gitignore-templates) -* [Obter um modelo do gitignore](/rest/reference/gitignore#get-a-gitignore-template) +* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates) +* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template) -#### Instalações +#### Installations -* [Listar repositórios acessíveis ao token de acesso do usuário](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) +* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) {% ifversion fpt or ghec %} -#### Limites de interação +#### Interaction Limits -* [Obter restrições de interação para uma organização](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) -* [Definir restrições de interação para uma organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) -* [Remover restrições de interação para uma organização](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) -* [Obter restrições de interação para um repositório](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) -* [Definir restrições de interação para um repositório](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) -* [Remover restrições de interação para um repositório](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) +* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) {% endif %} -#### Responsáveis pelo problema +#### Issue Assignees -* [Adicionar responsáveis a um problema](/rest/reference/issues#add-assignees-to-an-issue) -* [Remover responsáveis de um problema](/rest/reference/issues#remove-assignees-from-an-issue) +* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue) +* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue) -#### Comentários do problema +#### Issue Comments -* [Listar comentários do problema](/rest/reference/issues#list-issue-comments) -* [Criar um comentário do problema](/rest/reference/issues#create-an-issue-comment) -* [Listar comentários de problemas para um repositório](/rest/reference/issues#list-issue-comments-for-a-repository) -* [Obter um comentário do issue](/rest/reference/issues#get-an-issue-comment) -* [Atualizar um comentário do problema](/rest/reference/issues#update-an-issue-comment) -* [Excluir comentário do problema](/rest/reference/issues#delete-an-issue-comment) +* [List issue comments](/rest/reference/issues#list-issue-comments) +* [Create an issue comment](/rest/reference/issues#create-an-issue-comment) +* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Get an issue comment](/rest/reference/issues#get-an-issue-comment) +* [Update an issue comment](/rest/reference/issues#update-an-issue-comment) +* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment) -#### Eventos do problema +#### Issue Events -* [Listar eventos do problema](/rest/reference/issues#list-issue-events) +* [List issue events](/rest/reference/issues#list-issue-events) -#### Linha do tempo do problema +#### Issue Timeline -* [Listar eventos da linha do tempo para um problema](/rest/reference/issues#list-timeline-events-for-an-issue) +* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue) -#### Problemas +#### Issues -* [Listar problemas atribuídos ao usuário autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) -* [Listar responsáveis](/rest/reference/issues#list-assignees) -* [Verificar se um usuário pode ser atribuído](/rest/reference/issues#check-if-a-user-can-be-assigned) -* [Listar problemas do repositório](/rest/reference/issues#list-repository-issues) -* [Cria um problema](/rest/reference/issues#create-an-issue) -* [Obter um problema](/rest/reference/issues#get-an-issue) -* [Atualizar um problema](/rest/reference/issues#update-an-issue) -* [Bloquear um problema](/rest/reference/issues#lock-an-issue) -* [Desbloquear um problema](/rest/reference/issues#unlock-an-issue) +* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [List assignees](/rest/reference/issues#list-assignees) +* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [List repository issues](/rest/reference/issues#list-repository-issues) +* [Create an issue](/rest/reference/issues#create-an-issue) +* [Get an issue](/rest/reference/issues#get-an-issue) +* [Update an issue](/rest/reference/issues#update-an-issue) +* [Lock an issue](/rest/reference/issues#lock-an-issue) +* [Unlock an issue](/rest/reference/issues#unlock-an-issue) {% ifversion fpt or ghec %} -#### Trabalhos +#### Jobs -* [Obter um trabalho para uma execução de fluxo de trabalho](/rest/reference/actions#get-a-job-for-a-workflow-run) -* [Fazer o download dos registros de trabalho para execução de um fluxo de trabalho](/rest/reference/actions#download-job-logs-for-a-workflow-run) -* [Listar tarefas para execução de um fluxo de trabalho](/rest/reference/actions#list-jobs-for-a-workflow-run) +* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run) {% endif %} -#### Etiquetas +#### Labels -* [Listar etiquetas para um problema](/rest/reference/issues#list-labels-for-an-issue) -* [Adicionar etiquetas a um problema](/rest/reference/issues#add-labels-to-an-issue) -* [Definir etiquetas para um problema](/rest/reference/issues#set-labels-for-an-issue) -* [Remover todas as etiquetas de um problema](/rest/reference/issues#remove-all-labels-from-an-issue) -* [Remover uma etiqueta de um problema](/rest/reference/issues#remove-a-label-from-an-issue) -* [Listar etiquetas para um repositório](/rest/reference/issues#list-labels-for-a-repository) -* [Criar uma etiqueta](/rest/reference/issues#create-a-label) -* [Obter uma etiqueta](/rest/reference/issues#get-a-label) -* [Atualizar uma etiqueta](/rest/reference/issues#update-a-label) -* [Excluir uma etiqueta](/rest/reference/issues#delete-a-label) -* [Obter etiquetas para cada problema em um marco](/rest/reference/issues#list-labels-for-issues-in-a-milestone) +* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue) +* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue) +* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue) +* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue) +* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository) +* [Create a label](/rest/reference/issues#create-a-label) +* [Get a label](/rest/reference/issues#get-a-label) +* [Update a label](/rest/reference/issues#update-a-label) +* [Delete a label](/rest/reference/issues#delete-a-label) +* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone) -#### Licenças +#### Licenses -* [Obter todas as licenças comumente usadas](/rest/reference/licenses#get-all-commonly-used-licenses) -* [Obtenha uma licença](/rest/reference/licenses#get-a-license) +* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Get a license](/rest/reference/licenses#get-a-license) -#### markdown +#### Markdown -* [Renderizar um documento markdown](/rest/reference/markdown#render-a-markdown-document) -* [Renderizar um documento markdown no modo bruto](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document) +* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) #### Meta * [Meta](/rest/reference/meta#meta) -#### Marcos +#### Milestones -* [Listar marcos](/rest/reference/issues#list-milestones) -* [Criar um marco](/rest/reference/issues#create-a-milestone) -* [Obter um marco](/rest/reference/issues#get-a-milestone) -* [Atualizar um marco](/rest/reference/issues#update-a-milestone) -* [Excluir um marco](/rest/reference/issues#delete-a-milestone) +* [List milestones](/rest/reference/issues#list-milestones) +* [Create a milestone](/rest/reference/issues#create-a-milestone) +* [Get a milestone](/rest/reference/issues#get-a-milestone) +* [Update a milestone](/rest/reference/issues#update-a-milestone) +* [Delete a milestone](/rest/reference/issues#delete-a-milestone) -#### Hooks da organização +#### Organization Hooks -* [Listar webhooks da organização](/rest/reference/orgs#webhooks/#list-organization-webhooks) -* [Criar um webhook da organização](/rest/reference/orgs#webhooks/#create-an-organization-webhook) -* [Obter um webhook da organização](/rest/reference/orgs#webhooks/#get-an-organization-webhook) -* [Atualizar um webhook da organização](/rest/reference/orgs#webhooks/#update-an-organization-webhook) -* [Excluir um webhook da organização](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) -* [Consultar um webhook da organização](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) +* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks) +* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook) +* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook) +* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook) +* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) +* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) {% ifversion fpt or ghec %} -#### Convites da organização +#### Organization Invitations -* [Listar convites pendentes para organizações](/rest/reference/orgs#list-pending-organization-invitations) -* [Criar um convite de organização](/rest/reference/orgs#create-an-organization-invitation) -* [Listar equipes de convite da organização](/rest/reference/orgs#list-organization-invitation-teams) +* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations) +* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation) +* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams) {% endif %} -#### Integrantes da organização +#### Organization Members -* [Listar integrantes da organização](/rest/reference/orgs#list-organization-members) -* [Verificar associação da organização para um usuário](/rest/reference/orgs#check-organization-membership-for-a-user) -* [Remover um membro da organização](/rest/reference/orgs#remove-an-organization-member) -* [Obter a associação de uma organização para um usuário](/rest/reference/orgs#get-organization-membership-for-a-user) -* [Definir associação de organização para um usuário](/rest/reference/orgs#set-organization-membership-for-a-user) -* [Remover associação de organização para um usuário](/rest/reference/orgs#remove-organization-membership-for-a-user) -* [Listar membros públicos da organização](/rest/reference/orgs#list-public-organization-members) -* [Verificar a associação da organização pública para um usuário](/rest/reference/orgs#check-public-organization-membership-for-a-user) -* [Definir associação à organização pública para o usuário autenticado](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) -* [Remover associação à organização pública para o usuário autenticado](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) +* [List organization members](/rest/reference/orgs#list-organization-members) +* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member) +* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [List public organization members](/rest/reference/orgs#list-public-organization-members) +* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) -#### Colaboradores externos da organização +#### Organization Outside Collaborators -* [Listar colaboradores externos para uma organização](/rest/reference/orgs#list-outside-collaborators-for-an-organization) -* [Converter um integrante da organização em colaborador externo](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) -* [Remover colaboradores externos de uma organização](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) +* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) {% ifversion ghes %} -#### Hooks pre-receive da organização +#### Organization Pre Receive Hooks -* [Listar hooks pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) -* [Obter um hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) -* [Atualizar a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) -* [Remover a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) +* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) +* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) +* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) +* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} {% ifversion fpt or ghes or ghae or ghec %} -#### Projetos da aquipe da organização +#### Organization Team Projects -* [Listar projetos da equipe](/rest/reference/teams#list-team-projects) -* [Verificar permissões da equipe para um projeto](/rest/reference/teams#check-team-permissions-for-a-project) -* [Adicionar ou atualizar as permissões do projeto da equipe](/rest/reference/teams#add-or-update-team-project-permissions) -* [Remover um projeto de uma equipe](/rest/reference/teams#remove-a-project-from-a-team) +* [List team projects](/rest/reference/teams#list-team-projects) +* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project) +* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions) +* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team) {% endif %} -#### Repositórios da equipe da organização +#### Organization Team Repositories -* [Listar repositórios da equipe](/rest/reference/teams#list-team-repositories) -* [Verificar permissões da equipe para um repositório](/rest/reference/teams#check-team-permissions-for-a-repository) -* [Adicionar ou atualizar as permissões do repositório da equipe](/rest/reference/teams#add-or-update-team-repository-permissions) -* [Remover um repositório de uma equipe](/rest/reference/teams#remove-a-repository-from-a-team) +* [List team repositories](/rest/reference/teams#list-team-repositories) +* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team) {% ifversion fpt or ghec %} -#### Sincronizar equipe da organização +#### Organization Team Sync -* [Listar grupos de idp para uma equipe](/rest/reference/teams#list-idp-groups-for-a-team) -* [Criar ou atualizar conexões do grupo de idp](/rest/reference/teams#create-or-update-idp-group-connections) -* [Listar grupos de IdP para uma organização](/rest/reference/teams#list-idp-groups-for-an-organization) +* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team) +* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections) +* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} -#### Equipes da organização +#### Organization Teams -* [Listar equipes](/rest/reference/teams#list-teams) -* [Criar uma equipe](/rest/reference/teams#create-a-team) -* [Obter uma equipe por nome](/rest/reference/teams#get-a-team-by-name) -* [Atualizar uma equipe](/rest/reference/teams#update-a-team) -* [Excluir uma equipe](/rest/reference/teams#delete-a-team) +* [List teams](/rest/reference/teams#list-teams) +* [Create a team](/rest/reference/teams#create-a-team) +* [Get a team by name](/rest/reference/teams#get-a-team-by-name) +* [Update a team](/rest/reference/teams#update-a-team) +* [Delete a team](/rest/reference/teams#delete-a-team) {% ifversion fpt or ghec %} -* [Listar convites pendentes da equipe](/rest/reference/teams#list-pending-team-invitations) +* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations) {% endif %} -* [Listar integrantes da equipe](/rest/reference/teams#list-team-members) -* [Obter a associação à equipe para um usuário](/rest/reference/teams#get-team-membership-for-a-user) -* [Adicionar ou atualizar membros de equipe para um usuário](/rest/reference/teams#add-or-update-team-membership-for-a-user) -* [Remover associação à equipe para um usuário](/rest/reference/teams#remove-team-membership-for-a-user) -* [Listar equipes secundárias](/rest/reference/teams#list-child-teams) -* [Listar equipes para o usuário autenticado](/rest/reference/teams#list-teams-for-the-authenticated-user) +* [List team members](/rest/reference/teams#list-team-members) +* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user) +* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) +* [List child teams](/rest/reference/teams#list-child-teams) +* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user) -#### Organizações +#### Organizations -* [Listar organizações](/rest/reference/orgs#list-organizations) -* [Obter uma organização](/rest/reference/orgs#get-an-organization) -* [Atualizar uma organização](/rest/reference/orgs#update-an-organization) -* [Listar associações de organizações para os usuários autenticados](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) -* [Obter uma associação de organização para o usuário autenticado](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) -* [Atualizar uma associação de organização para o usuário autenticado](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) -* [Listar organizações para o usuário autenticado](/rest/reference/orgs#list-organizations-for-the-authenticated-user) -* [Listar organizações para um usuário](/rest/reference/orgs#list-organizations-for-a-user) +* [List organizations](/rest/reference/orgs#list-organizations) +* [Get an organization](/rest/reference/orgs#get-an-organization) +* [Update an organization](/rest/reference/orgs#update-an-organization) +* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user) {% ifversion fpt or ghec %} -#### Autorizações de credencial das organizações +#### Organizations Credential Authorizations -* [Listar autorizações do SAML SSO para uma organização](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) -* [Remover uma autorização do SAML SSO para uma organização](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) +* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %} {% ifversion fpt or ghec %} -#### Scim das organizações +#### Organizations Scim -* [Listar identidades provisionadas de SCIM](/rest/reference/scim#list-scim-provisioned-identities) -* [Provisionamento e convite para um usuário de SCIM](/rest/reference/scim#provision-and-invite-a-scim-user) -* [Obter informações de provisionamento de SCIM para um usuário](/rest/reference/scim#get-scim-provisioning-information-for-a-user) -* [Definir informações de SCIM para um usuário provisionado](/rest/reference/scim#set-scim-information-for-a-provisioned-user) -* [Atualizar um atributo para um usuário de SCIM](/rest/reference/scim#update-an-attribute-for-a-scim-user) -* [Excluir um usuário de SCIM de uma organização](/rest/reference/scim#delete-a-scim-user-from-an-organization) +* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities) +* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization) {% endif %} {% ifversion fpt or ghec %} -#### Importação de fonte +#### Source Imports -* [Obter um status de importação](/rest/reference/migrations#get-an-import-status) -* [Iniciar importação](/rest/reference/migrations#start-an-import) -* [Atualizar uma importação](/rest/reference/migrations#update-an-import) -* [Cancelar uma importação](/rest/reference/migrations#cancel-an-import) -* [Obtenha autores do commit](/rest/reference/migrations#get-commit-authors) -* [Mapear um autor de commit](/rest/reference/migrations#map-a-commit-author) -* [Obter arquivos grandes](/rest/reference/migrations#get-large-files) -* [Atualizar preferência de LFS do Git](/rest/reference/migrations#update-git-lfs-preference) +* [Get an import status](/rest/reference/migrations#get-an-import-status) +* [Start an import](/rest/reference/migrations#start-an-import) +* [Update an import](/rest/reference/migrations#update-an-import) +* [Cancel an import](/rest/reference/migrations#cancel-an-import) +* [Get commit authors](/rest/reference/migrations#get-commit-authors) +* [Map a commit author](/rest/reference/migrations#map-a-commit-author) +* [Get large files](/rest/reference/migrations#get-large-files) +* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference) {% endif %} -#### Colaboradores do projeto +#### Project Collaborators -* [Listar colaboradores do projeto](/rest/reference/projects#list-project-collaborators) -* [Adicionar colaborador do projeto](/rest/reference/projects#add-project-collaborator) -* [Remover colaborador do projeto](/rest/reference/projects#remove-project-collaborator) -* [Obter permissão de projeto para um usuário](/rest/reference/projects#get-project-permission-for-a-user) +* [List project collaborators](/rest/reference/projects#list-project-collaborators) +* [Add project collaborator](/rest/reference/projects#add-project-collaborator) +* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator) +* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user) -#### Projetos +#### Projects -* [Listar projetos da organização](/rest/reference/projects#list-organization-projects) -* [Criar um projeto da organização](/rest/reference/projects#create-an-organization-project) -* [Obter um projeto](/rest/reference/projects#get-a-project) -* [Atualizar um projeto](/rest/reference/projects#update-a-project) -* [Excluir um projeto](/rest/reference/projects#delete-a-project) -* [Listar colunas do projeto](/rest/reference/projects#list-project-columns) -* [Criar uma coluna do projeto](/rest/reference/projects#create-a-project-column) -* [Obter uma coluna do projeto](/rest/reference/projects#get-a-project-column) -* [Atualizar uma coluna do projeto](/rest/reference/projects#update-a-project-column) -* [Excluir uma coluna do projeto](/rest/reference/projects#delete-a-project-column) -* [Listar cartões do projeto](/rest/reference/projects#list-project-cards) -* [Criar um cartão de projeto](/rest/reference/projects#create-a-project-card) -* [Mover uma coluna do projeto](/rest/reference/projects#move-a-project-column) -* [Obter um cartão do projeto](/rest/reference/projects#get-a-project-card) -* [Atualizar um cartão do projeto](/rest/reference/projects#update-a-project-card) -* [Excluir um cartão do projeto](/rest/reference/projects#delete-a-project-card) -* [Mover um cartão do projeto](/rest/reference/projects#move-a-project-card) -* [Listar projetos do repositório](/rest/reference/projects#list-repository-projects) -* [Criar um projeto do repositório](/rest/reference/projects#create-a-repository-project) +* [List organization projects](/rest/reference/projects#list-organization-projects) +* [Create an organization project](/rest/reference/projects#create-an-organization-project) +* [Get a project](/rest/reference/projects#get-a-project) +* [Update a project](/rest/reference/projects#update-a-project) +* [Delete a project](/rest/reference/projects#delete-a-project) +* [List project columns](/rest/reference/projects#list-project-columns) +* [Create a project column](/rest/reference/projects#create-a-project-column) +* [Get a project column](/rest/reference/projects#get-a-project-column) +* [Update a project column](/rest/reference/projects#update-a-project-column) +* [Delete a project column](/rest/reference/projects#delete-a-project-column) +* [List project cards](/rest/reference/projects#list-project-cards) +* [Create a project card](/rest/reference/projects#create-a-project-card) +* [Move a project column](/rest/reference/projects#move-a-project-column) +* [Get a project card](/rest/reference/projects#get-a-project-card) +* [Update a project card](/rest/reference/projects#update-a-project-card) +* [Delete a project card](/rest/reference/projects#delete-a-project-card) +* [Move a project card](/rest/reference/projects#move-a-project-card) +* [List repository projects](/rest/reference/projects#list-repository-projects) +* [Create a repository project](/rest/reference/projects#create-a-repository-project) -#### Commentários pull +#### Pull Comments -* [Listar comentários de revisão em um pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) -* [Criar um comentário de revisão para um pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) -* [Listar comentários de revisão em um repositório](/rest/reference/pulls#list-review-comments-in-a-repository) -* [Obter um comentário de revisão para um pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) -* [Atualizar um comentário de revisão para um pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) -* [Excluir um comentário de revisão para um pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) +* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) -#### Eventos de revisão de pull request +#### Pull Request Review Events -* [Ignorar uma revisão para um pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) -* [Enviar uma revisão para um pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) +* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request) -#### Solicitações de revisão de pull request +#### Pull Request Review Requests -* [Listar revisores solicitados para um pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) -* [Solicitar revisores para um pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) -* [Remover revisores solicitados de um pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) +* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) -#### Revisões de pull request +#### Pull Request Reviews -* [Listar comentários para um pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) -* [Criar uma revisão para um pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) -* [Obter uma revisão para um pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) -* [Atualizar uma revisão para um pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) -* [Listar comentários para uma revisão de pull request](/rest/reference/pulls#list-comments-for-a-pull-request-review) +* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review) #### Pulls -* [Listar pull requests](/rest/reference/pulls#list-pull-requests) -* [Criar um pull request](/rest/reference/pulls#create-a-pull-request) -* [Obter um pull request](/rest/reference/pulls#get-a-pull-request) -* [Atualizar um pull request](/rest/reference/pulls#update-a-pull-request) -* [Listar commits em um pull request](/rest/reference/pulls#list-commits-on-a-pull-request) -* [Listar arquivos de pull requests](/rest/reference/pulls#list-pull-requests-files) -* [Verifiarse um pull request foi mesclado](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) -* [Mesclar um pull request (Botão de mesclar)](/rest/reference/pulls#merge-a-pull-request) +* [List pull requests](/rest/reference/pulls#list-pull-requests) +* [Create a pull request](/rest/reference/pulls#create-a-pull-request) +* [Get a pull request](/rest/reference/pulls#get-a-pull-request) +* [Update a pull request](/rest/reference/pulls#update-a-pull-request) +* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request) +* [List pull requests files](/rest/reference/pulls#list-pull-requests-files) +* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request) -#### Reações +#### Reactions {% ifversion fpt or ghes or ghae or ghec %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %} -* [Listar reações para um comentário de commit](/rest/reference/reactions#list-reactions-for-a-commit-comment) -* [Criar reação para um comentário de commit](/rest/reference/reactions#create-reaction-for-a-commit-comment) -* [Listar reações para um problema](/rest/reference/reactions#list-reactions-for-an-issue) -* [Criar reação para um problema](/rest/reference/reactions#create-reaction-for-an-issue) -* [Listar reações para um comentário do problema](/rest/reference/reactions#list-reactions-for-an-issue-comment) -* [Criar reação para um comentário do problema](/rest/reference/reactions#create-reaction-for-an-issue-comment) -* [Listar reações para um comentário de revisão de pull request](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) -* [Criar reação para um comentário de revisão de pull request](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) -* [Listar reações para um comentário de discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) -* [Criar reação para um comentário de discussão em equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) -* [Listar reações para uma discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue) +* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue) +* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion) * [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} -* [Excluir uma reação de comentário de commit](/rest/reference/reactions#delete-a-commit-comment-reaction) -* [Excluir uma reação do problema](/rest/reference/reactions#delete-an-issue-reaction) -* [Excluir uma reação a um comentário do commit](/rest/reference/reactions#delete-an-issue-comment-reaction) -* [Excluir reação de comentário do pull request](/rest/reference/reactions#delete-a-pull-request-comment-reaction) -* [Excluir reação para discussão em equipe](/rest/reference/reactions#delete-team-discussion-reaction) -* [Excluir reação de comentário para discussão de equipe](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction) +* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction) +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} -#### Repositórios +#### Repositories -* [Listar repositórios da organização](/rest/reference/repos#list-organization-repositories) -* [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) -* [Obter um repositório](/rest/reference/repos#get-a-repository) -* [Atualizar um repositório](/rest/reference/repos#update-a-repository) -* [Excluir um repositório](/rest/reference/repos#delete-a-repository) -* [Comparar dois commits](/rest/reference/repos#compare-two-commits) -* [Listar contribuidores do repositório](/rest/reference/repos#list-repository-contributors) -* [Listar bifurcações](/rest/reference/repos#list-forks) -* [Criar uma bifurcação](/rest/reference/repos#create-a-fork) -* [Listar idiomas do repositório](/rest/reference/repos#list-repository-languages) -* [Listar tags do repositório](/rest/reference/repos#list-repository-tags) -* [Listar equipes do repositório](/rest/reference/repos#list-repository-teams) -* [Transferir um repositório](/rest/reference/repos#transfer-a-repository) -* [Listar repositórios públicos](/rest/reference/repos#list-public-repositories) -* [Listar repositórios para o usuário autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user) -* [Listar repositórios para um usuário](/rest/reference/repos#list-repositories-for-a-user) -* [Criar repositório usando um modelo de repositório](/rest/reference/repos#create-repository-using-a-repository-template) +* [List organization repositories](/rest/reference/repos#list-organization-repositories) +* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [Get a repository](/rest/reference/repos#get-a-repository) +* [Update a repository](/rest/reference/repos#update-a-repository) +* [Delete a repository](/rest/reference/repos#delete-a-repository) +* [Compare two commits](/rest/reference/repos#compare-two-commits) +* [List repository contributors](/rest/reference/repos#list-repository-contributors) +* [List forks](/rest/reference/repos#list-forks) +* [Create a fork](/rest/reference/repos#create-a-fork) +* [List repository languages](/rest/reference/repos#list-repository-languages) +* [List repository tags](/rest/reference/repos#list-repository-tags) +* [List repository teams](/rest/reference/repos#list-repository-teams) +* [Transfer a repository](/rest/reference/repos#transfer-a-repository) +* [List public repositories](/rest/reference/repos#list-public-repositories) +* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user) +* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template) -#### Atividade do repositório +#### Repository Activity -* [Listar observadores](/rest/reference/activity#list-stargazers) -* [Listar inspetores](/rest/reference/activity#list-watchers) -* [Listar repositórios favoritados pelo usuário](/rest/reference/activity#list-repositories-starred-by-a-user) -* [Verificar se um repositório foi favoritado pelo usuário autenticado](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) -* [Favorite um repositório para o usuário autenticado](/rest/reference/activity#star-a-repository-for-the-authenticated-user) -* [Desmarque um repositório como favorito para o usuário autenticado](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) -* [Listar repositórios inspecionados por um usuário](/rest/reference/activity#list-repositories-watched-by-a-user) +* [List stargazers](/rest/reference/activity#list-stargazers) +* [List watchers](/rest/reference/activity#list-watchers) +* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user) +* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) +* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user) +* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) +* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user) {% ifversion fpt or ghec %} -#### Correções de segurança automatizadas no repositório +#### Repository Automated Security Fixes -* [Habilitar as correções de segurança automatizadas](/rest/reference/repos#enable-automated-security-fixes) -* [Desabilitar as correções de segurança automatizadas](/rest/reference/repos#disable-automated-security-fixes) +* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes) +* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes) {% endif %} -#### Branches do repositório +#### Repository Branches -* [Listar branches](/rest/reference/repos#list-branches) -* [Obter um branch](/rest/reference/repos#get-a-branch) -* [Obter proteção do branch](/rest/reference/repos#get-branch-protection) -* [Atualizar proteção do branch](/rest/reference/repos#update-branch-protection) -* [Excluir proteção do branch](/rest/reference/repos#delete-branch-protection) -* [Obter proteção do branch do administrador](/rest/reference/repos#get-admin-branch-protection) -* [Definir proteção do branch de administrador](/rest/reference/repos#set-admin-branch-protection) -* [Excluir proteção do branch de administrador](/rest/reference/repos#delete-admin-branch-protection) -* [Obter proteção de revisão do pull request](/rest/reference/repos#get-pull-request-review-protection) -* [Atualizar proteção de revisão do pull request](/rest/reference/repos#update-pull-request-review-protection) -* [Excluir proteção de revisão do pull request](/rest/reference/repos#delete-pull-request-review-protection) -* [Obter proteção de assinatura do commit](/rest/reference/repos#get-commit-signature-protection) -* [Criar proteção de assinatura do commit](/rest/reference/repos#create-commit-signature-protection) -* [Excluir proteção de assinatura do commit](/rest/reference/repos#delete-commit-signature-protection) -* [Obter proteção contra verificações de status](/rest/reference/repos#get-status-checks-protection) -* [Atualizar proteção da verificação de status](/rest/reference/repos#update-status-check-protection) -* [Remover proteção da verificação de status](/rest/reference/repos#remove-status-check-protection) -* [Obter todos os contextos de verificação de status](/rest/reference/repos#get-all-status-check-contexts) -* [Adicionar contextos de verificação de status](/rest/reference/repos#add-status-check-contexts) -* [Definir contextos de verificação de status](/rest/reference/repos#set-status-check-contexts) -* [Remover contextos de verificação de status](/rest/reference/repos#remove-status-check-contexts) -* [Obter restrições de acesso](/rest/reference/repos#get-access-restrictions) -* [Excluir restrições de acesso](/rest/reference/repos#delete-access-restrictions) -* [Listar equipes com acesso ao branch protegido](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) -* [Adicionar restrições de acesso da equipe](/rest/reference/repos#add-team-access-restrictions) -* [Definir restrições de acesso da equipe](/rest/reference/repos#set-team-access-restrictions) -* [Remover restrição de acesso da equipe](/rest/reference/repos#remove-team-access-restrictions) -* [Listar restrições de usuário do branch protegido](/rest/reference/repos#list-users-with-access-to-the-protected-branch) -* [Adicionar restrições de acesso do usuário](/rest/reference/repos#add-user-access-restrictions) -* [Definir restrições de acesso do usuário](/rest/reference/repos#set-user-access-restrictions) -* [Remover restrições de acesso do usuário](/rest/reference/repos#remove-user-access-restrictions) -* [Mesclar um branch](/rest/reference/repos#merge-a-branch) +* [List branches](/rest/reference/repos#list-branches) +* [Get a branch](/rest/reference/repos#get-a-branch) +* [Get branch protection](/rest/reference/repos#get-branch-protection) +* [Update branch protection](/rest/reference/repos#update-branch-protection) +* [Delete branch protection](/rest/reference/repos#delete-branch-protection) +* [Get admin branch protection](/rest/reference/repos#get-admin-branch-protection) +* [Set admin branch protection](/rest/reference/repos#set-admin-branch-protection) +* [Delete admin branch protection](/rest/reference/repos#delete-admin-branch-protection) +* [Get pull request review protection](/rest/reference/repos#get-pull-request-review-protection) +* [Update pull request review protection](/rest/reference/repos#update-pull-request-review-protection) +* [Delete pull request review protection](/rest/reference/repos#delete-pull-request-review-protection) +* [Get commit signature protection](/rest/reference/repos#get-commit-signature-protection) +* [Create commit signature protection](/rest/reference/repos#create-commit-signature-protection) +* [Delete commit signature protection](/rest/reference/repos#delete-commit-signature-protection) +* [Get status checks protection](/rest/reference/repos#get-status-checks-protection) +* [Update status check protection](/rest/reference/repos#update-status-check-protection) +* [Remove status check protection](/rest/reference/repos#remove-status-check-protection) +* [Get all status check contexts](/rest/reference/repos#get-all-status-check-contexts) +* [Add status check contexts](/rest/reference/repos#add-status-check-contexts) +* [Set status check contexts](/rest/reference/repos#set-status-check-contexts) +* [Remove status check contexts](/rest/reference/repos#remove-status-check-contexts) +* [Get access restrictions](/rest/reference/repos#get-access-restrictions) +* [Delete access restrictions](/rest/reference/repos#delete-access-restrictions) +* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Add team access restrictions](/rest/reference/repos#add-team-access-restrictions) +* [Set team access restrictions](/rest/reference/repos#set-team-access-restrictions) +* [Remove team access restriction](/rest/reference/repos#remove-team-access-restrictions) +* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Add user access restrictions](/rest/reference/repos#add-user-access-restrictions) +* [Set user access restrictions](/rest/reference/repos#set-user-access-restrictions) +* [Remove user access restrictions](/rest/reference/repos#remove-user-access-restrictions) +* [Merge a branch](/rest/reference/repos#merge-a-branch) -#### Colaboradores do repositório +#### Repository Collaborators -* [Listar colaboradores do repositório](/rest/reference/repos#list-repository-collaborators) -* [Verifique se um usuário é colaborador de um repositório](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) -* [Adicionar colaborador de repositório](/rest/reference/repos#add-a-repository-collaborator) -* [Remover um colaborador de repositório](/rest/reference/repos#remove-a-repository-collaborator) -* [Obter permissões de repositório para um usuário](/rest/reference/repos#get-repository-permissions-for-a-user) +* [List repository collaborators](/rest/reference/repos#list-repository-collaborators) +* [Check if a user is a repository collaborator](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator) +* [Remove a repository collaborator](/rest/reference/repos#remove-a-repository-collaborator) +* [Get repository permissions for a user](/rest/reference/repos#get-repository-permissions-for-a-user) -#### Comentários do commit do repositório +#### Repository Commit Comments -* [Listar comentários de commit para um repositório](/rest/reference/repos#list-commit-comments-for-a-repository) -* [Obter um comentário de commit](/rest/reference/repos#get-a-commit-comment) -* [Atualizar um comentário de commit](/rest/reference/repos#update-a-commit-comment) -* [Excluir um comentário de commit](/rest/reference/repos#delete-a-commit-comment) -* [Listar comentários de commit](/rest/reference/repos#list-commit-comments) -* [Criar um comentário de commit](/rest/reference/repos#create-a-commit-comment) +* [List commit comments for a repository](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Get a commit comment](/rest/reference/repos#get-a-commit-comment) +* [Update a commit comment](/rest/reference/repos#update-a-commit-comment) +* [Delete a commit comment](/rest/reference/repos#delete-a-commit-comment) +* [List commit comments](/rest/reference/repos#list-commit-comments) +* [Create a commit comment](/rest/reference/repos#create-a-commit-comment) -#### Commits do repositório +#### Repository Commits -* [Listar commits](/rest/reference/repos#list-commits) -* [Obter um commit](/rest/reference/repos#get-a-commit) -* [Listar branches para o commit principal](/rest/reference/repos#list-branches-for-head-commit) -* [Listar pull requests associados ao commit](/rest/reference/repos#list-pull-requests-associated-with-commit) +* [List commits](/rest/reference/repos#list-commits) +* [Get a commit](/rest/reference/repos#get-a-commit) +* [List branches for head commit](/rest/reference/repos#list-branches-for-head-commit) +* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit) -#### Comunidade do repositório +#### Repository Community -* [Obter o código de conduta para um repositório](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) +* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% ifversion fpt or ghec %} -* [Obter métricas do perfil da comunidade](/rest/reference/repos#get-community-profile-metrics) +* [Get community profile metrics](/rest/reference/repos#get-community-profile-metrics) {% endif %} -#### Conteúdo do repositório +#### Repository Contents -* [Fazer o download de um arquivo do repositório](/rest/reference/repos#download-a-repository-archive) -* [Obter conteúdo de repositório](/rest/reference/repos#get-repository-content) -* [Criar ou atualizar conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents) -* [Excluir um arquivo](/rest/reference/repos#delete-a-file) -* [Obter um README do repositório](/rest/reference/repos#get-a-repository-readme) -* [Obter a licença para um repositório](/rest/reference/licenses#get-the-license-for-a-repository) +* [Download a repository archive](/rest/reference/repos#download-a-repository-archive) +* [Get repository content](/rest/reference/repos#get-repository-content) +* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents) +* [Delete a file](/rest/reference/repos#delete-a-file) +* [Get a repository README](/rest/reference/repos#get-a-repository-readme) +* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository) {% ifversion fpt or ghes or ghae or ghec %} -#### Envio de eventos do repositório +#### Repository Event Dispatches -* [Criar um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event) +* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event) {% endif %} -#### Hooks do repositório +#### Repository Hooks -* [Listar webhooks de repositório](/rest/reference/repos#list-repository-webhooks) -* [Criar um webhook do repositório](/rest/reference/repos#create-a-repository-webhook) -* [Obter um webhook do repositório](/rest/reference/repos#get-a-repository-webhook) -* [Atualizar um webhook do repositório](/rest/reference/repos#update-a-repository-webhook) -* [Excluir um webhook do repositório](/rest/reference/repos#delete-a-repository-webhook) -* [Fazer ping no webhook de um repositório](/rest/reference/repos#ping-a-repository-webhook) -* [Testar o webhook do repositório de push](/rest/reference/repos#test-the-push-repository-webhook) +* [List repository webhooks](/rest/reference/repos#list-repository-webhooks) +* [Create a repository webhook](/rest/reference/repos#create-a-repository-webhook) +* [Get a repository webhook](/rest/reference/repos#get-a-repository-webhook) +* [Update a repository webhook](/rest/reference/repos#update-a-repository-webhook) +* [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) +* [Ping a repository webhook](/rest/reference/repos#ping-a-repository-webhook) +* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook) -#### Convites do repositório +#### Repository Invitations -* [Listar convites para repositórios](/rest/reference/repos#list-repository-invitations) -* [Atualizar um convite para um repositório](/rest/reference/repos#update-a-repository-invitation) -* [Excluir um convite para um repositório](/rest/reference/repos#delete-a-repository-invitation) -* [Listar convites de repositório para o usuário autenticado](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) -* [Aceitar um convite de repositório](/rest/reference/repos#accept-a-repository-invitation) -* [Recusar um convite de repositório](/rest/reference/repos#decline-a-repository-invitation) +* [List repository invitations](/rest/reference/repos#list-repository-invitations) +* [Update a repository invitation](/rest/reference/repos#update-a-repository-invitation) +* [Delete a repository invitation](/rest/reference/repos#delete-a-repository-invitation) +* [List repository invitations for the authenticated user](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Accept a repository invitation](/rest/reference/repos#accept-a-repository-invitation) +* [Decline a repository invitation](/rest/reference/repos#decline-a-repository-invitation) -#### Chaves de repositório +#### Repository Keys -* [Listar chaves de implantação](/rest/reference/repos#list-deploy-keys) -* [Criar uma chave de implantação](/rest/reference/repos#create-a-deploy-key) -* [Obter uma chave de implantação](/rest/reference/repos#get-a-deploy-key) -* [Excluir uma chave de implantação](/rest/reference/repos#delete-a-deploy-key) +* [List deploy keys](/rest/reference/repos#list-deploy-keys) +* [Create a deploy key](/rest/reference/repos#create-a-deploy-key) +* [Get a deploy key](/rest/reference/repos#get-a-deploy-key) +* [Delete a deploy key](/rest/reference/repos#delete-a-deploy-key) -#### Páginas do repositório +#### Repository Pages -* [Obter um site do GitHub Pages](/rest/reference/repos#get-a-github-pages-site) -* [Criar um site do GitHub Pages](/rest/reference/repos#create-a-github-pages-site) -* [Atualizar informações sobre um site do GitHub Pages](/rest/reference/repos#update-information-about-a-github-pages-site) -* [Excluir um site do GitHub Pages](/rest/reference/repos#delete-a-github-pages-site) -* [Listar criações do GitHub Pages](/rest/reference/repos#list-github-pages-builds) -* [Solicitar uma criação do GitHub Pages](/rest/reference/repos#request-a-github-pages-build) -* [Obter uma criação do GitHub Pages](/rest/reference/repos#get-github-pages-build) -* [Obter a última criação de páginas](/rest/reference/repos#get-latest-pages-build) +* [Get a GitHub Pages site](/rest/reference/repos#get-a-github-pages-site) +* [Create a GitHub Pages site](/rest/reference/repos#create-a-github-pages-site) +* [Update information about a GitHub Pages site](/rest/reference/repos#update-information-about-a-github-pages-site) +* [Delete a GitHub Pages site](/rest/reference/repos#delete-a-github-pages-site) +* [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) +* [Request a GitHub Pages build](/rest/reference/repos#request-a-github-pages-build) +* [Get GitHub Pages build](/rest/reference/repos#get-github-pages-build) +* [Get latest pages build](/rest/reference/repos#get-latest-pages-build) {% ifversion ghes %} -#### Hooks pre-receive do repositório +#### Repository Pre Receive Hooks -* [Listar hooks pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) -* [Obter um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) -* [Atualizar a aplicação de um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) -* [Remover a aplicação de um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) +* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) +* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) +* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) +* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) {% endif %} -#### Versões do repositório +#### Repository Releases -* [Listar versões](/rest/reference/repos/#list-releases) -* [Criar uma versão](/rest/reference/repos/#create-a-release) -* [Obter uma versão](/rest/reference/repos/#get-a-release) -* [Atualizar uma versão](/rest/reference/repos/#update-a-release) -* [Excluir uma versão](/rest/reference/repos/#delete-a-release) -* [Listar ativos da versão](/rest/reference/repos/#list-release-assets) -* [Obter um ativo da versão](/rest/reference/repos/#get-a-release-asset) -* [Atualizar um ativo da versão](/rest/reference/repos/#update-a-release-asset) -* [Excluir um ativo da versão](/rest/reference/repos/#delete-a-release-asset) -* [Obter a atualização mais recente](/rest/reference/repos/#get-the-latest-release) -* [Obter uma versão pelo nome da tag](/rest/reference/repos/#get-a-release-by-tag-name) +* [List releases](/rest/reference/repos/#list-releases) +* [Create a release](/rest/reference/repos/#create-a-release) +* [Get a release](/rest/reference/repos/#get-a-release) +* [Update a release](/rest/reference/repos/#update-a-release) +* [Delete a release](/rest/reference/repos/#delete-a-release) +* [List release assets](/rest/reference/repos/#list-release-assets) +* [Get a release asset](/rest/reference/repos/#get-a-release-asset) +* [Update a release asset](/rest/reference/repos/#update-a-release-asset) +* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset) +* [Get the latest release](/rest/reference/repos/#get-the-latest-release) +* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name) -#### Estatísticas do repositório +#### Repository Stats -* [Obter a atividade semanal do commit](/rest/reference/repos#get-the-weekly-commit-activity) -* [Obter o último ano da atividade de commit](/rest/reference/repos#get-the-last-year-of-commit-activity) -* [Obter toda a atividade do commit do contribuidor](/rest/reference/repos#get-all-contributor-commit-activity) -* [Obter a contagem semanal do commit](/rest/reference/repos#get-the-weekly-commit-count) -* [Obter a contagem do commit por hora para cada dia](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) +* [Get the weekly commit activity](/rest/reference/repos#get-the-weekly-commit-activity) +* [Get the last year of commit activity](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Get all contributor commit activity](/rest/reference/repos#get-all-contributor-commit-activity) +* [Get the weekly commit count](/rest/reference/repos#get-the-weekly-commit-count) +* [Get the hourly commit count for each day](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) {% ifversion fpt or ghec %} -#### Alertas de vulnerabilidade de repositório +#### Repository Vulnerability Alerts -* [Habilitar alertas de vulnerabilidade](/rest/reference/repos#enable-vulnerability-alerts) -* [Desabilitar alertas de vulnerabilidade](/rest/reference/repos#disable-vulnerability-alerts) +* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts) +* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts) {% endif %} -#### Raiz +#### Root -* [Ponto de extremidade raiz](/rest#root-endpoint) +* [Root endpoint](/rest#root-endpoint) * [Emojis](/rest/reference/emojis#emojis) -* [Obter status do limite de taxa para o usuário autenticado](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) -#### Pesquisar +#### Search -* [Buscar código](/rest/reference/search#search-code) -* [Pesquisar commits](/rest/reference/search#search-commits) -* [Pesquisar etiquetas](/rest/reference/search#search-labels) -* [Pesquisar repositórios](/rest/reference/search#search-repositories) -* [Pesquisar tópicos](/rest/reference/search#search-topics) -* [Pesquisar usuários](/rest/reference/search#search-users) +* [Search code](/rest/reference/search#search-code) +* [Search commits](/rest/reference/search#search-commits) +* [Search labels](/rest/reference/search#search-labels) +* [Search repositories](/rest/reference/search#search-repositories) +* [Search topics](/rest/reference/search#search-topics) +* [Search users](/rest/reference/search#search-users) -#### Status +#### Statuses -* [Obter o status combinado para uma referência específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) -* [Listar status de commit para uma referência](/rest/reference/repos#list-commit-statuses-for-a-reference) -* [Criar um status de commit](/rest/reference/repos#create-a-commit-status) +* [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [List commit statuses for a reference](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Create a commit status](/rest/reference/repos#create-a-commit-status) -#### Discussões de equipe +#### Team Discussions -* [Listar discussões](/rest/reference/teams#list-discussions) -* [Criar discussão](/rest/reference/teams#create-a-discussion) -* [Obter discussão](/rest/reference/teams#get-a-discussion) -* [Atualizar uma discussão](/rest/reference/teams#update-a-discussion) -* [Excluir uma discussão](/rest/reference/teams#delete-a-discussion) -* [Listar comentários da discussão](/rest/reference/teams#list-discussion-comments) -* [Criar um comentário da discussão](/rest/reference/teams#create-a-discussion-comment) -* [Obter um comentário da discussão](/rest/reference/teams#get-a-discussion-comment) -* [Atualizar um comentário da discussão](/rest/reference/teams#update-a-discussion-comment) -* [Excluir um comentário da discussão](/rest/reference/teams#delete-a-discussion-comment) +* [List discussions](/rest/reference/teams#list-discussions) +* [Create a discussion](/rest/reference/teams#create-a-discussion) +* [Get a discussion](/rest/reference/teams#get-a-discussion) +* [Update a discussion](/rest/reference/teams#update-a-discussion) +* [Delete a discussion](/rest/reference/teams#delete-a-discussion) +* [List discussion comments](/rest/reference/teams#list-discussion-comments) +* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment) +* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment) +* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment) +* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment) -#### Tópicos +#### Topics -* [Obter todos os tópicos do repositório](/rest/reference/repos#get-all-repository-topics) -* [Substituir todos os tópicos do repositório](/rest/reference/repos#replace-all-repository-topics) +* [Get all repository topics](/rest/reference/repos#get-all-repository-topics) +* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics) {% ifversion fpt or ghec %} -#### Tráfego +#### Traffic -* [Obter clones do repositório](/rest/reference/repos#get-repository-clones) -* [Obter caminhos de referência superior](/rest/reference/repos#get-top-referral-paths) -* [Obter fontes de referência superior](/rest/reference/repos#get-top-referral-sources) -* [Obter visualizações de páginas](/rest/reference/repos#get-page-views) +* [Get repository clones](/rest/reference/repos#get-repository-clones) +* [Get top referral paths](/rest/reference/repos#get-top-referral-paths) +* [Get top referral sources](/rest/reference/repos#get-top-referral-sources) +* [Get page views](/rest/reference/repos#get-page-views) {% endif %} {% ifversion fpt or ghec %} -#### Bloquear usuário +#### User Blocking -* [Listar usuários bloqueados pelo usuário autenticado](/rest/reference/users#list-users-blocked-by-the-authenticated-user) -* [Verificar se um usuário está bloqueado pelo usuário autenticado](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) -* [Listar usuários bloqueados por uma organização](/rest/reference/orgs#list-users-blocked-by-an-organization) -* [Verificar se um usuário está bloqueado por uma organização](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) -* [Bloquear um usuário de uma organização](/rest/reference/orgs#block-a-user-from-an-organization) -* [Desbloquear um usuário de uma organização](/rest/reference/orgs#unblock-a-user-from-an-organization) -* [Bloquear usuário](/rest/reference/users#block-a-user) -* [Desbloquear usuário](/rest/reference/users#unblock-a-user) +* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization) +* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Block a user](/rest/reference/users#block-a-user) +* [Unblock a user](/rest/reference/users#unblock-a-user) {% endif %} {% ifversion fpt or ghes or ghec %} -#### Emails do usuário +#### User Emails {% ifversion fpt or ghec %} -* [Configurar visibilidade do e-mail principal para o usuário autenticado](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) +* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %} -* [Listar endereços de e-mail para o usuário autenticado](/rest/reference/users#list-email-addresses-for-the-authenticated-user) -* [Adicionar endereço(s) de e-mail](/rest/reference/users#add-an-email-address-for-the-authenticated-user) -* [Excluir endereço(s) de e-mail](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) -* [Listar endereços de e-mail públicos para o usuário autenticado](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) +* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) {% endif %} -#### Seguidores do usuário +#### User Followers -* [Listar seguidores de um usuário](/rest/reference/users#list-followers-of-a-user) -* [Listar as pessoas que um usuário segue](/rest/reference/users#list-the-people-a-user-follows) -* [Verificar se uma pessoa é seguida pelo usuário autenticado](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) -* [Seguir um usuário](/rest/reference/users#follow-a-user) -* [Deixar de seguir um usuário](/rest/reference/users#unfollow-a-user) -* [Verificar se um usuário segue outro usuário](/rest/reference/users#check-if-a-user-follows-another-user) +* [List followers of a user](/rest/reference/users#list-followers-of-a-user) +* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows) +* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Follow a user](/rest/reference/users#follow-a-user) +* [Unfollow a user](/rest/reference/users#unfollow-a-user) +* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user) -#### Chaves Gpg do usuário +#### User Gpg Keys -* [Listar chaves GPG para o usuário autenticado](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) -* [Criar uma chave GPG para o usuário autenticado](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) -* [Obter uma chave GPG para o usuário autenticado](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) -* [Excluir uma chave GPG para o usuário autenticado](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) -* [Listar chaves gpg para um usuário](/rest/reference/users#list-gpg-keys-for-a-user) +* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user) -#### Chaves públicas do usuário +#### User Public Keys -* [Listar chaves SSH públicas para o usuário autenticado](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) -* [Criar uma chave SSH pública para o usuário autenticado](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) -* [Obter uma chave SSH pública para o usuário autenticado](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) -* [Excluir uma chave SSH pública para o usuário autenticado](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) -* [Listar chaves públicas para um usuário](/rest/reference/users#list-public-keys-for-a-user) +* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user) -#### Usuários +#### Users -* [Obter o usuário autenticado](/rest/reference/users#get-the-authenticated-user) -* [Listar instalações de aplicativos acessíveis ao token de acesso do usuário](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) +* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) +* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) {% ifversion fpt or ghec %} -* [Listar assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) {% endif %} -* [Listar usuários](/rest/reference/users#list-users) -* [Obter um usuário](/rest/reference/users#get-a-user) +* [List users](/rest/reference/users#list-users) +* [Get a user](/rest/reference/users#get-a-user) {% ifversion fpt or ghec %} -#### Execuções do fluxo de trabalho +#### Workflow Runs -* [Listar execuções do fluxo de trabalho para um repositório](/rest/reference/actions#list-workflow-runs-for-a-repository) -* [Obter execução de um fluxo de trabalho](/rest/reference/actions#get-a-workflow-run) -* [Cancelar execução de um fluxo de trabalho](/rest/reference/actions#cancel-a-workflow-run) -* [Fazer o download dos registros de execução do fluxo de trabalho](/rest/reference/actions#download-workflow-run-logs) -* [Excluir registros de execução do fluxo de trabalho](/rest/reference/actions#delete-workflow-run-logs) -* [Rexecutar um fluxo de trabalho](/rest/reference/actions#re-run-a-workflow) -* [Listar execuções do fluxo de trabalho](/rest/reference/actions#list-workflow-runs) -* [Obter uso da execução do fluxo de trabalho](/rest/reference/actions#get-workflow-run-usage) +* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Get a workflow run](/rest/reference/actions#get-a-workflow-run) +* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run) +* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs) +* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs) +* [Re run a workflow](/rest/reference/actions#re-run-a-workflow) +* [List workflow runs](/rest/reference/actions#list-workflow-runs) +* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage) {% endif %} {% ifversion fpt or ghec %} -#### Fluxos de trabalho +#### Workflows -* [Listar fluxos de trabalho do repositório](/rest/reference/actions#list-repository-workflows) -* [Obter um fluxo de trabalho](/rest/reference/actions#get-a-workflow) -* [Obter uso do workflow](/rest/reference/actions#get-workflow-usage) +* [List repository workflows](/rest/reference/actions#list-repository-workflows) +* [Get a workflow](/rest/reference/actions#get-a-workflow) +* [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Leia mais +## Further reading -- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" {% endif %} diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md b/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md index 37c1f5f3ee..54b69c1a34 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md @@ -1,34 +1,35 @@ --- -title: Gerenciando endereços IP permitidos para um aplicativo GitHub -intro: 'Você pode adicionar uma lista de permissões IP ao seu {% data variables.product.prodname_github_app %} para evitar que seu aplicativo seja bloqueado pela própria lista de permissões da organização.' +title: Managing allowed IP addresses for a GitHub App +intro: 'You can add an IP allow list to your {% data variables.product.prodname_github_app %} to prevent your app from being blocked by an organization''s own allow list.' versions: fpt: '*' ghae: '*' ghec: '*' topics: - GitHub Apps -shortTitle: Gerenciar endereços IP permitidos +shortTitle: Manage allowed IP addresses --- -## Sobre listas de endereços IP permitidos para {% data variables.product.prodname_github_apps %} +## About IP address allow lists for {% data variables.product.prodname_github_apps %} -Os proprietários da empresa e da organização podem restringir o acesso aos ativos configurando uma lista de endereços IP permitidos. Esta lista especifica os endereços IP autorizados a se conectar. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." +Enterprise and organization owners can restrict access to assets by configuring an IP address allow list. This list specifies the IP addresses that are allowed to connect. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." -Quando uma organização tem uma lista de autorizações, aplicativos de terceiros que se conectam por meio de {% data variables.product.prodname_github_app %}, terá acesso negado, a menos que ambos os pontos a seguir sejam verdadeiros: +When an organization has an allow list, third-party applications that connect via a {% data variables.product.prodname_github_app %} will be denied access unless both of the following are true: -* O criador do {% data variables.product.prodname_github_app %} configurou uma lista de permissões para o aplicativo que especifica os endereços IP em que o aplicativo é executado. Veja abaixo detalhes de como fazer isso. -* O proprietário da organização escolheu permitir que os endereços na lista de permitidos do {% data variables.product.prodname_github_app %} sejam adicionados à sua própria lista de permissões. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#allowing-access-by-github-apps)". +* The creator of the {% data variables.product.prodname_github_app %} has configured an allow list for the application that specifies the IP addresses at which their application runs. See below for details of how to do this. +* The organization owner has chosen to permit the addresses in the {% data variables.product.prodname_github_app %}'s allow list to be added to their own allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#allowing-access-by-github-apps)." {% data reusables.apps.ip-allow-list-only-apps %} -## Adicionando uma lista de endereços IP permitidos para {% data variables.product.prodname_github_app %} +## Adding an IP address allow list to a {% data variables.product.prodname_github_app %} {% data reusables.apps.settings-step %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -1. Role para baixo até a seção "Lista de permissão de IP". ![Seção de informações básicas para o seu aplicativo GitHub](/assets/images/github-apps/github-apps-allow-list-empty.png) +1. Scroll down to the "IP allow list" section. +![Basic information section for your GitHub App](/assets/images/github-apps/github-apps-allow-list-empty.png) {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} - A descrição é para sua referência e não é usada na lista de licenças de organizações em que {% data variables.product.prodname_github_app %} está instalado. Em vez disso, a organização permite que as listas incluam "Gerenciado pelo Nome do aplicativo Github" como descrição. + The description is for your reference and is not used in the allow list of organizations where the {% data variables.product.prodname_github_app %} is installed. Instead, organization allow lists will include "Managed by the NAME GitHub App" as the description. {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index f2094f1f0b..69254e7f3d 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Limites de taxa para aplicativos do GitHub +title: Rate limits for GitHub Apps intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' redirect_from: - /early-access/integrations/rate-limits/ @@ -14,16 +14,15 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Limites de taxa +shortTitle: Rate limits --- - -## Solicitações de servidor para servidor +## Server-to-server requests {% ifversion ghec %} The rate limits for server-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise. -### Limites de taxa normais de servidor a servidor +### Normal server-to-server rate limits {% endif %} @@ -31,32 +30,32 @@ The rate limits for server-to-server requests made by {% data variables.product. {% ifversion ghec %} -### Limites de taxa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %} +### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits {% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by an enterprise on {% data variables.product.product_location %} have a rate limit of 15,000 requests per hour for server-to-server requests. {% endif %} -## Solicitações de usuário para servidor +## User-to-server requests -{% data variables.product.prodname_github_apps %} também pode atuar [em nome de um usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), fazendo solicitações do usuário para servidor. +{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests. {% ifversion ghec %} The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise. -### Limites de taxa normais de usuário para servidor +### Normal user-to-server rate limits {% endif %} -User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário e solicitações autenticadas com o usuário {% ifversion ghae %} token{% else %} usuário e senha{% endif %} compartilham a mesma cota de 5.000 solicitações por hora para esse usuário. +User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% ifversion ghae %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user. {% ifversion ghec %} -### Limites de taxa de usuário para servidor de {% data variables.product.prodname_ghe_cloud %} +### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits -When a user belongs to an enterprise on {% data variables.product.product_location %}, user-to-server requests to resources owned by the same enterprise are rate limited at 15,000 requests per hour and per authenticated user. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário, e pedidos autenticados com o nome de usuário e senha compartilham a mesma cota de 5.000 solicitações por hora para esse usuário. +When a user belongs to an enterprise on {% data variables.product.product_location %}, user-to-server requests to resources owned by the same enterprise are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. {% endif %} -Para obter informações mais detalhadas sobre os limites de taxa, consulte "[Limite de taxa](/rest/overview/resources-in-the-rest-api#rate-limiting)" para API REST e "[Limitações de recursos]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" para API do GraphQL. +For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" for GraphQL API. diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index e189943f59..440811b7ab 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Escopos para aplicativos OAuth +title: Scopes for OAuth Apps intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ @@ -14,18 +14,17 @@ versions: topics: - OAuth Apps --- - -Ao configurar um aplicativo OAuth no GitHub, os escopos solicitados são exibidos para o usuário no formulário de autorização. +When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. {% note %} -**Observação:** Se você está criando um aplicativo no GitHub, você não precisa fornecer escopos na sua solicitação de autorização. Para obter mais informações sobre isso, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." {% endnote %} -Se seu {% data variables.product.prodname_oauth_app %} não tiver acesso a um navegador, como uma ferramenta de CLI, você não precisará especificar um escopo para que os usuários efetuem a autenticação no seu aplicativo. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". +If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." -Verifique os cabeçalhos para ver quais escopos do OAuth você tem e o que a ação da API aceita: +Check headers to see what OAuth scopes you have, and what the API action accepts: ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -34,53 +33,54 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` lista o escopo que seu token autorizou. -* `X-Accepted-OAuth-Scopes` lista os escopos verificados pela ação. +* `X-OAuth-Scopes` lists the scopes your token has authorized. +* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. -## Escopos disponíveis +## Available scopes -| Nome | Descrição | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% ifversion not ghae %} -| **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (incluindo informações do perfil do usuário, informações do repositório e gists){% endif %}{% ifversion ghes or ghae %} -| **`site_admin`** | Concede acesso de administrador aos pontos de extremidades da API de administração [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Concede acesso total aos repositórios, incluindo repositórios privados. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações. Também concede capacidade para gerenciar projetos de usuário. | -|  `repo:status` | Concede acesso de leitura/gravação a {% ifversion not ghae %}público{% else %}interno{% endif %} e status do commit do repositório privado. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código. | -|  `repo_deployment` | Concede acesso aos [status da implementação](/rest/reference/repos#deployments) para {% ifversion not ghae %}público{% else %}interno{% endif %} e repositórios privados. Este escopo só é necessário para conceder a outros usuários ou serviços acesso aos status de implantação, *sem* conceder acesso ao código.{% ifversion not ghae %} -|  `public_repo` | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados como favoritos.{% endif %} -|  `repo:invite` | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes > 3.0 or ghec %} -|  `security_events` | Concede:
    acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning)
    Este escopo só é necessário para conceder acesso a outros usuários ou serviços a eventos de segurança *sem* conceder acesso ao código.{% endif %}{% ifversion ghes < 3.1 %} -|  `security_events` | Concede acesso de leitura e gravação a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este escopo só é necessário para conceder a outros usuários ou serviços acesso a eventos de segurança *sem* conceder acesso ao código.{% endif %} -| **`admin:repo_hook`** | Concede acesso de leitura, gravação, marcação e exclusão a hooks de repositório em {% ifversion not ghae %}público{% else %}interno{% endif %} e repositórios privados. O escopos do `repo` {% ifversion not ghae %}e `public_repo` concedem{% else %}o escopo concede{% endif %} o acesso total aos repositórios, incluindo hooks de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas a hooks de repositório. | -|  `write:repo_hook` | Concede acesso de leitura, gravação e marcação a hooks em {% ifversion not ghae %}público{% else %}interno{% endif %} ou repositórios privados. | -|  `read:repo_hook` | Concede acesso de leitura e gravação a hooks em {% ifversion not ghae %}público{% else %}interno{% endif %} ou repositórios privados. | -| **`admin:org`** | Gerencia totalmente a organização e suas equipes, projetos e associações. | -|  `write:org` | Acesso de leitura e gravação à associação da organização, aos projetos da organização e à associação da equipe. | -|  `read:org` | Acesso somente leitura à associação da organização, aos projetos da organização e à associação da equipe. | -| **`admin:public_key`** | Gerenciar totalmente as chaves públicas. | -|  `write:public_key` | Criar, listar e visualizar informações das chaves públicas. | -|  `read:public_key` | Listar e visualizar informações para as chaves públicas. | -| **`admin:org_hook`** | Concede acesso de leitura, gravação, ping e e exclusão de hooks da organização. **Observação:** Os tokens do OAuth só serão capazes de realizar essas ações nos hooks da organização que foram criados pelo aplicativo OAuth. Os tokens de acesso pessoal só poderão realizar essas ações nos hooks da organização criados por um usuário. | -| **`gist`** | Concede acesso de gravação aos gists. | -| **`notificações`** | Condece:
    * acesso de gravação a notificações de um usuário
    * acesso para marcar como leitura nos threads
    * acesso para inspecionar e não inspecionar um repositório e
    * acesso de leitura, gravação e exclusão às assinaturas dos threads. | -| **`usuário`** | Concede acesso de leitura/gravação apenas às informações do perfil. Observe que este escopo inclui `user:email` e `user:follow`. | -|  `read:user` | Concede acesso para ler as informações do perfil de um usuário. | -|  `usuário:email` | Concede acesso de leitura aos endereços de e-mail de um usuário. | -|  `user:follow` | Concede acesso para seguir ou deixar de seguir outros usuários. | -| **`delete_repo`** | Concede acesso para excluir repositórios administráveis. | -| **`write:discussion`** | Permite acesso de leitura e gravação para discussões da equipe. | -|  `leia:discussion` | Allows read access for team discussions.{% ifversion fpt or ghae or ghec %} -| **`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)". | -| **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. For more information, see "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %} -| **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | -|  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | -|  `read:gpg_key` | List and view details for GPG keys.{% ifversion fpt or ghec %} -| **`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)." | -| **`fluxo de trabalho`** | Concede a capacidade de adicionar e atualizar arquivos do fluxo de trabalho do {% data variables.product.prodname_actions %}. Os arquivos do fluxo de trabalho podem ser confirmados sem este escopo se o mesmo arquivo (com o mesmo caminho e conteúdo) existir em outro branch no mesmo repositório. Os arquivos do fluxo de trabalho podem expor o `GITHUB_TOKEN` que pode ter um conjunto diferente de escopos. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".{% endif %} +Name | Description +-----|-----------|{% ifversion not ghae %} +**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %} +**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} +**`repo`** | Grants full access to repositories, including private repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for repositories and organizations. Also grants ability to manage user projects. + `repo:status`| Grants read/write access to {% ifversion not ghae %}public{% else %}internal{% endif %} and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. + `repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %} + `public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %} + `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes > 3.0 or ghec %} + `security_events` | Grants:
    read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
    This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %} + `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. The `repo` {% ifversion not ghae %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. + `write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion not ghae %}public{% else %}internal{% endif %} or private repositories. + `read:repo_hook`| Grants read and ping access to hooks in {% ifversion not ghae %}public{% else %}internal{% endif %} or private repositories. +**`admin:org`** | Fully manage the organization and its teams, projects, and memberships. + `write:org`| Read and write access to organization membership, organization projects, and team membership. + `read:org`| Read-only access to organization membership, organization projects, and team membership. +**`admin:public_key`** | Fully manage public keys. + `write:public_key`| Create, list, and view details for public keys. + `read:public_key`| List and view details for public keys. +**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. +**`gist`** | Grants write access to gists. +**`notifications`** | Grants:
    * read access to a user's notifications
    * mark as read access to threads
    * watch and unwatch access to a repository, and
    * read, write, and delete access to thread subscriptions. +**`user`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. + `read:user`| Grants access to read a user's profile data. + `user:email`| Grants read access to a user's email addresses. + `user:follow`| Grants access to follow or unfollow other users. +**`delete_repo`** | Grants access to delete adminable repositories. +**`write:discussion`** | Allows read and write access for team discussions. + `read:discussion` | Allows read access for team discussions.{% ifversion fpt or ghae or ghec %} +**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". +**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". +**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %} +**`admin:gpg_key`** | Fully manage GPG keys. + `write:gpg_key`| Create, list, and view details for GPG keys. + `read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %} +**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)." +**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% endif %} {% note %} -**Observação:** O seu aplicativo OAuth pode solicitar os escopos no redirecionamento inicial. Você pode especificar vários escopos separando-os com um espaço usando `%20`: +**Note:** Your OAuth App can request the scopes in the initial redirection. You +can specify multiple scopes by separating them with a space using `%20`: https://github.com/login/oauth/authorize? client_id=...& @@ -88,16 +88,31 @@ X-Accepted-OAuth-Scopes: user {% endnote %} -## Escopos solicitados e escopos concedidos +## Requested scopes and granted scopes -O atributo `escopo` lista os escopos adicionados ao token que foram concedido pelo usuário. Normalmente, estes escopos são idênticos aos que você solicitou. No entanto, os usuários podem editar seus escopos, concedendo, efetivamente, ao seu aplicativo um acesso menor do que você solicitou originalmente. Além disso, os usuários podem editar o escopo do token depois que o fluxo do OAuth for concluído. Você deve ter em mente esta possibilidade e ajustar o comportamento do seu aplicativo de acordo com isso. +The `scope` attribute lists scopes attached to the token that were granted by +the user. Normally, these scopes will be identical to what you requested. +However, users can edit their scopes, effectively +granting your application less access than you originally requested. Also, users +can edit token scopes after the OAuth flow is completed. +You should be aware of this possibility and adjust your application's behavior +accordingly. -É importante lidar com casos de erro em que um usuário escolhe conceder menos acesso do que solicitado originalmente. Por exemplo, os aplicativos podem alertar ou informar aos seus usuários que a funcionalidade será reduzida ou não serão capazes de realizar algumas ações. +It's important to handle error cases where a user chooses to grant you +less access than you originally requested. For example, applications can warn +or otherwise communicate with their users that they will see reduced +functionality or be unable to perform some actions. -Além disso, os aplicativos sempre podem enviar os usuários de volta através do fluxo para obter permissão adicional, mas não se esqueça de que os usuários sempre podem dizer não. +Also, applications can always send users back through the flow again to get +additional permission, but don’t forget that users can always say no. -Confira o [Príncípios do guia de autenticação](/guides/basics-of-authentication/), que fornece dicas para lidar com escopos de token modificável. +Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which +provides tips on handling modifiable token scopes. -## Escopos normalizados +## Normalized scopes -Ao solicitar vários escopos, o token é salvo com uma lista normalizada de escopos, descartando aqueles que estão implicitamente incluídos pelo escopo solicitado. Por exemplo, a solicitação do usuário `user,gist,user:email` irá gerar apenas um token com escopos de `usuário` e `gist`, desde que o acesso concedido com o escopo `user:email` esteja incluído no escopo `usuário`. +When requesting multiple scopes, the token is saved with a normalized list +of scopes, discarding those that are implicitly included by another requested +scope. For example, requesting `user,gist,user:email` will result in a +token with `user` and `gist` scopes only since the access granted with +`user:email` scope is included in the `user` scope. diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md index c7b26b2268..bcb5178dfb 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md @@ -1,5 +1,5 @@ --- -title: Sobre o aplicativo +title: About apps intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' redirect_from: - /apps/building-integrations/setting-up-a-new-integration/ @@ -15,92 +15,91 @@ versions: topics: - GitHub Apps --- +Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %} -Os aplicativos no {% data variables.product.prodname_dotcom %} permitem que você automatize e melhore seu fluxo de trabalho. Você pode criar aplicativos para melhorar seu fluxo de trabalho. {% ifversion fpt or ghec %} Você também pode compartilhar ou vender aplicativos em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender como listar um aplicativo no {% data variables.product.prodname_marketplace %}, consulte "[Introdução ao GitHub Marketplace](/marketplace/getting-started/)".{% endif %} - -{% data reusables.marketplace.github_apps_preferred %}, mas o GitHub é compatível com {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_github_apps %}. Para obter informações sobre a escolha de um tipo de aplicativo, consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)". +{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)." {% data reusables.apps.general-apps-restrictions %} -Para uma apresentação do processo de construção de um {% data variables.product.prodname_github_app %}, consulte "[Criando o seu primeiro {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". +For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)." -## Sobre o {% data variables.product.prodname_github_apps %} +## About {% data variables.product.prodname_github_apps %} -{% data variables.product.prodname_github_apps %} são atores de primeira classe no GitHub. Um {% data variables.product.prodname_github_app %} age em seu próprio nome, tomando ações por meio da API diretamente usando sua própria identidade, o que significa que você não precisa manter um bot ou conta de serviço como um usuário separado. +{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user. -O {% data variables.product.prodname_github_apps %} pode ser instalado diretamente em organizações e contas de usuários e conceder acesso a repositórios específicos. Eles vêm com webhooks integrados e permissões específicas e restritas. Ao configurar o {% data variables.product.prodname_github_app %}, você pode selecionar os repositórios que deseja que ele acesse. Por exemplo, você pode configurar um aplicativo denominado `MyGitHub` que escreve problemas no repositório `octocat` e _apenas_ no repositório `octocat`. Para instalar um {% data variables.product.prodname_github_app %}, você deve ser o proprietário de uma organização ou ter permissões de administrador em um repositório. +{% data variables.product.prodname_github_apps %} can be installed directly on organizations and user accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository. {% data reusables.apps.app_manager_role %} -{% data variables.product.prodname_github_apps %} são aplicativos que devem ser hospedados em algum lugar. Para obter as instruções do passo a passo que cobrem os servidores e hospedagem, consulte "[Construindo seu primeiro {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". +{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)." -Para melhorar seu fluxo de trabalho, você pode criar um {% data variables.product.prodname_github_app %} que contém vários scripts ou um aplicativo inteiro e, em seguida, conectar esse aplicativo a muitas outras ferramentas. Por exemplo, você pode conectar {% data variables.product.prodname_github_apps %} ao GitHub, Slack, ou a outros aplicativos que você pode ter, programas de e-mail ou outras APIs. +To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs. -Tenha isso em mente ao criar {% data variables.product.prodname_github_apps %}: +Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}: {% ifversion fpt or ghec %} * {% data reusables.apps.maximum-github-apps-allowed %} {% endif %} -* Um {% data variables.product.prodname_github_app %} deve tomar ações independentes do usuário (a menos que o aplicativo esteja usando um token [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %} +* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %} -* Certifique-se de que o {% data variables.product.prodname_github_app %} integre repositórios específicos. -* O {% data variables.product.prodname_github_app %} deve conectar-se a uma conta pessoal ou organização. -* Não espere que o {% data variables.product.prodname_github_app %} saiba e faça tudo o que um usuário pode fazer. -* Não use {% data variables.product.prodname_github_app %}, se você precisa apenas de um serviço de "Login com GitHub". No entanto, um {% data variables.product.prodname_github_app %} pode usar um [fluxo de identificação de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para iniciar sessão de usuários em _e_ fazer outras coisas. -* Não crie um {% data variables.product.prodname_github_app %} se você _apenas_ desejar atuar como um usuário do GitHub e fazer tudo o que o usuário pode fazer.{% ifversion fpt or ghec %} +* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories. +* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization. +* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can. +* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things. +* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %} * {% data reusables.apps.general-apps-restrictions %}{% endif %} To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} -## Sobre {% data variables.product.prodname_oauth_apps %} +## About {% data variables.product.prodname_oauth_apps %} -OAuth2 é um protocolo que permite que os aplicativos externos solicitem autorização para detalhes privados na conta {% data variables.product.prodname_dotcom %} de um usuário sem acessar sua senha. Isto é preferido em relação à autenticação básica, porque os tokens podem ser limitados a tipos específicos de dados e podem ser revogados pelos usuários a qualquer momento. +OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time. {% data reusables.apps.deletes_ssh_keys %} -Um {% data variables.product.prodname_oauth_app %} usa {% data variables.product.prodname_dotcom %} como um provedor de identidade para efetuar a autenticação como o usuário que concede acesso ao aplicativo. Isso significa que, quando um usuário concede acesso {% data variables.product.prodname_oauth_app %}, ele concedem permissões a _todos_ os repositórios aos quais tem acesso em sua conta, e também a qualquer organização a que pertence que não bloqueou o acesso de terceiros. +An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access. -Construir um {% data variables.product.prodname_oauth_app %} é uma boa opção se você estiver criando processos mais complexos do que um simples script pode gerenciar. Note que {% data variables.product.prodname_oauth_apps %} são aplicativos que precisam ser hospedados em algum lugar. +Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere. -Tenha isso em mente ao criar {% data variables.product.prodname_oauth_apps %}: +Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}: {% ifversion fpt or ghec %} * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} -* Um {% data variables.product.prodname_oauth_app %} deve sempre atuar como o usuário autenticado {% data variables.product.prodname_dotcom %} em todo o {% data variables.product.prodname_dotcom %} (por exemplo, ao fornecer notificações de usuário). -* Um {% data variables.product.prodname_oauth_app %} pode ser usado como um provedor de identidade, habilitando um "Login com {% data variables.product.prodname_dotcom %}" para o usuário autenticado. -* Não crie um {% data variables.product.prodname_oauth_app %}, se desejar que seu aplicativo atue em um único repositório. Com o escopo de `repo` do OAuth, {% data variables.product.prodname_oauth_apps %} pode atuar em _todos_ os repositórios de usuários autenticados. -* Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %} +* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications). +* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user. +* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories. +* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -Para obter mais informações sobre {% data variables.product.prodname_oauth_apps %}, consulte "[Criando um {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" e "[Registrando seu aplicativo](/rest/guides/basics-of-authentication#registering-your-app)". +For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." -## Tokens de acesso pessoal +## Personal access tokens -Um [token de acesso pessoal](/articles/creating-a-personal-access-token-for-the-command-line/) é uma string de caracteres que funciona da mesma forma que um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/), cujas permissões você pode especificar por meio de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Um token de acesso pessoal também é semelhante a uma senha, mas você pode ter muitos delas e você pode revogar o acesso a cada uma a qualquer momento. +A [personal access token](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A personal access token is also similar to a password, but you can have many of them and you can revoke access to each one at any time. -Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. Em seguida, se você executar um comando cURL ou escrever um script que [cria um problema](/rest/reference/issues#create-an-issue) no seu repositório, você informaria o token de acesso pessoal para efetuar a autenticação. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo. +As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it. -Tenha em mente essas ideias ao usar os tokens de acesso pessoais: +Keep these ideas in mind when using personal access tokens: -* Lembre-se de usar este token para representar apenas você. -* Você pode realizar solicitações de cURL únicas. -* Você pode executar scripts pessoais. -* Não configure um script para toda a sua equipe ou empresa usá-lo. +* Remember to use this token to represent yourself only. +* You can perform one-off cURL requests. +* You can run personal scripts. +* Don't set up a script for your whole team or company to use. * Don't set up a shared user account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} -* Defina um vencimento para os seus tokens de acesso pessoais para ajudar a manter suas informações seguras.{% endif %} +* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} -## Determinar qual integração criar +## Determining which integration to build -Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. A imagem a seguir oferece algumas perguntas de segurança ao decidir se usa tokens de acesso pessoais, {% data variables.product.prodname_github_apps %}ou {% data variables.product.prodname_oauth_apps %} para sua integração. +Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use personal access tokens, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration. -![Introdução ao fluxo de perguntas dos aplicativos](/assets/images/intro-to-apps-flow.png) +![Intro to apps question flow](/assets/images/intro-to-apps-flow.png) -Considere estas perguntas sobre como sua integração deve se comportar e o que é necessário para ter acesso: +Consider these questions about how your integration needs to behave and what it needs to access: -* A minha integração funcionará apenas como eu ou será mais como um aplicativo? -* Quero que ela aja independentemente de mim com sua própria entidade? -* Ela irá acessar tudo o que eu puder acessar ou eu quero limitar seu acesso? -* É simples ou complexo? Por exemplo, tokens de acesso pessoal são bons para scripts simples e cURLs, enquanto um {% data variables.product.prodname_oauth_app %} pode lidar com scripts mais complexos. +* Will my integration act only as me, or will it act more like an application? +* Do I want it to act independently of me as its own entity? +* Will it access everything that I can access, or do I want to limit its access? +* Is it simple or complex? For example, personal access tokens are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting. -## Solicitar suporte +## Requesting support {% data reusables.support.help_resources %} diff --git a/translations/pt-BR/content/developers/apps/guides/index.md b/translations/pt-BR/content/developers/apps/guides/index.md index e1eb86897f..4982239bab 100644 --- a/translations/pt-BR/content/developers/apps/guides/index.md +++ b/translations/pt-BR/content/developers/apps/guides/index.md @@ -1,5 +1,5 @@ --- -title: Guias +title: Guides intro: 'Learn about using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with your app, continuous integration, and how to build with apps.' redirect_from: - /apps/quickstart-guides diff --git a/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md b/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md index 36c3f7b954..fa623003d5 100644 --- a/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md +++ b/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md @@ -1,6 +1,6 @@ --- -title: Usar anexos de conteúdo -intro: Os anexos de conteúdo permitem que um aplicativo GitHub forneça mais informações no GitHub referente às URLs ligadas a domínios registrados. O GitHub interpreta as informações fornecidas pelo aplicativo sob a URL do texto ou comentário de um problema ou pull request. +title: Using content attachments +intro: Content attachments allow a GitHub App to provide more information in GitHub for URLs that link to registered domains. GitHub renders the information provided by the app under the URL in the body or comment of an issue or pull request. redirect_from: - /apps/using-content-attachments - /developers/apps/using-content-attachments @@ -12,35 +12,34 @@ versions: topics: - GitHub Apps --- - {% data reusables.pre-release-program.content-attachments-public-beta %} -## Sobre os anexos de conteúdo +## About content attachments -Um aplicativo GitHub pode registrar domínios que ativarão eventos `content_reference`. Quando alguém inclui uma URL que é ligada a um domínio registrado no texto ou comentário de um problema ou pull request, o aplicativo recebe o webhook[`content_reference`](/webhooks/event-payloads/#content_reference). Você pode usar os anexos de conteúdo para fornecer visualmente mais contexto ou dados para a URL adicionada a um problema ou pull request. A URL deve ser uma URL totalmente qualificada, começando com `http://` ou `https://`. As URLs que fazem parte de um link markdown são ignoradas e não ativam o evento `content_reference`. +A GitHub App can register domains that will trigger `content_reference` events. When someone includes a URL that links to a registered domain in the body or comment of an issue or pull request, the app receives the [`content_reference` webhook](/webhooks/event-payloads/#content_reference). You can use content attachments to visually provide more context or data for the URL added to an issue or pull request. The URL must be a fully-qualified URL, starting with either `http://` or `https://`. URLs that are part of a markdown link are ignored and don't trigger the `content_reference` event. -Antes de usar a API {% data variables.product.prodname_unfurls %}, você deverá configurar as referências de conteúdo para o seu aplicativo GitHub: -* Dê ao seu aplicativo permissões de `Leitura & gravação` para as "Referências de conteúdo". -* Registre até 5 domínios válidos e publicamente acessíveis ao configurar a permissão de "Referências de conteúdo". Não use endereços IP ao configurar domínios de referência de conteúdo. Você pode registrar um nome de domínio (exemplo.com) ou um subdomínio (subdomínio.exemplo.com). -* Assine seu aplicativo no evento "Referência do conteúdo". +Before you can use the {% data variables.product.prodname_unfurls %} API, you'll need to configure content references for your GitHub App: +* Give your app `Read & write` permissions for "Content references." +* Register up to 5 valid, publicly accessible domains when configuring the "Content references" permission. Do not use IP addresses when configuring content reference domains. You can register a domain name (example.com) or a subdomain (subdomain.example.com). +* Subscribe your app to the "Content reference" event. -Uma vez instalado seu aplicativo em um repositório, Os comentários do problema ou pull request no repositório que contêm URLs para seus domínios registrados gerarão um evento de referência de conteúdo. O aplicativo deve criar um anexo de conteúdo em seis horas após a URL de referência de conteúdo ser postada. +Once your app is installed on a repository, issue or pull request comments in the repository that contain URLs for your registered domains will generate a content reference event. The app must create a content attachment within six hours of the content reference URL being posted. -Os anexos de conteúdo não farão a atualização retroativa das URLs. Funciona apenas para as URLs adicionadas a problemas ou pull requests depois que você configurar o aplicativo que usa os requisitos descritos acima e, em seguida, alguém instalar o aplicativo em seu repositório. +Content attachments will not retroactively update URLs. It only works for URLs added to issues or pull requests after you configure the app using the requirements outlined above and then someone installs the app on their repository. -Consulte "[Criar um aplicativo GitHub](/apps/building-github-apps/creating-a-github-app/)" ou"[Editar as permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para as etapas necessárias para configurar as permissões e assinaturas de eventos do aplicativo GitHub. +See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" or "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" for the steps needed to configure GitHub App permissions and event subscriptions. -## Implementar o fluxo de anexo de conteúdo +## Implementing the content attachment flow -O fluxo de anexo de conteúdo mostra a relação entre a URL no problema ou pull request, o evento do webhook `content_reference`, de ` e o ponto de extremidade da API REST que você precisa chamar para atualizar o problema ou pull request com informações adicionais:

    +The content attachment flow shows you the relationship between the URL in the issue or pull request, the `content_reference` webhook event, and the REST API endpoint you need to call to update the issue or pull request with additional information: -

    Etapa 1. Configure seu aplicativo usando as diretrizes definidas em Sobre anexos de conteúdo. Você também pode usar o exemplo do aplicativo Probot para dar os primeiros passos com os anexos de conteúdo.

    +**Step 1.** Set up your app using the guidelines outlined in [About content attachments](#about-content-attachments). You can also use the [Probot App example](#example-using-probot-and-github-app-manifests) to get started with content attachments. -

    Etapa 2. Adicione a URL para o domínio que você registrou para um problema ou pull request. Você deve usar uma URL totalmente qualificada que comece com http://` ou `https://`. +**Step 2.** Add the URL for the domain you registered to an issue or pull request. You must use a fully qualified URL that starts with `http://` or `https://`. -![URL adicionada a um problema](/assets/images/github-apps/github_apps_content_reference.png) +![URL added to an issue](/assets/images/github-apps/github_apps_content_reference.png) -**Etapa 3.** Seu aplicativo receberá o [`content_reference` webhook](/webhooks/event-payloads/#content_reference) com a ação `criada`. +**Step 3.** Your app will receive the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) with the action `created`. ``` json { @@ -61,12 +60,12 @@ O fluxo de anexo de conteúdo mostra a relação entre a URL no problema ou pull } ``` -**Etapa 4.** O aplicativo usa os campos `content_reference` `id` e `repositório` `full_name` para [Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment) usando a API REST. Você também precisará do `id` da `instalação` para efetuar a autenticação como uma [instalação do aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Step 4.** The app uses the `content_reference` `id` and `repository` `full_name` fields to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} -O parâmetro do `texto` pode conter markdown: +The `body` parameter can contain markdown: ```shell curl -X POST \ @@ -74,24 +73,24 @@ curl -X POST \ -H 'Accept: application/vnd.github.corsair-preview+json' \ -H 'Authorization: Bearer $INSTALLATION_TOKEN' \ -d '{ - "title": "[A-1234] Error found in core/models.py file", - "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()" + "title": "[A-1234] Error found in core/models.py file", + "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()" }' ``` -Para obter mais informações sobre a criação de um token de instalação, consulte "[Efetuando a autenticação como um aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". +For more information about creating an installation token, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)." -**Etapa 5.** Você verá o novo anexo de conteúdo aparecer no link de um pull request ou comentário de um problema: +**Step 5.** You'll see the new content attachment appear under the link in a pull request or issue comment: -![Conteúdo anexado a uma referência em um problema](/assets/images/github-apps/content_reference_attachment.png) +![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png) -## Usar anexos de conteúdo no GraphQL -Nós fornecemos o `node_id` no evento [`content_reference` webhook](/webhooks/event-payloads/#content_reference) para que você possa fazer referência à mutação `createContentAttachment` na API do GraphQL. +## Using content attachments in GraphQL +We provide the `node_id` in the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) event so you can refer to the `createContentAttachment` mutation in the GraphQL API. {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} -Por exemplo: +For example: ``` graphql mutation { @@ -110,7 +109,7 @@ mutation { } } ``` -Exemplo de cURL: +Example cURL: ```shell curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \ @@ -124,21 +123,21 @@ curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \ For more information on `node_id`, see "[Using Global Node IDs]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)." -## Exemplo de uso de manifestos do Probot e do aplicativo GitHub +## Example using Probot and GitHub App Manifests -Para configurar rapidamente um aplicativo GitHub que pode usar a API do {% data variables.product.prodname_unfurls %}, você pode usar o [Probot](https://probot.github.io/). Consulte "[Criando aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para saber como o Probot usa manigestos do aplicativo GitHub. +To quickly setup a GitHub App that can use the {% data variables.product.prodname_unfurls %} API, you can use [Probot](https://probot.github.io/). See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" to learn how Probot uses GitHub App Manifests. -Para criar um aplicativo Probot, siga as etapas a seguir: +To create a Probot App, follow these steps: -1. [Gerar um novo aplicativo GitHub](https://probot.github.io/docs/development/#generating-a-new-app). -2. Abra o projeto que você criou e personalize as configurações no arquivo `app.yml`. Assine o evento `content_reference` e habilite as permissões de gravação `content_reference`: +1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app). +2. Open the project you created, and customize the settings in the `app.yml` file. Subscribe to the `content_reference` event and enable `content_references` write permissions: ``` yml default_events: - content_reference - # The set of permissions needed by the GitHub App. O formato do objeto usa - # o nome da permissão para a chave (por exemplo, problemas) e o tipo de acesso para - # o valor (por exemplo, gravação) + # The set of permissions needed by the GitHub App. The format of the object uses + # the permission name for the key (for example, issues) and the access type for + # the value (for example, write). # Valid values are `read`, `write`, and `none` default_permissions: content_references: write @@ -150,7 +149,7 @@ Para criar um aplicativo Probot, siga as etapas a seguir: value: example.org ``` -3. Adicione este código ao arquivo `index.js` para lidar com eventos `content_reference` e chamar a API REST: +3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API: ``` javascript module.exports = app => { @@ -171,13 +170,13 @@ Para criar um aplicativo Probot, siga as etapas a seguir: } ``` -4. [Execute o aplicativo GitHub localmente](https://probot.github.io/docs/development/#running-the-app-locally). Acesse `http://localhost:3000` e clique no botão **Registrar aplicativo GitHub**: +4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to `http://localhost:3000`, and click the **Register GitHub App** button: - ![Registrar um aplicativo GitHub do Probot](/assets/images/github-apps/github_apps_probot-registration.png) + ![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png) -5. Instale o aplicativo em um repositório de teste. -6. Crie um problema no seu repositório de teste. -7. Adicione um comentário ao problema aberto que inclui a URL que você configurou no arquivo `app.yml`. -8. Dê uma olhada no comentário do problema e você verá uma atualização que se parece com isso: +5. Install the app on a test repository. +6. Create an issue in your test repository. +7. Add a comment to the issue you opened that includes the URL you configured in the `app.yml` file. +8. Take a look at the issue comment and you'll see an update that looks like this: - ![Conteúdo anexado a uma referência em um problema](/assets/images/github-apps/content_reference_attachment.png) + ![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png) diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md index 4e3d31e66f..3fb0226641 100644 --- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md +++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md @@ -1,6 +1,6 @@ --- -title: Gerenciar chaves de implantação -intro: Aprenda maneiras diferentes de gerenciar chaves SSH em seus servidores ao automatizar scripts de implantação e da melhor maneira para você. +title: Managing deploy keys +intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you. redirect_from: - /guides/managing-deploy-keys/ - /v3/guides/managing-deploy-keys @@ -14,90 +14,85 @@ topics: --- -Você pode gerenciar chaves SSH em seus servidores ao automatizar scripts de implantação usando o encaminhamento do agente SSH, HTTPS com tokens do OAuth, chaves de implantação ou usuários de máquina. +You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users. -## Encaminhamento de agente SSH +## SSH agent forwarding -Em muitos casos, especialmente no início de um projeto, o encaminhamento de agentes SSH é o método mais rápido e simples de utilizar. O encaminhamento de agentes usa as mesmas chaves SSH que o seu computador de desenvolvimento local. +In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses. -#### Prós +#### Pros -* Você não tem que gerar ou monitorar nenhuma chave nova. -* Não há gerenciamento de chaves; os usuários têm as mesmas permissões no servidor e localmente. -* Não há chaves armazenadas no servidor. Portanto, caso o servidor esteja comprometido, você não precisa buscar e remover as chaves comprometidas. +* You do not have to generate or keep track of any new keys. +* There is no key management; users have the same permissions on the server that they do locally. +* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys. -#### Contras +#### Cons -* Os usuários **devem** ingressar com SSH para implantar; os processos de implantação automatizados não podem ser usados. -* Pode ser problemático executar o encaminhamento de agente SSH para usuários do Windows. +* Users **must** SSH in to deploy; automated deploy processes can't be used. +* SSH agent forwarding can be troublesome to run for Windows users. -#### Configuração +#### Setup -1. Ativar o encaminhamento do agente localmente. Consulte o [nosso guia sobre o encaminhamento de agentes SSH][ssh-agent-forwarding] para obter mais informações. -2. Defina seus scripts de implantação para usar o encaminhamento de agentes. Por exemplo, em um script bash, permitir o encaminhamento de agentes seria algo como isto: `ssh -A serverA 'bash -s' < deploy.sh` +1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information. +2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this: +`ssh -A serverA 'bash -s' < deploy.sh` -## Clonagem de HTTPS com tokens do OAuth +## HTTPS cloning with OAuth tokens -Se você não quiser usar chaves SSH, você poderá usar [HTTPS com tokens do OAuth][git-automation]. +If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-automation]. -#### Prós +#### Pros -* Qualquer pessoa com acesso ao servidor pode implantar o repositório. -* Os usuários não precisam alterar suas configurações SSH locais. -* Não são necessários vários tokens (um para cada usuário); um token por servidor é suficiente. -* Um token pode ser revogado a qualquer momento, transformando-o, basicamente, em uma senha de uso único. +* Anyone with access to the server can deploy the repository. +* Users don't have to change their local SSH settings. +* Multiple tokens (one for each user) are not needed; one token per server is enough. +* A token can be revoked at any time, turning it essentially into a one-use password. {% ifversion ghes %} -* Gerar novos tokens pode ser facilmente programado usando [a API do OAuth](/rest/reference/oauth-authorizations#create-a-new-authorization). +* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization). {% endif %} -#### Contras +#### Cons -* Você deve certificar-se de configurar seu token com os escopos de acesso corretos. -* Os Tokens são, basicamente, senhas e devem ser protegidos da mesma maneira. +* You must make sure that you configure your token with the correct access scopes. +* Tokens are essentially passwords, and must be protected the same way. -#### Configuração +#### Setup -Consulte o [nosso guia sobre automação Git com tokens][git-automation]. +See [our guide on Git automation with tokens][git-automation]. -## Chaves de implantação +## Deploy keys {% data reusables.repositories.deploy-keys %} {% data reusables.repositories.deploy-keys-write-access %} -#### Prós +#### Pros -* Qualquer pessoa com acesso ao repositório e servidor é capaz de implantar o projeto. -* Os usuários não precisam alterar suas configurações SSH locais. -* As chaves de implantação são somente leitura por padrão, mas você pode lhes conferir acesso de gravação ao adicioná-las a um repositório. +* Anyone with access to the repository and server has the ability to deploy the project. +* Users don't have to change their local SSH settings. +* Deploy keys are read-only by default, but you can give them write access when adding them to a repository. -#### Contras +#### Cons -* As chaves de implementação só concedem acesso a um único repositório. Projetos mais complexos podem ter muitos repositórios para extrair para o mesmo servidor. -* De modo geral, as chaves de implantação não são protegidas por uma frase secreta, o que a chave facilmente acessível se o servidor estiver comprometido. +* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server. +* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised. -#### Configuração +#### Setup -1. -Execute o procedimento `ssh-keygen` no seu servidor e lembre-se do local onde você salva o par de chaves RSA público/privadas gerado. - - 2 No canto superior direito de qualquer página do {% data variables.product.product_name %}, clique na sua foto do perfil e, em seguida, clique em **Seu perfil**. ![Navegação para o perfil](/assets/images/profile-page.png) -3 Na sua página de perfil, clique em **Repositórios** e, em seguida, clique no nome do seu repositório. ![Link dos repositórios](/assets/images/repos.png) -4 No seu repositório, clique em **Configurações**. ![Configurações do repositório](/assets/images/repo-settings.png) -5 Na barra lateral, clique em **Implantar Chaves** e, em seguida, clique em **Adicionar chave de implantação**. ![Link para adicionar chaves de implantação](/assets/images/add-deploy-key.png) -6 Forneça um título e cole na sua chave pública. ![Página da chave implantação](/assets/images/deploy-key.png) -7 Selecione **Permitir acesso de gravação**, se você quiser que esta chave tenha acesso de gravação no repositório. Uma chave de implantação com acesso de gravação permite que uma implantação faça push no repositório. -8 Clique em **Adicionar chave**. +1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public/private rsa key pair. +2. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**. ![Navigation to profile](/assets/images/profile-page.png) +3. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png) +4. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png) +5. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png) +6. Provide a title, paste in your public key. ![Deploy Key page](/assets/images/deploy-key.png) +7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. +8. Click **Add key**. +#### Using multiple repositories on one server +If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. -#### Usar vários repositórios em um servidor - -Se você usar vários repositórios em um servidor, você deverá gerar um par de chaves dedicado para cada um. Você não pode reutilizar uma chave de implantação para vários repositórios. - -No arquivo de configuração do SSH do servidor (geralmente `~/.ssh/config`), adicione uma entrada de pseudônimo para cada repositório. Por exemplo: - - +In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example: ```bash Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0 @@ -109,63 +104,49 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif IdentityFile=/home/user/.ssh/repo-1_deploy_key ``` - * `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias. * `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. -* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Atribui uma chave privada ao pseudônimo. - -Em seguida, você pode usar o apelido do host para interagir com o repositório usando SSH, que usará a chave de deploy exclusiva atribuída a esse pseudônimo. Por exemplo: - +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. +You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example: ```bash $ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +## Server-to-server tokens +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). -## Tokens do servidor para servidor +#### Pros -Se seu servidor precisar acessar repositórios em uma ou mais organizações, você poderá usar um aplicativo GitHub para definir o acesso que você precisa e, em seguida, gerar tokens de _escopo limitado_, _servidor para servidor_ a partir daquele aplicativo GitHub. Os tokens do servidor para servidor podem ter escopo de repositório único ou múltiplo e podem ter permissões refinadas. Por exemplo, você pode gerar um token com acesso somente leitura para o conteúdo de um repositório. +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. -Uma vez que os aplicativos GitHub são um ator de primeira classe em {% data variables.product.product_name %}, os tokens do servidor para servidor são dissociados de qualquer usuário do GitHub, o que os torna comparáveis aos "tokens de serviço". Além disso, tokens de servidor para servidor têm limites de taxa dedicados que escalam com o tamanho das organizações sobre as quais eles atuam. Para obter mais informações, consulte [Limites de taxa para os aplicativos Github](/developers/apps/rate-limits-for-github-apps). +#### Cons +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. +#### Setup -#### Prós +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. -- Tokens com escopo limitado com conjuntos de permissões bem definidos e tempos de expiração (1 hora, ou menos se for revogado manualmente usando a API). -- Limites de taxa dedicados que crescem com a sua organização. -- Separados das identidades de usuários do GitHub para que não consumam nenhuma estação licenciada. -- Nunca concedeu uma senha. Portanto, não pode efetuar o login diretamente. +## Machine users - - -#### Contras - -- É necessária uma configuração adicional para criar o aplicativo GitHub. -- Os tokens de servidor para servidor expiram após 1 hora. Portanto, precisam ser gerados novamente, geralmente sob demanda e usando código. - - - -#### Configuração - -1. Determine se seu aplicativo GitHub deve ser público ou privado. Se o seu aplicativo GitHub agir apenas nos repositórios da organização, é provável que você queira que ele seja privado. -1. Determine as permissões que o aplicativo GitHub exige, como acesso somente leitura ao conteúdo do repositório. -1. Crie seu aplicativo GitHub por meio da página de configurações da sua organização. Para obter mais informações, consulte [Criar um aplicativo GitHub](/developers/apps/creating-a-github-app). -1. Observe seu id `id` do aplicativo GitHub. -1. Gere e faça o download da chave privada do seu aplicativo GitHub e armazene-a com segurança. Para obter mais informações, consulte [Gerar uma chave privada](/developers/apps/authenticating-with-github-apps#generating-a-private-key). -1. Instale o aplicativo GitHub nos repositórios nos quais ele precisa agir. Opcionalmente você poderá instalar o aplicativo GitHub em todos os repositórios da sua organização. -1. Identifique o `installation_id` que representa a conexão entre o aplicativo GitHub e os repositórios da organização à qual ele pode acessar. Cada aplicativo GitHub e par de organização tem, no máximo, um `installation_id` único. Você pode identificar este `installation_id` por meio de [Obter uma instalação da organização para o aplicativo autenticado](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). Isto exige autenticação como um aplicativo GitHub usando um JWT. Para obter mais informações, consulte [Efetuar a autenticação como um aplicativo GitHub](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). -1. Gere um token de servidor para servidor usando o ponto de extremidade correspondente da API REST, [Crie um token de acesso de instalação para um aplicativo](/rest/reference/apps#create-an-installation-access-token-for-an-app). Isto exige autenticação como um aplicativo GitHub usando um JWT. Para obter mais informações, consulte [Efetuar a autenticação como um aplicativo GitHub](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app) e [Efetuar a autenticação como uma instalação](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). -1. Use este token de servidor para servidor para interagir com seus repositórios, seja por meio das APIs REST ou GraphQL, ou por meio de um cliente Git. - - - -## Usuários máquina - -If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. É possível adicionar o usuário máquina como [colaborador][collaborator] em um repositório pessoal (concedendo acesso de leitura e gravação), como [colaborador externo][outside-collaborator] em um repositório da organização (concedendo leitura, acesso gravação, ou administrador) ou como uma [equipe][team], com acesso aos repositórios que precisa automatizar (concedendo as permissões da equipe). +If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). {% ifversion fpt or ghec %} @@ -173,43 +154,34 @@ If your server needs to access multiple repositories, you can create a new accou **Tip:** Our [terms of service][tos] state: +> *Accounts registered by "bots" or other automated methods are not permitted.* - -> *Contas registradas por "bots" ou outros métodos automatizados não são permitidas.* - -Isto significa que você não pode automatizar a criação de contas. Mas se você desejar criar um único usuário máquina para automatizar tarefas como scripts de implantação em seu projeto ou organização, isso é muito legal. +This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool. {% endtip %} {% endif %} +#### Pros +* Anyone with access to the repository and server has the ability to deploy the project. +* No (human) users need to change their local SSH settings. +* Multiple keys are not needed; one per server is adequate. -#### Prós +#### Cons -* Qualquer pessoa com acesso ao repositório e servidor é capaz de implantar o projeto. -* Nenhum usuário (humano) precisa alterar suas configurações de SSH locais. -* Não são necessárias várias chaves; o adequado é uma por servidor. +* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access. +* Machine user keys, like deploy keys, are usually not protected by a passphrase. +#### Setup - -#### Contras - -* Apenas organizações podem restringir os usuários máquina para acesso somente leitura. Os repositórios pessoais sempre concedem aos colaboradores acesso de leitura/gravação. -* Chaves dos usuário máquina, como chaves de implantação, geralmente não são protegidas por senha. - - - -#### Configuração - -1. [Execute o procedimento `ssh-keygen`][generating-ssh-keys] no seu servidor e anexe a chave pública à conta do usuário máquina. -2. Dê acesso à conta de usuário máquina aos repositórios que deseja automatizar. Você pode fazer isso adicionando a conta como [colaborador][collaborator], como [colaborador externo][outside-collaborator] ou como uma [equipe][team] em uma organização. +1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account. +2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization. [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/ [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/ [git-automation]: /articles/git-automation-with-oauth-tokens -[git-automation]: /articles/git-automation-with-oauth-tokens [collaborator]: /articles/inviting-collaborators-to-a-personal-repository [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization [team]: /articles/adding-organization-members-to-a-team diff --git a/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md index fce7c9043c..c7ccfa8b72 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md @@ -1,6 +1,6 @@ --- -title: Tipos de eventos de problemas -intro: 'Para a API de eventos de problemas e API da Linha do tempo, aprenda sobre cada tipo de evento, ativando a ação em {% data variables.product.prodname_dotcom %}, bem como as propriedades únicas de cada evento.' +title: Issue event types +intro: 'For the Issues Events API and Timeline API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.' redirect_from: - /v3/issues/issue-event-types - /developers/webhooks-and-events/issue-event-types @@ -12,28 +12,27 @@ versions: topics: - Events --- +Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. -Eventos de problemas são acionados pela atividade em problemas e pull requests e estão disponíveis na [API de eventos de problemas](/rest/reference/issues#events) e na [API de eventos da linha do tempo](/rest/reference/issues#timeline). Cada tipo de evento especifica se o evento está disponível nos eventos do problema ou na API de eventos da linha do tempo. +GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. -A API REST do GitHub considera que todo pull request é um problema, mas nem todos os problemas são pull request. Por este motivo, os eventos de problemas e os pontos de extremidade dos eventos da linha do tempo podem retornar problemas e pull requests na resposta. Pull requests têm uma propriedade `pull_request` no objeto `problema`. Como os pull requests são problemas, os números de problemas e pull requests não se sobrepõem em um repositório. Por exemplo, se você abrir seu primeiro problema em um repositório, o número será 1. Se você abrir um pull request, o número será 2. Cada tipo de evento especifica se o evento ocorre em um pull request, em um problema ou em ambos. +## Issue event object common properties -## Propriedades comuns do objeto de evento do problema - -Todos os eventos de problema têm a mesma estrutura de objeto, exceto os eventos que estão disponíveis apenas na API de eventos da linha do tempo. Alguns eventos também incluem propriedades adicionais que fornecem mais contexto sobre os recursos do evento. Consulte o evento específico para obter informações sobre quaisquer propriedades que diferem deste formato de objeto. +Issue events all have the same object structure, except events that are only available in the Timeline Events API. Some events also include additional properties that provide more context about the event resources. Refer to the specific event to for details about any properties that differ from this object format. {% data reusables.issue-events.issue-event-common-properties %} ## added_to_project -O problema ou pull request foi adicionado a um quadro de projeto. {% data reusables.projects.disabled-projects %} +The issue or pull request was added to a project board. {% data reusables.projects.disabled-projects %} -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|

    • Problemas
    • Pull request
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull request
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -41,173 +40,173 @@ O problema ou pull request foi adicionado a um quadro de projeto. {% data reusab {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.project-card-properties %} -## atribuído +## assigned -O problema ou o pull request foi atribuído a um usuário. +The issue or pull request was assigned to a user. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.assignee-properties %} ## automatic_base_change_failed -O GitHub tentou alterar automaticamente o branch base do pull request sem sucesso. +GitHub unsuccessfully attempted to automatically change the base branch of the pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## automatic_base_change_succeeded -O GitHub tentou alterar automaticamente o branch base do pull request com sucesso. +GitHub successfully attempted to automatically change the base branch of the pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## ref_base_alterada +## base_ref_changed -O branch de referência do pull request alterado. +The base reference branch of the pull request changed. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## closed -O problema ou pull request foi fechado. Quando o `commit_id` está presente, ele identifica o commit que fechou o problema usando sintaxe "fecha/corrige". Para obter mais informações sobre a sintaxe, consulte "[Vinculando um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". +The issue or pull request was closed. When the `commit_id` is present, it identifies the commit that closed the issue using "closes / fixes" syntax. For more information about the syntax, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## comentado +## commented -Um comentário foi adicionado ao problema ou pull request. +A comment was added to the issue or pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nome | Tipo | Descrição | -| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `url` | `string` | A URL da API REST para recuperar o comentário do problema. | -| `html_url` | `string` | A URL de HTML do comentário do problema. | -| `issue_url` | `string` | A URL de HTML do problema. | -| `id` | `inteiro` | O identificador exclusivo do evento. | -| `node_id` | `string` | O [ID de nó global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) do evento. | -| `usuário` | `objeto` | A pessoa que comentou sobre o problema. | -| `created_at` | `string` | A marca de tempo que indica quando o comentário foi adicionado. | -| `updated_at` | `string` | A marca de tempo que indica quando o comentário foi atualizado ou criado, se o comentário nunca for atualizado. | -| `author_association` | `string` | As permissões que o usuário tem no repositório do problema. Por exemplo, o valor seria `"PROPRIETÁRIO"` se o proprietário do repositório criasse um comentário. | -| `texto` | `string` | O texto do comentário. | -| `event` | `string` | O valor da reunião é `"comentado"`. | -| `actor` | `objeto` | A pessoa que gerou o evento. | +Name | Type | Description +-----|------|-------------- +`url` | `string` | The REST API URL to retrieve the issue comment. +`html_url` | `string` | The HTML URL of the issue comment. +`issue_url` | `string` | The HTML URL of the issue. +`id` | `integer` | The unique identifier of the event. +`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event. +`user` | `object` | The person who commented on the issue. +`created_at` | `string` | The timestamp indicating when the comment was added. +`updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated. +`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment. +`body` | `string` | The comment body text. +`event` | `string` | The event value is `"commented"`. +`actor` | `object` | The person who generated the event. -## comprometido +## committed -Um commit foi adicionado ao branch `HEAD` do pull request. +A commit was added to the pull request's `HEAD` branch. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nome | Tipo | Descrição | -| ------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sha` | `string` | O SHA do commit no pull request. | -| `node_id` | `string` | O [ID de nó global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) do evento. | -| `url` | `string` | A URL da API REST para recuperar o commit. | -| `html_url` | `string` | A URL de HTML do commit. | -| `autor` | `objeto` | A pessoa que autorizou o commit. | -| `committer` | `objeto` | A pessoa que confirmou o commit em nome do autor. | -| `árvore` | `objeto` | A árvore Git do commit. | -| `mensagem` | `string` | A mensagem do commit. | -| `principais` | `array de objetos` | Uma lista de commits principais. | -| `verificação` | `objeto` | O resultado de verificação da assinatura do commit. Para obter mais informações, consulte "[Objeto verificação de assinatura](/rest/reference/git#get-a-commit)". | -| `event` | `string` | O valor do evento é `"commited"`. | +Name | Type | Description +-----|------|-------------- +`sha` | `string` | The SHA of the commit in the pull request. +`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event. +`url` | `string` | The REST API URL to retrieve the commit. +`html_url` | `string` | The HTML URL of the commit. +`author` | `object` | The person who authored the commit. +`committer` | `object` | The person who committed the commit on behalf of the author. +`tree` | `object` | The Git tree of the commit. +`message` | `string` | The commit message. +`parents` | `array of objects` | A list of parent commits. +`verification` | `object` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#get-a-commit)." +`event` | `string` | The event value is `"committed"`. -## conectado +## connected -O problema ou pull request foi vinculado a outro problema ou pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". +The issue or pull request was linked to another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## convert_to_draft -O pull request foi convertido para modo rascunho. +The pull request was converted to draft mode. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## converted_note_to_issue -O problema foi criado convertendo uma observação de um quadro de projeto em uma problema. {% data reusables.projects.disabled-projects %} +The issue was created by converting a note in a project board to an issue. {% data reusables.projects.disabled-projects %} -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -217,230 +216,232 @@ O problema foi criado convertendo uma observação de um quadro de projeto em um ## cross-referenced -O problema ou pull request foi referenciado a partir de outro problema ou pull request. +The issue or pull request was referenced from another issue or pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nome | Tipo | Descrição | -| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor` | `objeto` | A pessoa que gerou o evento. | -| `created_at` | `string` | A marca de tempo que indica quando a referência cruzada foi adicionada. | -| `updated_at` | `string` | A marca de tempo que indica quando a referência cruzada foi atualizada ou criada, se a referência cruzada nunca for atualizada. | -| `fonte` | `objeto` | O problema ou pull request que adicionou uma referência cruzada. | -| `source[type]` | `string` | Esse valor será sempre `"problema"`, porque os pull requests são do tipo problema. Apenas eventos de referência cruzada acionados por problemas são retornados na API de eventos da linha te tempo. Para determinar se o problema que acionou o evento é um pull request, você pode verificar se o objeto `[issue][pull_request` existe. | -| `source[issue]` | `objeto` | O objeto `problema` que adicionou a referência cruzada. | -| `event` | `string` | O valor do evento é `"referência cruzada"`. | +Name | Type | Description +-----|------|-------------- +`actor` | `object` | The person who generated the event. +`created_at` | `string` | The timestamp indicating when the cross-reference was added. +`updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated. +`source` | `object` | The issue or pull request that added a cross-reference. +`source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request` object exists. +`source[issue]` | `object` | The `issue` object that added the cross-reference. +`event` | `string` | The event value is `"cross-referenced"`. ## demilestoned -O problema ou pull request foi removido de um marco. +The issue or pull request was removed from a milestone. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`marco` | `objeto` | Objeto do marco. `marco[title]` | `string` | O título do marco. +`milestone` | `object` | The milestone object. +`milestone[title]` | `string` | The title of the milestone. -## implantado +## deployed -O pull request foi implantado. +The pull request was deployed. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## deployment_environment_changed -O ambiente de implantação do pull request foi alterado. +The pull request deployment environment was changed. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## desconectado +## disconnected -O problema ou o pull request foi desvinculado de outro problema ou pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". +The issue or pull request was unlinked from another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## head_ref_deleted -O branch `HEAD` do pull request foi excluído. +The pull request's `HEAD` branch was deleted. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## head_ref_restored -O branch `HEAD` do pull request foi restaurado para o último commit conhecido. +The pull request's `HEAD` branch was restored to the last known commit. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## etiquetado +## labeled -Uma etiqueta foi adicionada ao problema ou pull request. +A label was added to the issue or pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.label-properties %} -## bloqueado +## locked -O problema ou pull request foi bloqueado. +The issue or pull request was locked. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | O motivo pelo qual uma conversa sobre o problema ou pull request foi bloqueada, caso tenha sido fornecida. +`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided. -## mencionado +## mentioned -O `ator` foi `@mentioned` em um problema ou texto de pull request. +The `actor` was `@mentioned` in an issue or pull request body. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## marked_as_duplicate -Um usuário com permissões de gravação marcou um problema como duplicata de outro problema ou um pull request como duplicata de outro pull request. +A user with write permissions marked an issue as a duplicate of another issue, or a pull request as a duplicate of another pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## merged -O pull request foi mesclado. O atributo `commit_id` é o SHA1 do commit do `HEAD` que foi mesclado. O `commit_repository` é sempre o mesmo do repositório principal. +The pull request was merged. The `commit_id` attribute is the SHA1 of the `HEAD` commit that was merged. The `commit_repository` is always the same as the main repository. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## marcado +## milestoned -O problema ou pull request foi adicionado a um marco. +The issue or pull request was added to a milestone. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`marco` | `objeto` | Objeto do marco. `marco[title]` | `string` | O título do marco. +`milestone` | `object` | The milestone object. +`milestone[title]` | `string` | The title of the milestone. ## moved_columns_in_project -O problema ou pull request foi movido entre as colunas em um quadro de projeto. {% data reusables.projects.disabled-projects %} +The issue or pull request was moved between columns in a project board. {% data reusables.projects.disabled-projects %} -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.project-card-properties %} -`previous_column_name` | `string` | O nome da coluna da qual o problema foi movido. +`previous_column_name` | `string` | The name of the column the issue was moved from. -## fixado +## pinned -O problema foi fixado. +The issue was pinned. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} @@ -448,327 +449,280 @@ O problema foi fixado. A draft pull request was marked as ready for review. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## referenciado +## referenced -O problema foi referenciado a partir de uma mensagem de commit. O atributo do     commit_id` é o SHA1 do commit onde isso ocorreu e o commit_repository é o local onde esse commit foi feito carregado.

    +The issue was referenced from a commit message. The `commit_id` attribute is the commit SHA1 of where that happened and the commit_repository is where that commit was pushed. -

    Disponibilidade

    +### Availability - - - - - - - - - - - - - - - -
    Tipo de problemaAPI de eventos de problemaAPI de eventos da linha de tempo
    • Problemas
    • Pull requests
    		XX
    +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -

    Propriedades do objeto do evento

    +### Event object properties -

    {% data reusables.issue-events.issue-event-common-properties %}

    +{% data reusables.issue-events.issue-event-common-properties %} -

    removed_from_project

    +## removed_from_project -

    O problema ou pull request foi removido de um quadro de projeto. {% data reusables.projects.disabled-projects %}

    +The issue or pull request was removed from a project board. {% data reusables.projects.disabled-projects %} -

    Disponibilidade

    +### Availability - - - - - - - - - - - - - - - -
    Tipo de problemaAPI de eventos de problemaAPI de eventos da linha de tempo
    • Problemas
    • Pull requests
    		XX
    +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -

    Propriedades do objeto do evento

    +### Event object properties -

    {% data reusables.pre-release-program.starfox-preview %}

    +{% data reusables.pre-release-program.starfox-preview %} +{% data reusables.pre-release-program.api-preview-warning %} -

    -

    +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.project-card-properties %} -

    {% data reusables.pre-release-program.api-preview-warning %}

    +## renamed -

    {% data reusables.issue-events.issue-event-common-properties %}

    +The issue or pull request title was changed. -

    -

    +### Availability -

    {% data reusables.issue-events.project-card-properties %}

    +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -

    renamed

    +### Event object properties -

    O problema ou o título do pull request foi alterado.

    +{% data reusables.issue-events.issue-event-common-properties %} +`rename` | `object` | The name details. +`rename[from]` | `string` | The previous name. +`rename[to]` | `string` | The new name. -

    Disponibilidade

    +## reopened - - - - - - - - - - - - - - - -
    Tipo de problemaAPI de eventos de problemaAPI de eventos da linha de tempo
    • Problemas
    • Pull requests
    		XX
    +The issue or pull request was reopened. -

    Propriedades do objeto do evento

    +### Availability -

    {% data reusables.issue-events.issue-event-common-properties %}

    +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -

    -renomear` | `objeto` | As informações do nome. `renomear[from]` | `string` | O nome anterior. `Renomear[to]` | `string` | O novo nome. - -## reaberto - -O problema ou o pull request foi reaberto. - -### Disponibilidade - -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|

    • Problemas
    • Pull requests
    | **X** | **X** | - -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} ## review_dismissed -A revisão do pull request foi ignorada. +The pull request review was dismissed. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-dismissed-properties %} ## review_requested -Foi solicitada uma revisão do pull request. +A pull request review was requested. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-request-properties %} ## review_request_removed -Uma solicitação de revisão do pull request foi removida. +A pull request review request was removed. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-request-properties %} -## revisado +## reviewed -O pull request foi revisado. +The pull request was reviewed. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Pull requests
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Pull requests
    | | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.timeline_events_object_properties %} -| Nome | Tipo | Descrição | -| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `inteiro` | O identificador exclusivo do evento. | -| `node_id` | `string` | O [ID de nó global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) do evento. | -| `usuário` | `objeto` | A pessoa que comentou sobre o problema. | -| `texto` | `string` | O texto do resumo da revisão. | -| `commit_id` | `string` | O SHA do último commit no pull request no momento da revisão. | -| `submitted_at` | `string` | A marca de tempo que indica quando a revisão foi enviada. | -| `estado` | `string` | O estado da revisão enviada. Pode ser um desses: `comentado`, `changes_requested` ou `aprovado`. | -| `html_url` | `string` | A URL de HTML da revisão. | -| `pull_request_url` | `string` | A URL da API REST para recuperar a o pull request. | -| `author_association` | `string` | As permissões que o usuário tem no repositório do problema. Por exemplo, o valor seria `"PROPRIETÁRIO"` se o proprietário do repositório criasse um comentário. | -| `_links` | `objeto` | O `html_url` e `pull_request_url`. | -| `event` | `string` | O valor do evento é `"revisado"`. | +Name | Type | Description +-----|------|-------------- +`id` | `integer` | The unique identifier of the event. +`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event. +`user` | `object` | The person who commented on the issue. +`body` | `string` | The review summary text. +`commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review. +`submitted_at` | `string` | The timestamp indicating when the review was submitted. +`state` | `string` | The state of the submitted review. Can be one of: `commented`, `changes_requested`, or `approved`. +`html_url` | `string` | The HTML URL of the review. +`pull_request_url` | `string` | The REST API URL to retrieve the pull request. +`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment. +`_links` | `object` | The `html_url` and `pull_request_url`. +`event` | `string` | The event value is `"reviewed"`. -## assinado +## subscribed -Alguém faz a assinatura para receber notificações de um problema ou pull request. +Someone subscribed to receive notifications for an issue or pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## transferido +## transferred -O problema foi transferido para outro repositório. +The issue was transferred to another repository. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## não atribuido +## unassigned -Um usuário foi não foi atribuído a partir do problema. +A user was unassigned from the issue. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.assignee-properties %} -## sem etiqueta +## unlabeled -Uma etiqueta foi removida do problema. +A label was removed from the issue. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.label-properties %} -## desbloqueado +## unlocked -O problema estava desbloqueado. +The issue was unlocked. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | O motivo pelo qual uma conversa sobre o problema ou pull request foi bloqueada, caso tenha sido fornecida. +`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided. ## unmarked_as_duplicate -Um problema que um usuário havia marcado anteriormente como uma duplicata de outro problema não é considerado mais uma duplicata, ou um pull request que um usuário havia marcado anteriormente como uma duplicata de outro pull request não é mais considerado uma duplicata. +An issue that a user had previously marked as a duplicate of another issue is no longer considered a duplicate, or a pull request that a user had previously marked as a duplicate of another pull request is no longer considered a duplicate. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## desfixado +## unpinned -O problema foi desfixado. +The issue was unpinned. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} -## assinatura cancelada +## unsubscribed -Alguém cancelou a assinatura para receber notificações de um problema ou pull request. +Someone unsubscribed from receiving notifications for an issue or pull request. -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} {% ifversion fpt or ghec %} ## user_blocked -Um proprietário da organização bloqueou um usuário da organização. Isso foi feito [por meio de um dos comentários de um usuário bloqueado no problema](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). +An organization owner blocked a user from the organization. This was done [through one of the blocked user's comments on the issue](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). -### Disponibilidade +### Availability -| Tipo de problema | API de eventos de problema | API de eventos da linha de tempo | -|:-------------------------- |:--------------------------:|:--------------------------------:| -|
    • Problemas
    • Pull requests
    | **X** | **X** | +|Issue type | Issue events API | Timeline events API| +|:----------|:----------------:|:-----------------:| +|
    • Issues
    • Pull requests
    | **X** | **X** | -### Propriedades do objeto do evento +### Event object properties {% data reusables.issue-events.issue-event-common-properties %} diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index c225f3228f..bc383cc73c 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -1,6 +1,6 @@ --- -title: Protegendo seus webhooks -intro: 'Certifique-se de que seu servidor só esteja recebendo as solicitações esperadas do {% data variables.product.prodname_dotcom %} por motivos de segurança.' +title: Securing your webhooks +intro: 'Ensure your server is only receiving the expected {% data variables.product.prodname_dotcom %} requests for security reasons.' redirect_from: - /webhooks/securing - /developers/webhooks-and-events/securing-your-webhooks @@ -12,42 +12,42 @@ versions: topics: - Webhooks --- - -Assim que seu servidor estiver configurado para receber cargas, ele ouvirá qualquer carga enviada para o ponto de extremidade que você configurou. Por motivos de segurança, você provavelmente vai querer limitar os pedidos para aqueles provenientes do GitHub. Existem algumas maneiras de fazer isso. Você poderia, por exemplo, optar por permitir solicitações do endereço IP do GitHub. No entanto, um método muito mais fácil é configurar um token secreto e validar a informação. +Once your server is configured to receive payloads, it'll listen for any payload sent to the endpoint you configured. For security reasons, you probably want to limit requests to those coming from GitHub. There are a few ways to go about this--for example, you could opt to allow requests from GitHub's IP address--but a far easier method is to set up a secret token and validate the information. {% data reusables.webhooks.webhooks-rest-api-links %} -## Definir seu token secreto +## Setting your secret token -Você precisará configurar seu token secreto em dois lugares: no GitHub e no seu servidor. +You'll need to set up your secret token in two places: GitHub and your server. -Para definir seu token no GitHub: +To set your token on GitHub: -1. Navegue até o repositório onde você está configurando seu webhook. -2. Preencha a caixa de texto do segredo. Use uma string aleatória com alta entropia (por exemplo, pegando a saída de `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` no terminal). ![Campo de webhook e token secreto](/assets/images/webhook_secret_token.png) -3. Clique em **Atualizar o webhook**. +1. Navigate to the repository where you're setting up your webhook. +2. Fill out the Secret textbox. Use a random string with high entropy (e.g., by taking the output of `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` at the terminal). +![Webhook secret token field](/assets/images/webhook_secret_token.png) +3. Click **Update Webhook**. -Em seguida, configure uma variável de ambiente em seu servidor que armazene este token. Normalmente, isso é tão simples quanto executar: +Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running: ```shell $ export SECRET_TOKEN=your_token ``` -**Nunca** pré-programe o token no seu aplicativo! +**Never** hardcode the token into your app! -## Validar cargas do GitHub +## Validating payloads from GitHub -Quando seu token secreto está definido, {% data variables.product.product_name %} o utiliza para criar uma assinatura de hash com cada carga. This hash signature is included with the headers of each request as `X-Hub-Signature-256`. +When your secret token is set, {% data variables.product.product_name %} uses it to create a hash signature with each payload. This hash signature is included with the headers of each request as `X-Hub-Signature-256`. {% ifversion fpt or ghes or ghec %} {% note %} -**Observação:** Para compatibilidade com versões anteriores, também incluímos o cabeçalho `X-Hub-Signature` gerado usando a função de hash SHA-1. Se possível, recomendamos que você use o cabeçalho `X-Hub-Signature-256` para melhorar a segurança. O exemplo abaixo demonstra o uso do cabeçalho `X-Hub-Signature-256`. +**Note:** For backward-compatibility, we also include the `X-Hub-Signature` header that is generated using the SHA-1 hash function. If possible, we recommend that you use the `X-Hub-Signature-256` header for improved security. The example below demonstrates using the `X-Hub-Signature-256` header. {% endnote %} {% endif %} -Por exemplo, se você tem um servidor básico que ouve webhooks, ele poderá ser configurado de forma semelhante a isso: +For example, if you have a basic server that listens for webhooks, it might be configured similar to this: ``` ruby require 'sinatra' @@ -60,7 +60,7 @@ post '/payload' do end ``` -O objetivo é calcular um hash usando seu `SECRET_TOKEN` e garantir que o resultado corresponda ao hash de {% data variables.product.product_name %}. {% data variables.product.product_name %} usa um resumo hexadecimal HMAC para calcular o hash. Portanto, você pode reconfigurar o seu servidor para que se pareça mais ou menos assim: +The intention is to calculate a hash using your `SECRET_TOKEN`, and ensure that the result matches the hash from {% data variables.product.product_name %}. {% data variables.product.product_name %} uses an HMAC hex digest to compute the hash, so you could reconfigure your server to look a little like this: ``` ruby post '/payload' do @@ -79,14 +79,14 @@ end {% note %} -**Observação:** As cargas de webhook podem conter caracteres de unicode. Se o seu idioma e a implementação de servidor especificarem uma codificação de caracteres, certifique-se de que você manipula a carga como UTF-8. +**Note:** Webhook payloads can contain unicode characters. If your language and server implementation specifies a character encoding, ensure that you handle the payload as UTF-8. {% endnote %} -A sua linguagem e implementações do servidor podem ser diferentes deste código de exemplo. No entanto, há uma série de aspectos muito importantes a destacar: +Your language and server implementations may differ from this example code. However, there are a number of very important things to point out: * No matter which implementation you use, the hash signature starts with `sha256=`, using the key of your secret token and your payload body. -* Não **se recomenda** usar um operador simples de`==`. Um método como [`secure_compare`][secure_compare] executa uma comparação de strings "tempo constante", o que ajuda a mitigar certos ataques de tempo contra operadores de igualdade regular. +* Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. [secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md deleted file mode 100644 index 1940448651..0000000000 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ /dev/null @@ -1,1445 +0,0 @@ ---- -title: Eventos de webhook e cargas -intro: 'Para cada evento de webhook, você pode revisar quando o evento ocorrer, uma carga de exemplo, bem como as descrições sobre os parâmetros do objeto da carga.' -product: '{% data reusables.gated-features.enterprise_account_webhooks %}' -redirect_from: - - /early-access/integrations/webhooks/ - - /v3/activity/events/types/ - - /webhooks/event-payloads - - /developers/webhooks-and-events/webhook-events-and-payloads -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Webhooks -shortTitle: Eventos webhook & cargas ---- - -{% ifversion fpt or ghec %} - -{% endif %} - -{% data reusables.webhooks.webhooks_intro %} - -Você pode criar webhooks que assinam os eventos listados nesta página. Cada evento de webhook inclui uma descrição das propriedades do webhook e uma carga de exemplo. Para obter mais informações, consulte "[Criar webhooks](/webhooks/creating/)." - -## Propriedades comuns do objeto da carga do webhook - -Cada carga do evento do webhook também contém propriedades únicas para o evento. Você pode encontrar as propriedades únicas nas seções individuais de tipos de evento. - -| Tecla | Tipo | Descrição | -| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A maioria das cargas de webhook contém uma ação `` propriedade que contém a atividade específica que acionou o evento. | -{% data reusables.webhooks.sender_desc %} Esta propriedade está incluída em todas as cargas do webhook. -{% data reusables.webhooks.repo_desc %} As cargas do webhook contêm a propriedade `repository` quando ocorre o evento a partir da atividade em um repositório. -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} Para obter mais informações, consulte "[Criar um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/). - -As propriedades únicas para um evento de webhook são as mesmas propriedades que você encontrará na propriedade `payload` ao usar a [Eventos API](/rest/reference/activity#events). Uma exceção é o evento de [`push`](#push). As propriedades únicas da carga do webhook do evento `push` e a propriedade `carga` na API de eventos são diferentes. A carga do webhook contém informações mais detalhadas. - -{% tip %} - -**Observação:** As cargas são limitados a 25 MB. Se o seu evento gerar uma carga maior, um webhook não será disparado. Isso pode acontecer, por exemplo, em um evento `criar`, caso muitos branches ou tags sejam carregados de uma só vez. Sugerimos monitorar o tamanho da sua carga para garantir a entrega. - -{% endtip %} - -### Cabeçalhos de entrega - -As cargas de HTTP POST que são entregues no ponto de extremidade da URL configurado do seu webhook conterão vários cabeçalhos especiais: - -| Header | Descrição | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Nome do evento que ativou a entrega. | -| `X-GitHub-Delivery` | Um [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) para identificar a entrega.{% ifversion ghes or ghae %} -| `X-GitHub-Enterprise-Version` | A versão da instância do {% data variables.product.prodname_ghe_server %} que enviou a carga do HTTP POST. | -| `X-GitHub-Enterprise-Host` | O nome de host da instância do {% data variables.product.prodname_ghe_server %} que enviou a carga HTTP POST.{% endif %}{% ifversion not ghae %} -| `X-Hub-Signature` | Este cabeçalho é enviado se o webhook for configurado com um [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% ifversion fpt or ghes or ghec %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %} -| `X-Hub-Signature-256` | Este cabeçalho é enviado se o webhook for configurado com um [`secret`](/rest/reference/repos#create-hook-config-params). Este é o resumo hexadecimal HMAC do texto da solicitação e é gerado usando a função hash SHA-256 e a `segredo` como a `chave` HMAC. | - -Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hookshot/`. - -### Exemplo de entrega - -```shell -> POST /payload HTTP/2 - -> Host: localhost:4567 -> X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% ifversion ghes or ghae %} -> X-GitHub-Enterprise-Version: 2.15.0 -> X-GitHub-Enterprise-Host: example.com{% endif %}{% ifversion not ghae %} -> X-Hub-Signature: sha1=7d38cdd689735b008b3c702edd92eea23791c5f6{% endif %} -> X-Hub-Signature-256: sha256=d57c68ca6f92289e6987922ff26938930f6e66a2d161ef06abdf1859230aa23c -> User-Agent: GitHub-Hookshot/044aadd -> Content-Type: application/json -> Content-Length: 6615 -> X-GitHub-Event: issues - -> { -> "action": "opened", -> "issue": { -> "url": "{% data variables.product.api_url_pre %}/repos/octocat/Hello-World/issues/1347", -> "number": 1347, -> ... -> }, -> "repository" : { -> "id": 1296269, -> "full_name": "octocat/Hello-World", -> "owner": { -> "login": "octocat", -> "id": 1, -> ... -> }, -> ... -> }, -> "sender": { -> "login": "octocat", -> "id": 1, -> ... -> } -> } -``` - -{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} -## branch_protection_rule - -Atividade relacionada a uma regra de proteção do branch. Para obter mais informações, consulte[Sobre as regras de proteção do branch](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)". - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com pelo menos acesso `somente leitura` na administração de repositórios - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `criado`, `editado` ou `excluído`. | -| `rule` | `objeto` | A regra de proteção do branch. Inclui um `nome` e todas as [configurações de proteção de branch](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) aplicadas a branches que correspondem ao nome. As configurações binárias são booleanas. As configurações de multi-nível tem um dos valores a seguir:`off`, `non_admins` ou `everyone`. As listas do criador e da criação são matrizes de strings. | -| `alterações` | `objeto` | Se a ação foi `editada`, as alterações para a regra. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.branch_protection_rule.edited }} -{% endif %} -## check_run - -{% data reusables.webhooks.check_run_short_desc %} - -{% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} - -### Disponibilidade - -- Os webhooks de repositório só recebem cargas para os tipos de evento `criados` e `concluídos` em um repositório -- Os webhooks da organização só recebem cargas para os tipos de eventos `criados` e `concluídos` nos repositórios -- {% data variables.product.prodname_github_apps %} com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `requested_action`. As cargas do tipo de evento `solicitadas` e `requested_action` são enviadas apenas para o {% data variables.product.prodname_github_app %} que está sendo solicitado. {% data variables.product.prodname_github_apps %} com `checks:write` são automaticamente inscritos neste evento webhook. - -### Objeto da carga do webhook - -{% data reusables.webhooks.check_run_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.check_run.created }} - -## check_suite - -{% data reusables.webhooks.check_suite_short_desc %} - -{% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} - -### Disponibilidade - -- Os webhooks de repositório só recebem cargas para os tipos de evento `concluídos` em um repositório -- Os webhooks da organização só recebem cargas para os tipos de eventos `concluídos` nos repositórios -- {% data variables.product.prodname_github_apps %} com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `ressolicitados.`. As cargas de evento `solicitadas` e `ressolicitadas` são enviadas apenas para {% data variables.product.prodname_github_app %} que está sendo solicitado. {% data variables.product.prodname_github_apps %} com `checks:write` são automaticamente inscritos neste evento webhook. - -### Objeto da carga do webhook - -{% data reusables.webhooks.check_suite_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.check_suite.completed }} - -## code_scanning_alert - -Os {% data variables.product.prodname_github_app %}s com a permissão `security_events` - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão de `security_events :read` - -### Objeto da carga do webhook - -{% data reusables.webhooks.code_scanning_alert_event_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -    remetente`| objeto` | Se a de ação ` for reopened_by_user` ou `closed_by_user`, o objeto `remetente` será o usuário que ativou o evento. O objeto `remetente` é {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}vazio{% endif %} para todas as outras ações. - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} - -## commit_comment - -{% data reusables.webhooks.commit_comment_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -{% data reusables.webhooks.commit_comment_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.commit_comment.created }} - -## content_reference - -{% data reusables.webhooks.content_reference_short_desc %} - -Os eventos de webhook são acionados com base na especificidade do domínio que você registra. Por exemplo, se você registrar um subdomínio (`https://subdomain.example.com`), apenas as URLs para o subdomínio irão ativar este evento. Se você registrar um domínio (`https://example.com`), as URLs para domínio e todos os subdomínios irão ativar este evento. Consulte "[Crie um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment)" para criar um novo anexo de conteúdo. - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} com a permissão `content_references:write` - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.content_reference.created }} - -## create - -{% data reusables.webhooks.create_short_desc %} - -{% note %} - -**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez. - -{% endnote %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -{% data reusables.webhooks.create_properties %} -{% data reusables.webhooks.pusher_type_desc %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.create }} - -## delete - -{% data reusables.webhooks.delete_short_desc %} - -{% note %} - -**Observação:** Você não receberá um webhook para este evento ao excluir mais de três tags de uma só vez. - -{% endnote %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -{% data reusables.webhooks.delete_properties %} -{% data reusables.webhooks.pusher_type_desc %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.delete }} - -## deploy_key - -{% data reusables.webhooks.deploy_key_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização - -### Objeto da carga do webhook - -{% data reusables.webhooks.deploy_key_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.deploy_key.created }} - -## implantação - -{% data reusables.webhooks.deployment_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `implantações` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------------- | ------------------------------------------- | ---------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} -| `implantação` | `objeto` | The [implantação](/rest/reference/repos#list-deployments). | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.deployment }} - -## implantação_status - -{% data reusables.webhooks.deployment_status_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `implantações` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ---------------------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------ |{% ifversion fpt or ghes or ghae or ghec %} -| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} -| `implantação_status` | `objeto` | O [estado de implantação](/rest/reference/repos#list-deployment-statuses). | -| `deployment_status["state"]` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | -| `deployment_status["target_url"]` | `string` | O link opcional adicionado ao status. | -| `deployment_status["description"]` | `string` | A descrição opcional legível para pessoas adicionada ao status. | -| `implantação` | `objeto` | A [implantação](/rest/reference/repos#list-deployments) à qual este status está associado. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.deployment_status }} - -{% ifversion fpt or ghec %} -## discussão - -{% data reusables.webhooks.discussions-webhooks-beta %} - -Atividade relacionada a uma discussão. Para obter mais informações, consulte "[Usar a API do GraphQL para discussões]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)". -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `discussões` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered` ou `unanswered`. | -{% data reusables.webhooks.discussion_desc %} -{% data reusables.webhooks.repo_desc_graphql %} -{% data reusables.webhooks.org_desc_graphql %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.discussion.created }} - -## discussion_comment - -{% data reusables.webhooks.discussions-webhooks-beta %} - -Atividade relacionada a um comentário em uma discussão. Para obter mais informações, consulte "[Usar a API do GraphQL para discussões]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)". - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `discussões` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `criado`, `editado` ou `excluído`. | -| `comentário` | `objeto` | O recurso [`comentário de discussão`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment). | -{% data reusables.webhooks.discussion_desc %} -{% data reusables.webhooks.repo_desc_graphql %} -{% data reusables.webhooks.org_desc_graphql %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.discussion_comment.created }} -{% endif %} - -{% ifversion ghes or ghae %} - -## enterprise - -{% data reusables.webhooks.enterprise_short_desc %} - -### Disponibilidade - -- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)." - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------ | -------- | ------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `anonymous_access_enabled` ou `anonymous_access_disabled`. | - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} - -{% endif %} - -## bifurcação - -{% data reusables.webhooks.fork_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -{% data reusables.webhooks.fork_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.fork }} - -## github_app_authorization - -Este evento ocorre quando alguém revoga a autorização de um {% data variables.product.prodname_github_app %}. Um {% data variables.product.prodname_github_app %} recebe este webhook por padrão e não pode cancelar a assinatura deste evento. - -{% data reusables.webhooks.authorization_event %} Para obter informações sobre solicitações de usuário para servidor, que exigem autorização do {% data variables.product.prodname_github_app %}, consulte "[Identificando e autorizando usuários para {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------ | -------- | -------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `revogada`. | -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} - -## gollum - -{% data reusables.webhooks.gollum_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -{% data reusables.webhooks.gollum_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.gollum }} - -## instalação - -{% data reusables.webhooks.installation_short_desc %} - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} - -### Objeto da carga do webhook - -{% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_always_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.installation.deleted }} - -## installation_repositories - -{% data reusables.webhooks.installation_repositories_short_desc %} - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} - -### Objeto da carga do webhook - -{% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_always_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.installation_repositories.added }} - -## issue_comment - -{% data reusables.webhooks.issue_comment_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `problemas` - -### Objeto da carga do webhook - -{% data reusables.webhooks.issue_comment_webhook_properties %} -{% data reusables.webhooks.issue_comment_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.issue_comment.created }} - -## Problemas - -{% data reusables.webhooks.issues_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `problemas` - -### Objeto da carga do webhook - -{% data reusables.webhooks.issue_webhook_properties %} -{% data reusables.webhooks.issue_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook quando alguém editar um problema - -{{ webhookPayloadsForCurrentVersion.issues.edited }} - -## etiqueta - -{% data reusables.webhooks.label_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `metadados` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ---------------------- | -------- | --------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser `criado`, `editado` ou `excluído`. | -| `etiqueta` | `objeto` | A etiqueta que foi adicionada. | -| `alterações` | `objeto` | As alterações na etiqueta se a ação foi `editada`. | -| `changes[name][from]` | `string` | A versão anterior do nome se a ação foi `editada`. | -| `changes[color][from]` | `string` | A versão anterior da cor se a ação foi `editada`. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.label.deleted }} - -{% ifversion fpt or ghec %} -## marketplace_purchase - -Atividade relacionada a uma compra do GitHub Marketplace. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte o "[GitHub Marketplace](/marketplace/)". - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada para um plano do [GitHub Marketplace](https://github.com/marketplace). Pode ser uma das ações a seguir:
    • `comprado` - Alguém comprou um plano do GitHub Marketplace. A mudança deve entrar em vigor na conta imediatamente.
    • `pending_change` - Você receberá o evento `pending_change` quando alguém tiver feito o downgrade ou cancelado um plano do GitHub Marketplace para indicar que uma alteração ocorrerá na conta. O novo plano ou cancelamento entra em vigor no final do ciclo de cobrança. O tipo de evento `cancelado` ou `alterado` será enviado quando o ciclo de cobrança terminar e o cancelamento ou o novo plano entrarem em vigor.
    • `pending_change_cancelled` - Alguém cancelou uma alteração pendente. Alterações pendentes incluem planos de cancelamento e downgrades que entrarão em vigor ao fim de um ciclo de cobrança.
    • `alterado` - Alguém fez o upgrade ou downgrade de um plano do GitHub Marketplace e a alteração entrará em vigor na conta imediatamente.
    • `cancelado` - Alguém cancelou um plano do GitHub Marketplace e o último ciclo de cobrança foi finalizado. A mudança deve entrar em vigor na conta imediatamente.
    | - -Para obter uma descrição detalhada desta carga e da carga para cada tipo de `ação`, consulte [eventos do webhook de {% data variables.product.prodname_marketplace %} ](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). - -### Exemplo de carga de webhook quando alguém compra o plano - -{{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} - -{% endif %} - -## integrante - -{% data reusables.webhooks.member_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` - -### Objeto da carga do webhook - -{% data reusables.webhooks.member_webhook_properties %} -{% data reusables.webhooks.member_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.member.added }} - -## filiação - -{% data reusables.webhooks.membership_short_desc %} - -### Disponibilidade - -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` - -### Objeto da carga do webhook - -{% data reusables.webhooks.membership_properties %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.membership.removed }} - -## meta - -O webhook em que este evento está configurado em foi excluído. Este evento só ouvirá alterações no hook em que o evento está instalado. Portanto, deve ser selecionado para cada hook para o qual você gostaria de receber metaeventos. - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| --------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `excluído`. | -| `hook_id` | `inteiro` | O ID do webhook modificado. | -| `hook` | `objeto` | O webhook modificado. Isto irá conter chaves diferentes com base no tipo de webhook que é: repositório, organização, negócios, aplicativo ou GitHub Marketplace. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.meta.deleted }} - -## marco - -{% data reusables.webhooks.milestone_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` - -### Objeto da carga do webhook - -{% data reusables.webhooks.milestone_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.milestone.created }} - -## organização - -{% data reusables.webhooks.organization_short_desc %} - -### Disponibilidade - -{% ifversion ghes or ghae %} -- Os webhooks do GitHub Enterprise recebem apenas eventos `criados` e `excluídos`. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} -- Os webhooks da organização recebem apenas os eventos `excluídos`, `adicionados`, `removidos`, `renomeado` e `convidados` -- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser um dos valores a seguir:{% ifversion ghes or ghae %} `criado`,{% endif %} `excluído`, `renomeado`, `member_added`, `member_removed` ou `member_invited`. | -| `convite` | `objeto` | O convite para o usuário ou e-mail se a ação for `member_invited`. | -| `filiação` | `objeto` | A associação entre o usuário e a organização. Ausente quando a ação é `member_invited`. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.organization.member_added }} - -{% ifversion fpt or ghec %} - -## org_block - -{% data reusables.webhooks.org_block_short_desc %} - -### Disponibilidade - -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `organization_administration` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| -------------- | -------- | --------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `bloqueado` ou `desbloqueado`. | -| `blocked_user` | `objeto` | Informações sobre o usuário bloqueado ou desbloqueado. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.org_block.blocked }} - -{% endif %} - -{% ifversion fpt or ghae or ghec %} - -## pacote - -Atividade relacionada a {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Gerenciar pacotes com {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para saber mais sobre {% data variables.product.prodname_registry %}. - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização - -### Objeto da carga do webhook - -{% data reusables.webhooks.package_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.package.published }} -{% endif %} - -## page_build - -{% data reusables.webhooks.page_build_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `pages` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------- | --------- | --------------------------------------------------------------------------------------- | -| `id` | `inteiro` | O identificador exclusivo da criação de páginas. | -| `build` | `objeto` | A [Listar as criações do GitHub Pages](/rest/reference/repos#list-github-pages-builds). | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.page_build }} - -## ping - -{% data reusables.webhooks.ping_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} recebe um evento de ping com um `app_id` usado para registrar o aplicativo - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| -------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `zen` | `string` | String aleatória do Github zen. | -| `hook_id` | `inteiro` | O ID do webhook que acionou o ping. | -| `hook` | `objeto` | A [configuração do webhook](/rest/reference/repos#get-a-repository-webhook). | -| `hook[app_id]` | `inteiro` | Ao registrar um novo {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} envia um evento de ping para a **URL do webhook** que você especificou no registro. O evento contém o `app_id`, que é necessário para a [efetuar a autenticação](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) em um aplicativo. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.ping }} - -## project_card - -{% data reusables.webhooks.project_card_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects` - -### Objeto da carga do webhook - -{% data reusables.webhooks.project_card_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.project_card.created }} - -## project_column - -{% data reusables.webhooks.project_column_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects` - -### Objeto da carga do webhook - -{% data reusables.webhooks.project_column_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.project_column.created }} - -## project - -{% data reusables.webhooks.project_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects` - -### Objeto da carga do webhook - -{% data reusables.webhooks.project_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.project.created }} - -{% ifversion fpt or ghes or ghec %} -## público - -{% data reusables.webhooks.public_short_desc %} -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `metadados` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ----- | ---- | --------- | -| | | | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.public }} -{% endif %} -## pull_request - -{% data reusables.webhooks.pull_request_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` - -### Objeto da carga do webhook - -{% data reusables.webhooks.pull_request_webhook_properties %} -{% data reusables.webhooks.pull_request_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -As entregas para eventos `review_requested` e `review_request_removed` terão um campo adicional denominado `requested_reviewer`. - -{{ webhookPayloadsForCurrentVersion.pull_request.opened }} - -## pull_request_review - -{% data reusables.webhooks.pull_request_review_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` - -### Objeto da carga do webhook - -{% data reusables.webhooks.pull_request_review_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }} - -## pull_request_review_comment - -{% data reusables.webhooks.pull_request_review_comment_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` - -### Objeto da carga do webhook - -{% data reusables.webhooks.pull_request_review_comment_webhook_properties %} -{% data reusables.webhooks.pull_request_review_comment_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }} - -## push - -{% data reusables.webhooks.push_short_desc %} - -{% note %} - -**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez. - -{% endnote %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | O [`git ref completo`](/rest/reference/git#refs) que foi empurrado. Exemplo: `refs/heads/main` ou `refs/tags/v3.14.1`. | -| `antes` | `string` | O SHA do último commit em `ref` antes do push. | -| `depois` | `string` | O SHA do último commit no `ref` após o push. | -| `created` | `boolean` | Se este push criou o `ref`. | -| `deleted` | `boolean` | Se este push excluiu o `ref`. | -| `forced` | `boolean` | Se este push foi um push forçado do `ref`. | -| `head_commit` | `objeto` | Para pushes em que `after` é ou aponta para um objeto de commit, uma representação expandida desse commit. Para pushes em que `after` refere-se a um objeto de tag anotada, uma representação expandida do commit apontada pela tag anotada. | -| `compare` | `string` | A URL que mostra as alterações na atualização deste `ref`, do commit `before` para o commit `after`. Para um `ref` recém-criado que é diretamente baseado no branch padrão, esta é a comparação entre o cabeçalho do branch padrão e o commit `after`. Caso contrário, isso mostra todos os commits até o commit `after`. | -| `commits` | `array` | Um array de objetos de commit, que descreve os commits carregados. (Os commits que sofreram push são todos commits incluídos no `compare` entre o commit `before` e o commit `after`.) O array inclui um máximo de 20 commits. Se necessário, você pode usar a [API de Commits](/rest/reference/repos#commits) para obter commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook. | -| `commits[][id]` | `string` | O SHA do commit. | -| `commits[][timestamp]` | `string` | O carimbo de tempo ISO 8601 do commit. | -| `commits[][message]` | `string` | A mensagem do commit. | -| `commits[][author]` | `objeto` | O autor do git do commit. | -| `commits[][author][name]` | `string` | O nome do autor do git. | -| `commits[][author][email]` | `string` | O endereço de e-mail do autor do git. | -| `commits[][url]` | `url` | URL que aponta para o recurso de commit de API. | -| `commits[][distinct]` | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente. | -| `commits[][added]` | `array` | Um array de arquivos adicionados no commit. | -| `commits[][modified]` | `array` | Um array de arquivos modificados pelo commit. | -| `commits[][removed]` | `array` | Um array de arquivos removidos no commit. | -| `pusher` | `objeto` | O usuário que fez o push dos commits. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.push }} - -## versão - -{% data reusables.webhooks.release_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` - -### Objeto da carga do webhook - -{% data reusables.webhooks.release_webhook_properties %} -{% data reusables.webhooks.release_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.release.published }} - -{% ifversion fpt or ghes or ghae or ghec %} -## repository_dispatch - -Este evento ocorre quando um {% data variables.product.prodname_github_app %} envia uma solicitação de `POST` para o "[Crie um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} deve ter a permissão do conteúdo `` para receber este webhook. - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} - -## repositório - -{% data reusables.webhooks.repository_short_desc %} - -### Disponibilidade - -- Os webhooks do repositório recebem todos os tipos de eventos, exceto `excluído` -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão de `metadados`, recebe todos os tipos de eventos, exceto `excluídos` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------ | -------- | ---------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Este pode ser um dos seguintes:
    • `created` - Um repositório foi criado.
    • `deleted` - Um repositório foi excluído.
    • `archived` - Um repositório está arquivado.
    • `unarchived` - Um repositório não está arquivado.
      • {% ifversion ghes or ghae %}
    • `anonymous_access_enabled` - Um repositório está [habilitado para acesso anônimo ao Git](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - Um repositório está [desativado para acesso anônimo ao Git](/rest/overview/api-previews#anonymous-git-access-to-repositories)
      • {% endif %}
    • `edited` - As informações de um repositório são editadas.
    • `renamed` - Um repositório é renomeado.
    • `transferred` - Um repositório é transferido.
    • `publicized` - Um repositório é publicado.
    • `privatizado` - Um repositório é privatizado.
    | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.repository.publicized }} - -{% ifversion fpt or ghec %} -## repository_import - -{% data reusables.webhooks.repository_import_short_desc %} Para receber este evento para um repositório pessoal, você deve criar um repositório vazio antes da importação. Este evento pode ser acionado usando o [Importador do GitHub](/articles/importing-a-repository-with-github-importer/) ou a API [Api de Importação de Fonte](/rest/reference/migrations#source-imports). - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização - -### Objeto da carga do webhook - -{% data reusables.webhooks.repository_import_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.repository_import }} - -## repository_vulnerability_alert - -{% data reusables.webhooks.repository_vulnerability_alert_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização - -### Objeto da carga do webhook - -{% data reusables.webhooks.repository_vulnerability_alert_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }} - -{% endif %} - -{% ifversion fpt or ghes > 3.0 or ghec %} - -## secret_scanning_alert - -{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `secret_scanning_alerts:read` - -### Objeto da carga do webhook - -{% data reusables.webhooks.secret_scanning_alert_event_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -`sender` | `object` | Se a `action` is `resolved` ou `reopened`, o objeto de `sender` será o usuário que acionou o evento. O objeto `remetente` está vazio para todas as outras ações. - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} -{% endif %} - -{% ifversion fpt or ghes or ghec %} -## security_advisory - -Atividade relacionada a uma consultora de segurança. Uma consultoria de segurança fornece informações sobre vulnerabilidades relacionadas à segurança em softwares no GitHub. O conjunto de dados da consultoria de segurança também promove os alertas de segurança do GitHub, consulte "[Sobre os alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)." -{% endif %} - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} com a permissão `security_events` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. A ação pode ser `published`, `updated`, `performed` ou `withdrawn` para todos os novos eventos. | -| `security_advisory` | `objeto` | As informações da consultoria de segurança, incluindo resumo, descrição e gravidade. | - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.security_advisory.published }} - -{% ifversion fpt or ghec %} -## patrocínio - -{% data reusables.webhooks.sponsorship_short_desc %} - -Você só pode criar um webhook de patrocínio em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Configurar webhooks para eventos na sua conta patrocinada](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)". - -### Disponibilidade - -- Contas patrocinadas - -### Objeto da carga do webhook - -{% data reusables.webhooks.sponsorship_webhook_properties %} -{% data reusables.webhooks.sponsorship_properties %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook quando alguém cria um patrocínio - -{{ webhookPayloadsForCurrentVersion.sponsorship.created }} - -### Exemplo de carga de webhook quando alguém faz o downgrade de um patrocínio - -{{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }} - -{% endif %} - -## estrela - -{% data reusables.webhooks.star_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização - -### Objeto da carga do webhook - -{% data reusables.webhooks.star_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.star.created }} - -## status - -{% data reusables.webhooks.status_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `status` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `inteiro` | O identificador exclusivo do status. | -| `sha` | `string` | O SHA do commit. | -| `estado` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | -| `descrição` | `string` | A descrição opcional legível para pessoas adicionada ao status. | -| `url_destino` | `string` | O link opcional adicionado ao status. | -| `branches` | `array` | Um array de objetos de branch que contém o SHA do status. Cada branch contém o SHA fornecido, mas o SHA pode ou não ser o cabeçalho do branch. O array inclui, no máximo, 10 branches. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.status }} - -## equipe - -{% data reusables.webhooks.team_short_desc %} - -### Disponibilidade - -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| ----------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser `criado`, `excluído`, `editados`, `added_to_repository`, ou `removed_from_repository`. | -| `equipe` | `objeto` | A própria equipe. | -| `alterações` | `objeto` | As alterações para a equipe se a ação foi `editada`. | -| `changes[description][from]` | `string` | A versão anterior da descrição se a ação foi `editada`. | -| `changes[name][from]` | `string` | A versão anterior do nome se a ação foi `editada`. | -| `changes[privacy][from]` | `string` | A versão anterior da equipe de privacidade se a ação foi `editada`. | -| `changes[repository][permissions][from][admin]` | `boolean` | A versão anterior da permissão `admin` do integrante da equipe no repositório, se a ação foi `editada`. | -| `changes[repository][permissions][from][pull]` | `boolean` | A versão anterior da permissão `pull` do integrante da equipe em um repositório, se a ação foi `editada`. | -| `changes[repository][permissions][from][push]` | `boolean` | A versão anterior da permissão `push` do integrante da equipe no repositório, se a ação foi `editada`. | -| `repositório` | `objeto` | O repositório adicionado ou removido à função da equipe se a ação foi `added_to_repository`, `removed_from_repository`, ou `editada`. Para ações `editadas`, o `repositório` também contém os novos níveis de permissão da equipe para o repositório. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.team.added_to_repository }} - -## team_add - -{% data reusables.webhooks.team_add_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` - -### Objeto da carga do webhook - -| Tecla | Tipo | Descrição | -| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------- | -| `equipe` | `objeto` | A [equipe](/rest/reference/teams) que foi modificada. **Observação:** Os eventos mais antigos podem não incluir isso na carga. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.team_add }} - -{% ifversion ghes or ghae %} - -## usuário - -Quando um usuário é `criado` ou `excluído`. - -### Disponibilidade -- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)." - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.user.created }} - -{% endif %} - -## inspecionar - -{% data reusables.webhooks.watch_short_desc %} - -O ator do evento é o [usuário](/rest/reference/users) que favoritou um repositório, e o repositório do evento é [repositório](/rest/reference/repos) que foi marcado com estrela. - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- {% data variables.product.prodname_github_apps %} com a permissão `metadados` - -### Objeto da carga do webhook - -{% data reusables.webhooks.watch_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.watch.started }} - -{% ifversion fpt or ghes or ghec %} -## workflow_dispatch - -Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no GitHub ou envia uma solicitação de `POST` para o ponto de extremidade "[Criar um evento de envio de fluxo de trabalho](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} deve ter a permissão do conteúdo `` para receber este webhook. - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.workflow_dispatch }} -{% endif %} - -{% ifversion fpt or ghes > 3.2 or ghec %} - -## workflow_job - -{% data reusables.webhooks.workflow_job_short_desc %} - -### Disponibilidade - -- Webhooks do repositório -- Webhooks da organização -- Webhooks corporativos - -### Objeto da carga do webhook - -{% data reusables.webhooks.workflow_job_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.workflow_job }} - -{% endif %} -{% ifversion fpt or ghes or ghec %} -## workflow_run - -Quando uma execução do fluxo de trabalho de {% data variables.product.prodname_actions %} for solicitada ou concluída. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_run)". - -### Disponibilidade - -- {% data variables.product.prodname_github_apps %} com as permissões `ações` ou `conteúdos`. - -### Objeto da carga do webhook - -{% data reusables.webhooks.workflow_run_properties %} -{% data reusables.webhooks.workflow_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.sender_desc %} - -### Exemplo de carga de webhook - -{{ webhookPayloadsForCurrentVersion.workflow_run }} -{% endif %} diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md index 74269ee5bf..77e4c35b89 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md @@ -1,6 +1,6 @@ --- -title: Sobre Consultores de campus -intro: 'Como um instrutor ou mentor, aprenda a usar o {% data variables.product.prodname_dotcom %} na sua escola com treinamento e suporte de Consultores de campus.' +title: About Campus Advisors +intro: 'As an instructor or mentor, learn to use {% data variables.product.prodname_dotcom %} at your school with Campus Advisors training and support.' redirect_from: - /education/teach-and-learn-with-github-education/about-campus-advisors - /github/teaching-and-learning-with-github-education/about-campus-advisors @@ -9,8 +9,7 @@ redirect_from: versions: fpt: '*' --- - -Os mestres, professores e mentores podem usar o treinamento online Consultores de campus para dominar o Git e o {% data variables.product.prodname_dotcom %}, bem como para conhecer as práticas recomendadas de ensino com o {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Consultores de campus](https://education.github.com/teachers/advisors)". +Professors, teachers and mentors can use the Campus Advisors online training to master Git and {% data variables.product.prodname_dotcom %} and learn best practices for teaching students with {% data variables.product.prodname_dotcom %}. For more information, see "[Campus Advisors](https://education.github.com/teachers/advisors)." {% note %} @@ -18,6 +17,6 @@ Os mestres, professores e mentores podem usar o treinamento online Consultores d {% endnote %} -Os professores podem gerenciar um curso sobre desenvolvimento de software com {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} permite distribuir código, fornecer feedback e gerenciar trabalhos do curso usando {% data variables.product.product_name %}. Para obter mais informações, consulte "[Gerenciar cursos com {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)". +Teachers can manage a course on software development with {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} allows you to distribute code, provide feedback, and manage coursework using {% data variables.product.product_name %}. For more information, see "[Manage coursework with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)." -Se você for estudante ou professor acadêmico e sua escola não faz parceria com o {% data variables.product.prodname_dotcom %} como uma escola do {% data variables.product.prodname_campus_program %}, ainda assim é possível solicitar descontos individualmente para usar o {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_dotcom %} para fazer o trabalho de escola](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" ou "[Usar o {% data variables.product.prodname_dotcom %} em sala de aula e em pesquisas](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)". +If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" or "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)." diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md index aa0480f2cb..e99cae3fc8 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md @@ -1,6 +1,6 @@ --- -title: Sobre o Programa do GitHub Campus -intro: '{% data variables.product.prodname_campus_program %} oferece {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} gratuitamente para as escolas que querem tirar o máximo proveito de {% data variables.product.prodname_dotcom %} para a sua comunidade.' +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' redirect_from: - /education/teach-and-learn-with-github-education/about-github-education - /github/teaching-and-learning-with-github-education/about-github-education @@ -9,39 +9,38 @@ redirect_from: - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program versions: fpt: '*' -shortTitle: Programa de campus do GitHub +shortTitle: GitHub Campus Program --- +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: -{% data variables.product.prodname_campus_program %} é um pacote de acesso premium de {% data variables.product.prodname_dotcom %} para instituições orientadas para o ensino que concedem graus, diplomas ou certificados. {% data variables.product.prodname_campus_program %} inclui: +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- 50,000 {% data variables.product.prodname_actions %} minutes and 50 GB {% data variables.product.prodname_registry %} storage +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our [Campus Advisor program](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} -- Acesso sem custo a {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} para todos os seus departamentos técnicos e acadêmicos -- 50.000 {% data variables.product.prodname_actions %} minutos e 50 GB {% data variables.product.prodname_registry %} de armazenamento -- Treinamento do professor para dominar o Git e {% data variables.product.prodname_dotcom %} com o nosso [Programa de Consultor de Campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) -- Acesso exclusivo a novas funcionalidades, swage específico do GitHub Education e ferramentas grátis de desenvolvedor dos parceiros de {% data variables.product.prodname_dotcom %} -- Acesso automatizado a recursos premium do {% data variables.product.prodname_education %}, como o {% data variables.product.prodname_student_pack %} +To read about how GitHub is used by educators, see [GitHub Education stories.](https://education.github.com/stories) -Para ler sobre como o GitHub é usado pelos educadores, consulte [histórias do GitHub Education](https://education.github.com/stories). +## {% data variables.product.prodname_campus_program %} terms and conditions -## Termos e condições de {% data variables.product.prodname_campus_program %} +- The license is free for one year and will automatically renew for free every 2 years. You may continue on the free license so long as you continue to operate within the terms of the agreement. Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. -- A licença é grátis por um ano e será renovada automaticamente a cada 2 anos. Você pode continuar com a licença grátis desde que você continue operando nos termos do contrato. Qualquer escola que concorde com os [termos do programa](https://education.github.com/schools/terms) é bem-vinda. +- Please note that the licenses are for use by the whole school. Internal IT departments, academic research groups, collaborators, students, and other non-academic departments are eligible to use the licenses so long as they are not making a profit from its use. Externally funded research groups that are housed at the university may not use the free licenses. -- Observe que as licenças são usadas por toda a escola. Os departamentos internos de TI, grupos de pesquisa acadêmica, colaboradores, estudantes, e outros departamentos não acadêmicos são elegíveis para a utilização das licenças, desde que não lucrem com a sua utilização. Os grupos de investigação alojados na universidade financiados externamente podem não utilizar as licenças grátis. +- You must offer {% data variables.product.prodname_dotcom %} to all of your technical and academic departments and your school’s logo will be shared on the GitHub Education website as a {% data variables.product.prodname_campus_program %} Partner. -- Você deve oferecer {% data variables.product.prodname_dotcom %} para todos os seus departamentos técnicos e acadêmicos e o logotipo da sua escola será compartilhado no site do GitHub Education como parceiro do {% data variables.product.prodname_campus_program %}. - -- Novas organizações da empresa são automaticamente adicionadas à sua conta corporativa. Para adicionar organizações que existiam antes de sua escola juntar-se à {% data variables.product.prodname_campus_program %}, entre em contato com o [suporte do GitHub Education](https://support.github.com/contact/education). For more information about administrating your enterprise, see the [enterprise administrators documentation](/admin). Novas organizações da empresa são automaticamente adicionadas à sua conta corporativa. Para adicionar organizações que existiam antes de sua escola juntar-se à {% data variables.product.prodname_campus_program %}, entre em contato com o suporte do GitHub Education. +- New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact [GitHub Education Support](https://support.github.com/contact/education). For more information about administrating your enterprise, see the [enterprise administrators documentation](/admin). New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact GitHub Education Support. -Para ler mais sobre as práticas de privacidade de {% data variables.product.prodname_dotcom %}, consulte ["Práticas Globais de Privacidade"](/github/site-policy/global-privacy-practices) +To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices) -## Elegibilidade do aplicativo de {% data variables.product.prodname_campus_program %} +## {% data variables.product.prodname_campus_program %} Application Eligibility -- Muitas vezes, um campus CTO/CIO, Dean, presidente do departamento ou responsável pela tecnologia assina os termos do programa em nome do campus. +- Often times, a campus CTO/CIO, Dean, Department Chair, or Technology Officer signs the terms of the program on behalf of the campus. -- Se sua escola não emitir endereços de e-mail, {% data variables.product.prodname_dotcom %} entrará em contato com os administradores da sua conta com uma opção alternativa para permitir que você distribua o pacote de desenvolvedor para estudante para os seus alunos. +- If your school does not issue email addresses, {% data variables.product.prodname_dotcom %} will reach out to your account administrators with an alternative option to allow you to distribute the student developer pack to your students. -Para obter mais informações, consulte a página [oficial do {% data variables.product.prodname_campus_program %}](https://education.github.com/schools). +For more information, see the [official {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) page. -Se você for estudante ou professor acadêmico e sua escola não faz parceria com o {% data variables.product.prodname_dotcom %} como uma escola do {% data variables.product.prodname_campus_program %}, ainda assim é possível solicitar descontos individualmente para usar o {% data variables.product.prodname_dotcom %}. Para candidatar-se ao pacote de desenvolvedor para estudantes, [consulte o formulário de candidatura](https://education.github.com/pack/join). +If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. To apply for the Student Developer Pack, [see the application form](https://education.github.com/pack/join). diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md deleted file mode 100644 index 482eea3371..0000000000 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Motivos da reprovação da candidatura ao pacote de desenvolvedor para estudante -intro: 'Analise os motivos comuns para a reprovação de candidaturas ao {% data variables.product.prodname_student_pack %} e veja dicas para se candidatar novamente sem problemas.' -redirect_from: - - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved - - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved - - /articles/why-was-my-application-for-a-student-developer-pack-denied/ - - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved - - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved - - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved -versions: - fpt: '*' -shortTitle: Solicitação recusada ---- - -{% tip %} - -**Dica:** {% data reusables.education.about-github-education-link %} - -{% endtip %} - -## Falta de clareza em documentos de afiliação acadêmica - -Se as datas ou cronogramas mencionados na sua imagem carregada não corresponderem aos nossos critérios de elegibilidade, precisaremos de mais provas do seu status acadêmico. - -Se a imagem que você subiu não identificar claramente o seu status acadêmico atual ou se a imagem carregada estiver desfocada, precisaremos de uma prova adicional do seu status acadêmico. {% data reusables.education.upload-proof-reapply %} - -{% data reusables.education.pdf-support %} - -## Uso de e-mail acadêmico com domínio não verificado - -Se o seu endereço de e-mail acadêmico tiver um domínio não verificado, exigiremos mais provas do seu status acadêmico. {% data reusables.education.upload-proof-reapply %} - -{% data reusables.education.pdf-support %} - -## Uso de e-mail acadêmico de uma escola com políticas de e-mail pouco rígidas - -Se os seus endereços de e-mail concedidos pela instituição de ensino forem anteriores à inscrição paga por aluno, exigiremos mais provas do seu status acadêmico. {% data reusables.education.upload-proof-reapply %} - -{% data reusables.education.pdf-support %} - -Se você tiver outras dúvidas sobre o domínio da instituição de ensino, peça à equipe de TI dela para entrar em contato conosco. - -## Endereço de e-mail acadêmico já usado - -Se seu endereço de e-mail acadêmico já foi usado para solicitar um {% data variables.product.prodname_student_pack %} para uma conta de {% data variables.product.prodname_dotcom %} diferente, você não poderá reutilizar o endereço de e-mail acadêmico para se inscrever com sucesso em outro {% data variables.product.prodname_student_pack %}. - -{% note %} - -**Observação:** é contra os [Termos de serviço](/articles/github-terms-of-service/#3-account-requirements) do {% data variables.product.prodname_dotcom %} manter mais de uma conta individual. - -{% endnote %} - -Se você tiver mais de uma conta de usuário pessoal, precisará fazer merge delas. Para não perder o desconto, mantenha a conta que recebeu o desconto. Você pode renomear a conta mantida e permanecer com o histórico de contribuições adicionando todos os seus endereços de e-mail à conta mantida. - -Para obter mais informações, consulte: -- "[Fazer merge de várias contas de usuário](/articles/merging-multiple-user-accounts)" -- "[Alterar seu nome de usuário do {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)" -- "[Adicionar um endereço de e-mail à sua conta do {% data variables.product.prodname_dotcom %}](/articles/adding-an-email-address-to-your-github-account)" - -## Status de aluno não qualificado - -Você não estará qualificado para um {% data variables.product.prodname_student_pack %} se: -- Você está inscrito em um programa de aprendizagem informal que não faz parte de [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) e não está inscrito em curso que irá conceder uma título ou diploma. -- Você irá obter um título que não estará mais disponível na sessão acadêmica atual. -- Tiver menos de 13 anos. - -Seu instrutor ainda poderá se candidatar a um desconto {% data variables.product.prodname_education %} para uso em sala de aula. Se você é um estudante em uma escola de programação ou bootcamp, você irá tornar-se elegível a {% data variables.product.prodname_student_pack %}, caso sua escola ingresse em [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). - -## Leia mais - -- "[Candidatar-se a um pacote de desenvolvedor para estudante](/articles/applying-for-a-student-developer-pack)" -- "[Solicite um pacote de desenvolvedor para estudante](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md index 7584a45e6f..e08cd628d3 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md @@ -1,6 +1,6 @@ --- -title: Gerenciar salas de aula -intro: 'Você pode criar e gerenciar uma sala de aula para cada curso que você der usando {% data variables.product.prodname_classroom %}.' +title: Manage classrooms +intro: 'You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}.' permissions: Organization owners can manage a classroom for an organization. versions: fpt: '*' @@ -9,101 +9,116 @@ redirect_from: - /education/manage-coursework-with-github-classroom/manage-classrooms --- -## Sobre as salas de aula +## About classrooms {% data reusables.classroom.about-classrooms %} -![Sala de aula](/assets/images/help/classroom/classroom-hero.png) +![Classroom](/assets/images/help/classroom/classroom-hero.png) -## Sobre o gerenciamento de salas de aula +## About management of classrooms -{% data variables.product.prodname_classroom %} usa contas da organização em {% data variables.product.product_name %} para gerenciar permissões, administração e segurança para cada sala de aula que você criar. Cada organização pode ter várias salas de aula. +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. -Depois de criar uma sala de aula, {% data variables.product.prodname_classroom %} solicitará que você convide assistentes de ensino (ETI) e administradores para a sala de aula. Cada sala de aula pode ter um ou mais administradores. Os administradores podem ser professores, TAs ou qualquer outro administrador do curso o qual que você gostaria que tivesse controle das suas salas de aula em {% data variables.product.prodname_classroom %}. +After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}. -Convide TAs e administradores para a sua sala de aula, convidando as contas de usuário em {% data variables.product.product_name %} para a sua organização como proprietários e compartilhando a URL da sua sala de aula. Os proprietários da organização podem administrar qualquer sala de aula da organização. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." +Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." -Ao terminar de usar uma sala de aula, você pode arquivar a sala de aula e consultar a sala de aula, lista, e recomendações posteriormente, ou você pode excluir a sala de aula se não precisar mais dela. +When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom. -## Sobre as listas de salas de aula +## About classroom rosters -Cada sala de aula tem uma lista. Uma lista é uma lista de identificadores para os alunos que participam do seu curso. +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. -A primeira vez que você compartilha a URL de uma atividade com um estudante, o aluno precisa efetuar o login em {% data variables.product.product_name %} com uma conta de usuário para vincular a conta do usuário a um identificador da sala de aula. Depois que o aluno vincular uma conta de usuário, você poderá ver a conta de usuário associada na lista. Você também pode ver quando o aluno aceita ou envia uma atividade. +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. -![Lista de salas de aula](/assets/images/help/classroom/roster-hero.png) +![Classroom roster](/assets/images/help/classroom/roster-hero.png) -## Pré-requisitos +## Prerequisites -Você precisa ter uma conta de organização em {% data variables.product.product_name %} para gerenciar as salas de aula em {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.company_short %}](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" e "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -Você deve autorizar o aplicativo OAuth {% data variables.product.prodname_classroom %} para sua organização gerenciar salas de aula para sua conta da organização. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". +You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." -## Criar uma sala de aula +## Creating a classroom {% data reusables.classroom.sign-into-github-classroom %} -1. Clique em **Nova sala de aula**. ![Botão "Nova sala de aula"](/assets/images/help/classroom/click-new-classroom-button.png) +1. Click **New classroom**. + !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) {% data reusables.classroom.guide-create-new-classroom %} -Depois de criar uma sala de aula, você pode começar a criar atividades para os alunos. Para obter mais informações, consulte "[Use a atividade inicial do Git e {% data variables.product.company_short %}](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment), "[Crie uma tarefa individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" ou "[Crie uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." +After you create a classroom, you can begin creating assignments for students. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." -## Criando uma lista para sua sala de aula +## Creating a roster for your classroom -Você pode criar uma lista de alunos que participam do seu curso. +You can create a roster of the students who participate in your course. -Se o seu curso já tem uma lista, você pode atualizar os alunos na lista ou excluir a lista. Para mais informações consulte "[Adicionar um aluno à lista de participantes para sua sala de aula](#adding-students-to-the-roster-for-your-classroom)" ou "[Excluir uma lista para uma sala de aula](#deleting-a-roster-for-a-classroom)." +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-students %} -1. Para conectar {% data variables.product.prodname_classroom %} ao seu LMS e importar uma lista, clique em {% octicon "mortar-board" aria-label="The mortar board icon" %} **Importar de um sistema de gerenciamento de aprendizagem** e siga as instruções. Para obter mais informações, consulte "[Conectar um sistema de gerenciamento de aprendizagem a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". ![Botão "Importar de um sistema de gerenciamento de aprendizagem"](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) -1. Forneça os identificadores dos alunos para a sua lista. - - Para importar uma lista de participantes fazendo o upload de um arquivo que contém identificadores de alunos, clique no **upload de um arquivo CSV ou texto**. - - Para criar uma lista manualmente, digite os identificadores do aluno. ![Campo de texto para digitar identificadores de aluno e botão "Fazer upload de um arquivo CSV ou texto"](/assets/images/help/classroom/type-or-upload-student-identifiers.png) -1. Clique **Criar lista**. ![Botão "Criar lista"](/assets/images/help/classroom/click-create-roster-button.png) +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. Provide the student identifiers for your roster. + - To import a roster by uploading a file containing student identifiers, click **Upload a CSV or text file**. + - To create a roster manually, type your student identifiers. + ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. + !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) -## Adicionar alunos à lista de participantes para sua sala de aula +## Adding students to the roster for your classroom -A sua sala de aula precisa ter uma lista existente para adicionar alunos à lista. Para obter mais informações sobre como criar uma lista, consulte "[Criar uma lista de participantes para sua sala de aula](#creating-a-roster-for-your-classroom)." +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classroom](#creating-a-roster-for-your-classroom)." {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-students %} -1. À direita do "Lista de sala de aula", clique em **Atualizar alunos**. ![Botão "Atualizar os alunos" à direita de "lista de salas de aula" destacando-se acima da lista de alunos](/assets/images/help/classroom/click-update-students-button.png) -1. Siga as instruções para adicionar alunos à lista. - - Para importar os alunos de um LMS, clique em **Sincronizar a partir de um sistema de gerenciamento de aprendizagem**. Para obter mais informações sobre a importação de uma lista de participantes de um LMS, consulte "[Conectar um sistema de gerenciamento de aprendizagem a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". - - Para adicionar alunos manualmente, em "Adicionar alunos manualmente", clique em **Enviar um arquivo CSV ou de texto** ou digite os identificadores para os alunos e, em seguida, clique em **Adicionar entradas da lista**. ![Modal para escolher o método de adicionar os alunos à sala de aula](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) +1. To the right of "Classroom roster", click **Update students**. + !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. + ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) -## Renomear uma sala de aula +## Renaming a classroom {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-settings %} -1. Em "Nome da sala de aula", digite um novo nome para a sala de aula. ![Campo de texto em "Nome da sala de aula" para digitar o nome da sala de aula](/assets/images/help/classroom/settings-type-classroom-name.png) -1. Clique em **Renomear sala de aula**. ![Botão "Renomear sala de aula"](/assets/images/help/classroom/settings-click-rename-classroom-button.png) +1. Under "Classroom name", type a new name for the classroom. + ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. + !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) -## Arquivar ou desarquivar uma sala de aula +## Archiving or unarchiving a classroom -Você pode arquivar uma sala de aula que você não usa mais em {% data variables.product.prodname_classroom %}. Ao arquivar uma sala de aula, não é possível criar novas atividades ou editar as atividades existentes para a sala de aula. Os alunos não podem aceitar convites para atividades em salas de aula arquivadas. +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. {% data reusables.classroom.sign-into-github-classroom %} -1. À direita do nome da sala de aula, selecione o menu suspenso {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Arquivar**. ![Menu suspenso do ícone do kebab horizontal e item do menu "Arquivo"](/assets/images/help/classroom/use-drop-down-then-click-archive.png) -1. Para desarquivar uma sala de aula, à direita do nome de uma sala de aula, selecione o menu suspenso {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Desarquivar**. ![Menu suspenso do ícone do kebab horizontal e item do menu "Desarquivar"](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. + ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. + ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) -## Excluir uma lista de participantes para uma sala de aula +## Deleting a roster for a classroom {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-students %} -1. Em "Excluir esta lista", clique em **Excluir lista**. ![Botão "Excluir lista" em "Excluir esta lista" na aba "Alunos" para uma sala de aula](/assets/images/help/classroom/students-click-delete-roster-button.png) -1. Leia os avisos e, em seguida, clique em **Excluir lista**. ![Botão "Excluir lista" em "Excluir esta lista" na aba "Alunos" para uma sala de aula](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) +1. Under "Delete this roster", click **Delete roster**. + !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. + !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) -## Excluir uma sala de aula +## Deleting a classroom {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-settings %} -1. À direita de "Excluir essa sala de aula", clique em **Excluir sala de aula**. ![Botão "Excluir repositório"](/assets/images/help/classroom/click-delete-classroom-button.png) -1. **Leia os avisos**. -1. Para verificar se você está excluindo a sala de aula correta, digite o nome da sala de aula que você deseja excluir. ![Modal para excluir uma sala de aula com avisos e campo de texto para o nome da sala de aula](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) -1. Clique em **Excluir sala de aula**. ![Botão "Excluir sala de aula"](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) +1. To the right of "Delete this classroom", click **Delete classroom**. + !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **Read the warnings**. +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. + ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. + !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md index 3e5b281db1..52cbeed516 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -1,5 +1,5 @@ --- -title: Sobre repositórios remotos +title: About remote repositories redirect_from: - /articles/working-when-github-goes-down/ - /articles/sharing-repositories-without-github/ @@ -10,89 +10,89 @@ redirect_from: - /github/using-git/about-remote-repositories - /github/getting-started-with-github/about-remote-repositories - /github/getting-started-with-github/getting-started-with-git/about-remote-repositories -intro: 'A abordagem colaborativa do GitHub para o desenvolvimento depende da publicação de commits do seu repositório local para {% data variables.product.product_name %} para que outras pessoas visualizem, façam buscas e atualizações.' +intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +## About remote repositories -## Sobre repositórios remotos +A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server. -Uma URL remota é outra forma de o Git dizer "o lugar onde seu código é armazenado". A URL poderia ser seu repositório no GitHub, ou a bifurcação de outro usuário, ou até mesmo em um servidor totalmente diferente. +You can only push to two types of URL addresses: -Você pode fazer push apenas de dois tipos de endereço URL: +* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git` +* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git` -* Uma URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git` -* Uma URL SSH, como `git@{% data variables.command_line.backticks %}:user/repo.git` +Git associates a remote URL with a name, and your default remote is usually called `origin`. -O Git associa uma URL remota a um nome, e seu remote padrão geralmente é chamado de `origin`. +## Creating remote repositories -## Criar repositórios remotos - -Você pode usar o comando `git remote add` para corresponder uma URL remota a um nome. Por exemplo, você digitaria o seguinte na linha de comando: +You can use the `git remote add` command to match a remote URL with a name. +For example, you'd type the following in the command line: ```shell -git remote add origin <URL_REMOTO> +git remote add origin <REMOTE_URL> ``` -Isso associa o nome `origin` ao `URL_REMOTO`. +This associates the name `origin` with the `REMOTE_URL`. -É possível usar o comando `git remote set-url` para [alterar uma URL de remote](/github/getting-started-with-github/managing-remote-repositories). +You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories). -## Escolher uma URL para o seu repositório remoto +## Choosing a URL for your remote repository -Existem várias maneiras de clonar repositórios disponíveis no {% data variables.product.product_location %}. +There are several ways to clone repositories available on {% data variables.product.product_location %}. -Quando você visualiza um repositório conectado à sua conta, as URLs que podem ser usadas para clonar o projeto no computador ficam disponíveis abaixo dos detalhes do repositório. +When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details. -Para obter informações sobre a configuração ou alteração da URL remota, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Clonando com as URLs de HTTPS +## Cloning with HTTPS URLs -As URLs de clone de `https:/` estão disponíveis em todos os repositórios, independentemente da visibilidade. As URL de clone de `https://` funcionam mesmo se você estiver atrás de um firewall ou proxy. +The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy. -Quando você aplicar `git clone`, `git fetch`, `git pull` ou `git push` a um repositório remote usando URLS de HTTPS na linha de comando, o Git solicitará o seu nome de usuário e sua senha do {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %} +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %} {% data reusables.command_line.provide-an-access-token %} {% tip %} -**Dicas**: -- Você pode usar um auxiliar de credenciais para que o Git se lembre de suas credenciais de {% data variables.product.prodname_dotcom %} toda vez que falar com {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Armazenar as suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)". -- Para clonar um repositório sem autenticar no {% data variables.product.product_name %} na linha de comando, use o {% data variables.product.prodname_desktop %}. Para obter mais informações, consulte "[Clonar um repositório do {% data variables.product.prodname_dotcom %} para o {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". +**Tips**: +- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." +- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." {% endtip %} - {% ifversion fpt or ghec %}Se você prefere usar o SSH mas não consegue conectar-se pela porta 22, você poderá usar o SSH através da porta HTTPS. Para obter mais informações, consulte "[Usar SSH através da porta HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %} + {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %} -## Clonar com URLs de SSH +## Cloning with SSH URLs -As URLs de SSH fornecem acesso a um repositório do Git via SSH, um protocolo seguro. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Conectar-se ao {% data variables.product.prodname_dotcom %} com SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)". +SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)." -Quando você aplicar `git clone`, `git fetch`, `git pull` ou `git push` a um repositório remote usando URLs de SSH, precisará digitar uma senha e a frase secreta da sua chave SSH. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)". +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)." -{% ifversion fpt or ghec %}Se você estiver acessando uma organização que usa o logon único SAML (SSO), você deverá autorizar sua chave SSH para acessar a organização antes de efetuar a autenticação. Para mais informações, consulte "[Sobre autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" e "[Autorizando uma chave SSH para uso com logon único SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} {% tip %} -**Dica**: Você pode usar uma URL com SSH para clonar um repositório para o seu computador ou como uma forma segura de implantar seu código nos servidores de produção. Você também pode usar o encaminhamento de agente SSH com o seu script de implantação para evitar o gerenciamento de chaves no servidor. Para obter mais informações, consulte "[Usar o encaminhamento do agente SSH](/developers/overview/using-ssh-agent-forwarding)." +**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} {% ifversion fpt or ghes or ghae or ghec %} -## Clonar com {% data variables.product.prodname_cli %} +## Cloning with {% data variables.product.prodname_cli %} -Você também pode instalar o {% data variables.product.prodname_cli %} para usar os fluxos de trabalho do {% data variables.product.product_name %} no seu terminal. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% endif %} {% ifversion not ghae %} -## Clonar com o Subversion +## Cloning with Subversion -Você também pode usar um cliente de [Subversion](https://subversion.apache.org/) para acessar qualquer repositório no {% data variables.product.prodname_dotcom %}. O Subversion oferece um conjunto de recursos diferente do Git. Para obter mais informações, consulte "[Quais são as diferenças entre Subversion e Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" +You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" -Você também pode acessar repositórios no {% data variables.product.prodname_dotcom %} a partir de clientes do Subversion. Para obter mais informações, consulte "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". +You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)." {% endif %} diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md b/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md index 00a8c565ab..3d7991aad9 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md @@ -1,5 +1,5 @@ --- -title: Ignorar arquivos +title: Ignoring files redirect_from: - /git-ignore/ - /ignore-files/ @@ -7,62 +7,60 @@ redirect_from: - /github/using-git/ignoring-files - /github/getting-started-with-github/ignoring-files - /github/getting-started-with-github/getting-started-with-git/ignoring-files -intro: 'Você pode configurar o Git para ignorar arquivos dos quais você não deseja fazer o check-in para {% data variables.product.product_name %}.' +intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +## Configuring ignored files for a single repository -## Configurar arquivos ignorados para um único repositório +You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit. +To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository. -Você pode criar um arquivo *.gitignore* arquivo no diretório-raiz do seu repositório para dizer ao Git quais arquivos e diretórios devem ser ignorados ao fazer um commit. Para compartilhar as regras de ignorar com outros usuários que clonarem o repositório, faça o commit do arquivo *.gitignore* no seu repositório. - -O GitHub mantém uma lista oficial de arquivos *.gitignore* recomendados para muitos sistemas operacionais populares, ambientes e linguagens no repositório público `github/gitignore`. É possível usar gitignore.io para criar um arquivo *.gitignore* para seu sistema operacional, linguagem de programação ou Ambiente de Desenvolvimento Integrado (IDE, Integrated Development Environment). Para obter mais informações, consulte "[github/gitignore](https://github.com/github/gitignore)" e o site "[gitignore.io](https://www.gitignore.io/)". +GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Navegue para o local do seu repositório do Git. -3. Crie um arquivo de *.gitignore* para o seu repositório. +2. Navigate to the location of your Git repository. +3. Create a *.gitignore* file for your repository. ```shell $ touch .gitignore ``` If the command succeeds, there will be no output. + +For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository. -Por obter um exemplo do arquivo *.gitignore*, consulte "[Algumas configurações comuns do .gitignore](https://gist.github.com/octocat/9257657)" no repositório do Octocat. - -Se você deseja ignorar um arquivo que já foi ingressado, você deve cancelar o rastreamento do arquivo antes de adicionar uma regra para ignorá-lo. No seu terminal, deixe de rastrear o arquivo. +If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file. ```shell $ git rm --cached FILENAME ``` -## Configurar arquivos ignorados para todos os repositórios no seu computador +## Configuring ignored files for all repositories on your computer -Você também pode criar um arquivo global *.gitignore* para definir uma lista de regras para ignorar arquivos em cada repositório do Git no seu computador. Por exemplo, você deverá criar o arquivo em *~/.gitignore_global* e adicionar algumas regras a ele. +You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Configure o Git para usar o arquivo de exclusão *~/.gitignore_global* para todos os repositórios do Git. +2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories. ```shell $ git config --global core.excludesfile ~/.gitignore_global ``` -## Excluir arquivos locais sem criar um arquivo *.gitignore* +## Excluding local files without creating a *.gitignore* file -Se você não quiser criar um arquivo *.gitignore* para compartilhar com outras pessoas, é possível criar regras sem fazer o commit no repositório. Você pode usar essa técnica para arquivos que você gerou localmente e que não espera que outros usuários o façam, como arquivos criados pelo seu editor. +If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor. -Use seu editor de textos preferido para abrir o arquivo *.git/info/exclude* dentro da raiz do repositório Git. Qualquer regra que você adicionar aqui não será verificada e ignorará arquivos somente em seu repositório local. +Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Navegue para o local do seu repositório do Git. -3. Abra o arquivo *.git/info/exclude* com seu editor de texto preferido. +2. Navigate to the location of your Git repository. +3. Using your favorite text editor, open the file *.git/info/exclude*. -## Leia mais +## Further Reading -* [Ignorar arquivos](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) no livro do Pro Git -* [.gitignore](https://git-scm.com/docs/gitignore) nas páginas de man para o Git -* -Uma coleção de *modelos úteis de *.gitignore* no repositório github/gitignore - - * Site do [gitignore.io](https://www.gitignore.io/) +* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book +* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git +* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository +* [gitignore.io](https://www.gitignore.io/) site diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md index 360fd17a54..3ffdb947b4 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -1,6 +1,6 @@ --- -title: Gerenciar repositórios remotos -intro: 'Aprenda a trabalhar com seus repositórios locais no seu computador e repositórios remotos hospedados no {% data variables.product.product_name %}.' +title: Managing remote repositories +intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.' redirect_from: - /categories/18/articles/ - /remotes/ @@ -23,83 +23,82 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Gerenciar repositórios remotos +shortTitle: Manage remote repositories --- +## Adding a remote repository -## Adicionar um repositório remoto +To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at. -Para adicionar um novo remoto, use o comando `adicionar remoto do git` no terminal do diretório no qual seu repositório está armazenado. +The `git remote add` command takes two arguments: +* A remote name, for example, `origin` +* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git` -O comando `git remote add` usa dois argumentos: -* Um nome de remote, por exemplo, `origin` -* Uma URL remota, por exemplo `https://{% data variables.command_line.backticks %}/user/repo.git` - -Por exemplo: +For example: ```shell $ git remote add origin https://{% data variables.command_line.codeblock %}/user/repo.git -# Defina um novo remote +# Set a new remote $ git remote -v -# Verifique o novo remote +# Verify new remote > origin https://{% data variables.command_line.codeblock %}/user/repo.git (fetch) > origin https://{% data variables.command_line.codeblock %}/user/repo.git (push) ``` -Para obter mais informações sobre qual URL usar, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". +For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." -### Solução de problemas: A origem remota já existe +### Troubleshooting: Remote origin already exists -Esse erro significa que você tentou adicionar um remote com um nome que já existe no repositório local. +This error means you've tried to add a remote with a name that already exists in your local repository. ```shell $ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` -Para corrigir isso, é possível: -* Usar um nome diferente para o novo remote. -* Renomeie o repositório remoto existente antes de adicionar o novo repositório remoto. Para obter mais informações, consulte "[Renomear um repositório remoto](#renaming-a-remote-repository)" abaixo. -* Exclua o repositório remoto existente antes de adicionar o novo repositório remoto. Para obter mais informações, consulte "[Removendo um repositório remoto](#removing-a-remote-repository)" abaixo. +To fix this, you can: +* Use a different name for the new remote. +* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below. +* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below. -## Alterar a URL de um repositório remoto +## Changing a remote repository's URL -O comando `git remote set-url` altera a URL de um repositório remoto existente. +The `git remote set-url` command changes an existing remote repository URL. {% tip %} -**Dica:** Para obter informações sobre a diferença entre as URLs de HTTPS e SSH, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". +**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." {% endtip %} -O comando `git remote set-url` usa dois argumentos: +The `git remote set-url` command takes two arguments: -* Um nome remote existente. Por exemplo, `origin` ou `upstream` são duas escolhas comuns. -* Uma nova URL para o remote. Por exemplo: - * Se estiver atualizando para usar HTTPS, a URL poderá ser parecida com esta: +* An existing remote name. For example, `origin` or `upstream` are two common choices. +* A new URL for the remote. For example: + * If you're updating to use HTTPS, your URL might look like: ```shell https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git ``` - * Se estiver atualizando para usar SSH, a URL poderá ser parecida com esta: + * If you're updating to use SSH, your URL might look like: ```shell git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git ``` -### Alternar URLs remotes de SSH para HTTPS +### Switching remote URLs from SSH to HTTPS {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual referente ao seu projeto local. -3. Liste seus remotes existentes para obter o nome do remote que deseja alterar. +2. Change the current working directory to your local project. +3. List your existing remotes in order to get the name of the remote you want to change. ```shell $ git remote -v > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) ``` -4. Altere a URL do remote de SSH para HTTPS com o comando `git remote set-url`. +4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command. ```shell $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git ``` -5. Verifique se o URL remote foi alterado. +5. Verify that the remote URL has changed. ```shell $ git remote -v # Verify new remote URL @@ -107,25 +106,25 @@ git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) ``` -Na próxima vez que você aplicar `git fetch`, `git pull` ou `git push` no repositório remote, precisará fornecer seu nome de usuário e a senha do GitHub. {% data reusables.user_settings.password-authentication-deprecation %} +The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %} -Você pode [usar um auxiliar de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git) para que o Git lembre seu nome de usuário e token de acesso pessoal toda vez que conversar com o GitHub. +You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and personal access token every time it talks to GitHub. -### Mudar as URLs remotas de HTTPS para SSH +### Switching remote URLs from HTTPS to SSH {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual referente ao seu projeto local. -3. Liste seus remotes existentes para obter o nome do remote que deseja alterar. +2. Change the current working directory to your local project. +3. List your existing remotes in order to get the name of the remote you want to change. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) ``` -4. Altere a URL do remote de HTTPS para SSH com o comando `git remote set-url`. +4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command. ```shell $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git ``` -5. Verifique se o URL remote foi alterado. +5. Verify that the remote URL has changed. ```shell $ git remote -v # Verify new remote URL @@ -133,105 +132,106 @@ Você pode [usar um auxiliar de credenciais](/github/getting-started-with-github > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) ``` -### Solução de problemas: Não há tal '[name]' remoto ' +### Troubleshooting: No such remote '[name]' -Este erro informa que o remote que você tentou alterar não existe: +This error means that the remote you tried to change doesn't exist: ```shell $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife > fatal: No such remote 'sofake' ``` -Verifique se você inseriu corretamente o nome do remote. +Check that you've correctly typed the remote name. -## Renomear um repositório remoto +## Renaming a remote repository -Use o comando `renomear o remoto do git` para renomear um remoto existente. +Use the `git remote rename` command to rename an existing remote. -O comando `git remote rename` tem dois argumentos: -* O nome de um remote existente, como `origin` -* Um novo nome para o remote, como `destination` +The `git remote rename` command takes two arguments: +* An existing remote name, for example, `origin` +* A new name for the remote, for example, `destination` -## Exemplo +## Example -Estes exemplos supõem que você está [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), que é o método recomendado. +These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. ```shell $ git remote -v -# Consulta os remotes existentes +# View existing remotes > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) $ git remote rename origin destination -# Altera o nome do remote de 'origin' para 'destination' +# Change remote name from 'origin' to 'destination' $ git remote -v -# Confirma o novo nome do remote +# Verify remote's new name > destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) > destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` -### Solução de problemas: Não foi possível renomear a seção de configuração 'remote.[old name]' para 'remote.[new name]' +### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]' This error means that the old remote name you typed doesn't exist. -Você pode consultar os remotes existentes no momento com o comando `git remote -v`: +You can check which remotes currently exist with the `git remote -v` command: ```shell $ git remote -v -# Consulta os remotes existentes +# View existing remotes > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` -### Solução de problemas: Já existe um [new name] remoto +### Troubleshooting: Remote [new name] already exists -Esse erro informa que o nome de remote que você deseja usar já existe. Para resolver isso, use um nome remoto diferente ou renomeie o remoto original. +This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote. -## Remover um repositório remoto +## Removing a remote repository -Use o comando `git remote rm` para remover uma URL remota do seu repositório. +Use the `git remote rm` command to remove a remote URL from your repository. -O comando `git remote rm` tem um argumento: -* O nome de um remote, como `destination` +The `git remote rm` command takes one argument: +* A remote name, for example, `destination` -## Exemplo +## Example -Estes exemplos supõem que você está [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), que é o método recomendado. +These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. ```shell $ git remote -v -# Ver remotes atuais +# View current remotes > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) > destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) > destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) $ git remote rm destination -# Remover remote +# Remove remote $ git remote -v -# Confirmar a remoção +# Verify it's gone > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) > origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` {% warning %} -**Observação**: o comando `git remote rm` não exclui o repositório do remote no servidor. Ele simplesmente remove o remote e suas referências do repositório local. +**Note**: `git remote rm` does not delete the remote repository from the server. It simply +removes the remote and its references from your local repository. {% endwarning %} -### Solução de problemas: Não foi possível remover a seção 'remote.[name]' +### Troubleshooting: Could not remove config section 'remote.[name]' -Esse erro informa que o remote que você tentou excluir não existe: +This error means that the remote you tried to delete doesn't exist: ```shell $ git remote rm sofake > error: Could not remove config section 'remote.sofake' ``` -Verifique se você inseriu corretamente o nome do remote. +Check that you've correctly typed the remote name. -## Leia mais +## Further reading -- "[Working with Remotes" (Trabalhar com remotes) no livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md index 72cf7efa88..d5330b1689 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md @@ -1,6 +1,6 @@ --- -title: Sobre o GitHub Advanced Security -intro: '{% data variables.product.prodname_dotcom %} disponibiliza funcionalidades extras de segurança para os clientes sob uma licença de {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} Esses recursos também estão habilitados para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license.{% ifversion fpt or ghec %} These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' product: '{% data reusables.gated-features.ghas %}' versions: fpt: '*' @@ -12,28 +12,27 @@ topics: redirect_from: - /github/getting-started-with-github/about-github-advanced-security - /github/getting-started-with-github/learning-about-github/about-github-advanced-security -shortTitle: Segurança Avançada GitHub +shortTitle: GitHub Advanced Security --- +## About {% data variables.product.prodname_GH_advanced_security %} -## Sobre o {% data variables.product.prodname_GH_advanced_security %} - -{% data variables.product.prodname_dotcom %} tem muitas funcionalidades que ajudam você a melhorar e manter a qualidade do seu código. Alguns deles são incluídos em todos os planos{% ifversion not ghae %}, como o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Outras funcionalidades de segurança exigem uma licença de {% data variables.product.prodname_GH_advanced_security %} para ser executada em repositórios, além dos repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans{% ifversion not ghae %}, such as dependency graph and {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% ifversion fpt or ghes > 3.0 or ghec %}For more information about purchasing {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% endif %} -## Sobre as funcionalidades de {% data variables.product.prodname_advanced_security %} +## About {% data variables.product.prodname_advanced_security %} features -Uma licença de {% data variables.product.prodname_GH_advanced_security %} fornece as funcionalidades adicionais a seguir: +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: -- **{% data variables.product.prodname_code_scanning_capc %}** - Pesquisa de possíveis vulnerabilidades de segurança e erros de codificação no seu código. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." -- **{% data variables.product.prodname_secret_scanning_caps %}** - Detectar segredos, por exemplo, chaves e tokens, que foram verificados no repositório. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)". +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)." {% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} -- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -Para obter informações sobre funcionalidades de {% data variables.product.prodname_advanced_security %} em desenvolvimento, consulte "[Plano de trabalho de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para uma visão geral de todas as funcionalidades de segurança, consulte "[ funcionalidades de segurança de{% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion ghes or ghec %} @@ -46,33 +45,33 @@ To review the rollout phases we recommended in more detail, see "[Deploying {% d {% endif %} {% ifversion ghes or ghae %} -## Habilitar funcionalidades de {% data variables.product.prodname_advanced_security %} em {% data variables.product.product_name %} +## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.product_name %} {% ifversion ghes %} -O administrador do site deve habilitar {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de poder utilizar essas funcionalidades. Para obter mais informações, consulte "[Configurar funcionalidades avançadas de segurança](/admin/configuration/configuring-advanced-security-features)". +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." {% endif %} -Após configurar o sistema, você poderá habilitar e desabilitar esses recursos no nível da organização ou repositório. Para mais informações, consulte "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +Once your system is set up, you can enable and disable these features at the organization or repository level. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." {% endif %} {% ifversion not ghae %} -## Habilitar funcionalidades de {% data variables.product.prodname_advanced_security %} em {% data variables.product.prodname_dotcom_the_website %} +## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} -Para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}, Essas funcionalidades estão permanentemente habilitadas e só podem ser desabilitadas se você alterar a visibilidade do projeto para que o código não seja mais público. +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -Para outros repositórios, uma vez que você tenha uma licença da conta corporativa, é possível habilitar e desabilitar essas funcionalidades no nível da organização ou repositório. {% ifversion fpt or ghes > 3.0 or ghec %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% ifversion fpt or ghes > 3.0 or ghec %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} {% endif %} {% ifversion fpt or ghec %} -Se você tem uma conta corporativa, a utilização da licença para toda a empresa é exibida na página de licença corporativa. Para obter mais informações, consulte "[Visualizar o uso do seu {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". +If you have an enterprise account, license use for the entire enterprise is shown on your enterprise license page. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." {% endif %} {% ifversion ghec or ghes > 3.0 or ghae-next %} -## Leia mais +## Further reading - "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)" diff --git a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md index 7e1e1efa9d..e12f41cae3 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md @@ -1,5 +1,5 @@ --- -title: Permissões de acesso no GitHub +title: Access permissions on GitHub redirect_from: - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do/ - /articles/what-are-the-different-types-of-team-permissions/ @@ -7,7 +7,7 @@ redirect_from: - /articles/access-permissions-on-github - /github/getting-started-with-github/access-permissions-on-github - /github/getting-started-with-github/learning-about-github/access-permissions-on-github -intro: 'Embora você possa conceder acesso de leitura/gravação a colaboradores em um repositório pessoal, os integrantes de uma organização podem ter permissões de acesso mais granulares para os repositórios da organização.' +intro: 'While you can grant read/write access to collaborators on a personal repository, members of an organization can have more granular access permissions for the organization''s repositories.' versions: fpt: '*' ghes: '*' @@ -16,33 +16,32 @@ versions: topics: - Permissions - Accounts -shortTitle: Permissões de acesso +shortTitle: Access permissions --- +## Personal user accounts -## Contas de usuário pessoais +A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)." -Um repositório pertencente a uma conta de usuário tem dois níveis de permissão: o *proprietário do repositório* e *colaboradores*. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository)". +## Organization accounts -## Contas da organização - -Os integrantes da organização podem ter funções de *proprietário*{% ifversion fpt or ghec %}, *gerente de cobrança*{% endif %} ou *integrante*. Os proprietários têm acesso administrativo completo à sua organização{% ifversion fpt or ghec %}, enquanto os gerentes de cobrança podem gerenciar configurações de cobrança{% endif %}. O integrante é a função padrão de todos os outros. Você pode gerenciar as permissões de acesso para vários integrantes por vez com equipes. Para obter mais informações, consulte: +Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see: - "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" -- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" -- "[Sobre equipes](/articles/about-teams)" +- "[About teams](/articles/about-teams)" {% ifversion fpt or ghec %} -## Contas corporativas +## Enterprise accounts -Os *proprietários de empresa* têm poder absoluto sobre a conta corporativa e podem realizar todas as ações nela. Os *gerentes de cobrança* podem gerenciar as configurações de cobrança da sua conta corporativa. Os integrantes e colaboradores externos das organizações pertencentes à sua conta corporativa são automaticamente integrantes da conta corporativa, embora eles não tenham acesso à conta corporativa em si nem às configurações dela. Para obter mais informações, consulte "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)". +*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." -Se uma empresa usar {% data variables.product.prodname_emus %}, serão fornecidos novos os integrantes como novas contas de usuário em {% data variables.product.prodname_dotcom %} e serão totalmente gerenciados pelo provedor de identidade. O {% data variables.product.prodname_managed_users %} tem acesso somente leitura a repositórios que não fazem parte da sua empresa e não podem interagir com usuários que não são também integrantes da empresa. Nas organizações pertencentes à empresa, é possível conceder ao {% data variables.product.prodname_managed_users %} os mesmos níveis de acesso granular disponíveis para organizações regulares. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %} +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %} {% data reusables.gated-features.enterprise-accounts %} {% endif %} -## Leia mais +## Further reading -- "[Tipos de conta do {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" +- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" diff --git a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md index 8a138b3efe..242358a9c1 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md @@ -1,6 +1,6 @@ --- -title: Tipos de contas do GitHub -intro: 'Sua conta de usuário é o que identifica você no {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}' +title: Types of GitHub accounts +intro: 'Your user account is your identity on {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}' redirect_from: - /manage-multiple-clients/ - /managing-clients/ @@ -21,26 +21,25 @@ topics: - Desktop - Security --- - {% ifversion fpt or ghec %} -Para uma lista completa de recursos para cada {% data variables.product.product_name %} produto, consulte produtos do "[{% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)." +For a full list of features for each {% data variables.product.product_name %} product, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)." {% endif %} -## Contas de usuário pessoais +## Personal user accounts -Cada pessoa que utiliza {% data variables.product.product_location %} tem sua própria conta de usuário, que inclui: +Every person who uses {% data variables.product.product_location %} has their own user account, which includes: {% ifversion fpt or ghec %} -- Repositórios públicos e privados ilimitados com o {% data variables.product.prodname_free_user %} -- Colaboradores ilimitados com {% data variables.product.prodname_free_user %} -- Recursos adicionais para repositórios privados com o {% data variables.product.prodname_pro %} -- Capacidade de [convidar colaboradores do repositório](/articles/inviting-collaborators-to-a-personal-repository) +- Unlimited public and private repositories with {% data variables.product.prodname_free_user %} +- Unlimited collaborators with {% data variables.product.prodname_free_user %} +- Additional features for private repositories with {% data variables.product.prodname_pro %} +- Ability to [invite repository collaborators](/articles/inviting-collaborators-to-a-personal-repository) {% else %} -- [Colaboradores](/articles/permission-levels-for-a-user-account-repository) e repositórios ilimitados -- Capacidade de [adicionar colaboradores do repositório ilimitados](/articles/inviting-collaborators-to-a-personal-repository) +- Unlimited repositories and [collaborators](/articles/permission-levels-for-a-user-account-repository) +- Ability to [add unlimited repository collaborators](/articles/inviting-collaborators-to-a-personal-repository) {% endif %} @@ -48,10 +47,10 @@ Cada pessoa que utiliza {% data variables.product.product_location %} tem sua pr {% tip %} -**Dicas**: +**Tips**: -- Você pode usar uma conta para várias finalidades, como uso pessoal e uso profissional. Não é recomendável criar mais de uma conta. Para obter mais informações, consulte "[Fazer merge de várias contas de usuário](/articles/merging-multiple-user-accounts)". -- Embora as contas de usuário sejam destinadas a seres humanos, você pode conceder uma a um robô, como um bot de integração contínua, se necessário. +- You can use one account for multiple purposes, such as for personal use and business use. We do not recommend creating more than one account. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)." +- User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary. {% endtip %} @@ -59,7 +58,7 @@ Cada pessoa que utiliza {% data variables.product.product_location %} tem sua pr {% tip %} -**Dica**: embora as contas de usuário sejam destinadas a seres humanos, você pode conceder uma a um robô, como um bot de integração contínua, se necessário. +**Tip**: User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary. {% endtip %} @@ -68,27 +67,27 @@ Cada pessoa que utiliza {% data variables.product.product_location %} tem sua pr {% ifversion fpt or ghec %} ### {% data variables.product.prodname_emus %} -Com {% data variables.product.prodname_emus %}, em vez de usar sua conta pessoal, os integrantes de um {% data variables.product.prodname_emu_enterprise %} são contas fornecidas que usam o provedor de identidade da empresa (IdP). {% data variables.product.prodname_managed_users_caps %} efetua a autenticação usando seu IdP ao invés de um usuário e senha de {% data variables.product.prodname_dotcom_the_website %}. +With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. -{% data variables.product.prodname_managed_users_caps %} só pode interagir com usuários, repositórios e organizações que fazem parte das suas empresas. {% data variables.product.prodname_managed_users_caps %} tem acesso somente leitura ao restante de {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} -## Contas da organização +## Organization accounts -As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. +Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. {% data reusables.organizations.organizations_include %} {% ifversion fpt or ghec %} -## Contas corporativas +## Enterprise accounts -Com contas corporativas, é possível gerenciar centralmente a política e a cobrança referentes a várias organizações do {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.enterprise-accounts %} +With enterprise accounts, you can centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. {% data reusables.gated-features.enterprise-accounts %} {% endif %} -## Leia mais +## Further reading {% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" -- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/githubs-products)"{% endif %} -- "[Criar uma conta de organização](/articles/creating-a-new-organization-account)" +- "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)"{% endif %} +- "[Creating a new organization account](/articles/creating-a-new-organization-account)" diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md index a9486a5561..34adcc9fcb 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md @@ -1,80 +1,80 @@ --- -title: Introdução ao GitHub AE -intro: 'Comece a configurar {% data variables.product.product_name %} para {% data variables.product.product_location %}.' +title: Getting started with GitHub AE +intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.product.product_location %}.' versions: ghae: '*' --- -Este guia irá ajudar você a configurar e gerenciar as configurações para {% data variables.product.product_location %} em {% data variables.product.product_name %} como proprietário corporativo. +This guide will walk you through setting up, configuring, and managing settings for {% data variables.product.product_location %} on {% data variables.product.product_name %} as an enterprise owner. -## Parte 1: Configurando {% data variables.product.product_name %} -Para dar os primeiros passos com {% data variables.product.product_name %}, você pode criar a conta corporativa, inicializar {% data variables.product.product_name %}, configurar uma lista de permissões de IP, configurar a autenticação e provisionamento de usuário e gerenciar a cobrança para {% data variables.product.product_location %}. +## Part 1: Setting up {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.product.product_location %}. -### 1. Criando sua conta corporativa de {% data variables.product.product_name %} -Primeiro você precisará comprar {% data variables.product.product_name %}. Para obter mais informações, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). +### 1. Creating your {% data variables.product.product_name %} enterprise account +You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). {% data reusables.github-ae.initialize-enterprise %} -### 2. Inicializando {% data variables.product.product_name %} -Depois de {% data variables.product.company_short %} criar a conta do proprietário para {% data variables.product.product_location %} em {% data variables.product.product_name %}, você receberá um e-mail para efetuar o login e e concluir a inicialização. Durante a inicialização, você, como o proprietário da empresa, irá nomear {% data variables.product.product_location %}, configurar o SAML SSO, criar políticas para todas as organizações em {% data variables.product.product_location %} e configurar um contato de suporte para os integrantes da empresa. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)". +### 2. Initializing {% data variables.product.product_name %} +After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)." -### 3. Restringir tráfego de rede -É possível configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)". +### 3. Restricting network traffic +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)." -### 4. Gerenciando a identidade e o acesso para {% data variables.product.product_location %} -Você pode gerenciar centralmente o acesso a {% data variables.product.product_location %} em {% data variables.product.product_name %} a partir de um provedor de identidade (IdP) usando o logon único SAML (SSO) para autenticação de usuário e o sistema para gerenciamento de identidade de domínio cruzado (SCIM) para provisionamento de usuários. Depois de configurar o provisionamento, você poderá atribuir ou remover usuários para o aplicativo a partir do IdP, criando ou desabilitando as contas de usuários na empresa. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +### 4. Managing identity and access for {% data variables.product.product_location %} +You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -### 5. Gerenciando cobrança para {% data variables.product.product_location %} -Os proprietários da assinatura de {% data variables.product.product_location %} em {% data variables.product.product_name %} podem ver informações de cobrança para {% data variables.product.product_name %} no portal do Azure. Para obter mais informações, consulte "[Gerenciando a cobrança da sua empresa](/admin/overview/managing-billing-for-your-enterprise)". +### 5. Managing billing for {% data variables.product.product_location %} +Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." -## Parte 2: Organização e gestão dos integrantes da empresa -Como proprietário corporativo de {% data variables.product.product_name %}, você pode gerenciar as configurações nos níveis do usuário, repositório, equipe e organização. Você pode gerenciar os integrantes de {% data variables.product.product_location %}, criar e gerenciar organizações, definir políticas para o gerenciamento do repositório e criar e gerenciar equipes. +## Part 2: Organizing and managing enterprise members +As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams. -### 1. Gerenciando integrantes de {% data variables.product.product_location %} +### 1. Managing members of {% data variables.product.product_location %} {% data reusables.getting-started.managing-enterprise-members %} -### 2. Criar organizações +### 2. Creating organizations {% data reusables.getting-started.creating-organizations %} -### 3. Adicionando integrantes a organizações +### 3. Adding members to organizations {% data reusables.getting-started.adding-members-to-organizations %} -### 4. Criar equipes +### 4. Creating teams {% data reusables.getting-started.creating-teams %} -### 5. Definindo níveis de permissões para a organização e para o repositório +### 5. Setting organization and repository permission levels {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Aplicando políticas de gerenciamento do repositório +### 6. Enforcing repository management policies {% data reusables.getting-started.enforcing-repo-management-policies %} -## Parte 3: Criando com segurança -Para aumentar a segurança de {% data variables.product.product_location %}, você pode monitorar {% data variables.product.product_location %} e configurar as funcionalidades de segurança e análise das suas organizações. +## Part 3: Building securely +To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations. -### 1. Monitorando {% data variables.product.product_location %} -Você pode monitorar {% data variables.product.product_location %} com o seu painel de atividade e log de auditoria. Para obter mais informações, consulte "[Atividade de monitoramento na sua empresa](/admin/user-management/monitoring-activity-in-your-enterprise)". +### 1. Monitoring {% data variables.product.product_location %} +You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)." -### 2. Configurar as funcionalidades de segurança para as suas organizações +### 2. Configuring security features for your organizations {% data reusables.getting-started.configuring-security-features %} -## Parte 4: Personalizando e automatizando o trabalho em {% data variables.product.product_location %} +## Part 4: Customizing and automating work on {% data variables.product.product_location %} You can customize and automate work in organizations in {% data variables.product.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}. ### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 2. Criando {% data variables.product.prodname_actions %} +### 2. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -Para obter mais informações sobre como habilitar e configurar {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)". +For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)." -### 3. Usar {% data variables.product.prodname_pages %} +### 3. Using {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Parte 5: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e os recursos de suporte -Os integrantes da sua empresa podem aprender mais sobre Git e {% data variables.product.prodname_dotcom %} com nossos recursos de aprendizado. e você pode obter o suporte de que precisa com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %}. +## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Aprendendo com {% data variables.product.prodname_learning %} +### 1. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Trabalhando com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %} +### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 0d9daa5071..336444f7a6 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -1,212 +1,212 @@ --- -title: Introdução ao GitHub Enterprise Cloud -intro: 'Comece a criar e gerenciar sua organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}.' +title: Getting started with GitHub Enterprise Cloud +intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.' versions: fpt: '*' ghec: '*' --- -Este guia irá ajudar você a configurar e gerenciar sua conta de {% data variables.product.prodname_ghe_cloud %} como uma organização ou proprietário da empresa. +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner. {% data reusables.enterprise.ghec-cta-button %} -## Parte 1: Escolhendo o seu tipo de conta +## Part 1: Choosing your account type -{% data variables.product.prodname_dotcom %} fornece dois tipos de produtos corporativos: +{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -A principal diferença entre os produtos é que {% data variables.product.prodname_ghe_cloud %} é hospedado por {% data variables.product.prodname_dotcom %}, enquanto {% data variables.product.prodname_ghe_server %} é auto-hospedado. +The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Com {% data variables.product.prodname_ghe_cloud %}, você tem a opção de usar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} -Se você optar por deixar seus integrantes criarem e gerenciarem suas próprias contas de usuário, há dois tipos de contas que você pode usar com {% data variables.product.prodname_ghe_cloud %}: +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: -- Uma conta de organização única -- Uma conta corporativa que contém várias organizações +- A single organization account +- An enterprise account that contains multiple organizations -### 1. Compreender as diferenças entre uma conta de organização e a conta corporativa +### 1. Understanding the differences between an organization account and enterprise account -As contas da organização e da empresa estão disponíveis com {% data variables.product.prodname_ghe_cloud %}. Uma organização é uma conta compartilhada em que grupos de pessoas podem colaborar em vários projetos de uma só vez, e os proprietários e administradores podem gerenciar o acesso a dados e projetos. Uma conta corporativa permite a colaboração entre várias organizações e permite que os proprietários gerenciem centralmente a política, cobrança e segurança dessas organizações. Para obter mais informações sobre as diferenças, consulte "[Organizações e contas corporativas](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)". +Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." -Se você escolher uma conta corporativa, tenha em mente que algumas políticas só podem ser definidas no nível organizacional, enquanto outras podem ser aplicadas a todas as organizações de uma empresa. +If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. -Depois de escolher o tipo de conta que você desejar, você poderá continuar a criar a sua conta. Em cada uma das seções deste guia, acesse a seção de organização única ou conta corporativa com base no seu tipo de conta. +Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. -## Parte 2: Configurando a sua conta -Para começar com {% data variables.product.prodname_ghe_cloud %}, você deverá criar sua conta organizativa ou corporativa e configurar e ver as configurações de cobrança, assinaturas e uso. -### Como criar uma conta de organização única com {% data variables.product.prodname_ghe_cloud %} +## Part 2: Setting up your account +To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage. +### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %} -#### 1. Sobre organizações -As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. Com o {% data variables.product.prodname_ghe_cloud %}, os proprietários e administradores podem gerenciar sua organização com autenticação e gestão de usuário sofisticada, bem como com opções de segurança e suporte escaladas. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". -#### 2. Criando ou atualizando a conta de uma organização +#### 1. About organizations +Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." +#### 2. Creating or upgrading an organization account -Para usar a conta de uma organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você precisará criar uma organização. Quando solicitado para escolher um plano, selecione "Enterprise". Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -Como alternativa, se você tiver a conta de uma organização existente que você gostaria de atualizar, siga as etapas em "[atualizando a sua assinatura de {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". -#### 3. Configuração e gerenciamento de cobrança +Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." +#### 3. Setting up and managing billing -Ao optar por usar uma conta de organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você terá acesso a um [](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)de teste de 14 dias. Se você não comprar {% data variables.product.prodname_enterprise %} ou {% data variables.product.prodname_team %} antes do seu período de teste terminar, a sua organização será rebaixada para {% data variables.product.prodname_free_user %} e você perderá acesso a quaisquer ferramentas avançadas e recursos que sejam incluídos apenas com produtos pagos. Para obter mais informações, consulte "[Concluindo o seu teste](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)". +When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." -A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento e ciclo de cobrança, exiba informações sobre sua assinatura e faça a atualização do seu armazenamento e minutos de {% data variables.product.prodname_actions %}. Para obter mais informações sobre como gerenciar suas configurações de cobrança, consulte "[Gerenciando suas configurações de cobrança de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". +Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." -Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -### Configurando uma conta corporativa com {% data variables.product.prodname_ghe_cloud %} +### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} {% note %} -Para obter uma conta corporativa criada para você, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). +To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). {% endnote %} -#### 1. Sobre contas corporativas +#### 1. About enterprise accounts -Uma conta corporativa permite que você gerencie centralmente as políticas e configurações para várias organizações {% data variables.product.prodname_dotcom %}, incluindo acesso de integrantes, cobrança e uso e segurança. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)". -#### 2. Adicionar organizações à suas conta corporativa +An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." +#### 2. Adding organizations to your enterprise account -É possível criar novas organizações para serem gerenciadas em sua conta corporativa. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". +You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -Entre em contato com o seu representante da conta de vendas de {% data variables.product.prodname_dotcom %} se você quiser transferir uma organização existente para a sua conta corporativa. -#### 3. Exibir assinatura e uso da conta corporativa -Você pode visualizar a sua assinatura atual, uso da licença, faturas, histórico de pagamentos e outras informações de cobrança para sua conta corporativa a qualquer momento. Os proprietários da empresa e os gerentes de cobrança podem acessar e gerenciar as configurações de cobrança para contas corporativas. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." +Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. +#### 3. Viewing the subscription and usage for your enterprise account +You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## Parte 3: Gerenciando seus integrantes e equipes da empresa com {% data variables.product.prodname_ghe_cloud %} +## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} -### Gerenciando integrantes e equipes na sua organização -Você pode definir permissões e funções dos integrantes, criar e gerenciar equipes e conceder acesso a repositórios na sua organização. -#### 1. Gerenciando integrantes da sua organização +### Managing members and teams in your organization +You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. +#### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -#### 2. Permissões e funções da organização +#### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -#### 3. Sobre e criar equipes +#### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -#### 4. Gerenciando as configurações de equipe +#### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -#### 5. Dar às pessoas e equipes acesso a repositórios, seções de projetos e aplicativos +#### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -### Gerenciando integrantes de uma conta corporativa -O gerenciamento dos integrantes de uma empresa é separado da gestão dos integrantes ou equipes em uma organização. É importante notar que os proprietários ou administradores da empresa não podem acessar as configurações a nível da organização ou gerenciar integrantes de organizações na sua empresa, a não ser que sejam proprietários de uma organização. Para obter mais informações, consulte a seção acima, "[Gerenciar integrantes e equipes da sua organização](#managing-members-and-teams-in-your-organization)". +### Managing members of an enterprise account +Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." -Se sua empresa usar {% data variables.product.prodname_emus %}, seus integrantes serão totalmente gerenciados por meio de seu provedor de identidade. As funções de adicionar integrantes, fazer alterações na sua associação e atribuir cargos são geranciadas usando seu IdP. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -Se a sua empresa não usar {% data variables.product.prodname_emus %}, siga as etapas abaixo. +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. -#### 1. Atribuindo funções em uma empresa -Por padrão, todas as pessoas em uma empresa são integrantes da empresa. Além disso, há funções administrativas, que incluem o proprietário da empresa e o gerente de cobrança, que têm diferentes níveis de acesso às configurações e dados da empresa. Para obter mais informações, consulte "[Funções em uma empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)". -#### 2. Convidar pessoas para gerenciar sua empresa -Você pode convidar pessoas para gerenciar a sua empresa como, por exemplo, proprietários corporativos ou gerentes de cobrança, bem como remover aqueles que não precisam mais de acesso. Para obter mais informações, consulte[Convidando pessoas para gerenciar a sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)". +#### 1. Assigning roles in an enterprise +By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." +#### 2. Inviting people to manage your enterprise +You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." -Você também pode conceder aos integrandes da empresa a capacidade de gerenciar tíquetes de suporte no portal de suporte. Para obter mais informações, consulte "[Gerenciar direitos de suporte para a sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". -#### 3. Visualizar pessoas na sua empresa -Para auditoria ao acesso a recursos pertencentes à empresa ou ao uso da licença de usuário, você pode ver todos os administradores corporativos, integrantes da empresa e colaboradores externos da sua empresa. Você pode ver as organizações às quais um integrante pertence e os repositórios específicos aos quais um colaborador externo tem acesso. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". +You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." +#### 3. Viewing people in your enterprise +To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)." -## Parte 4: Gerenciando a segurança com {% data variables.product.prodname_ghe_cloud %} +## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} -* [Gerenciando a segurança de uma única organização](#managing-security-for-a-single-organization) -* [Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) -* [Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) -### Gerenciando a segurança de uma única organização -Você pode ajudar a manter sua organização segura exigindo autenticação de dois fatores, configurando recursos de segurança, revisando o log de auditoria e as integrações da sua organização e habilitando a sincronização de equipe e logon único SAML. -#### 1. Exigindo a autenticação de dois fatores +### Managing security for a single organization +You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. +#### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -#### 2. Configurando recursos de segurança para a sua organização +#### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -#### 3. Revisando o log de auditoria e as integrações da sua organização +#### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -#### 4. Habilitando e aplicando o logon único SAML para a sua organização -Se você gerenciar seus aplicativos e as identidades dos integrantes da sua organização com um provedor de identidade (IdP), você poderá configurar logon único SAML (SSO) para controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. Quando os integrantes da sua organização acessam os recursos da organização que usam o SAML SSO, {% data variables.product.prodname_dotcom %} irá redirecioná-los para o seu dispositivo para autenticação. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". +#### 4. Enabling and enforcing SAML single sign-on for your organization +If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." -Os proprietários da organização podem optar por habilitar e desabilitar, mas não implementar, habilitar e aplicar o SAML SSO. Para obter mais informações, consulte "[Habilitando e testando o login único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" e "[Aplicando o login único SAML paraa sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." -#### 5. Gerenciar a sincronização de equipe para a sua organização -Os proprietários da organização podem habilitar a sincronização de equipes entre o seu provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que os proprietários da organização e mantenedores de equipes conectem equipes na sua organização aos grupos do IdP. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". +Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." +#### 5. Managing team synchronization for your organization +Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -### Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %} +### Managing security for an {% data variables.product.prodname_emu_enterprise %} -Com {% data variables.product.prodname_emus %}, o acesso e a identidade são gerenciados centralmente por meio do seu provedor de identidade. A autenticação de dois fatores e outros requisitos de login devem ser habilitados e aplicados no seu IdP. +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. -#### 1. Habilitando e o provisionamento de um logon único SAML no seu {% data variables.product.prodname_emu_enterprise %} +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} -Em um {% data variables.product.prodname_emu_enterprise %}, todos os integrantes são provisionados e gerenciados pelo seu provedor de identidade. Você deve habilitar o provisionamento SAML SSO e SCIM antes de começar a usar a sua empresa. Para mais informações sobre a configuração do SAML SSO e provisionamento para um {% data variables.product.prodname_emu_enterprise %}, consulte "[Configurando o logon único SAML para usuários gerenciados pela empresa](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." -#### 2. Gerenciando equipes no seu {% data variables.product.prodname_emu_enterprise %} com o seu provedor de identidade +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider -Você pode conectar as equipes das suas organizações a grupos de segurança do seu provedor de identidade, gerenciar integrantes das suas equipes e acesso aos repositórios por meio do seu IdP. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." -#### 3. Gerenciar endereços IP permitidos para organizações no seu {% data variables.product.prodname_emu_enterprise %} +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} -Você pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações no seu {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." -#### 4. Aplicando políticas de segurança avançada no seu {% data variables.product.prodname_emu_enterprise %} +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} {% data reusables.getting-started.enterprise-advanced-security %} -### Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %} -Para gerenciar a segurança da sua empresa, você pode exigir autenticação de dois fatores, gerenciar endereços IP permitidos, habilitar o logon único SAML e a sincronização de equipes no nível corporativo e inscrever-se aplicar as funcionalidades do GitHub Advanced Security. +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} +To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. -#### 1. Exigir autenticação de dois fatores e gerenciar endereços IP permitidos para organizações na conta corporativa -Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma conta corporativa usem autenticação de dois fatores para proteger suas contas pessoais. Antes de fazer isso, recomendamos que você notifique todas as pessoas que têm acesso a organizações da sua empresa. Você também pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. +#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account +Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)." -#### 2. Habilitar e aplicar o login único SAML para organizações na sua conta corporativa -Você pode gerenciar centralmente o acesso aos recursos da sua empresa, a associação à organização e a associação à equipe usando seu IdP e o logon único SAML (SSO). Os proprietários corporativos podem habilitar o SAML SSO em todas as organizações pertencentes a uma conta corporativa. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account +You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -#### 3. Gerenciando a sincronização de equipe -You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)". +#### 3. Managing team synchronization +You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." -#### 4. Aplicando políticas de segurança avançada na sua conta corporativa +#### 4. Enforcing policies for Advanced Security features in your enterprise account {% data reusables.getting-started.enterprise-advanced-security %} -## Parte 5: Gerenciar políticas e configurações da organização e do nível empresarial +## Part 5: Managing organization and enterprise level policies and settings -### Gerenciando configurações para uma única organização -Para gerenciar e moderar sua organização, você pode definir políticas da organização, gerenciar permissões para alterações de repositórios e usar arquivos de saúde da comunidade no nível da organização. -#### 1. Gerenciando as políticas da organização +### Managing settings for a single organization +To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files. +#### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -#### 2. Gerenciando alterações de repositório +#### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -#### 3. Usando arquivos de saúde da comunidade no nível da organização e as ferramentas de moderação +#### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -### Gerenciando as configurações para uma conta corporativa -Para gerenciar e moderar sua empresa, você pode definir políticas para organizações dentro da empresa, visualizar logs de auditoria, configurar webhooks e restringir notificações de e-mail. -#### 1. Gerenciar políticas para organizações na sua conta corporativa +### Managing settings for an enterprise account +To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications. +#### 1. Managing policies for organizations in your enterprise account -Você pode optar por aplicar várias políticas para todas as organizações pertencentes à sua empresa, ou escolher permitir que essas políticas sejam definidas em cada organização. Os tipos de políticas que você pode aplicar incluem gerenciamento de repositórios, quadro de projetos e políticas de equipe. Para obter mais informações, consulte "[Definindo políticas para a sua empresa](/enterprise-cloud@latest/admin/policies)". -#### 2. Visualizando logs de auditoria, configurando webhooks, e restringindo notificações de e-mail para a sua empresa -Você pode visualizar as ações de todas as organizações pertencentes à sua conta corporativa no log de auditoria da empresa. Você também pode configurar webhooks para receber eventos de organizações pertencentes à sua conta corporativa. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)." +You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)." +#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise +You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)." -Você também pode restringir as notificações de e-mail da conta corporativa para que os integrantes da empresa só possam usar um endereço de e-mail em um domínio verificado ou aprovado para receber notificações. Para obter mais informações, consulte "[Restringindo notificações de e-mail para a sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)". +You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." -## Parte 6: Personalizar e automatizar o trabalho da sua organização ou empresa em {% data variables.product.prodname_dotcom %} +## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %} Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. -### 1. Usar {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. Criando {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publicando e gerenciando {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -### 5. Usar {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. Você pode gerenciar a publicação de sites de {% data variables.product.prodname_pages %} no nível da organização. Para obter mais informações, consulte "[Gerenciando a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" e "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". -## Parte 7: Participando da comunidade de {% data variables.product.prodname_dotcom %} +### 5. Using {% data variables.product.prodname_pages %} +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." +## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community -Os integrantes da sua organização ou empresa podem usar os recursos de aprendizado e suporte do GitHub para obter a ajuda de que precisam. Você também pode apoiar a comunidade de código aberto. -### 1. Aprendendo com {% data variables.product.prodname_learning %} -Os integrantes da sua organização ou empresa podem aprender novas habilidades realizando projetos divertidos e realistas no seu repositório do GitHub com [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. +### 1. Learning with {% data variables.product.prodname_learning %} +Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. -Para obter mais informações, consulte "[Git e recursos de aprendizado de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources). " -### 2. Apoiar a comunidade de código aberto +For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." +### 2. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 3. Entrar em contato com o {% data variables.contact.github_support %} +### 3. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -{% data variables.product.prodname_ghe_cloud %} permite que você envie solicitações de suporte prioritárias com um tempo de resposta de oito horas. Para obter mais informações, consulte "[suporte do {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/github-enterprise-cloud-support)". +{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index 8fa77b6598..6022968de4 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -1,120 +1,120 @@ --- -title: Introdução ao GitHub Enterprise Server -intro: 'Comece a configurar e gerenciar {% data variables.product.product_location %}.' +title: Getting started with GitHub Enterprise Server +intro: 'Get started with setting up and managing {% data variables.product.product_location %}.' versions: ghes: '*' --- -Este guia irá ajudar você a configurar e gerenciar {% data variables.product.product_location %} como administrador da empresa. +This guide will walk you through setting up, configuring and managing {% data variables.product.product_location %} as an enterprise administrator. -{% data variables.product.company_short %} oferece duas maneiras de implantar {% data variables.product.prodname_enterprise %}. +{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -{% data variables.product.company_short %} hospeda {% data variables.product.prodname_ghe_cloud %}. Você pode implantar e hospedar {% data variables.product.prodname_ghe_server %} no seu próprio centro de dados ou em um provedor da nuvem compatível. +{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider. -Para obter uma visão geral de como {% data variables.product.product_name %} funciona, consulte "[Visão geral do sistema](/admin/overview/system-overview)". +For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)." -## Parte 1: Instalar {% data variables.product.product_name %} -Para começar com {% data variables.product.product_name %}, você deverá criar a conta corporativa, instalar a instância, usar o Console de Gerenciamento para configuração inicial, configurar a sua instância e gerenciar a cobrança. -### 1. Criando a sua conta corporativa -Antes de instalar {% data variables.product.product_name %}, você pode criar uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} entrando em contato com a [](https://enterprise.github.com/contact) equipe de vendas de {% data variables.product.prodname_dotcom %}. Uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} é útil para a cobrança e para recursos compartilhados com o {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". -### 2. Instalar o {% data variables.product.product_name %} -Para começar com {% data variables.product.product_name %}, você deverá instalar o dispositivo em uma plataforma de virtualização de sua escolha. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)". +## Part 1: Installing {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. +### 1. Creating your enterprise account +Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." +### 2. Installing {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)." -### 3. Usando o Console de Gerenciamento -Você usará o Console de Gerenciamento para apresentar o processo de configuração inicial ao iniciar {% data variables.product.product_location %}. Você também pode usar o Console de Gerenciamento para gerenciar configurações de instância, como licença, domínio, autenticação e TLS. Para obter mais informações, consulte "[Acessando o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". +### 3. Using the Management Console +You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." -### 4. Configurar o {% data variables.product.product_location %}; -Além do console de gerenciamento, você pode usar o painel de administração do site e o shell administrativo (SSH) para gerenciar {% data variables.product.product_location %}. Por exemplo, você pode configurar aplicativos e limites de taxa, ver relatórios, usar utilitários de linha de comando. Para obter mais informações, consulte "[Configurando sua empresa](/admin/configuration/configuring-your-enterprise)". +### 4. Configuring {% data variables.product.product_location %} +In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." -Você pode usar as configurações de rede padrão usadas por {% data variables.product.product_name %} por meio do protocolo de configuração do host dinâmico (DHCP) ou você também pode definir as configurações de rede usando o console de máquina virtual. Você também pode configurar um servidor proxy ou regras de firewall. Para obter mais informações, consulte "[Definindo as configurações de rede](/admin/configuration/configuring-network-settings)". +You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." -### 5. Configurar alta disponibilidade -Você pode configurar {% data variables.product.product_location %} para alta disponibilidade a fim de minimizar o impacto de falhas de hardware e falhas de rede. Para obter mais informações, consulte "[Configurando alta disponibilidade](/admin/enterprise-management/configuring-high-availability)". +### 5. Configuring high availability +You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)." -### 6. Configurar uma instância de preparo -Você pode configurar uma instância de preparo para testar modificações, planejar a recuperação de desastres e testar atualizações antes de aplicá-las a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". +### 6. Setting up a staging instance +You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." -### 7. Designando backups e recuperação de desastres -Para proteger seus dados de produção, você pode configurar backups automatizados de {% data variables.product.product_location %} com {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte "[Configurar backups no appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)". +### 7. Designating backups and disaster recovery +To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% 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)." -### 8. Gerenciar a cobrança para a sua empresa -A cobrança para todas as organizações e instâncias de {% data variables.product.product_name %} conectadas à sua conta corporativa é agregada em uma única taxa de cobrança para todos os seus serviços pagos de {% data variables.product.prodname_dotcom %}.com. Proprietários corporativos e gerentes de cobrança podem acessar e gerenciar as configurações de cobrança relativas a contas corporativas. Para obter mais informações, consulte "[Gerenciando a cobrança da sua empresa](/admin/overview/managing-billing-for-your-enterprise)". +### 8. Managing billing for your enterprise +Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." -## Parte 2: Organização e gerenciamento da sua equipe -Como proprietário corporativo ou administrador, você pode gerenciar configurações em níveis de usuário, repositório, equipe e organização. É possível gerenciar os integrantes da sua empresa, criar e gerenciar organizações, definir políticas para a gestão do repositório e criar e gerenciar as equipes. +## Part 2: Organizing and managing your team +As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams. -### 1. Gerenciando integrantes de {% data variables.product.product_location %} +### 1. Managing members of {% data variables.product.product_location %} {% data reusables.getting-started.managing-enterprise-members %} -### 2. Criar organizações +### 2. Creating organizations {% data reusables.getting-started.creating-organizations %} -### 3. Adicionando integrantes a organizações +### 3. Adding members to organizations {% data reusables.getting-started.adding-members-to-organizations %} -### 4. Criar equipes +### 4. Creating teams {% data reusables.getting-started.creating-teams %} -### 5. Definindo níveis de permissões para a organização e para o repositório +### 5. Setting organization and repository permission levels {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Aplicando políticas de gerenciamento do repositório +### 6. Enforcing repository management policies {% data reusables.getting-started.enforcing-repo-management-policies %} -## Parte 3: Criando com segurança -Para aumentar a segurança de {% data variables.product.product_location %}, você pode configurar a autenticação para integrantes da empresa, usar ferramentas e registro de auditoria para manter a conformidade, configurar recursos de segurança e análise para as suas organizações e, opcionalmente, habilitar {% data variables.product.prodname_GH_advanced_security %}. -### 1. Efetuando a autenticação dos integrantes da empresa -Você pode usar o método de autenticação interno do {% data variables.product.product_name %} ou você pode escolher entre um provedor de autenticação estabelecido como o CAS, LDAP, ou SAML, para integrar suas contas existentes e gerenciar centralmente o acesso do usuário a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Autenticando usuários para {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)". +## Part 3: Building securely +To increase the security of {% data variables.product.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}. +### 1. Authenticating enterprise members +You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an established authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." -Você também pode exigir autenticação de dois fatores para cada uma de suas organizações. Para obter mais informações, consulte "[Exigindo a autenticação de dois fatores para uma organização](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)". +You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)." -### 2. Manter a conformidade -Você pode implementar verificações de status necessárias e realizar verificações de commit para fazer cumprir os padrões de conformidade da sua organização e automatizar os fluxos de trabalho de conformidade. Você também pode usar o log de auditoria para sua organização revisar as ações executadas pela sua equipe. Para obter mais informações, consulte "[Aplicando a política com hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks)" e "[Log de auditoria](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)". +### 2. Staying in compliance +You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)." {% ifversion ghes %} -### 3. Configurar as funcionalidades de segurança para as suas organizações +### 3. Configuring security features for your organizations {% data reusables.getting-started.configuring-security-features %} {% endif %} {% ifversion ghes %} ### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features -Você pode atualizar sua licença do {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}. Isso fornece funcionalidades extras que ajudam os usuários a encontrar e corrigir problemas de segurança no seu código como, por exemplo, digitalização de código e segredo. Para obter mais informações, consulte "[{% data variables.product.prodname_GH_advanced_security %} para a sua empresa "](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)". +You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." {% endif %} -## Parte 4: Personalizando e automatizando o trabalho da sua empresa em {% data variables.product.prodname_dotcom %} +## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. -### 1. Criando {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} -You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. Para obter mais informações, consulte "[Sobre os aplicativos](/developers/apps/getting-started-with-apps/about-apps)". +### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} +You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)." ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} {% ifversion ghes %} -### 3. Criando {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -Para obter mais informações sobre como ativar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.product_name %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)". +For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -### 4. Publicando e gerenciando {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -Para obter mais informações sobre como habilitar e configurar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, consulte "[Primeiros passos com {% data variables.product.prodname_registry %} para a sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". +For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." {% endif %} -### 5. Usar {% data variables.product.prodname_pages %} +### 5. Using {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Parte 5: Conectando com outros recursos de {% data variables.product.prodname_dotcom %} -Você pode usar {% data variables.product.prodname_github_connect %} para compartilhar recursos. +## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources +You can use {% data variables.product.prodname_github_connect %} to share resources. -Se você for o proprietário de uma instância de {% data variables.product.product_name %} e uma organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}, você poderá habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} permite que você compartilhe fluxos de trabalho específicos e recursos entre {% data variables.product.product_location %} e {% data variables.product.prodname_ghe_cloud %}, como pesquisa unificada e contribuições. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". +If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." -## Parte 6: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e o suporte recursos -Os membros da sua empresa podem aprender mais sobre o Git e {% data variables.product.prodname_dotcom %} com os nossos recursos de aprendizagem. e você pode obter o suporte de que precisa ao configurar e gerenciar {% data variables.product.product_location %} com o suporte do enterprise de {% data variables.product.prodname_dotcom %}. -### 1. Aprendendo com {% data variables.product.prodname_learning %} +## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. +### 1. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Trabalhando com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %} +### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md index 528119988e..f98c11638d 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md @@ -1,96 +1,96 @@ --- -title: Introdução ao GitHub Team -intro: 'Com grupos de {% data variables.product.prodname_team %}, as pessoas podem colaborar em vários projetos ao mesmo tempo na conta de uma organização.' +title: Getting started with GitHub Team +intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.' versions: fpt: '*' --- -Este guia irá ajudar você a configurar e gerenciar sua conta {% data variables.product.prodname_team %} como proprietário da organização. +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner. ## Part 1: Configuring your account on {% data variables.product.product_location %} -Como os primeiros passos para começar com {% data variables.product.prodname_team %}, você deverá criar uma conta de usuário ou entrar na sua conta existente em {% data variables.product.prodname_dotcom %}, criar uma organização e configurar a cobrança. +As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing. -### 1. Sobre organizações -As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. Para obter mais informações sobre os recursos das organizações, consulte "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)". +### 1. About organizations +Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)." -### 2. Criando uma organização e inscrevendo-se em {% data variables.product.prodname_team %} -Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. Para obter mais informações, consulte "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)". +### 2. Creating an organization and signing up for {% data variables.product.prodname_team %} +Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)." -Uma vez que a sua conta de usuário está configurada, você derá criar uma organização e escolher um plano. Aqui é onde você pode escolher uma assinatura de {% data variables.product.prodname_team %} para a sua organização. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -### 3. Gerenciando a cobrança para uma organização -Você deve gerenciar as configurações de cobrança, método de pagamento e produtos pagos para cada uma das suas contas pessoais e organizações separadamente. Você pode alternar entre as configurações para a suas diferentes contas usando o alternador de contexto nas suas configurações. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)." +### 3. Managing billing for an organization +You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)." -A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento, ciclo de cobrança e e-mail de cobrança, ou visualize informações como a sua assinatura, data de faturamento e histórico de pagamento. Você também pode ver e fazer a atualização do seu armazenamento e dos minutos do GitHub Action. Para obter mais informações sobre como gerenciar suas configurações de cobrança, consulte "[Gerenciando suas configurações de cobrança de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". +Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." -Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -## Parte 2: Adicionar integrantes e criar equipes -Depois de criar a sua organização, você poderá convidar integrantes e definir permissões e funções. Você também pode criar diferentes níveis de equipes e definir níveis personalizados de permissões para repositórios da sua organização, quadros de projetos e aplicativos. +## Part 2: Adding members and setting up teams +After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps. -### 1. Gerenciando integrantes da sua organização +### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -### 2. Permissões e funções da organização +### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -### 3. Sobre e criar equipes +### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -### 4. Gerenciando as configurações de equipe +### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -### 5. Dar às pessoas e equipes acesso a repositórios, seções de projetos e aplicativos +### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -## Parte 3: Gerenciando a segurança da sua organização -Você pode ajudar a tornar sua organização mais segura ao recomendar ou exigir a autenticação de dois fatores para os integrantes da sua organização, configurando as funcionalidades de segurança e revisando o log de auditoria e integrações da sua organização. +## Part 3: Managing security for your organization +You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations. -### 1. Exigindo a autenticação de dois fatores +### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -### 2. Configurando recursos de segurança para a sua organização +### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -### 3. Revisando o log de auditoria e as integrações da sua organização +### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -## Parte 4: Definindo as políticas no nível da organização -### 1. Gerenciando as políticas da organização +## Part 4: Setting organization level policies +### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -### 2. Gerenciando alterações de repositório +### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -### 3. Usando arquivos de saúde da comunidade no nível da organização e as ferramentas de moderação +### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -## Parte 5: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %} +## Part 5: Customizing and automating your work on {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} -### 1. Usar {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. Criando {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publicando e gerenciando {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %} +## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community {% data reusables.getting-started.participating-in-community %} -### 1. Contribuindo para projetos de código aberto +### 1. Contributing to open source projects {% data reusables.getting-started.open-source-projects %} -### 2. Interagindo com o {% data variables.product.prodname_gcf %} +### 2. Interacting with the {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Aprendendo com {% data variables.product.prodname_learning %} +### 3. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} -### 4. Apoiar a comunidade de código aberto +### 4. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 5. Entrar em contato com o {% data variables.contact.github_support %} +### 5. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -## Leia mais +## Further reading -- "[Introdução à sua conta do GitHub](/get-started/onboarding/getting-started-with-your-github-account)" +- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)" diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md index 84b72a2afc..8c5c1036a1 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -1,6 +1,6 @@ --- -title: Introdução à sua conta do GitHub -intro: 'Com uma conta de usuário no {% data variables.product.prodname_dotcom %}, você pode importar ou criar repositórios, colaborar com outros e conectar-se com a comunidade de {% data variables.product.prodname_dotcom %}.' +title: Getting started with your GitHub account +intro: 'With a user account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.' versions: fpt: '*' ghes: '*' @@ -8,192 +8,192 @@ versions: ghec: '*' --- -Este guia irá ajudar você a configurar sua conta de {% data variables.product.company_short %} e dar os primeiros passos com as funcionalidades de {% data variables.product.product_name %} para colaboração e comunidade. +This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community. -## Parte 1: Configurando sua conta de {% data variables.product.prodname_dotcom %} +## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account {% ifversion fpt or ghec %} -Os primeiros passos para começar com {% data variables.product.product_name %} são criar uma conta, escolher um produto que se adeque melhor às suas necessidades, verificar o seu e-mail, configurar a autenticação de dois fatores e verificar o seu perfil. +The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile. {% elsif ghes %} -Os primeiros passos para começar com {% data variables.product.product_name %} são acessar sua conta, configurar a autenticação de dois fatores e ver seu perfil. +The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile. {% elsif ghae %} -Os primeiros passos para começar com {% data variables.product.product_name %} são acessar a sua conta e ver o seu perfil. +The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile. {% endif %} -{% ifversion fpt or ghec %}Existem vários tipos de contas em {% data variables.product.prodname_dotcom %}. {% endif %} Toda pessoa que usar {% data variables.product.product_name %} terá sua própria conta de usuário e poderá fazer parte de várias organizações e equipes. A sua conta de usuário é sua identidade em {% data variables.product.product_location %} e representa você como indivíduo. +{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual. {% ifversion fpt or ghec %} -### 1. Criar uma conta +### 1. Creating an account To sign up for an account on {% data variables.product.product_location %}, navigate to https://github.com/ and follow the prompts. -Para manter a sua conta de {% data variables.product.prodname_dotcom %} segura, você deverá usar uma senha forte e exclusiva. Para obter mais informações, consulte "[Criar uma senha forte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)". +To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)." -### 2. Escolhendo seu produto de {% data variables.product.prodname_dotcom %} -Você pode escolher {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %} para obter acesso a diferentes recursos da sua conta pessoal. Você pode fazer a atualização a qualquer momento se não tiver certeza qual o produto você deseja. +### 2. Choosing your {% data variables.product.prodname_dotcom %} product +You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want. -Para obter mais informações sobre todos os planos de {% data variables.product.prodname_dotcom %}, consulte "[Produtos de {% data variables.product.prodname_dotcom %}de](/get-started/learning-about-github/githubs-products)". +For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." -### 3. Verificar endereço de e-mail -Para garantir que você possa utilizar todos os recursos do seu plano de {% data variables.product.product_name %}, verifique o seu endereço de e-mail após inscrever-se em uma nova conta. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)". +### 3. Verifying your email address +To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)." {% endif %} {% ifversion ghes %} -### 1. Acessando a sua conta -O administrador da sua instância de {% data variables.product.product_name %} irá notificar você sobre como efetuar a autenticação e acessar a sua conta. O processo varia dependendo do modo de autenticação que eles configuraram para a instância. +### 1. Accessing your account +The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance. {% endif %} {% ifversion ghae %} -### 1. Acessando a sua conta -Você receberá uma notificação por e-mail assim que o proprietário corporativo de {% data variables.product.product_name %} tiver configurado a sua conta permitindo que você efetue a autenticação com o logon único SAML (SSO) e acesse sua conta. +### 1. Accessing your account +You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account. {% endif %} {% ifversion fpt or ghes or ghec %} -### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configurando a autenticação de dois fatores -A autenticação de dois fatores, ou 2FA, é uma camada extra de segurança usada no logon em sites ou apps. É altamente recomendável que você configure a 2FA para a segurança da sua conta. Para obter mais informações, consulte "[Sobre a autenticação de dois fatores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)". +### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication +Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)." {% endif %} -### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Visualizando seu {% data variables.product.prodname_dotcom %} perfil e gráfico de contribuição -Seu perfil de {% data variables.product.prodname_dotcom %} conta a história do seu trabalho por meio dos repositórios e dos gists que você fixou, as associações da organização que você escolheu divulgar, as contribuições que você fez e os projetos que você criou. Para obter mais informações, consulte "[Sobre o seu perfil](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" e "[Visualizando as contribuições no seu perfil](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)". +### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph +Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)." -## Parte 2: Usando ferramentas e processos de {% data variables.product.product_name %} -Para usar {% data variables.product.product_name %} da melhor forma, você deverá configurar o Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador. Para colaborar de forma efetiva em {% data variables.product.product_name %}, você escreverá em problemas e pull requests usando o Markdown enriquecido de {% data variables.product.prodname_dotcom %}. +## Part 2: Using {% data variables.product.product_name %}'s tools and processes +To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown. -### 1. Aprendendo a usar o Git -A abordagem colaborativa do {% data variables.product.prodname_dotcom %} para o desenvolvimento depende da publicação dos commits do repositório local para {% data variables.product.product_name %} para que outras pessoas vejam, busquem e atualizem outras pessoas que usam o Git. Para obter mais informações sobre o Git, consulte o guia "[Manual do Git](https://guides.github.com/introduction/git-handbook/)". Para obter mais informações sobre como Git é usado em {% data variables.product.product_name %}, consulte "[Fuxo de {% data variables.product.prodname_dotcom %}](/get-started/quickstart/github-flow)". -### 2. Configurar o Git -Se você planeja usar o Git localmente no seu computador, por meio da linha de comando, editor de IDE ou texto, você deverá instalar e configurar o Git. Para obter mais informações, consulte "[Configurar o Git](/get-started/quickstart/set-up-git)". +### 1. Learning Git +{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)." +### 2. Setting up Git +If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)." -Se você preferir usar uma interface visual, você poderá fazer o download e usar {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} vem empacotado com o Git. Portanto não há a necessidade de instalar o Git separadamente. Para obter mais informações, consulte "[Introdução ao {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". +If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." -Depois de instalar o Git, você poderá conectar-se aos repositórios de {% data variables.product.product_name %} a partir do seu computador local, independentemente de ser o seu próprio repositório ou a bifurcação de outro usuário. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. Para obter mais informações, consulte "[Sobre repositórios remotos](/get-started/getting-started-with-git/about-remote-repositories)." +Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)." -### 3. Escolhendo como interagir com {% data variables.product.product_name %} -Todos têm seu próprio fluxo de trabalho único para interagir com {% data variables.product.prodname_dotcom %}; as interfaces e métodos que você usa dependem da sua preferência e do que funciona melhor para as suas necessidades. +### 3. Choosing how to interact with {% data variables.product.product_name %} +Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs. -Para obter mais informações sobre como efetuar a autenticação em {% data variables.product.product_name %} com cada um desses métodos, consulte "[Sobre autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)". +For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)." -| **Método** | **Descrição** | **Casos de uso** | -| ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Acesse {% data variables.product.prodname_dotcom_the_website %} | Se você não precisar trabalhar com arquivos localmente, {% data variables.product.product_name %} permite que você realize a maioria das ações relacionadas ao Gits diretamente no navegador, da criação e bifurcação de repositórios até a edição de arquivos e abertura de pull requests. | Esse método é útil se você quiser uma interface visual e precisar fazer mudanças rápidas e simples que não requerem trabalho local. | -| {% data variables.product.prodname_desktop %} | O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Para obter mais informações sobre como começar com {% data variables.product.prodname_desktop %}, consulte "[Primeiros passos com o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". | Este método é melhor se você precisa ou deseja trabalhar com arquivos localmente, mas preferir usar uma interface visual para usar o Git e interagir com {% data variables.product.product_name %}. | -| Editor de IDE ou de texto | Você pode definir um editor de texto padrão, curtir [Atom](https://atom.io/) ou [Visual Studio Code](https://code.visualstudio.com/) para abrir e editar seus arquivos com o Git, usar extensões e ver a estrutura do projeto. Para obter mais informações, consulte "[Associando editores de texto ao Git](/github/using-git/associating-text-editors-with-git)". | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor. | -| Linha de comando, com ou sem {% data variables.product.prodname_cli %} | Para o controle e personalização mais granulares de como você usa o Git e interage com {% data variables.product.product_name %}, você pode usar a linha de comando. Para obter mais informações sobre como usar comandos do Git, consulte "[Folha de informações do Git](/github/getting-started-with-github/quickstart/git-cheatsheet).

    {% data variables.product.prodname_cli %} é uma ferramenta separada de linha de comando separada que você pode instalar e que traz pull requests, problemas, {% data variables.product.prodname_actions %}, e outros recursos de {% data variables.product.prodname_dotcom %} para o seu terminal, para que você possa fazer todo o seu trabalho em um só lugar. Para obter mais informações, consulte "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Isto é muito conveniente se você já estiver trabalhando na linha de comando, o que permite que você evite mudar o contexto, ou se você estiver mais confortável usando a linha de comando. | -| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} tem uma API REST e uma API do GraphQL que você pode usar para interagir com {% data variables.product.product_name %}. Para obter mais informações, consulte "[Primeiros passos com a API](/github/extending-github/getting-started-with-the-api)". | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | -### 4. Escrevendo em {% data variables.product.product_name %} -Para deixar sua comunicação clara e organizada nos problemas e pull requests, você pode usar o Markdown enriquecido {% data variables.product.prodname_dotcom %} para formatação, que combina uma sintaxe fácil de ler e fácil de escrever com algumas funcionalidades personalizadas. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)". +| **Method** | **Description** | **Use cases** | +| ------------- | ------------- | ------------- | +| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. | +| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. | +| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | +| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."

    {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. | +| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | +### 4. Writing on {% data variables.product.product_name %} +To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." -Você pode aprender o Markdown enriquecido de {% data variables.product.prodname_dotcom %} com o curso "[Comunicando-se usando o Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" em {% data variables.product.prodname_learning %}. +You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}. -### 5. Pesquisando em {% data variables.product.product_name %} -Nossa pesquisa integrada permite que você encontre o que você está procurando entre os muitos repositórios, usuários e linhas de código em {% data variables.product.product_name %}. Você pode pesquisar globalmente em todos os {% data variables.product.product_name %} ou limitar sua pesquisa a um repositório ou organização em particular. Para obter mais informações sobre os tipos de pesquisas que você pode fazer em {% data variables.product.product_name %}, consulte "[Sobre pesquisar no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)". +### 5. Searching on {% data variables.product.product_name %} +Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." -Nossa sintaxe de pesquisa permite que você construa consultas usando qualificadores para especificar o que você deseja pesquisar. Para obter mais informações sobre a sintaxe de pesquisa para usar na pesquisa, consulte "[Pesquisando em {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)". +Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)." -### 6. Gerenciando arquivos em {% data variables.product.product_name %} -Com {% data variables.product.product_name %}, você pode criar, editar, mover e excluir arquivos no seu repositório ou em qualquer repositório ao qual você tenha acesso de gravação. Você também pode acompanhar o histórico de alterações de um arquvo linha por linha. Para obter mais informações, consulte "[Gerenciar arquivos em {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)". +### 6. Managing files on {% data variables.product.product_name %} +With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)." -## Parte 3: Colaborando em {% data variables.product.product_name %} -Qualquer quantidade de pessoas pode trabalhar juntas nos repositórios de {% data variables.product.product_name %}. É possível configurar configurações, criar quadros de projetos e gerenciar suas notificações para incentivar uma colaboração eficaz. +## Part 3: Collaborating on {% data variables.product.product_name %} +Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration. -### 1. Trabalhando com repositórios +### 1. Working with repositories -#### Criar um repositório -Um repositório é como uma pasta para seu projeto. Você pode ter qualquer número de repositórios públicos e privados na sua conta de usuário. Os repositórios podem conter pastas e arquivos, imagens, vídeos, planilhas e conjuntos de dados, bem como o histórico de revisão para todos os arquivos no repositório. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/about-repositories)". +#### Creating a repository +A repository is like a folder for your project. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)." -Ao criar um novo repositório, você deverá inicializar o repositório com um arquivo README para que as pessoas conheçam o seu projeto. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." +When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." -#### Clonar um repositório -Você pode clonar um repositório existente a partir de {% data variables.product.product_name %} para o seu computador local, facilitando a adição ou remoção dos arquivos, correção de conflitos de merge ou realização de commits complexos. Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.prodname_dotcom %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Para obter mais informações, consulte "[Clonar um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)". +#### Cloning a repository +You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)." -#### Bifurcar um repositório -Uma bifurcação é uma cópia de um repositório que você gerencia, em que todas as alterações que você fizer não afetarão o repositório original a menos que você envie um pull request para o proprietário do projeto. O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-pull-requests/working-with-forks)". -### 2. Importar seus projetos -Se você tiver projetos existentes que deseja mover para {% data variables.product.product_name %}, você poderá importar projetos usando o Importador de {% data variables.product.prodname_dotcom %}, a linha de comando ou as ferramentas externas de migração. Para obter mais informações, consulte "[Importando código-fonte para {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)". +#### Forking a repository +A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)." +### 2. Importing your projects +If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)." -### 3. Gerenciando colaboradores e permissões -Você pode colaborar em seu projeto com outras pessoas usando os problemas, as pull requests e os quadros de projeto do repositório. Você pode convidar outras pessoas para o seu repositório como colaboradores na aba **Colaboradores** nas configurações do repositório. Para obter mais informações, consulte "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)". +### 3. Managing collaborators and permissions +You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)." -Você é o proprietário de qualquer repositório que você cria na sua conta de usuário e você tem controle total sobre repositório. Os colaboradores têm acesso de gravação ao seu repositório, limitando o que eles têm permissão para fazer. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)". +You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)." -### 4. Gerenciar configurações do repositório -Como proprietário de um repositório, você pode configurar diversas configurações, incluindo a visibilidade do repositório, tópicos e a pré-visualização das mídias sociais. Para obter mais informações, consulte "[Gerenciar configurações do repositório](/github/administering-a-repository/managing-repository-settings)". +### 4. Managing repository settings +As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)." -### 5. Configurar projeto para contribuições úteis +### 5. Setting up your project for healthy contributions {% ifversion fpt or ghec %} -Para incentivar os colaboradores do seu repositório, você precisa de uma comunidade que incentive as pessoas a usar, contribuir e evangelizar o seu projeto. Para obter mais informações, consulte "[Criando comunidades de bem-estar](https://opensource.guide/building-community/)" nos guias de código aberto. +To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides. -Ao adicionar arquivos como diretrizes de contribuição, um código de conduta e uma licença para o repositório é possível criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições úteis e significativas. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)." +By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} {% ifversion ghes or ghae %} -Ao adicionar arquivos como diretrizes de contribuição, um código de conduta, e recursos de suporte ao seu repositório, você pode criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições significativas e úteis. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)." +By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} -### 6. Usando os problemas e os quadros de projeto do GitHub -Você pode usar os problemas do GitHub para organizar seu trabalho com problemas e pull requests, bem como gerenciar seu fluxo de trabalho com quadros de projetos. Para obter mais informações, consulte "[Sobre os problemas](/issues/tracking-your-work-with-issues/about-issues)" e "[Sobre os quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)". +### 6. Using GitHub Issues and project boards +You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." -### 7. Gerenciando notificações -As notificações fornecem atualizações sobre a atividade em {% data variables.product.prodname_dotcom %} que você assinou ou da qual você participou. Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". +### 7. Managing notifications +Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." -### 8. Trabalhar com o {% data variables.product.prodname_pages %} -You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +### 8. Working with {% data variables.product.prodname_pages %} +You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." {% ifversion fpt or ghec %} -### 9. Usar {% data variables.product.prodname_discussions %} -Você pode habilitar {% data variables.product.prodname_discussions %} para o repositório ajudar a criar uma comunidade em torno do seu projeto. Mantenedores, colaboradores e visitantes podem usar discussões para compartilhar anúncios, fazer e responder a perguntas e participar de conversas sobre objetivos. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +### 9. Using {% data variables.product.prodname_discussions %} +You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." {% endif %} -## Parte 4: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %} +## Part 4: Customizing and automating your work on {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} {% ifversion fpt or ghec %} -### 1. Usar {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} {% endif %} ### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Criando {% data variables.product.prodname_actions %} +### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publicando e gerenciando {% data variables.product.prodname_registry %} +### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## Parte 5: Criando com segurança em {% data variables.product.product_name %} -{% data variables.product.product_name %} tem uma variedade de recursos de segurança que ajudam a manter códigos e segredos seguros nos repositórios. Algumas funcionalidades estão disponíveis para todos os repositórios, enquanto outras estão disponíveis apenas para repositórios públicos e repositórios com uma licença de {% data variables.product.prodname_GH_advanced_security %}. Para uma visão geral das funcionalidades de segurança de {% data variables.product.product_name %}, consulte "[Funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". +## Part 5: Building securely on {% data variables.product.product_name %} +{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." -### 1. Proteger o repositório -Como administrador do repositório, você pode proteger os seus repositórios definindo as configurações de segurança do repositório. Elas incluem o gerenciamento de acesso ao seu repositório, a definição de uma política de segurança e o gerenciamento de dependências. Para repositórios públicos e para repositórios privados pertencentes a organizações em que o {% data variables.product.prodname_GH_advanced_security %} está habilitado, você também pode configurar o código e a digitalização de segredos para identificar automaticamente vulnerabilidades e garantir que os tokens e chaves não sejam expostos. +### 1. Securing your repository +As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. -Para obter mais informações sobre as medidas que você pode tomar para proteger seus repositórios, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)". +For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." {% ifversion fpt or ghec %} -### 2. Gerenciando suas dependências -Uma grande parte da criação é manter as dependências do seu projeto para garantir que todos os pacotes e aplicativos dos quais você depende estejam atualizados e seguros. Você pode gerenciar as dependências do seu repositório em {% data variables.product.product_name %}, explorando o gráfico de dependências para o seu repositório, usando o Dependabot para aumentar automaticamente os pull requests para manter as suas dependências atualizadas e receber alertas de dependência e atualizações de segurança para dependências vulneráveis. +### 2. Managing your dependencies +A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. -Para obter mais informações, consulte "[Protegendo a cadeia de suprimentos do seu software](/code-security/supply-chain-security)". +For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)." {% endif %} -## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %} +## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community {% data reusables.getting-started.participating-in-community %} -### 1. Contribuindo para projetos de código aberto +### 1. Contributing to open source projects {% data reusables.getting-started.open-source-projects %} -### 2. Interagindo com {% data variables.product.prodname_gcf %} +### 2. Interacting with {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Aprendendo com {% data variables.product.prodname_learning %} +### 3. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} {% ifversion fpt or ghec %} -### 4. Apoiar a comunidade de código aberto +### 4. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 5. Entrar em contato com o {% data variables.contact.github_support %} +### 5. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} {% ifversion fpt %} -## Leia mais -- "[Começar com {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)" +## Further reading +- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)" {% endif %} {% endif %} diff --git a/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md b/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md index 7ad12ceed3..41c80b642e 100644 --- a/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md +++ b/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md @@ -1,5 +1,5 @@ --- -title: Contribuir para projetos +title: Contributing to projects intro: Learn how to contribute to a project through forking. permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: @@ -18,14 +18,15 @@ topics: After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking. -Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. Para obter mais informações, consulte "[Bifurcar um repositório](/get-started/quickstart/fork-a-repo)". +Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)." -## Bifurcar um repositório +## Forking a repository This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom_the_website %} that lets you test the fork and pull request workflow. 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife. -2. Click **Fork**. ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.jpg) +2. Click **Fork**. + ![Fork button](/assets/images/help/repository/fork_button.jpg) 1. {% data variables.product.product_name %} will take you to your copy (your fork) of the Spoon-Knife repository. ## Cloning a fork @@ -37,21 +38,21 @@ You can clone your fork with the command line, {% data variables.product.prodnam {% include tool-switcher %} {% webui %} -1. Em {% data variables.product.product_name %}, vá até **your fork** (sua bifurcação) no repositório Spoon-Knife. +1. On {% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository. {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} -4. Digite `git clone` (clonar git) e cole a URL que você copiou anteriormente. Ficará assim, com seu {% data variables.product.product_name %} nome de usuário no lugar de `YOUR-USERNAME`: +4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`: ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife ``` -5. Pressione **Enter**. Seu clone local estará criado. +5. Press **Enter**. Your local clone will be created. ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife - > Clonando para `Spoon-Knife`... - > remote: Contando objetos: 10, concluído. - > remote: Compactando objetos: 100% (8/8), concluído. + > Cloning into `Spoon-Knife`... + > remote: Counting objects: 10, done. + > remote: Compressing objects: 100% (8/8), done. > remove: Total 10 (delta 1), reused 10 (delta 1) > Unpacking objects: 100% (10/10), done. ``` @@ -62,7 +63,7 @@ You can clone your fork with the command line, {% data variables.product.prodnam {% data reusables.cli.cli-learn-more %} -Para criar um clone da sua *bifurcação*, use o sinalizador `--clone`. +To create a clone of your fork, use the `--clone` flag. ```shell gh repo fork repository --clone=true @@ -144,7 +145,7 @@ At last, you're ready to propose changes into the main project! This is the fina To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://www.github.com//Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**. -{% data variables.product.product_name %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Clique em **Create pull request** (Criar pull request). +{% data variables.product.product_name %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**. {% data variables.product.product_name %} will bring you to a page where you can enter a title and a description of your changes. It's important to provide as much useful information and a rationale for why you're making this pull request in the first place. The project owner needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request**. @@ -154,4 +155,5 @@ Pull Requests are an area for discussion. In this case, the Octocat is very busy ## Finding projects -You've successfully forked and contributed back to a repository. Go forth, and contribute some more!{% ifversion fpt %} For more information, see "[Finding ways to contribute to open source on GitHub](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %} +You've successfully forked and contributed back to a repository. Go forth, and +contribute some more!{% ifversion fpt %} For more information, see "[Finding ways to contribute to open source on GitHub](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %} diff --git a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md index e98f1fe620..56c2e95fd0 100644 --- a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md @@ -1,11 +1,11 @@ --- -title: Criar um repositório +title: Create a repo redirect_from: - /create-a-repo/ - /articles/create-a-repo - /github/getting-started-with-github/create-a-repo - /github/getting-started-with-github/quickstart/create-a-repo -intro: 'Para colocar seu projeto no {% data variables.product.prodname_dotcom %}, você precisará criar um repositório no qual ele residirá.' +intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you''ll need to create a repository for it to live in.' versions: fpt: '*' ghes: '*' @@ -17,16 +17,15 @@ topics: - Notifications - Accounts --- - -## Criar um repositório +## Create a repository {% ifversion fpt or ghec %} -Você pode armazenar vários projetos nos repositórios do {% data variables.product.prodname_dotcom %}, incluindo projetos de código aberto. Com os [projetos de código aberto](http://opensource.org/about), é possível compartilhar código para criar softwares melhores e mais confiáveis. Você pode usar repositórios para colaborar com outras pessoas e acompanhar seu trabalho. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)". +You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)." {% elsif ghes or ghae %} -Você pode armazenar uma série de projetos em repositórios de {% data variables.product.product_name %}, incluindo projetos de innersource. Com o innersource, você pode compartilhar código para criar um software melhor e mais confiável. Para obter mais informações sobre innersource, consulte o white paper de {% data variables.product.company_short %}"[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)". +You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% endif %} @@ -34,7 +33,7 @@ Você pode armazenar uma série de projetos em repositórios de {% data variable {% note %} -**Observação:** você pode criar repositórios públicos para um projeto de código aberto. Ao criar um repositório público, certifique-se de incluir um [arquivo de licença](https://choosealicense.com/) que determina como deseja que seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} +**Note:** You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} {% endnote %} @@ -45,13 +44,15 @@ Você pode armazenar uma série de projetos em repositórios de {% data variable {% webui %} {% data reusables.repositories.create_new %} -2. Digite um nome curto e fácil de memorizar para seu repositório. Por exemplo, "olá mundo". ![Campo para inserir um nome de repositório](/assets/images/help/repository/create-repository-name.png) -3. Se desejar, adicione uma descrição do repositório. Por exemplo, "Meu primeiro repositório no {% data variables.product.product_name %}". ![Campo para inserir uma descrição do repositório](/assets/images/help/repository/create-repository-desc.png) +2. Type a short, memorable name for your repository. For example, "hello-world". + ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png) +3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}." + ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png) {% data reusables.repositories.choose-repo-visibility %} {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -Parabéns! Você criou com êxito seu primeiro repositório e o inicializou com um arquivo *README*. +Congratulations! You've successfully created your first repository, and initialized it with a *README* file. {% endwebui %} @@ -59,34 +60,33 @@ Parabéns! Você criou com êxito seu primeiro repositório e o inicializou com {% data reusables.cli.cli-learn-more %} -1. Na linha de comando, acesse o diretório onde você gostaria de criar um clone local do seu novo projeto. -2. Para criar um repositório para o seu projeto, use o subcomando `gh repo create`. Substitua `project-name` pelo nome desejado para o repositório. Se você quiser que o seu projeto pertença a uma organização em vez de sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`. - - ```shell - gh repo create project-name - ``` - -3. Siga as instruções interativas. Para clonar o repositório localmente, marque sim quando perguntarem se você deseja clonar o diretório do projeto remoto. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_repo_create). +1. In the command line, navigate to the directory where you would like to create a local clone of your new project. +2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. +3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory. +4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create). {% endcli %} -## Fazer commit da primeira alteração +## Commit your first change {% include tool-switcher %} {% webui %} -Um *[commit](/articles/github-glossary#commit)* é como um instantâneo de todos os arquivos no seu projeto em um determinado momento. +A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time. -Na criação do repositório, você o inicializou com um arquivo *README*. Os arquivos *README* são um excelente local para descrever seu projeto mais detalhadamente ou para adicionar alguma documentação, por exemplo, como instalar ou usar seu projeto. O conteúdo do arquivo *README* é mostrado automaticamente na primeira página do repositório. +When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. -Vamos fazer commit de uma alteração no arquivo *README*. +Let's commit a change to the *README* file. -1. Na lista de arquivos do repositório, clique em ***README.m***. ![Arquivo README na lista de arquivos](/assets/images/help/repository/create-commit-open-readme.png) -2. Acima do conteúdo do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %}. -3. Na guia **Edit file** (Editar arquivo), digite algumas informações sobre si mesmo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png) +1. In your repository's list of files, click ***README.md***. + ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png) +2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}. +3. On the **Edit file** tab, type some information about yourself. + ![New content in file](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} -5. Revise as alterações feitas no arquivo. Você verá o novo conteúdo em verde. ![Visualização de arquivo](/assets/images/help/repository/create-commit-review.png) +5. Review the changes you made to the file. You'll see the new content in green. + ![File preview view](/assets/images/help/repository/create-commit-review.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} @@ -95,18 +95,18 @@ Vamos fazer commit de uma alteração no arquivo *README*. {% cli %} -Agora que você criou um projeto, você pode começar a fazer commit das alterações. +Now that you have created a project, you can start committing changes. -Os arquivos *README* são um excelente local para descrever seu projeto mais detalhadamente ou para adicionar alguma documentação, por exemplo, como instalar ou usar seu projeto. O conteúdo do arquivo *README* é mostrado automaticamente na primeira página do repositório. Siga estas etapas para adicionar um arquivo *README*. +*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file. -1. Na linha de comando, acesse o diretório raiz do seu novo projeto. (Este diretório foi criado quando você executou o repositório `gh repo create`.) -1. Crie um arquivo *README* com algumas informações sobre o projeto. +1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.) +1. Create a *README* file with some information about the project. ```shell echo "info about this project" >> README.md ``` -1. Insira `git status`. Você verá que você tem um arquivo `README.md` não rastreado. +1. Enter `git status`. You will see that you have an untracked `README.md` file. ```shell $ git status @@ -118,13 +118,13 @@ Os arquivos *README* são um excelente local para descrever seu projeto mais det nothing added to commit but untracked files present (use "git add" to track) ``` -1. Stage e commit do arquivo. +1. Stage and commit the file. ```shell git add README.md && git commit -m "Add README" ``` -1. Faça push das alterações para seu branch. +1. Push the changes to your branch. ```shell git push --set-upstream origin HEAD @@ -132,18 +132,18 @@ Os arquivos *README* são um excelente local para descrever seu projeto mais det {% endcli %} -## Comemore +## Celebrate -Parabéns! Você criou um repositório, incluindo um arquivo *README*, assim como seu primeiro commit no {% data variables.product.product_location %}. +Congratulations! You have now created a repository, including a *README* file, and created your first commit on {% data variables.product.product_location %}. {% webui %} -Agora você pode clonar um repositório de {% data variables.product.prodname_dotcom %} para criar uma cópia local no seu computador. A partir do seu repositório local, você pode fazer commit e criar um pull request para atualizar as alterações no repositório upstream. Para obter mais informações, consulte "[Clonando um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" e "[Configurar o Git](/articles/set-up-git)". +You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)." {% endwebui %} -Você pode encontrar projetos e repositórios interessantes em {% data variables.product.prodname_dotcom %} e fazer alterações neles criando uma bifurcação no repositório. Para obter mais informações, "[Bifurcar um repositório](/articles/fork-a-repo)". +You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. For more information see, "[Fork a repository](/articles/fork-a-repo)." -Cada repositório em {% data variables.product.prodname_dotcom %} pertence a uma pessoa ou organização. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Seja social](/articles/be-social)". +Each repository in {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.prodname_dotcom %}. For more information see "[Be social](/articles/be-social)." {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md index bcd659b57b..f40be52431 100644 --- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md @@ -1,12 +1,12 @@ --- -title: Bifurcar um repo +title: Fork a repo redirect_from: - /fork-a-repo/ - /forking/ - /articles/fork-a-repo - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo -intro: Uma bifurcação é uma cópia de um repositório. Bifurcar um repositório permite que você faça experiências à vontade sem comprometer o projeto original. +intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' @@ -19,46 +19,46 @@ topics: - Notifications - Accounts --- +## About forks -## Sobre bifurcações +Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." -O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". +### Propose changes to someone else's project -### Proponha mudanças no projeto de outra pessoa +For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you've found, you can: -Por exemplo, você pode usar bifurcações para propor alterações relacionadas à correção de um bug. Em vez de registrar um erro encontrado, é possível: +- Fork the repository. +- Make the fix. +- Submit a pull request to the project owner. -- Bifurcar o repositório. -- Fazer a correção. -- Enviar um pull request ao proprietário do projeto. +### Use someone else's project as a starting point for your own idea. -### Use o projeto de outra pessoa como ponto de partida para sua própria ideia. +Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](http://opensource.org/about)" on the Open Source Initiative. -O software de código aberto baseia-se na ideia de que ao compartilhar códigos, podemos criar softwares melhores e mais confiáveis. Para obter mais informações, consulte "[Sobre a Iniciativa Open Source](http://opensource.org/about)" em Iniciativa Open Source. - -Para obter mais informações sobre a aplicação dos princípios de código aberto ao trabalho de desenvolvimento da sua organização em {% data variables.product.product_location %}, consulte o white paper de {% data variables.product.prodname_dotcom %} "[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% ifversion fpt or ghes or ghec %} -Ao criar um repositório público a partir de uma bifurcação do projeto de outra pessoa, confirme que incluiu um arquivo de licença que estabelece como você quer que seu projeto seja compartilhado com outros. Para obter mais informações, consulte [Escolha uma licença de código aberto](https://choosealicense.com/)" em choosealicense.com. +When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} {% endif %} -## Pré-requisitos +## Prerequisites -Se ainda não o fez, primeiro [configure o Git](/articles/set-up-git). Lembre-se também de [configurar a autenticação para {% data variables.product.product_location %} a partir do Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). +If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.product.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well. -## Bifurcar um repositório +## Forking a repository {% include tool-switcher %} {% webui %} -Você pode bifurcar um projeto para propor alterações no repositório upstream ou original. Nesse caso, uma boa prática é sincronizar regularmente sua bifurcação com o repositório upstream. Para isso, é necessário usar Git na linha de comando. Pratique configurando o repositório upstream com o mesmo repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) que você acabou de bifurcar. +You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked. 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. -2. No canto superior direito da página, clique em **Fork** (Bifurcação). ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.jpg) +2. In the top-right corner of the page, click **Fork**. +![Fork button](/assets/images/help/repository/fork_button.jpg) {% endwebui %} @@ -66,13 +66,13 @@ Você pode bifurcar um projeto para propor alterações no repositório upstream {% data reusables.cli.cli-learn-more %} -Para criar a bifurcação de um repositório, use o subcomando `gh repo fork`. +To create a fork of a repository, use the `gh repo fork` subcommand. ```shell gh repo fork repository ``` -Para criar a bifurcação em uma organização, use o sinalizador `--org`. +To create the fork in an organization, use the `--org` flag. ```shell gh repo fork repository --org "octo-org" @@ -83,9 +83,9 @@ gh repo fork repository --org "octo-org" {% desktop %} {% enddesktop %} -## Clonando o seu repositório bifurcado +## Cloning your forked repository -Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não tem os arquivos nesse repositório localmente no seu computador. +Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer. {% include tool-switcher %} {% webui %} @@ -94,17 +94,17 @@ Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não te {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} -4. Digite `git clone` (clonar git) e cole a URL que você copiou anteriormente. Ficará assim, com seu {% data variables.product.product_name %} nome de usuário no lugar de `YOUR-USERNAME`: +4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`: ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife ``` -5. Pressione **Enter**. Seu clone local estará criado. +5. Press **Enter**. Your local clone will be created. ```shell $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife - > Clonando para `Spoon-Knife`... - > remote: Contando objetos: 10, concluído. - > remote: Compactando objetos: 100% (8/8), concluído. + > Cloning into `Spoon-Knife`... + > remote: Counting objects: 10, done. + > remote: Compressing objects: 100% (8/8), done. > remove: Total 10 (delta 1), reused 10 (delta 1) > Unpacking objects: 100% (10/10), done. ``` @@ -115,7 +115,7 @@ Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não te {% data reusables.cli.cli-learn-more %} -Para criar um clone da sua *bifurcação*, use o sinalizador `--clone`. +To create a clone of your fork, use the `--clone` flag. ```shell gh repo fork repository --clone=true @@ -133,9 +133,9 @@ gh repo fork repository --clone=true {% enddesktop %} -## Configurar o Git para sincronizar a bifurcação com o repositório original +## Configuring Git to sync your fork with the original repository -Ao bifurcar um projeto para propor mudanças no repositório original, é possível configurar o Git para fazer pull de mudanças do repositório original ou upstream no clone local de sua bifurcação. +When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork. {% include tool-switcher %} {% webui %} @@ -143,24 +143,24 @@ Ao bifurcar um projeto para propor mudanças no repositório original, é possí 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} -4. Mude os diretórios para a localidade da bifurcação que você clonou. - - Para acessar seu diretório pessoal, apenas digite `cd` sem nenhum outro texto. - - Para listar os arquivos e pastas em seu diretório atual, digite `ls`. - - Para acessar um dos diretórios listados, digite `cd your_listed_directory`. - - Para acessar um diretório, digite `cd ..`. -5. Digite `git remote -v` e pressione **Enter**. Você verá o repositório remote atual configurado para sua bifurcação. +4. Change directories to the location of the fork you cloned. + - To go to your home directory, type just `cd` with no other text. + - To list the files and folders in your current directory, type `ls`. + - To go into one of your listed directories, type `cd your_listed_directory`. + - To go up one directory, type `cd ..`. +5. Type `git remote -v` and press **Enter**. You'll see the current configured remote repository for your fork. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) ``` -6. Digite `git remote add upstream`, cole a URL que você copiou na etapa 2 e pressione **Enter**. Ficará assim: +6. Type `git remote add upstream`, and then paste the URL you copied in Step 2 and press **Enter**. It will look like this: ```shell $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git ``` -7. Para verificar o novo repositório upstream que você especificou para sua bifurcação, digite novamente `git remote -v`. Você deverá visualizar a URL da sua bifurcação como `origin` (origem) e a URL do repositório original como `upstream`. +7. To verify the new upstream repository you've specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) @@ -169,7 +169,7 @@ Ao bifurcar um projeto para propor mudanças no repositório original, é possí > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) ``` -Agora é possível manter a bifurcação sincronizada com o repositório upstream usando apenas alguns comandos Git. Para obter mais informações, consulte "[Sincronizar uma bifurcação](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)". +Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)." {% endwebui %} @@ -177,13 +177,13 @@ Agora é possível manter a bifurcação sincronizada com o repositório upstrea {% data reusables.cli.cli-learn-more %} -Para configurar um repositório remoto para o repositório bifurcado, use o sinalizador `--remote`. +To configure a remote repository for the forked repository, use the `--remote` flag. ```shell gh repo fork repository --remote=true ``` -Para especificar o nome do repositório remoto, use o sinalizador `--remote-name`. +To specify the remote repository's name, use the `--remote-name` flag. ```shell gh repo fork repository --remote-name "main-remote-repo" @@ -191,26 +191,26 @@ gh repo fork repository --remote-name "main-remote-repo" {% endcli %} -### Próximas etapas +### Next steps -Você pode fazer alterações em uma bifurcação, incluindo: +You can make any changes to a fork, including: -- **Criar branches: ** os [* branches*](/articles/creating-and-deleting-branches-within-your-repository/) permitem desenvolver novos recursos ou testar novas ideias sem colocar o projeto atual em risco. -- **Abrir pull requests:** caso queira fazer contribuições no repositório original, ao enviar uma [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests), você pode solicitar que o autor do repositório original faça pull de sua bifurcação no repositório dele. +- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk. +- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -## Localize outro repositório para bifurcar -Bifurque um repositório para começar a contribuir com um projeto. {% data reusables.repositories.you-can-fork %} +## Find another repository to fork +Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %} -{% ifversion fpt or ghec %}Você pode navegar em [Explore](https://github.com/explore) (Explorar) para encontrar projetos e começar a contribuir com repositórios de código aberto. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." +{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." {% endif %} -## Comemore +## Celebrate -Você já bifurcou um repositório, treinou clonar sua bifurcação e configurou um repositório upstream. Para obter mais informações sobre a clonagem da bifurcação e sincronizar as alterações em um repositório bifurcado a partir do seu computador"[Configurar o Git](/articles/set-up-git)". +You have now forked a repository, practiced cloning your fork, and configured an upstream repository. For more information about cloning the fork and syncing the changes in a forked repository from your computer see "[Set up Git](/articles/set-up-git)." -Você também pode criar um novo repositório onde você pode colocar todos os seus projetos e compartilhar o código em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Criar um repositório](/articles/create-a-repo)". +You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. For more information see, "[Create a repository](/articles/create-a-repo)." -Cada repositório em {% data variables.product.product_name %} pertence a uma pessoa ou organização. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Seja social](/articles/be-social)". +Each repository in {% data variables.product.product_name %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)." {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md index 3b46eb3645..5ce711cfb5 100644 --- a/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md +++ b/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md @@ -1,12 +1,12 @@ --- -title: Recursos de aprendizagem Git e GitHub +title: Git and GitHub learning resources redirect_from: - /articles/good-resources-for-learning-git-and-github/ - /articles/what-are-other-good-resources-for-learning-git-and-github/ - /articles/git-and-github-learning-resources - /github/getting-started-with-github/git-and-github-learning-resources - /github/getting-started-with-github/quickstart/git-and-github-learning-resources -intro: 'Existem muitos recursos Git e {% data variables.product.product_name %} na Web. Essa é uma lista de nossos preferidos!' +intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!' versions: fpt: '*' ghes: '*' @@ -14,51 +14,50 @@ versions: ghec: '*' authors: - GitHub -shortTitle: Recursos de aprendizagem +shortTitle: Learning resources --- +## Using Git -## Usar o Git +Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator. -Familiarize-se com o Git acessando o [site oficial do projeto Git](https://git-scm.com) e lendo o [livro do ProGit](http://git-scm.com/book). Você pode revisar a [lista de comandos Git](https://git-scm.com/docs) ou a [referência de consultas de comandos Git](http://gitref.org) e usar o simulador [Try Git](https://try.github.com) (Experimentar o Git). - -## Usar {% data variables.product.product_name %} +## Using {% data variables.product.product_name %} {% ifversion fpt or ghec %} -O {% data variables.product.prodname_learning %} oferece cursos interativos grátis que são desenvolvidos em {% data variables.product.prodname_dotcom %} e possuem ajuda e respostas automáticas e instantâneas. Aprenda a abrir sua primeira pull request, fazer sua primeira contribuição a um código aberto, criar um site {% data variables.product.prodname_pages %} e muito mais. Para obter mais informações sobre a oferta de cursos, consulte [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). +{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). {% endif %} -Conheça melhor o {% data variables.product.product_name %} por meio dos nossos [artigos](/categories/getting-started-with-github/). Consulte nosso fluxo [{% data variables.product.prodname_dotcom %} ](https://guides.github.com/introduction/flow) para uma introdução ao processo. Examine as [orientações gerais](https://guides.github.com) para conhecer os conceitos básicos. +Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts. {% data reusables.support.ask-and-answer-forum %} -### Branches, bifurcações e pull requests +### Branches, forks, and pull requests -Saiba como [criar branches no Git ](http://learngitbranching.js.org/) com uma ferramenta interativa. Leia sobre [bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) e [pull requests](/articles/using-pull-requests) e também sobre [como usamos pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) em {% data variables.product.prodname_dotcom %}. Acesse as referências sobre como usar {% data variables.product.prodname_dotcom %} na [linha de comando](https://cli.github.com/). +Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). -### Fique antenado +### Tune in -Nosso {% data variables.product.prodname_dotcom %} [canal do YouTube de Treinamentos e Orientações](https://youtube.com/githubguides) oferece tutoriais sobre as funções [pull request](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [bifurcar](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22) e [redefinir](https://www.youtube.com/watch?v=BKPjPMVB81g). Cada tema é abordado em cinco minutos ou menos. +Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less. -## Treinamentos +## Training -### Cursos grátis +### Free courses -{% data variables.product.product_name %} oferece uma série de treinamentos interativos, [sob demanda](https://lab.github.com/), incluindo [Introdução a {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); cursos sobre linguagens de programação e ferramentas, como HTML, Python e NodeJS; e cursos sobre ferramentas específicas de {% data variables.product.product_name %}, como {% data variables.product.prodname_actions %}. +{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://lab.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); courses on programming languages and tools such as HTML, Python, and NodeJS; and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}. -### Programas educacionais online do {% data variables.product.prodname_dotcom %} +### {% data variables.product.prodname_dotcom %}'s web-based educational programs -O {% data variables.product.prodname_dotcom %} disponibiliza [treinamentos](https://services.github.com/#upcoming-events) ao vivo com abordagens práticas e baseadas em projetos para aqueles que adoram linhas de comando e também para aqueles que as odeiam. +{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't. -### Treinamentos para sua empresa +### Training for your company -O {% data variables.product.prodname_dotcom %} oferece [aulas presenciais](https://services.github.com/#offerings) com nossos instrutores altamente qualificados. [Entre em contato](https://services.github.com/#contact) para tirar suas dúvidas sobre os treinamentos. +{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions. ## Extras -An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Fique à vontade para adaptar nossos [modelos .gitignore](https://github.com/github/gitignore) de acordo com as suas necessidades. +An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs. -Amplie seu alcance {% data variables.product.prodname_dotcom %} com {% ifversion fpt or ghec %}[integrações](/articles/about-integrations){% else %}integrações{% endif %} ou instalando [{% data variables.product.prodname_desktop %}](https://desktop.github.com) o robusto editor de texto [Atom](https://atom.io). +Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [Atom](https://atom.io) text editor. -Saiba como iniciar e desenvolver seu projeto de código aberto em [Open Source Guides](https://opensource.guide/) (Guias de Código aberto). +Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/). diff --git a/translations/pt-BR/content/get-started/quickstart/hello-world.md b/translations/pt-BR/content/get-started/quickstart/hello-world.md index 9f17e13f4a..51d7eefd55 100644 --- a/translations/pt-BR/content/get-started/quickstart/hello-world.md +++ b/translations/pt-BR/content/get-started/quickstart/hello-world.md @@ -13,7 +13,7 @@ topics: miniTocMaxHeadingLevel: 3 --- -## Introdução +## Introduction {% data variables.product.product_name %} is a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere. @@ -28,7 +28,7 @@ In this quickstart guide, you will: To complete this tutorial, you need a [{% data variables.product.product_name %} account](http://github.com) and Internet access. You don't need to know how to code, use the command line, or install Git (the version control software that {% data variables.product.product_name %} is built on). -## Criar um repositório +## Creating a repository A repository is usually used to organize a single project. Repositories can contain folders and files, images, videos, spreadsheets, and data sets -- anything your project needs. Often, repositories include a `README` file, a file with information about your project. {% data variables.product.product_name %} makes it easy to add one at the same time you create your new repository. It also offers other common options such as a license file. @@ -38,11 +38,11 @@ Your `hello-world` repository can be a place where you store ideas, resources, o 1. In the **Repository name** box, enter `hello-world`. 2. In the **Description** box, write a short description. 3. Select **Add a README file**. -4. Clique em **Create Repository** (Criar repositório). +4. Click **Create repository**. ![Create a hello world repository](/assets/images/help/repository/hello-world-repo.png) -## Criar um branch +## Creating a branch Branching lets you have different versions of a repository at one time. @@ -68,10 +68,11 @@ Branches accomplish similar goals in {% data variables.product.product_name %} r Here at {% data variables.product.product_name %}, our developers, writers, and designers use branches for keeping bug fixes and feature work separate from our `main` (production) branch. When a change is ready, they merge their branch into `main`. -### Criar uma branch +### Create a branch 1. Click the **Code** tab of your `hello-world` repository. -2. Click the drop down at the top of the file list that says **main**. ![Branch menu](/assets/images/help/branch/branch-selection-dropdown.png) +2. Click the drop down at the top of the file list that says **main**. + ![Branch menu](/assets/images/help/branch/branch-selection-dropdown.png) 4. Type a branch name, `readme-edits`, into the text box. 5. Click **Create branch: readme-edits from main**. @@ -89,13 +90,13 @@ You can make and save changes to the files in your repository. On {% data variab 1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file. 3. In the editor, write a bit about yourself. 4. In the **Commit changes** box, write a commit message that describes your changes. -5. Clique em **Commit changes** (Fazer commit das alterações). +5. Click **Commit changes**. ![Commit example](/assets/images/help/repository/first-commit.png) These changes will be made only to the README file on your `readme-edits` branch, so now this branch contains content that's different from `main`. -## Abrir um pull request +## Opening a pull request Now that you have changes in a branch off of `main`, you can open a pull request. @@ -114,9 +115,9 @@ You can even open pull requests in your own repository and merge them yourself. ![diff example](/assets/images/help/repository/diffs.png) -5. Clique em **Create pull request** (Criar pull request). +5. Click **Create pull request**. 6. Give your pull request a title and write a brief description of your changes. You can include emojis and drag and drop images and gifs. -7. Clique em **Create pull request** (Criar pull request). +7. Click **Create pull request**. Your collaborators can now review your edits and make suggestions. @@ -125,10 +126,10 @@ Your collaborators can now review your edits and make suggestions. In this final step, you will merge your `readme-edits` branch into the `main` branch. 1. Click **Merge pull request** to merge the changes into `main`. -2. Clique em **Confirmar a merge**. +2. Click **Confirm merge**. 3. Go ahead and delete the branch, since its changes have been incorporated, by clicking **Delete branch**. -## Próximas etapas +## Next steps By completing this tutorial, you've learned to create a project and make a pull request on {% data variables.product.product_name %}. diff --git a/translations/pt-BR/content/get-started/quickstart/set-up-git.md b/translations/pt-BR/content/get-started/quickstart/set-up-git.md index 895a3ecc41..836d69cabc 100644 --- a/translations/pt-BR/content/get-started/quickstart/set-up-git.md +++ b/translations/pt-BR/content/get-started/quickstart/set-up-git.md @@ -1,5 +1,5 @@ --- -title: Configurar o Git +title: Set up Git redirect_from: - /git-installation-redirect/ - /linux-git-installation/ @@ -12,7 +12,7 @@ redirect_from: - /articles/set-up-git - /github/getting-started-with-github/set-up-git - /github/getting-started-with-github/quickstart/set-up-git -intro: 'No centro do {% data variables.product.prodname_dotcom %} há um sistema de controle de versões (VCS) de código aberto chamado Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador.' +intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.' versions: fpt: '*' ghes: '*' @@ -24,50 +24,49 @@ topics: - Notifications - Accounts --- +## Using Git -## Usar o Git +To use Git on the command line, you'll need to download, install, and configure Git on your computer. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.prodname_dotcom %} a partir da linha de comando. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +If you want to work with Git locally, but don't want to use the command line, you can instead download and install the [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) client. For more information, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)." -Se quiser trabalhar com o Git, mas não quiser usar a linha de comando, você poderá baixar e instalar o cliente do [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obter mais informações, consulte "[Instalar e configurar o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". +If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including: -Se não precisar trabalhar nos arquivos localmente, o {% data variables.product.product_name %} permite a execução de diversas ações relacionadas ao Git diretamente no navegador, incluindo: +- [Creating a repository](/articles/create-a-repo) +- [Forking a repository](/articles/fork-a-repo) +- [Managing files](/repositories/working-with-files/managing-files) +- [Being social](/articles/be-social) -- [Criar um repositório](/articles/create-a-repo) -- [Bifurcar um repositório](/articles/fork-a-repo) -- [Gerenciar arquivos](/repositories/working-with-files/managing-files) -- [Interagir socialmente](/articles/be-social) +## Setting up Git -## Configurar o Git +1. [Download and install the latest version of Git](https://git-scm.com/downloads). +2. [Set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). +3. [Set your commit email address in Git](/articles/setting-your-commit-email-address). -1. [Faça download e instale a versão mais recente do Git](https://git-scm.com/downloads). -2. [Configure seu nome de usuário no Git](/github/getting-started-with-github/setting-your-username-in-git). -3. [Configure seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address). +## Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git -## Próximas etapas: autenticar no {% data variables.product.prodname_dotcom %} do Git - -Quando você se conecta a um repositório do {% data variables.product.prodname_dotcom %} a partir do Git, precisa fazer a autenticação no {% data variables.product.product_name %} usando HTTPS ou SSH. +When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. {% note %} -**Observação:** Você pode efetuar a autenticação em {% data variables.product.product_name %} usando {% data variables.product.prodname_cli %}, para HTTP ou SSH. Para obter mais informações, consulte [`login gh auth`](https://cli.github.com/manual/gh_auth_login). +**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). {% endnote %} -### Conexão por HTTPS (recomendada) +### Connecting over HTTPS (recommended) -Se você [clonar com HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), [armazene suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) usando um auxiliar de credenciais. +If you [clone with HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), you can [cache your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) using a credential helper. -### Conexão por SSH +### Connecting over SSH -Se você [clonar com SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), poderá [gerar chaves SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) em cada computador usado para fazer push ou pull a partir do {% data variables.product.product_name %}. +If you [clone with SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), you must [generate SSH keys](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on each computer you use to push or pull from {% data variables.product.product_name %}. -## Comemore +## Celebrate -Parabéns! Agora o Git e o {% data variables.product.prodname_dotcom %} estão configurados! Agora você pode optar por criar um repositório onde possa colocar seus projetos. Esta é uma ótima maneira de fazer backup do seu código e facilita o compartilhamento do código no mundo todo. Para obter mais informações, consulte "[Criar um repositório](/articles/create-a-repo)". +Congratulations, you now have Git and {% data variables.product.prodname_dotcom %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)". -Você pode criar a cópia de um repositório, fazendo uma bifurcação dele e propondo as alterações que deseja ver sem afetar o repositório upstream. Para obter mais informações, consulte "[Bifurcar um repositório](/articles/fork-a-repo)". +You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "[Fork a repository](/articles/fork-a-repo)." -Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Seja social](/articles/be-social)". +Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)." {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md deleted file mode 100644 index 133c599c73..0000000000 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Configurar uma versão de avaliação do GitHub Enterprise Cloud -intro: 'Você pode avaliar o {% data variables.product.prodname_ghe_cloud %} gratuitamente.' -redirect_from: - - /articles/setting-up-a-trial-of-github-enterprise-cloud - - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud - - /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud -versions: - fpt: '*' - ghec: '*' - ghes: '*' -topics: - - Accounts -shortTitle: Desafio da nuvem corporativa ---- - -{% data reusables.enterprise.ghec-cta-button %} - - -## Sobre o {% data variables.product.prodname_ghe_cloud %} - -{% data reusables.organizations.about-organizations %} - -Você pode usar organizações gratuitamente com {% data variables.product.prodname_free_team %}, que inclui recursos limitados. Para funcionalidades adicionais, como o logon único SAML (SSO), controle de acesso para {% data variables.product.prodname_pages %} e minutos de {% data variables.product.prodname_actions %} incluídos, você pode fazer a atualização para {% data variables.product.prodname_ghe_cloud %}. Para obter uma lista detalhada dos recursos disponíveis com {% data variables.product.prodname_ghe_cloud %}, consulte nossa página de [Preços](https://github.com/pricing). - -{% data reusables.saml.saml-accounts %} Para obter mais informações, consulte "Sobre identidade e gerenciamento de acesso com o logon único SAML". - -{% data reusables.products.which-product-to-use %} - -## Sobre as versões de avaliação do {% data variables.product.prodname_ghe_cloud %} - -Você pode definir uma avaliação de 14 dias para avaliar {% data variables.product.prodname_ghe_cloud %}. Não há necessidade de fornecer um método de pagamento durante a avaliação, a menos que você adicione à sua organização aplicativos do {% data variables.product.prodname_marketplace %} que exijam um método de pagamento. Para obter mais informações, consulte "Sobre a cobrança do {% data variables.product.prodname_marketplace %}". - -Sua versão de avaliação inclui 50 estações. Se precisar de mais estações para avaliar o {% data variables.product.prodname_ghe_cloud %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Ao final da avaliação, você poderá escolher um número diferente de estações. - -As versões de avaliação também estão disponíveis para o {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)". - -## Configurar a versão de avaliação do {% data variables.product.prodname_ghe_cloud %} - -Antes de testar {% data variables.product.prodname_ghe_cloud %}, você deverá estar conectado a uma conta de usuário. Se você ainda não tem uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}, você deverá criar uma. Para obter mais informações, consulte "Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}". - -1. Acesse [{% data variables.product.prodname_dotcom %} para as empresas](https://github.com/enterprise). -1. Clique em **Iniciar teste grátis**. ![Botão "Iniciar teste grátisl"](/assets/images/help/organizations/start-a-free-trial-button.png) -1. Clique em **Nuvem Corporativa**. ![Botão "Nuvem Corporativa"](/assets/images/help/organizations/enterprise-cloud-trial-option.png) -1. Siga as instruções para configurar seu teste. - -## Explorar o {% data variables.product.prodname_ghe_cloud %} - -Depois de configurar sua versão de avaliação, você pode explorar o {% data variables.product.prodname_ghe_cloud %} seguindo o [Guia de Ativação Enterprise](https://resources.github.com/enterprise-onboarding/). - -{% data reusables.products.product-roadmap %} - -## Finalizar a versão de avaliação - -Você pode comprar o {% data variables.product.prodname_enterprise %} ou fazer downgrade para o {% data variables.product.prodname_team %} em qualquer momento de sua avaliação. - -Se você não comprar o {% data variables.product.prodname_enterprise %} ou o {% data variables.product.prodname_team %} antes de expirar sua versão de avaliação, sua organização será rebaixada para o {% data variables.product.prodname_free_team %} e perder acesso a ferramentas e recursos avançados incluídos apenas em produtos pagos, incluindo sites {% data variables.product.prodname_pages %} publicados a partir desses repositórios privados. Se você não planeja atualizar, para evitar a perda de acesso aos recursos avançados, transforme-os em repositórios públicos antes de sua versão de avaliação expirar. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/articles/setting-repository-visibility)". - -Fazer downgrade para o {% data variables.product.prodname_free_team %} para organizações também desabilita quaisquer configurações SAML feitas durante o período de avaliação. Ao adquirir o {% data variables.product.prodname_enterprise %} ou o {% data variables.product.prodname_team %}, suas configurações SAML serão habilitadas novamente para os usuários da organização se autenticarem. - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.billing_plans %} -5. Em "{% data variables.product.prodname_ghe_cloud %} Free Trial" (Versão de avaliação grátis do {% data variables.product.prodname_ghe_cloud %}) clique em **Buy Enterprise** (Comprar versão Enterprise) ou **Downgrade to Team** (Fazer downgrade para versão Team). ![Botões comprar versão Enterprise e fazer downgrade para versão Team](/assets/images/help/organizations/finish-trial-buttons.png) -6. Siga as instruções para inserir seu método de pagamento e clique em **Submit** (Enviar). diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md index 4388a6969b..bab72cc1e6 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md @@ -1,6 +1,6 @@ --- -title: Verificar endereço de e-mail -intro: 'A verificação do endereço de e-mail principal garante segurança reforçada, permite que a equipe do {% data variables.product.prodname_dotcom %} auxilie melhor caso você esqueça sua senha e fornece acesso a mais recursos no {% data variables.product.prodname_dotcom %}.' +title: Verifying your email address +intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/troubleshooting-email-verification/ - /articles/setting-up-email-verification/ @@ -12,59 +12,60 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Verifique seu endereço de e-mail +shortTitle: Verify your email address --- +## About email verification -## Sobre a verificação de e-mail +You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified. -Você pode verificar seu endereço de e-mail depois de se inscrever em uma nova conta ou ao adicionar um novo endereço de e-mail. Se um endereço de e-mail não puder ser entregue ou retornar, ele será considerado como não verificado. - -Se você não verificar seu endereço de e-mail, não poderá: - - Criar ou bifurcar repositórios - - Criar problemas ou pull requests - - Fazer comentários em problema, pull request ou commits - - Autorizar aplicativos do {% data variables.product.prodname_oauth_app %} - - Gerar tokens de acesso pessoais - - Receber notificações de e-mail - - Marcar repositórios com estrela - - Criar ou atualizar quadros de projeto, inclusive adicionando cartões - - Criar ou atualizar gists - - Criar ou usar o {% data variables.product.prodname_actions %} - - Patrocine desenvolvedores com {% data variables.product.prodname_sponsors %} +If you do not verify your email address, you will not be able to: + - Create or fork repositories + - Create issues or pull requests + - Comment on issues, pull requests, or commits + - Authorize {% data variables.product.prodname_oauth_app %} applications + - Generate personal access tokens + - Receive email notifications + - Star repositories + - Create or update project boards, including adding cards + - Create or update gists + - Create or use {% data variables.product.prodname_actions %} + - Sponsor developers with {% data variables.product.prodname_sponsors %} {% warning %} -**Avisos**: +**Warnings**: - {% data reusables.user_settings.no-verification-disposable-emails %} - {% data reusables.user_settings.verify-org-approved-email-domain %} {% endwarning %} -## Verificar endereço de e-mail +## Verifying your email address {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.emails %} -1. Sob o seu endereço de e-mail, clique em **Reenviar e-mail de verificação**. ![Reenviar link do e-mail de verificação](/assets/images/help/settings/email-verify-button.png) -4. O {% data variables.product.prodname_dotcom %} enviará a você um e-mail com um link. Clicando nesse link, você será redirecionado para o painel do {% data variables.product.prodname_dotcom %} e verá um banner de confirmação. ![Banner confirmando que seu e-mail foi verificado](/assets/images/help/settings/email-verification-confirmation-banner.png) +1. Under your email address, click **Resend verification email**. + ![Resend verification email link](/assets/images/help/settings/email-verify-button.png) +4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner. + ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png) -## Resolver problemas na verificação de e-mail +## Troubleshooting email verification -### Não é possível enviar verificação de e-mail +### Unable to send verification email {% data reusables.user_settings.no-verification-disposable-emails %} -### Página de erro depois de clicar no link de verificação +### Error page after clicking verification link -O link de verificação expira após 24 horas. Se você não verificar seu e-mail dentro de 24 horas, poderá solicitar outro link de verificação de e-mail. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)". +The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)." If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}. 1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}. -2. Saia e reinicie o navegador. +2. Quit and restart your browser. 3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}. -4. Clique no link de verificação no e-mail que enviamos para você. +4. Click on the verification link in the email we sent you. -## Leia mais +## Further reading -- "[Alterar endereço de e-mail principal](/articles/changing-your-primary-email-address)" +- "[Changing your primary email address](/articles/changing-your-primary-email-address)" diff --git a/translations/pt-BR/content/get-started/using-git/about-git.md b/translations/pt-BR/content/get-started/using-git/about-git.md index 4a0a3d9b15..75d4607cf6 100644 --- a/translations/pt-BR/content/get-started/using-git/about-git.md +++ b/translations/pt-BR/content/get-started/using-git/about-git.md @@ -34,7 +34,7 @@ In a distributed version control system, every developer has a full copy of the - Businesses using Git can break down communication barriers between teams and keep them focused on doing their best work. Plus, Git makes it possible to align experts across a business to collaborate on major projects. -## Sobre repositórios +## About repositories A repository, or Git project, encompasses the entire collection of files and folders associated with a project, along with each file's revision history. The file history appears as snapshots in time called commits. The commits can be organized into multiple lines of development called branches. Because Git is a DVCS, repositories are self-contained units and anyone who has a copy of the repository can access the entire codebase and its history. Using the command line or other ease-of-use interfaces, a Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more. @@ -44,7 +44,7 @@ Through platforms like {% data variables.product.product_name %}, Git also provi {% data variables.product.product_name %} hosts Git repositories and provides developers with tools to ship better code through command line features, issues (threaded discussions), pull requests, code review, or the use of a collection of free and for-purchase apps in the {% data variables.product.prodname_marketplace %}. With collaboration layers like the {% data variables.product.product_name %} flow, a community of 15 million developers, and an ecosystem with hundreds of integrations, {% data variables.product.product_name %} changes the way software is built. -{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. Para obter mais informações, consulte "[fluxo do GitHub](/get-started/quickstart/github-flow)". +{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see "[GitHub flow](/get-started/quickstart/github-flow)." ## {% data variables.product.product_name %} and the command line @@ -164,7 +164,7 @@ With a shared repository, individuals and teams are explicitly designated as con For an open source project, or for projects to which anyone can contribute, managing individual permissions can be challenging, but a fork and pull model allows anyone who can view the project to contribute. A fork is a copy of a project under an developer's personal account. Every developer has full control of their fork and is free to implement a fix or new feature. Work completed in forks is either kept separate, or is surfaced back to the original project via a pull request. There, maintainers can review the suggested changes before they're merged. For more information, see "[Contributing to projects](/get-started/quickstart/contributing-to-projects)." -## Leia mais +## Further reading The {% data variables.product.product_name %} team has created a library of educational videos and guides to help users continue to develop their skills and build better software. diff --git a/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md index b20eb9580f..209c0beb0e 100644 --- a/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md +++ b/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md @@ -1,6 +1,6 @@ --- -title: Obter alterações de um repositório remote -intro: É possível usar comandos Git comuns para acessar repositórios remotes. +title: Getting changes from a remote repository +intro: You can use common Git commands to access remote repositories. redirect_from: - /articles/fetching-a-remote/ - /articles/getting-changes-from-a-remote-repository @@ -12,71 +12,76 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Obter alterações de um controle remoto +shortTitle: Get changes from a remote --- +## Options for getting changes -## Opções para obter alterações +These commands are very useful when interacting with [a remote repository](/github/getting-started-with-github/about-remote-repositories). `clone` and `fetch` download remote code from a repository's remote URL to your local computer, `merge` is used to merge different people's work together with yours, and `pull` is a combination of `fetch` and `merge`. -Esses comandos são muito úteis ao interagir com [um repositório remote](/github/getting-started-with-github/about-remote-repositories). `clone` e `fetch` baixam códigos remote de uma URL remota do repositório para seu computador, `merge` é usado para mesclar o trabalho de diferentes pessoas com o seu e `pull` é uma combinação de `fetch` e `merge`. +## Cloning a repository -## Clonar um repositório - -Para capturar uma cópia integral do repositório de outro usuário, use `git clone` desta forma: +To grab a complete copy of another user's repository, use `git clone` like this: ```shell $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git -# Clona um repositório em seu computador +# Clones a repository to your computer ``` -Você pode escolher entre [várias URLs diferentes](/github/getting-started-with-github/about-remote-repositories) ao clonar um repositório. Quando estiver conectado em {% data variables.product.prodname_dotcom %}, esses URLs estarão disponíveis abaixo dos detalhes do repositório: +You can choose from [several different URLs](/github/getting-started-with-github/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available below the repository details: -![Lista de URLs remotas](/assets/images/help/repository/remotes-url.png) +![Remote URL list](/assets/images/help/repository/remotes-url.png) -Ao executar `git clone`, as seguintes ações ocorrem: -- Um novo folder denominado `repo` é criado -- Ele é inicializado como um repositório Git -- Um remote nomeado `origin` (origem) é criado, apontando para o URL que você clonou -- Todos os arquivos e commits do repositório são baixados ali -- O branch-padrão foi desmarcado +When you run `git clone`, the following actions occur: +- A new folder called `repo` is made +- It is initialized as a Git repository +- A remote named `origin` is created, pointing to the URL you cloned from +- All of the repository's files and commits are downloaded there +- The default branch is checked out -Para cada branch `foo` no repositório remote, um branch de acompanhamento remoto correspondente `refs/remotes/origin/foo` é criado em seu repositório local. Normalmente, você pode abreviar os nomes dos branches de acompanhamento remoto para `origin/foo`. +For every branch `foo` in the remote repository, a corresponding remote-tracking branch +`refs/remotes/origin/foo` is created in your local repository. You can usually abbreviate +such remote-tracking branch names to `origin/foo`. -## Fazer fetch de um repositório remote +## Fetching changes from a remote repository -Use `git fetch` para recuperar trabalhos novos feitos por outra pessoas. Fazer fetch de um repositório captura todos os branches de acompanhamento remoto e tags novos *sem* fazer merge dessas alterações em seus próprios branches. +Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags *without* merging those changes into your own branches. -Se você já tem um repositório local com uma URL remota configurada para o projeto desejado, você pode pegar todas as novas informações usando `git buscar *remotename*` no terminal: +If you already have a local repository with a remote URL set up for the desired project, you can grab all the new information by using `git fetch *remotename*` in the terminal: ```shell $ git fetch remotename -# Faz fetch de atualizações feitas em um repositório remote +# Fetches updates made to a remote repository ``` -Caso contrário, você sempre pode adicionar um novo remoto e, em seguida, procurar. Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +Otherwise, you can always add a new remote and then fetch. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Fazer merge de alterações em seu branch local +## Merging changes into your local branch -O merge combina suas alterações locais com as alterações feitas por outras pessoas. +Merging combines your local changes with changes made by others. -Geralmente, você faria um merge de um branch de acompanhamento remoto (por exemplo, um branch com fetch de um repositório remote) com seu branch local: +Typically, you'd merge a remote-tracking branch (i.e., a branch fetched from a remote repository) with your local branch: ```shell $ git merge remotename/branchname -# Faz merge de atualizações feitas online com seu trabalho local +# Merges updates made online with your local work ``` -## Fazer pull de alterações de um repositório remote +## Pulling changes from a remote repository -`git pull` é um atalho conveniente para executar `git fetch` e `git merge` no mesmo comando: +`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command: ```shell $ git pull remotename branchname -# Captura atualizações online e faz merge delas em seu trabalho local +# Grabs online updates and merges them with your local work ``` -Você deve garantir que fez commit de seu trabalho local antes de executar o comando `pull`, pois `pull` faz um merge nas alterações recuperadas. If you run into \[a merge conflict\](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort` to take the branch back to where it was in before you pulled. +Because `pull` performs a merge on the retrieved changes, you should ensure that +your local work is committed before running the `pull` command. If you run into +[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line) +you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort` +to take the branch back to where it was in before you pulled. -## Leia mais +## Further reading -- ["Trabalhar com remotes" no livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %} -- "[Solucionar problemas de conectividade](/articles/troubleshooting-connectivity-problems)"{% endif %} +- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %} +- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"{% endif %} diff --git a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 1ca7fc6310..f070c323c5 100644 --- a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -1,81 +1,90 @@ --- -title: Dividir uma subpasta em um novo repositório +title: Splitting a subfolder out into a new repository redirect_from: - /articles/splitting-a-subpath-out-into-a-new-repository/ - /articles/splitting-a-subfolder-out-into-a-new-repository - /github/using-git/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository -intro: Você pode transformar uma pasta em um repositório do Git repository em um novo repositório. +intro: You can turn a folder within a Git repository into a brand new repository. versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -shortTitle: Dividindo uma subpasta +shortTitle: Splitting a subfolder --- - -Se você criar um clone do repositório, não perderá nenhuma alteração ou histórico do Git quando dividir uma pasta e criar um repositório separado. +If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para o local em que deseja criar o novo repositório. -3. Clone o repositório que contém a subpasta. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME - ``` -4. Altere o diretório de trabalho atual para o repositório clonado. - ```shell - $ cd REPOSITORY-NAME - ``` -5. Para filtrar a subpasta do restante dos arquivos no repositório, execute [`git filter-repo`](https://github.com/newren/git-filter-repo), fornecendo estas informações: - - `FOLDER-NAME`: A pasta dentro do seu projeto onde você deseja criar um repositório separado. - {% windows %} +2. Change the current working directory to the location where you want to create your new repository. - {% tip %} +4. Clone the repository that contains the subfolder. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME + ``` - **Dica:** os usuários do Windows devem usar `/` para delimitar as pastas. +4. Change the current working directory to your cloned repository. + ```shell + $ cd REPOSITORY-NAME + ``` - {% endtip %} +5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information: + - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository. - {% endwindows %} + {% windows %} + {% tip %} + + **Tip:** Windows users should use `/` to delimit folders. + + {% endtip %} + + {% endwindows %} + + ```shell + $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/ + # Filter the specified branch in your directory and remove empty commits + > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) + > Ref 'refs/heads/BRANCH-NAME' was rewritten + ``` + + The repository should now only contain the files that were in your subfolder(s). + +6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}. + +7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) + + {% tip %} + + **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." + + {% endtip %} + +8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) + ``` + +9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7. + ```shell + git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git + ``` + +10. Verify that the remote URL has changed with your new repository name. ```shell - $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/ - # Filter the specified branch in your directory and remove empty commits - > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) - > Ref 'refs/heads/BRANCH-NAME' was rewritten + $ git remote -v + # Verify new remote URL + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) ``` - Agora o repositório deve conter apenas os arquivos que estava(m) na(s) subpasta(s). -6. [Crie um repositório](/articles/creating-a-new-repository/) no {% data variables.product.product_name %}. -7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) - - {% tip %} - - **Dica:** Para obter informações sobre a diferença entre as URLs de HTTPS e SSH, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". - - {% endtip %} - -8. Verifique o nome remoto do repositório. Por exemplo, `origin` ou `upstream` são duas escolhas comuns. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) - ``` - -9. Configure uma nova URL remota para o novo repositório usando o nome e a URL do repositório remote copiados na etapa 7. - ```shell - git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git - ``` -10. Verifique se a URL remota mudou com o nome do novo repositório. - ```shell - $ git remote -v - # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) - ``` -11. Faça push das alterações para o novo repositório no {% data variables.product.product_name %}. - ```shell - git push -u origin BRANCH-NAME - ``` +11. Push your changes to the new repository on {% data variables.product.product_name %}. + ```shell + git push -u origin BRANCH-NAME + ``` diff --git a/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md b/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md index 2575e7d191..3b8bdfe7b5 100644 --- a/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md +++ b/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md @@ -1,6 +1,6 @@ --- -title: Explorar versões de acesso antecipado com visualização de recursos -intro: Você pode usar a visualização de recursos para ver produtos ou recursos que estão disponíveis na versão beta e para habilitar ou desabilitar cada recurso para sua conta de usuário. +title: Exploring early access releases with feature preview +intro: You can use feature preview to see products or features that are available in beta and to enable or disable each feature for your user account. redirect_from: - /articles/exploring-early-access-releases-with-feature-preview - /github/getting-started-with-github/exploring-early-access-releases-with-feature-preview @@ -10,22 +10,22 @@ versions: ghec: '*' topics: - Early access -shortTitle: Visualização do recurso +shortTitle: Feature preview --- +## {% data variables.product.prodname_dotcom %}'s release cycle -## Ciclo de versões do {% data variables.product.prodname_dotcom %} +{% data variables.product.prodname_dotcom %}'s products and features can go through multiple release phases. -Os produtos e recursos do {% data variables.product.prodname_dotcom %} podem passar por várias fases de versão. +| Phase | Description | +|-------|-------------| +| Alpha | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. Alpha releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations.

    **Note**: A product or feature released as a "Technology Preview" is considered to be in the alpha release stage. Technology Preview releases share the same characteristics of alpha releases as described above.| +| Beta | The product or feature is ready for broader distribution. Beta releases can be public or private, are documented, but do not have any SLAs or technical support obligations. | +| General availability (GA) | The product or feature is fully tested and open publicly to all users. GA releases are ready for production use, and associated SLA and technical support obligations apply. | -| Fase | Descrição | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Alfa | O produto ou recurso está em pleno desenvolvimento e tem seus requisitos e seu escopo alterados com frequência. O recurso está disponível para fins de demonstração e teste, mas não está documentado. Nas versões alfa, os recursos não estão necessariamente completos, não são fornecidos Contratos de nível de serviço (SLAs) e não existe obrigação de oferecer suporte técnico.

    **Note**: A product or feature released as a "Technology Preview" is considered to be in the alpha release stage. Technology Preview releases share the same characteristics of alpha releases as described above. | -| Beta | O produto ou recurso está pronto para uma distribuição mais ampla. As versões beta podem ser públicas ou privadas e estão documentadas, mas não têm obrigação de oferecer suporte técnico ou SLAs. | -| Disponibilidade geral (GA) | O produto ou recurso está totalmente testado e é disponibilizado publicamente a todos os usuários. As versões GA estão prontas para uso na produção e há obrigação de suporte técnico e SLAs associados. | +## Exploring beta releases with feature preview -## Explorar versões beta com visualização de recursos - -Você pode ver uma lista de recursos disponíveis na versão beta e uma breve descrição de cada um deles. Cada recurso inclui um link para dar feedback. +You can see a list of features that are available in beta and a brief description for each feature. Each feature includes a link to give feedback. {% data reusables.feature-preview.feature-preview-setting %} -2. Outra opção é clicar em **Enable** (Habilitar) ou **Disable** (Desabilitar) à direita de um recurso. ![Botão Enable (Habilitar) na visualização de recursos](/assets/images/help/settings/enable-feature-button.png) +2. Optionally, to the right of a feature, click **Enable** or **Disable**. + ![Enable button in feature preview](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/pt-BR/content/get-started/using-github/github-command-palette.md b/translations/pt-BR/content/get-started/using-github/github-command-palette.md index 59e3048a44..37b977176b 100644 --- a/translations/pt-BR/content/get-started/using-github/github-command-palette.md +++ b/translations/pt-BR/content/get-started/using-github/github-command-palette.md @@ -4,13 +4,13 @@ intro: 'Use the command palette in {% data variables.product.product_name %} to versions: fpt: '*' ghec: '*' - feature: command-palette + feature: 'command-palette' shortTitle: GitHub Command Palette --- {% data reusables.command-palette.beta-note %} -## Sobre o {% data variables.product.prodname_command_palette %} +## About the {% data variables.product.prodname_command_palette %} You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard. @@ -26,31 +26,31 @@ The ability to run commands directly from your keyboard, without navigating thro ![Command palette change theme](/assets/images/help/command-palette/command-palette-command-change-theme.png) -## Abrindo o {% data variables.product.prodname_command_palette %} +## Opening the {% data variables.product.prodname_command_palette %} Open the command palette using one of the following keyboard shortcuts: -- Windows and Linux: Ctrlk or Ctrlaltk +- Windows and Linux: Ctrlk or Ctrlaltk - Mac: ⌘k or ⌘optionk -When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). +When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png) {% note %} -**Notas:** +**Notes:** - If you are editing Markdown text, open the command palette with Ctrlaltk (Windows and Linux) or ⌘optionk (Mac). -- If you are working on a project (beta), a project-specific command palette is displayed instead. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)". +- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." {% endnote %} ## Navigating with the {% data variables.product.prodname_command_palette %} -You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. +You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. {% data reusables.command-palette.open-palette %} -2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. +2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png) @@ -64,18 +64,18 @@ You can use the command palette to navigate to any page that you have access to ## Searching with the {% data variables.product.prodname_command_palette %} -You can use the command palette to search for anything on {% data variables.product.product_location %}. +You can use the command palette to search for anything on {% data variables.product.product_location %}. {% data reusables.command-palette.open-palette %} {% data reusables.command-palette.change-scope %} -3. Optionally, use keystrokes to find specific types of resource: +3. Optionally, use keystrokes to find specific types of resource: - # Search for issues, pull requests, discussions, and projects - ! Search for projects - @ Search for users, organizations, and repositories - - / Search for files within a repository scope + - / Search for files within a repository scope ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png) @@ -94,7 +94,7 @@ You can use the command palette to search for anything on {% data variables.prod You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette. - Pull request and issue commands always run on the underlying page. -- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. +- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)." @@ -121,100 +121,100 @@ When the command palette is active, you can use one of the following keyboard sh These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode. -| Keystroke | Function | -|:--------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| > | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." | -| # | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| @ | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| / | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| ! | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | -| Ctrlc or ⌘c | Copy the search or navigation URL for the highlighted result to the clipboard. | -| Enter | Jump to the highlighted result or run the highlighted command. | -| CtrlEnter or ⌘Enter | Open the highlighted search or navigation result in a new brower tab. | -| ? | Display help within the command palette. | +| Keystroke | Function | +| :- | :- | +|>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." | +|#| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|@| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|/| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | +|!| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|Ctrlc or ⌘c| Copy the search or navigation URL for the highlighted result to the clipboard.| +|Enter| Jump to the highlighted result or run the highlighted command.| +|CtrlEnter or ⌘Enter| Open the highlighted search or navigation result in a new brower tab.| +|?| Display help within the command palette.| ### Global commands These commands are available from all scopes. -| Command | Behavior | -|:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Import repository` | Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | -| `New gist` | Open a new gist. For more information, see "[Creating a gist](/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | -| `New organization` | Create a new organization. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". | -| `Novo projeto` | Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | -| `New repository` | Create a new repository from scratch. Para obter mais informações, consulte "[Criar um novo repositório](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | -| `Switch theme to ` | Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | +| Command | Behavior| +| :- | :- | :- | +|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | +|`New gist`|Open a new gist. For more information, see "[Creating a gist](/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | +|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | +|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | +|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | ### Organization commands These commands are available only within the scope of an organization. -| Command | Behavior | -|:---------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `New team` | Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." | +| Command | Behavior| +| :- | :- | +| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." ### Repository commands Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column. -| Command | Behavior | -|:------------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Clone repository: ` | Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. Para obter mais informações, consulte "[Clonar um repositório](/repositories/creating-and-managing-repositories/cloning-a-repository)". | -| `New discussion` | Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)." | -| `New file` | Create a new file from any page in the repository. Para obter mais informações, consulte "[Adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." | -| `New issue` | Open a new issue from any page in the repository. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue)". | -| `Open in new codespace` | Create and open a codespace for this repository. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | -| `Open in github.dev editor` | Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)." | +| Command | Behavior| +| :- | :- | +|`Clone repository: `|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."| +|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."| +|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." +|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."| +|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."| +|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| ### File commands These commands are available only when you open the command palette from a file in a repository. -| Command | Behavior | -|:--------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Copy permalink` | Create a link to the file that includes the current commit SHA and copy the link to the clipboard. Para obter mais informações, consulte "[Obter links permanentes em arquivos](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)". | -| `Open in github.dev editor` | Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)." | +| Command | Behavior| +| :- | :- | +|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)." +|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| ### Discussion commands These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette. -| Command | Behavior | -|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Delete discussion...` | Permanently delete the discussion. Para obter mais informações, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)". | -| `Edit discussion body` | Open the main body of the discussion ready for editing. | -| `Subscribe`/`unsubscribe` | Opt in or out of notifications for additions to the discussion. Para obter mais informações, consulte "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". | -| `Transfer discussion...` | Move the discussion to a different repository. Para obter mais informações, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)". | +| Command | Behavior| +| :- | :- | +|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." +|`Edit discussion body`|Open the main body of the discussion ready for editing. +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)." ### Issue commands These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette. -| Command | Behavior | -|:-------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Close`/`reopen issue` | Close or reopen the current issue. Para obter mais informações, consulte "[Sobre problemas](/issues/tracking-your-work-with-issues/about-issues)". | -| `Convert issue to discussion...` | Convert the current issue into a discussion. Para obter mais informações, consulte "[Moderação de discussões](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)". | -| `Delete issue...` | Delete the current issue. Para obter mais informações, consulte "[Excluir uma problema](/issues/tracking-your-work-with-issues/deleting-an-issue)". | -| `Edit issue body` | Open the main body of the issue ready for editing. | -| `Edit issue title` | Open the title of the issue ready for editing. | -| `Lock issue` | Limit new comments to users with write access to the repository. Para obter mais informações, consulte "[Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)". | -| `Pin`/`unpin issue` | Change whether or not the issue is shown in the pinned issues section for the repository. Para obter mais informações, consulte "[Fixar um problema no seu repositório](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)". | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this issue. Para obter mais informações, consulte "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". | -| `Transfer issue...` | Transfer the issue to another repository. Para obter mais informações, consulte "[Transferir um problema para outro repositório](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)". | +| Command | Behavior| +| :- | :- | +|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."| +|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." +|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."| +|`Edit issue body`|Open the main body of the issue ready for editing. +|`Edit issue title`|Open the title of the issue ready for editing. +|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." +|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."| +|`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."| ### Pull request commands These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette. -| Command | Behavior | -|:---------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Close`/`reopen pull request` | Close or reopen the current pull request. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)". | -| `Convert to draft`/`Mark pull request as ready for review` | Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." | -| `Copy current branch name` | Add the name of the head branch for the pull request to the clipboard. | -| `Edit pull request body` | Open the main body of the pull request ready for editing. | -| `Edit pull request title` | Open the title of the pull request ready for editing. | -| `Open in new codespace` | Create and open a codespace for the head branch of the pull request. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this pull request. Para obter mais informações, consulte "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". | -| `Update current branch` | Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)". | +| Command | Behavior| +| :- | :- | +|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."| +|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."| +|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard. +|`Edit pull request body`|Open the main body of the pull request ready for editing. +|`Edit pull request title`|Open the title of the pull request ready for editing. +|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +|`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."| diff --git a/translations/pt-BR/content/get-started/using-github/github-for-mobile.md b/translations/pt-BR/content/get-started/using-github/github-for-mobile.md index 5736469565..c1331d6da4 100644 --- a/translations/pt-BR/content/get-started/using-github/github-for-mobile.md +++ b/translations/pt-BR/content/get-started/using-github/github-for-mobile.md @@ -1,6 +1,6 @@ --- -title: GitHub para dispositivos móveis -intro: 'Faça triagem, colabore e gerencie seu trabalho em {% data variables.product.product_name %} do seu dispositivo móvel.' +title: GitHub for mobile +intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' versions: fpt: '*' ghes: '*' @@ -11,81 +11,80 @@ redirect_from: - /github/getting-started-with-github/github-for-mobile - /github/getting-started-with-github/using-github/github-for-mobile --- - {% data reusables.mobile.ghes-release-phase %} -## Sobre o {% data variables.product.prodname_mobile %} +## About {% data variables.product.prodname_mobile %} {% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} oferece a você uma maneira de realizar trabalhos de alto impacto {% data variables.product.product_name %} rapidamente e de qualquer lugar. O {% data variables.product.prodname_mobile %}é uma maneira segura e confiável de acessar seus dados {% data variables.product.product_name %} através de um aplicativo cliente confiável e primordial. +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. -Com o {% data variables.product.prodname_mobile %} você pode: -- Gerenciar, fazer triagem e limpar notificações -- Leia, analisar e colaborar em problemas e pull requests -- Pesquisar, navegar e interagir com usuários, repositórios e organizações -- Receber uma notificação push quando alguém mencionar seu nome de usuário +With {% data variables.product.prodname_mobile %} you can: +- Manage, triage, and clear notifications +- Read, review, and collaborate on issues and pull requests +- Search for, browse, and interact with users, repositories, and organizations +- Receive a push notification when someone mentions your username -Para mais informações sobre notificações para {% data variables.product.prodname_mobile %}, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." +For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." -## Instalar o {% data variables.product.prodname_mobile %} +## Installing {% data variables.product.prodname_mobile %} -Para instalar {% data variables.product.prodname_mobile %} para Android ou iOS, consulte [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). -## Gerenciar contas +## Managing accounts -Você pode estar conectado simultaneamente em um celular com uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %} e com uma conta de usuário em {% data variables.product.prodname_ghe_server %}. +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. {% data reusables.mobile.push-notifications-on-ghes %} -{% data variables.product.prodname_mobile %} pode não funcionar com a sua empresa se for necessário acessar sua empresa através da VPN. +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. -### Pré-requisitos +### Prerequisites -Você precisa instalar {% data variables.product.prodname_mobile %} 1.4 ou superior no seu dispositivo para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}. +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. -Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/managing-github-for-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/managing-github-for-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} -Durante o beta para {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, você deve estar conectado com uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}. +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. -### Adicionar, alternar ou encerrar a sessão das contas +### Adding, switching, or signing out of accounts -Você pode iniciar a sessão no celular com uma conta de usuário em {% data variables.product.product_location %}. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil** e, em seguida, toque em {% octicon "plus" aria-label="The plus icon" %} **Adicionar Conta Corporativa**. Siga as instruções para efetuar o login. +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. -Após efetuar o login no celular com uma conta de usuário em {% data variables.product.product_location %}, você poderá alternar entre a conta e sua conta em {% data variables.product.prodname_dotcom_the_website %}. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil** e, em seguida, toque na conta para a qual você deseja mudar. +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. -Se você não precisar mais acessar os dados da sua conta de usuário em {% data variables.product.product_location %} de {% data variables.product.prodname_mobile %}, você poderá encerrar a sessão da conta. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil**, deslize para a esquerda na conta para encerrar sessão e toque em **Encerrar sessão**. +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. -## Idiomas compatíveis com {% data variables.product.prodname_mobile %} +## Supported languages for {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} está disponível nos seguintes idiomas. +{% data variables.product.prodname_mobile %} is available in the following languages. - English - Japanese -- Português do Brasil -- Chinês simplificado +- Brazilian Portuguese +- Simplified Chinese - Spanish -Se você configurar o idioma do seu dispositivo para um idioma compatível, {% data variables.product.prodname_mobile %} será o idioma-padrão. Você pode alterar o idioma para {% data variables.product.prodname_mobile %} no no menu **Configurações** de {% data variables.product.prodname_mobile %}. +If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. -## Gerenciando links universais para {% data variables.product.prodname_mobile %} no iOS +## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS -{% data variables.product.prodname_mobile %} ativa automaticamente o Universal Links para iOS. Quando você clica em qualquer link {% data variables.product.product_name %}, a URL de destino vai abrir em {% data variables.product.prodname_mobile %} em vez do Safari. Para obter mais informações, consulte [Universal Links](https://developer.apple.com/ios/universal-links/) no site de desenvolvedor da Apple +{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site. -Para desabilitar os links universais, mantenha qualquer link {% data variables.product.product_name %} pressionado e, em seguida, pressione **Abrir**. Toda vez que você clica em um link {% data variables.product.product_name %} no futuro, a URL de destino abrirá no Safari em vez do {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.product_name %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. -## Compartilhando feedback +## Sharing feedback -Se você encontrar um erro em {% data variables.product.prodname_mobile %}, você pode nos enviar um e-mail para mobilefeedback@github.com. +If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at mobilefeedback@github.com. -Você pode enviar solicitações de recursos ou outros feedbacks para {% data variables.product.prodname_mobile %} em [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). +You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). -## Desativando versões beta para iOS +## Opting out of beta releases for iOS -Se você estiver testando uma versão beta do {% data variables.product.prodname_mobile %} para iOS usando TestFlight, você pode deixar a versão beta a qualquer momento. +If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time. -1. Em seu dispositivo iOS, abra o app TestFlight. -2. Em "Apps", clique em **{% data variables.product.prodname_dotcom %}**. -3. Na parte inferior da página, clique em **Interromper testes**. +1. On your iOS device, open the TestFlight app. +2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**. +3. At the bottom of the page, tap **Stop Testing**. 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 c8dce3163f..bc0dfabdb6 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 @@ -1,6 +1,6 @@ --- -title: Atalhos de teclado -intro: 'Quase todas as páginas no {% data variables.product.prodname_dotcom %} tem um atalho de teclado que executa as ações mais rapidamente.' +title: Keyboard shortcuts +intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.' redirect_from: - /articles/using-keyboard-shortcuts/ - /categories/75/articles/ @@ -14,211 +14,209 @@ versions: ghae: '*' ghec: '*' --- +## About keyboard shortcuts -## Sobre atalhos do teclado +Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate. -Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. Você pode usar esses atalhos de teclado para executar ações no site sem precisar usar o mouse para navegar. +{% if keyboard-shortcut-accessibility-setting %} +You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %} -Veja abaixo uma lista dos atalhos de teclado disponíveis. +Below is a list of some of the available keyboard shortcuts. {% if command-palette %} The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} -## Atalhos para o site +## Site wide shortcuts -| Atalho | Descrição | -| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". | -| g n | Vai para suas notificações. Para obter mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications)"{% endif %}." | -| esc | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está | +| Keyboard shortcut | Description +|-----------|------------ +|s or / | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." +|g n | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +|esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in +{% if command-palette %}|controlk or commandk | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Ctlaltk or ⌘optionk. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} -{% if command-palette %} +## Repositories -controlk or commandk | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Ctlaltk or ⌘optionk. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +| Keyboard shortcut | Description +|-----------|------------ +|g c | Go to the **Code** tab +|g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." +|g p | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %} +|g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} +|g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." +|g w | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %} +|g g | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %} -## Repositórios +## Source code editing -| Atalho | Descrição | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | Vai para a aba **Code** (Código) | -| g i | Vai para a aba **Issues** (Problemas). Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)". | -| g p | Vai para a aba **Pull requests**. Para obter mais informações, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %} -| g a | Acesse a aba de **Ações**. Para obter mais informações, consulte "[Sobre ações](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %} -| g b | Vai para a aba **Projects** (Projetos). Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". | -| g w | Vai para a aba **Wiki**. Para obter mais informações, consulte "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %} -| g g | Acesse a aba **Discussões**. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".{% endif %} +| Keyboard shortcut | Description +|-----------|------------{% ifversion fpt or ghec %} +|.| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %} +| control b or command b | Inserts Markdown formatting for bolding text +| control i or command i | Inserts Markdown formatting for italicizing text +| control k or command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %} +| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list +| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list +| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %} +|e | Open source code file in the **Edit file** tab +|control f or command f | Start searching in file editor +|control g or command g | Find next +|control shift g or command shift g | Find previous +|control shift f or command option f | Replace +|control shift r or command shift option f | Replace all +|alt g | Jump to line +|control z or command z | Undo +|control y or command y | Redo +|command shift p | Toggles between the **Edit file** and **Preview changes** tabs +|control s or command s | Write a commit message -## Edição de código-fonte +For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands). -| Atalho | Descrição | -| --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} -| . | Abre um repositório ou um pull request no editor baseado na web. Para obter mais informações, consulte "[Editor baseado na web](/codespaces/developing-in-codespaces/web-based-editor)".{% endif %} -| control b ou command b | Insere formatação Markdown para texto em negrito | -| control i ou command i | Insere formatação Markdown para texto em itálico | -| control k ou command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %} -| control shift 7 ou command shift 7 | Insere a formatação de Markdown para uma lista ordenada | -| control shift 8 ou command shift 8 | Inserts Markdown formatting for an unordered list | -| control shift . ou command shift. | Inserts Markdown formatting for a quote{% endif %} -| e | Abra o arquivo de código-fonte na aba **Editar arquivo** | -| control f ou command f | Começa a pesquisar no editor de arquivo | -| control g ou command g | Localiza o próximo | -| control shift g or command shift g | Localiza o anterior | -| control shift f or command option f | Substitui | -| control shift r or command shift option f | Substitui todos | -| alt g | Pula para linha | -| control z ou command z | Desfaz | -| control y ou command y | Refaz | -| command shift p | Alterna entre as abas **Edit file** (Editar aquivo) e **Preview changes** (Visualizar alterações) | -| control s ou comando s | Escrever uma mensagem de commit | +## Source code browsing -Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://codemirror.net/doc/manual.html#commands). +| Keyboard shortcut | Description +|-----------|------------ +|t | Activates the file finder +|l | Jump to a line in your code +|w | Switch to a new branch or tag +|y | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)." +|i | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)." +|a | Show or hide annotations on diffs +|b | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)." -## Navegação de código-fonte +## Comments -| Atalho | Descrição | -| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| t | Ativa o localizador de arquivos | -| l | Pula para uma linha no código | -| w | Muda para um novo branch ou tag | -| y | Expande a URL para sua forma canônica. Para obter mais informações, consulte "[Obter links permanentes em arquivos](/articles/getting-permanent-links-to-files)". | -| i | Mostra ou oculta comentários em diffs. Para obter mais informações, consulte "[Comentar no diff de uma pull request](/articles/commenting-on-the-diff-of-a-pull-request)". | -| a | Exibir ou ocultar anotações em diffs | -| b | Abre a vsualização de blame. Para obter mais informações, consulte "[Rastrear alterações em um arquivo](/articles/tracing-changes-in-a-file)". | +| Keyboard shortcut | Description +|-----------|------------ +| control b or command b | Inserts Markdown formatting for bolding text +| control i or command i | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} +| control e or command e | Inserts Markdown formatting for code or a command within a line{% endif %} +| control k or command k | Inserts Markdown formatting for creating a link +| control shift p or command shift p| Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} +| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list +| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} +| control enter | Submits a comment +| control . and then control [saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} +| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} +|control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} +| r | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | -## Comentários +## Issue and pull request lists -| Atalho | Descrição | -| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| control b ou command b | Insere formatação Markdown para texto em negrito | -| control i ou command i | Insere a formatação Markdown para texto em itálico{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} -| controle e ou comando e | Insere a formatação Markdown para código ou um comando dentro da linha{% endif %} -| control k ou command k | Insere formatação Markdown para criar um link | -| control shift p ou command shift p | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} -| control shift 7 ou command shift 7 | Insere a formatação de Markdown para uma lista ordenada | -| control shift 8 ou command shift 8 | Insere a formatação Markdown para uma lista não ordenada{% endif %} -| control enter | Envia um comentário | -| control . e control [número de resposta salvo] | Abre o menu de respostas salvas e autocompleta o campo de comentário com uma resposta salva. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)".{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} -| control shift . ou command shift. | Insere a formatação Markdown para uma citação{% endif %}{% ifversion fpt or ghec %} -| control g ou command g | Insere uma sugestão. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)". -{% endif %} -| r | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)". | +| Keyboard shortcut | Description +|-----------|------------ +|c | Create an issue +| control / or command / | Focus your cursor on the issues or pull requests search bar. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."|| +|u | Filter by author +|l | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." +| alt and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." +|m | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)." +|a | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)." +|o or enter | Open issue -## Listas de problemas e pull requests +## Issues and pull requests +| Keyboard shortcut | Description +|-----------|------------ +|q | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)." +|m | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)." +|l | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)." +|a | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)." +|cmd + shift + p or control + shift + p | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %} +|alt and click | When creating an issue from a task list, open the new issue form in the current tab by holding alt and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." +|shift and click | When creating an issue from a task list, open the new issue form in a new tab by holding shift and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." +|command or control + shift and click | When creating an issue from a task list, open the new issue form in the new window by holding command or control + shift and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %} -| Atalho | Descrição | -| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Cria um problema | -| control / ou command / | Evidencia seu cursor na barra de pesquisa de problemas e pull requests. Para obter mais informações, consulte "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests). "£" | -| u | Filtra por autor | -| l | Filtra por ou edita etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| alt e clique | Ao filtrar por etiquetas, exclui etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| m | Filtra por ou edita marcos. Para obter mais informações, consulte "[Filtrar problemas e pull requests por marcos](/articles/filtering-issues-and-pull-requests-by-milestone)". | -| a | Filtra por ou edita um responsável. Para obter mais informações, consulte "[Filtrar problemas e pull requests por responsáveis](/articles/filtering-issues-and-pull-requests-by-assignees)". | -| o ou enter | Abre um problema | +## Changes in pull requests -## Problemas e pull requests -| Atalho | Descrição | -| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| q | Solicita um revisor. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review/)". | -| m | Define um marco. Para obter mais informações, consulte "[Associar marcos a problemas e pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)". | -| l | Aplica uma etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests/)". | -| a | Define um responsável. Para obter mais informações, consulte "[Atribuir problemas e pull requests a outros usuários {% data variables.product.company_short %}](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". | -| cmd + shift + p ou control + shift + p | Alterna entre as abas **Escrever** e **Visualizar**{% ifversion fpt or ghec %} -| alt e clique | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas na aba atual, mantendo alt pressionado e clicando no {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". | -| shift e clique | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas em uma nova aba mantendo shift pressionado e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". | -| command ou control + shift e clique | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas na nova janela mantendo command ou controle + shift pressionado e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %} +| Keyboard shortcut | Description +|-----------|------------ +|c | Open the list of commits in the pull request +|t | Open the list of changed files in the pull request +|j | Move selection down in the list +|k | Move selection up in the list +| cmd + shift + enter | Add a single comment on a pull request diff | +| alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %} +| Click, then shift and click | Comment on multiple lines of a pull request by clicking a line number, holding shift, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} -## Alterações em pull requests +## Project boards -| Atalho | Descrição | -| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Abre a lista de commits na pull request | -| t | Abre a lista de arquivos alterados na pull request | -| j | Move a seleção para baixo na lista | -| k | Move a seleção para cima na lista | -| cmd + shift + enter | Adiciona um comentário único no diff da pull request | -| alt e clique | Alterna entre opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request ao manter pressionada a tecla `alt` e clicar em **Mostrar desatualizados** ou **Ocultar desatualizados**.|{% ifversion fpt or ghes or ghae or ghec %} -| Clique, em seguida shift e clique | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado shift, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." -{% endif %} +### Moving a column -## Quadros de projeto +| Keyboard shortcut | Description +|-----------|------------ +|enter or space | Start moving the focused column +|escape | Cancel the move in progress +|enter | Complete the move in progress +|← or h | Move column to the left +|command + ← or command + h or control + ← or control + h | Move column to the leftmost position +|→ or l | Move column to the right +|command + → or command + l or control + → or control + l | Move column to the rightmost position -### Mover uma coluna +### Moving a card -| Atalho | Descrição | -| ---------------------------------------------------------------------------------------------------- | -------------------------------------------- | -| enter ou space | Começa a mover a coluna em evidência | -| escape | Cancela o movimento em curso | -| enter | Completa o movimento em curso | -| ← ou h | Move a coluna para a esquerda | -| command + ← ou command + h ou control + ← ou control + h | Move a coluna para a posição mais à esquerda | -| → ou l | Move a coluna para a direita | -| command + → ou command + l ou control + → ou control + l | Move a coluna para a posição mais à direita | +| Keyboard shortcut | Description +|-----------|------------ +|enter or space | Start moving the focused card +|escape | Cancel the move in progress +|enter | Complete the move in progress +|↓ or j | Move card down +|command + ↓ or command + j or control + ↓ or control + j | Move card to the bottom of the column +|↑ or k | Move card up +|command + ↑ or command + k or control + ↑ or control + k | Move card to the top of the column +|← or h | Move card to the bottom of the column on the left +|shift + ← or shift + h | Move card to the top of the column on the left +|command + ← or command + h or control + ← or control + h | Move card to the bottom of the leftmost column +|command + shift + ← or command + shift + h or control + shift + ← or control + shift + h | Move card to the top of the leftmost column +|→ | Move card to the bottom of the column on the right +|shift + → or shift + l | Move card to the top of the column on the right +|command + → or command + l or control + → or control + l | Move card to the bottom of the rightmost column +|command + shift + → or command + shift + l or control + shift + → or control + shift + l | Move card to the bottom of the rightmost column -### Mover um cartão +### Previewing a card -| Atalho | Descrição | -| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | -| enter ou space | Começa a mover o cartão em evidência | -| escape | Cancela o movimento em curso | -| enter | Completa o movimento em curso | -| ↓ ou j | Move o cartão para baixo | -| command + ↓ ou command + j ou control + ↓ ou control + j | Move o cartão para a parte inferior da coluna | -| ↑ ou k | Move o cartão para cima | -| command + ↑ ou command + k ou control + ↑ ou control + k | Move o cartão para a parte superior da coluna | -| ← ou h | Move o cartão para a parte inferior da coluna à esquerda | -| shift + ← ou shift + h | Move o cartão para a parte superior da coluna à esquerda | -| command + ← ou command + h ou control + ← ou control + h | Move o cartão para a parte inferior da coluna mais à esquerda | -| command + shift + ← ou command + shift + h ou control + shift + ← ou control + shift + h | Move o cartão para a parte superior da coluna mais à esquerda | -| → | Move o cartão para a parte inferior da coluna à direita | -| shift + → ou shift + l | Move o cartão para a parte superior da coluna à direita | -| command + → ou command + l ou control + → ou control + l | Move o cartão para a parte inferior da coluna mais à direita | -| command + shift + → ou command + shift + l ou control + shift + → ou control + shift + l | Move o cartão para a parte inferior da coluna mais à direita | - -### Pré-visualizar um cartão - -| Atalho | Descrição | -| -------------- | ---------------------------------------- | -| esc | Fecha o painel de visualização do cartão | +| Keyboard shortcut | Description +|-----------|------------ +|esc | Close the card preview pane {% ifversion fpt or ghec %} ## {% data variables.product.prodname_actions %} -| Atalho | Descrição | -| --------------------------------------------------------- | ------------------------------------------------------------------------------------ | -| command + space ou control + space | No editor de fluxo de trabalho, obtém sugestões para o arquivo de fluxo de trabalho. | -| g f | Acesse o arquivo do fluxo de trabalho | -| shift + t or T | Alternar as marcas de tempo nos registros | -| shift + f ou F | Alternar os registros em tela cheia | -| esc | Sair dos registros em tela cheia | +| Keyboard shortcut | Description +|-----------|------------ +|command + space or control + space | In the workflow editor, get suggestions for your workflow file. +|g f | Go to the workflow file +|shift + t or T | Toggle timestamps in logs +|shift + f or F | Toggle full-screen logs +|esc | Exit full-screen logs {% endif %} -## Notificações +## Notifications + {% ifversion fpt or ghes or ghae or ghec %} -| Atalho | Descrição | -| -------------------- | -------------------- | -| e | Marcar como pronto | -| shift + u | Marcar como não lido | -| shift + i | Marca como lido | -| shift + m | Cancelar assinatura | +| Keyboard shortcut | Description +|-----------|------------ +|e | Mark as done +| shift + u| Mark as unread +| shift + i| Mark as read +| shift + m | Unsubscribe {% else %} -| Atalho | Descrição | -| -------------------------------------------- | --------------- | -| e ou I ou y | Marca como lido | -| shift + m | Desativa o som | +| Keyboard shortcut | Description +|-----------|------------ +|e or I or y | Mark as read +|shift + m | Mute thread {% endif %} -## gráfico de rede +## Network graph -| Atalho | Descrição | -| -------------------------------------------- | -------------------------------- | -| ← ou h | Rola para a esquerda | -| → ou l | Rola para a direita | -| ↑ ou k | Rola para cima | -| ↓ ou j | Rola para baixo | -| shift + ← ou shift + h | Rola até o final para a esquerda | -| shift + → ou shift + l | Rola até o final para a direita | -| shift + ↑ ou shift + k | Rola até o final para cima | -| shift + ↓ ou shift + j | Rola até o final para baixo | +| Keyboard shortcut | Description +|-----------|------------ +|← or h | Scroll left +|→ or l | Scroll right +|↑ or k | Scroll up +|↓ or j | Scroll down +|shift + ← or shift + h | Scroll all the way left +|shift + → or shift + l | Scroll all the way right +|shift + ↑ or shift + k | Scroll all the way up +|shift + ↓ or shift + j | Scroll all the way down diff --git a/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md index 925e4c4591..589ce46209 100644 --- a/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md +++ b/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md @@ -1,6 +1,6 @@ --- -title: Criando extensões da CLI do GitHub -intro: 'Aprenda a compartilhar novos comandos {% data variables.product.prodname_cli %} com outros usuários criando extensões personalizadas para {% data variables.product.prodname_cli %}.' +title: Creating GitHub CLI extensions +intro: 'Learn how to share new {% data variables.product.prodname_cli %} commands with other users by creating custom extensions for {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -10,43 +10,43 @@ topics: - CLI --- -## Sobre extensões de {% data variables.product.prodname_cli %} +## About {% data variables.product.prodname_cli %} extensions -{% data reusables.cli.cli-extensions %} Para obter mais informações sobre como usar as extensões de {% data variables.product.prodname_cli %}, consulte "[Usando extensões de {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)". +{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)." -É necessário um repositório para cada extensão que você criar. O nome do repositório deve iniciar com `gh-`. O restante do nome do repositório é o nome da extensão. Na raiz do repositório, deve haver um arquivo executável com o mesmo nome do repositório. Este arquivo será executado quando a extensão for chamada. +You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. At the root of the repository, there must be an executable file with the same name as the repository. This file will be executed when the extension is invoked. {% note %} -**Observação**: Recomendamos que o arquivo executável seja um script de bash, porque bash é um intérprete amplamente disponível. Você pode usar scripts que não são de bash, mas o usuário deverá ter o intérprete necessário instalado para usar a extensão. +**Note**: We recommend that the executable file is a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. {% endnote %} -## Criando uma extensão com `gh extension create` +## Creating an extension with `gh extension create` -Você pode usar o comando `gh extension create` para criar um projeto para sua extensão, incluindo um script de bash que contém um código inicial. +You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code. -1. Configure uma nova extensão usando a o subcomando `gh extension create`. Substitua `EXTENSION-NAME` pelo nome da sua extensão. +1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension. ```shell gh extension create EXTENSION-NAME ``` -1. Siga as instruções impressas para finalizar e, opcionalmente, publicar sua extensão. +1. Follow the printed instructions to finalize and optionally publish your extension. -## Criando uma extensão manualmente +## Creating an extension manually -1. Crie um diretório local denominado `gh-EXTENSION-NAME` para a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `gh-whoami`. +1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`. -1. No diretório que você criou, adicione um arquivo executável com o mesmo nome do diretório. +1. In the directory that you created, add an executable file with the same name as the directory. {% note %} - **Observação:** Certifique-se de que seu arquivo seja executável. No Unix, você pode executar `chmod +x file_name` na linha de comando para tornar `file_name` executável. No Windows, você pode executar `git init -b main`, `git add file_name` e, em seguida, `git update-index --chmod=+x file_name`. + **Note:** Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`. {% endnote %} -1. Escreva seu script no arquivo executável. Por exemplo: +1. Write your script in the executable file. For example: ```bash #!/usr/bin/env bash @@ -54,43 +54,35 @@ Você pode usar o comando `gh extension create` para criar um projeto para sua e exec gh api user --jq '"You are @\(.login) (\(.name))."' ``` -1. No seu diretório, instale a extensão como uma extensão local. +1. From your directory, install the extension as a local extension. ```bash gh extension install . ``` -1. Verifique se sua extensão funciona. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `whoami`. +1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`. ```shell gh EXTENSION-NAME ``` -1. No seu diretório, crie um repositório para publicar a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão. +1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension. ```shell git init -b main - gh repo create gh-EXTENSION-NAME --confirm - git add . && git commit -m "initial commit" && git push --set-upstream origin main + git add . && git commit -m "initial commit" + gh repo create gh-EXTENSION-NAME --source=. --public --push ``` -1. Opcionalmente, para ajudar outros usuários a descobrir sua extensão, adicione o tópico do repositório `gh-extension`. Isso fará com que a extensão apareça na página do tópico de +1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)." -`gh-extension`. Para obter mais informações sobre como adicionar um tópico do repositório, consulte "[Classificando seu repositório com tópicos](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)".

    - - +## Tips for writing {% data variables.product.prodname_cli %} extensions -## Dicas para escrever extensões de {% data variables.product.prodname_cli %} - - - -### Manipulando argumentos e sinalizadores - -Todos os argumentos de linha de comando após um `gh my-extension-name` serão passados para o script da extensão. Em um script de bash, você pode fazer referência a argumentos com `$1`, `$2`, etc. Você pode usar argumentos para inserir o usuário ou modificar o comportamento do script. - -Por exemplo, este script manipula vários sinalizadores. Quando o script é chamado com o sinalizador `-h` ou `--help` flag, o script imprime texto ao invés de continuar a execução. Quando o script é chamado com o o sinalizador `--name`, o script define o próximo valor após o sinalizador para `name_arg`. Quando o script é chamado com o sinalizador `--verbose`, o script imprime uma saudação diferente. +### Handling arguments and flags +All command line arguments following a `gh my-extension-name` command will be passed to the extension script. In a bash script, you can reference arguments with `$1`, `$2`, etc. You can use arguments to take user input or to modify the behavior of the script. +For example, this script handles multiple flags. When the script is called with the `-h` or `--help` flag, the script prints help text instead of continuing execution. When the script is called with the `--name` flag, the script sets the next value after the flag to `name_arg`. When the script is called with the `--verbose` flag, the script prints a different greeting. ```bash #!/usr/bin/env bash @@ -126,55 +118,36 @@ else fi ``` +### Calling core commands in non-interactive mode +Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments. - -### Chamar comandos do núcleo em modo não interativo - -Alguns comandos principais de {% data variables.product.prodname_cli %} principais pedirão entrada ao usuário. Ao escrever com esses comandos, a instrução é frequentemente indesejável. Para evitar a instrução, forneça a informação necessária explicitamente por meio de argumentos. - -Por exemplo, para criar um problema de modo programático, especifique o título e o texto: - - +For example, to create an issue programmatically, specify the title and body: ```bash gh issue create --title "My Title" --body "Issue description" ``` +### Fetching data programatically - - -### Buscando dados programaticamente - -Muitos comandos principais são compatíveis o sinalizador `--json` para obter dados programaticamente. Por exemplo, para retornar um objeto JSON listando o número, título e status de mesclabilidade dos pull requests: - - +Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests: ```bash gh pr list --json number,title,mergeStateStatus ``` - -Se não houver um comando do núcleo para buscar dados específicos do GitHub, você poderá usar o comando [`gh api`](https://cli.github.com/manual/gh_api) para acessar a API do GitHub. Por exemplo, para obter informações sobre o usuário atual: - - +If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user: ```bash gh api user ``` - -Todos os comandos que os dados JSON de saída também têm opções para filtrar esses dados em algo mais imediatamente utilizável por scripts. Por exemplo, para obter o nome do usuário atual: - - +All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name: ```bash gh api user --jq '.name' ``` +For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting). -Para obter mais informações, consulte [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting). +## Next steps - - -## Próximas etapas - -Para ver mais exemplos de extensões {% data variables.product.prodname_cli %}, consulte [repositórios com o tópico de extensão `gh-extension`](https://github.com/topics/gh-extension). +To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension). diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md index f97f37cba3..a0bd851731 100644 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md +++ b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md @@ -1,6 +1,6 @@ --- -title: Sobre integrações -intro: 'As integrações são ferramentas e serviços que se conectam ao {% data variables.product.product_name %} para complementar e estender o fluxo de trabalho.' +title: About integrations +intro: 'Integrations are tools and services that connect with {% data variables.product.product_name %} to complement and extend your workflow.' redirect_from: - /articles/about-integrations - /github/customizing-your-github-workflow/about-integrations @@ -8,35 +8,34 @@ versions: fpt: '*' ghec: '*' --- +You can install integrations in your personal account or organizations you own. You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization. -Você pode instalar integrações em sua conta pessoal ou em organizações que possui. Você também pode instalar {% data variables.product.prodname_github_apps %} a partir de um repositório específico em um repositório específico em que você tem permissões de administrador ou que pertencem à sua organização. - -## Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} +## Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs or webhooks. -{% data variables.product.prodname_github_apps %} oferecem permissões granulares e solicitam acesso apenas ao que o aplicativo precisa. {% data variables.product.prodname_github_apps %} também oferece permissões específicas no nível de usuário que cada um deve autorizar individualmente quando um aplicativo está instalado ou quando o integrador altera as permissões solicitadas pelo aplicativo. +{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_github_apps %} also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app. -Para obter mais informações, consulte: -- "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" -- "[Sobre aplicativos](/apps/about-apps/)" -- "[Permissões de nível de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)" -- "[Autorizar {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" -- "[Autorizar {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" -- "[Revisar integrações autorizadas](/articles/reviewing-your-authorized-integrations/)" +For more information, see: +- "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" +- "[About apps](/apps/about-apps/)" +- "[User-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)" +- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" +- "[Authorizing {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" +- "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations/)" -Será possível instalar um {% data variables.product.prodname_github_app %} pré-configurado se os integradores ou criadores de app tiverem criado o respectivo app com o fluxo de manifesto do {% data variables.product.prodname_github_app %}. Para obter informações sobre como executar o {% data variables.product.prodname_github_app %} com configuração automatizada, entre em contato com o integrador ou criador do app. +You can install a preconfigured {% data variables.product.prodname_github_app %}, if the integrators or app creators have created their app with the {% data variables.product.prodname_github_app %} manifest flow. For information about how to run your {% data variables.product.prodname_github_app %} with automated configuration, contact the integrator or app creator. -Você poderá criar um {% data variables.product.prodname_github_app %} com configuração simplificada se usar o Probot. Para obter mais informações, consulte o site de [documentos do Probot](https://probot.github.io/docs/). +You can create a {% data variables.product.prodname_github_app %} with simplified configuration if you build your app with Probot. For more information, see the [Probot docs](https://probot.github.io/docs/) site. -## Descobrir integrações no {% data variables.product.prodname_marketplace %} +## Discovering integrations in {% data variables.product.prodname_marketplace %} -É possível encontrar uma integração para instalar ou publicar a sua própria integração no {% data variables.product.prodname_marketplace %}. +You can find an integration to install or publish your own integration in {% data variables.product.prodname_marketplace %}. -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contém {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}. Para obter mais informações sobre como encontrar uma integração ou criar sua própria integração, consulte "[Sobre o {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. For more information on finding an integration or creating your own integration, see "[About {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)." -## Integrações compradas diretamente de integradores +## Integrations purchased directly from integrators -Você também pode comprar algumas integrações diretamente de integradores. Como um integrante da organização, ao encontrar um {% data variables.product.prodname_github_app %} que queira usar, você poderá solicitar que uma organização aprove e instale o app para a organização. +You can also purchase some integrations directly from integrators. As an organization member, if you find a {% data variables.product.prodname_github_app %} that you'd like to use, you can request that an organization approve and install the app for the organization. -Se você tiver permissões de administrador para todos os repositórios de organizações em que o app está instalado, você poderá instalar {% data variables.product.prodname_github_apps %} com permissões de nível de repositório sem ter que solicitar que o proprietário da organização aprove o aplicativo. Quando um integrador altera as permissões do app, se as permissões forem apenas para um repositório, os proprietários da organização e as pessoas com permissões de administrador para um repositório com esse app instalado poderão revisar e aceitar as novas permissões. +If you have admin permissions for all organization-owned repositories the app is installed on, you can install {% data variables.product.prodname_github_apps %} with repository-level permissions without having to ask an organization owner to approve the app. When an integrator changes an app's permissions, if the permissions are for a repository only, organization owners and people with admin permissions to a repository with that app installed can review and accept the new permissions. diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md deleted file mode 100644 index 90cbbc369d..0000000000 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Extensões e integrações do GitHub -intro: 'Use extensões {% data variables.product.product_name %} para trabalhar com facilidade nos repositórios {% data variables.product.product_name %} dentro de aplicativos de terceiros.' -redirect_from: - - /articles/about-github-extensions-for-third-party-applications/ - - /articles/github-extensions-and-integrations - - /github/customizing-your-github-workflow/github-extensions-and-integrations -versions: - fpt: '*' - ghec: '*' -shortTitle: Extensões & integrações ---- - -## Ferramentas de edição - -Você pode conectar-se aos repositórios de {% data variables.product.product_name %} de ferramentas de editores de terceiros, como o Atom, Unity e o Visual Studio. - -### {% data variables.product.product_name %} para Atom - -É possível fazer commits, push, pull, resolver conflitos de merge e mais no editor Atom, usando a extensão {% data variables.product.product_name %} para Atom. Para obter mais informações, consulte o site oficial [{% data variables.product.product_name %} para Atom](https://github.atom.io/). - -### {% data variables.product.product_name %} para Unity - -Você pode desenvolver em Unity, a plataforma de desenvolvimento de jogos de código aberto, e ver seu trabalho em {% data variables.product.product_name %}, usando a extensão de editor {% data variables.product.product_name %} para Unity. Para obter mais informações, consulte o [site](https://unity.github.com/) oficial da extensão de editor Unity ou a [documentação](https://github.com/github-for-unity/Unity/tree/master/docs). - -### {% data variables.product.product_name %} para Visual Studio - -A extensão {% data variables.product.product_name %} para Visual Studio, permite que você trabalhe em repositórios {% data variables.product.product_name %} sem sair do Visual Studio. Para obter mais informações, consulte o [site](https://visualstudio.github.com/) oficial da extensão Visual Studio ou a [documentação](https://github.com/github/VisualStudio/tree/master/docs). - -### {% data variables.product.prodname_dotcom %} para Visual Studio Code - -É possível revisar e gerenciar pull requests {% data variables.product.product_name %} no Visual Studio Code com a extensão {% data variables.product.prodname_dotcom %} para Visual Studio Code. Para obter mais informações, consulte o [site](https://vscode.github.com/) oficial da extensão Visual Studio Code ou a [documentação](https://github.com/Microsoft/vscode-pull-request-github). - -## Ferramentas de gerenciamento de projetos - -You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira. - -### Integração Jira Cloud e {% data variables.product.product_name %}.com - -É possível integrar o Jira Cloud à sua conta pessoal ou de sua organização para analisar commits e pull requests e criar metadados e hyperlinks relevantes em qualquer problema mencionado no Jira. Para obter mais informações, visite o [aplicativo de integração do Jira](https://github.com/marketplace/jira-software-github) no marketplace. - -## Ferramentas de comunicação de equipe - -You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams. - -### Integração com Slack e {% data variables.product.product_name %} - -Você pode assinar os seus repositórios ou organizações e receber atualizações em tempo real sobre problemas, pull requests, commits, versões, análises de implantação e status da implantação. Você também pode realizar atividades como problemas fechados ou abertos e fornecer referências enriquecidas para problemas e pull requests sem sair do Slack. Para obter mais informações, visite o [aplicativo de integração do Slack](https://github.com/marketplace/slack-github) no Marketplace. - -### Integração com o Microsoft Teams e {% data variables.product.product_name %} - -Você pode assinar os seus repositórios ou organizações e receber atualizações em tempo real sobre problemas, pull requests, commits, análises de implantação e status da implantação. Você também pode realizar atividades como fechar ou abrir problemas, comentar nos seus problemas e fornecer referências enriquecidas para problemas e pull requests sem sair do Microsoft Teams. Para obter mais informações, acesse o [aplicativo de integração do Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) no Microsoft AppSource. diff --git a/translations/pt-BR/content/github/extending-github/about-webhooks.md b/translations/pt-BR/content/github/extending-github/about-webhooks.md index 1831eabc21..427f5d57d0 100644 --- a/translations/pt-BR/content/github/extending-github/about-webhooks.md +++ b/translations/pt-BR/content/github/extending-github/about-webhooks.md @@ -1,11 +1,11 @@ --- -title: Sobre webhooks +title: About webhooks redirect_from: - /post-receive-hooks/ - /articles/post-receive-hooks/ - /articles/creating-webhooks/ - /articles/about-webhooks -intro: Webhooks permitem que notificações sejam entregues a um servidor web externo sempre que determinadas ações ocorrem em um repositório ou uma organização. +intro: Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization. versions: fpt: '*' ghes: '*' @@ -15,17 +15,17 @@ versions: {% tip %} -**Dica:** {% data reusables.organizations.owners-and-admins-can %} gerenciar webhooks para uma organização. {% data reusables.organizations.new-org-permissions-more-info %} +**Tip:** {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %} {% endtip %} -Os webhooks podem ser acionados sempre que uma variedade de ações for executada em um repositório ou uma organização. Por exemplo, você pode configurar um webhook para ser executado sempre que: +Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever: -* É feito push de um repositório -* Uma pull request é aberta -* Um site do {% data variables.product.prodname_pages %} é construído -* Um novo integrante é adicionado a uma equipe +* A repository is pushed to +* A pull request is opened +* A {% data variables.product.prodname_pages %} site is built +* A new member is added to a team Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. -Para configurar um novo webhook, você deverá acessar um servidor externo e ter familiaridade com os procedimentos técnicos envolvidos. Para obter ajuda sobre como criar um webhook, incluindo uma lista completa de ações que podem ser associadas a ele, consulte "[Webhooks](/webhooks)." +To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "[Webhooks](/webhooks)." diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md index bcf3ba3452..5011d23fb9 100644 --- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -1,6 +1,6 @@ --- -title: Adicionar um projeto existente ao GitHub usando a linha de comando -intro: 'Colocar um trabalho que já existe no {% data variables.product.product_name %} pode permitir que você compartilhe e colabore de muitas maneiras.' +title: Adding an existing project to GitHub using the command line +intro: 'Putting your existing work on {% data variables.product.product_name %} can let you share and collaborate in lots of great ways.' redirect_from: - /articles/add-an-existing-project-to-github/ - /articles/adding-an-existing-project-to-github-using-the-command-line @@ -10,79 +10,74 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Adicionar um projeto localmente +shortTitle: Add a project locally --- -## Sobre a adição de projetos existentes para {% data variables.product.product_name %} +## About adding existing projects to {% data variables.product.product_name %} {% tip %} -**Dica:** se estiver mais familiarizado com uma interface de usuário de apontar e clicar, tente adicionar seu projeto com o {% data variables.product.prodname_desktop %}. Para obter mais informações, consulte "[Adicionar um repositório do seu computador local ao GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" na Ajuda do *{% data variables.product.prodname_desktop %}*. +**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*. {% endtip %} {% data reusables.repositories.sensitive-info-warning %} -## Adicionando um projeto a {% data variables.product.product_name %} com {% data variables.product.prodname_cli %} +## Adding a project to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %} -{% data variables.product.prodname_cli %} é uma ferramenta de código aberto para usar {% data variables.product.prodname_dotcom %} a partir da linha de comando do seu computador. {% data variables.product.prodname_cli %} pode simplificar o processo de adicionar um projeto existente a {% data variables.product.product_name %} usando a linha de comando. Para saber mais sobre {% data variables.product.prodname_cli %}, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -1. Na linha de comando, acesse o diretório raiz do seu projeto. -1. Inicialize o diretório local como um repositório Git. +1. In the command line, navigate to the root directory of your project. +1. Initialize the local directory as a Git repository. ```shell git init -b main ``` -1. Para criar um repositório para o seu projeto em {% data variables.product.product_name %}, use o subcomando `gh repo create`. Substitua `project-name` pelo nome desejado para o repositório. Se você quiser que o seu projeto pertença a uma organização em vez de sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`. +1. Stage and commit all the files in your project ```shell - gh repo create project-name + git add . && git commit -m "initial commit" ``` -1. Siga as instruções interativas. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_repo_create). -1. Faça pull das alterações do novo repositório que você criou. (Se você criou um arquivo `.gitignore` ou `LICENSE` na etapa anterior, isso irá fazer pull dessas alterações para seu diretório local.) +1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`. + +1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch. - ```shell - git pull --set-upstream origin main - ``` +1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create). -1. Stage, commit e push de todos os arquivos do seu projeto. - - ```shell - git add . && git commit -m "initial commit" && git push - ``` - -## Adicionando um projeto a {% data variables.product.product_name %} sem {% data variables.product.prodname_cli %} +## Adding a project to {% data variables.product.product_name %} without {% data variables.product.prodname_cli %} {% mac %} -1. [Crie um repositório ](/repositories/creating-and-managing-repositories/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com os arquivos *README*, de licença ou `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. ![Menu suspenso Create New Repository (Criar novo repositório)](/assets/images/help/repository/repo-create.png) +1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. Altere o diretório de trabalho atual referente ao seu projeto local. -4. Inicialize o diretório local como um repositório Git. +3. Change the current working directory to your local project. +4. Initialize the local directory as a Git repository. ```shell $ git init -b main ``` -5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit. +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . - # Adiciona os arquivos no repositório local e faz stage deles para commit. {% data reusables.git.unstage-codeblock %} + # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. Faça commit dos arquivos com stage em seu repositório local. +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. No Terminal, [adicione a URL para o repositório remote](/github/getting-started-with-github/managing-remote-repositories) onde será feito push do seu repositório local. +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) (Faça push das alterações no seu repositório local para o {% data variables.product.product_location %}. +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}. ```shell $ git push -u origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -92,32 +87,34 @@ shortTitle: Adicionar um projeto localmente {% windows %} -1. [Crie um repositório ](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com os arquivos *README*, de licença ou `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. ![Menu suspenso Create New Repository (Criar novo repositório)](/assets/images/help/repository/repo-create.png) +1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. Altere o diretório de trabalho atual referente ao seu projeto local. -4. Inicialize o diretório local como um repositório Git. +3. Change the current working directory to your local project. +4. Initialize the local directory as a Git repository. ```shell $ git init -b main ``` -5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit. +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . - # Adiciona os arquivos no repositório local e faz stage deles para commit. {% data reusables.git.unstage-codeblock %} + # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. Faça commit dos arquivos com stage em seu repositório local. +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. No prompt de comando, [adicione a URL para o repositório remote](/github/getting-started-with-github/managing-remote-repositories) onde será feito push do seu repositório local. +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) (Faça push das alterações no seu repositório local para o {% data variables.product.product_location %}. +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}. ```shell $ git push origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -127,32 +124,34 @@ shortTitle: Adicionar um projeto localmente {% linux %} -1. [Crie um repositório ](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com os arquivos *README*, de licença ou `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. ![Menu suspenso Create New Repository (Criar novo repositório)](/assets/images/help/repository/repo-create.png) +1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. Altere o diretório de trabalho atual referente ao seu projeto local. -4. Inicialize o diretório local como um repositório Git. +3. Change the current working directory to your local project. +4. Initialize the local directory as a Git repository. ```shell $ git init -b main ``` -5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit. +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . - # Adiciona os arquivos no repositório local e faz stage deles para commit. {% data reusables.git.unstage-codeblock %} + # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. Faça commit dos arquivos com stage em seu repositório local. +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. No Terminal, [adicione a URL para o repositório remote](/github/getting-started-with-github/managing-remote-repositories) onde será feito push do seu repositório local. +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) (Faça push das alterações no seu repositório local para o {% data variables.product.product_location %}. +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}. ```shell $ git push origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -160,6 +159,6 @@ shortTitle: Adicionar um projeto localmente {% endlinux %} -## Leia mais +## Further reading -- "[Adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" +- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index fbafd9ee9b..b1ca69a0dc 100644 --- a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -1,6 +1,6 @@ --- -title: Sintaxe básica de escrita e formatação no GitHub -intro: Crie formatação sofisticada para narração e código no GitHub com sintaxe simples. +title: Basic writing and formatting syntax +intro: Create sophisticated formatting for your prose and code on GitHub with simple syntax. redirect_from: - /articles/basic-writing-and-formatting-syntax - /github/writing-on-github/basic-writing-and-formatting-syntax @@ -9,65 +9,64 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Sintaxe de formatação básica +shortTitle: Basic formatting syntax --- +## Headings -## Títulos - -Para criar um título, adicione de um a seis símbolos `#` antes do texto do título. O número de `#` que você usa determinará o tamanho do título. +To create a heading, add one to six `#` symbols before your heading text. The number of `#` you use will determine the size of the heading. ```markdown -# O título maior -## O segundo maior título -###### O título menor +# The largest heading +## The second largest heading +###### The smallest heading ``` -![Títulos H1, H2 e H6 renderizados](/assets/images/help/writing/headings-rendered.png) +![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png) -## Estilizar texto +## Styling text -Você pode indicar ênfase com texto em negrito, itálico ou riscado em campos de comentários e arquivos de `.md`. +You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files. -| Estilo | Sintaxe | Atalho | Exemplo | Resultado | -| -------------------------- | ------------------ | ------------------- | -------------------------------------------- | ------------------------------------------ | -| Negrito | `** **` ou `__ __` | command/control + b | `**Esse texto está em negrito**` | **Esse texto está em negrito** | -| Itálico | `* *` ou `_ _` | command/control + i | `*Esse texto está em itálico*` | *Esse texto está em itálico* | -| Tachado | `~~ ~~` | | `~~Esse texto estava errado~~` | ~~Esse texto estava errado~~ | -| Negrito e itálico aninhado | `** **` e `_ _` | | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** | -| Todo em negrito e itálico | `*** ***` | | `***Todo esse texto é importante***` | ***Todo esse texto é importante*** | +| Style | Syntax | Keyboard shortcut | Example | Output | +| --- | --- | --- | --- | --- | +| Bold | `** **` or `__ __` | command/control + b | `**This is bold text**` | **This is bold text** | +| Italic | `* *` or `_ _` | command/control + i | `*This text is italicized*` | *This text is italicized* | +| Strikethrough | `~~ ~~` | | `~~This was mistaken text~~` | ~~This was mistaken text~~ | +| Bold and nested italic | `** **` and `_ _` | | `**This text is _extremely_ important**` | **This text is _extremely_ important** | +| All bold and italic | `*** ***` | | `***All this text is important***` | ***All this text is important*** | -## Citar texto +## Quoting text -Você pode citar texto com um `>`. +You can quote text with a `>`. ```markdown -Texto que não é uma citação +Text that is not a quote -> Texto que é uma citação +> Text that is a quote ``` -![Texto citado renderizado](/assets/images/help/writing/quoted-text-rendered.png) +![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png) {% tip %} -**Dica:** ao exibir uma conversa, você pode citar textos automaticamente em um comentário destacando o texto e digitando `r`. É possível citar um comentário inteiro clicando em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Quote reply** (Resposta à citação). Para obter mais informações sobre atalhos de teclado, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts/)". +**Tip:** When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing `r`. You can quote an entire comment by clicking {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Quote reply**. For more information about keyboard shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts/)." {% endtip %} -## Citar código +## Quoting code -Você pode chamar código ou um comando em uma frase com aspas simples. O texto entre aspas simples não será formatado.{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} Você também pode pressionar o comando `` ou `Ctrl` + `e` o atalho do teclado para inserir as aspas simples para um bloco de código dentro de uma linha de Markdown.{% endif %} +You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %} ```markdown -Use 'git status' para listar todos os arquivos novos ou modificados que ainda não receberam commit. +Use `git status` to list all new or modified files that haven't yet been committed. ``` -![Bloco de código inline renderizado](/assets/images/help/writing/inline-code-rendered.png) +![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png) -Para formatar código ou texto no próprio bloco distinto, use aspas triplas. +To format code or text into its own distinct block, use triple backticks. 
    -Alguns comandos Git básicos são:
+Some basic Git commands are:
 ```
 git status
 git add
@@ -75,70 +74,82 @@ git commit
 ```
    -![Bloco de código renderizado](/assets/images/help/writing/code-block-rendered.png) +![Rendered code block](/assets/images/help/writing/code-block-rendered.png) -Para obter mais informações, consulte "[Criar e destacar blocos de código](/articles/creating-and-highlighting-code-blocks)". +For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)." ## Links -Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` e, em seguida, o URL entre parênteses `( )`. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %} +You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %} -`Este site foi construído usando [GitHub Pages](https://pages.github.com/).` +`This site was built using [GitHub Pages](https://pages.github.com/).` -![Link renderizado](/assets/images/help/writing/link-rendered.png) +![Rendered link](/assets/images/help/writing/link-rendered.png) {% tip %} -**Dica:** o {% data variables.product.product_name %} cria links automaticamente quando URLs válidos são escritos em um comentário. Para obter mais informações, consulte "[Referências e URLs vinculados automaticamente](/articles/autolinked-references-and-urls)". +**Tip:** {% data variables.product.product_name %} automatically creates links when valid URLs are written in a comment. For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)." {% endtip %} -## Links de seção +## Section links {% data reusables.repositories.section-links %} -## Links relativos +## Relative links {% data reusables.repositories.relative-links %} -## Imagens +## Images -Você pode exibir uma imagem adicionando `!` e por o texto alternativo em`[ ]`. Em seguida, coloque o link da imagem entre parênteses `()`. +You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then wrap the link for the image in parentheses `()`. -`![Isso é uma imagem](https://myoctocat.com/assets/images/base-octocat.svg)` +`![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)` -![Imagem interpretada](/assets/images/help/writing/image-rendered.png) +![Rendered Image](/assets/images/help/writing/image-rendered.png) -{% data variables.product.product_name %} é compatível com a incorporação de imagens nos seus problemas, pull requests{% ifversion fpt or ghec %}, discussões{% endif %}, comentários e arquivos `.md`. Você pode exibir uma imagem do seu repositório, adicionar um link para uma imagem on-line ou fazer o upload de uma imagem. Para obter mais informações, consulte[Fazer o upload de ativos](#uploading-assets)". +{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt or ghec %}, discussions{% endif %}, comments and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)." {% tip %} -**Dica:** quando você quiser exibir uma imagem que está no seu repositório, você deverá usar links relativos em vez de links absolutos. +**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. {% endtip %} -Aqui estão alguns exemplos para usar links relativos para exibir uma imagem. +Here are some examples for using relative links to display an image. -| Contexto | Link relativo | -| -------------------------------------------------------------- | ---------------------------------------------------------------------- | -| Em um arquivo `.md` no mesmo branch | `/assets/images/electrocat.png` | -| Em um arquivo `.md` em outro branch | `/../main/assets/images/electrocat.png` | -| Em problemas, pull requests e comentários do repositório | `../blob/main/assets/images/electrocat.png` | -| Em um arquivo `.md` em outro repositório | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | -| Em problemas, pull requests e comentários de outro repositório | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | +| Context | Relative Link | +| ------ | -------- | +| In a `.md` file on the same branch | `/assets/images/electrocat.png` | +| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` | +| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` | +| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | +| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | {% note %} -**Observação**: Os dois últimos links relativos na tabela acima funcionarão para imagens em um repositório privado somente se o visualizador tiver pelo menos acesso de leitura ao repositório privado que contém essas imagens. +**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images. {% endnote %} -Para obter mais informações, consulte[Links relativos,](#relative-links)." +For more information, see "[Relative Links](#relative-links)." +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5559 %} +### Specifying the theme an image is shown to -## Listas +You can specify the theme an image is displayed to by appending `#gh-dark-mode-only` or `#gh-light-mode-only` to the end of an image URL, in Markdown. -Você pode criar uma lista não ordenada precedendo uma ou mais linhas de texto com `-` ou `*`. +We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images. + +| Context | URL | +|--------|--------| +| Dark Theme | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` | +| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)` | +{% endif %} + +## Lists + +You can make an unordered list by preceding one or more lines of text with `-` or `*`. ```markdown - George Washington @@ -146,9 +157,9 @@ Você pode criar uma lista não ordenada precedendo uma ou mais linhas de texto - Thomas Jefferson ``` -![Lista não ordenada renderizada](/assets/images/help/writing/unordered-list-rendered.png) +![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png) -Para ordenar a lista, coloque um número na frente de cada linha. +To order your list, precede each line with a number. ```markdown 1. James Madison @@ -156,126 +167,126 @@ Para ordenar a lista, coloque um número na frente de cada linha. 3. John Quincy Adams ``` -![Lista ordenada renderizada](/assets/images/help/writing/ordered-list-rendered.png) +![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png) -### Listas aninhadas +### Nested Lists -Você pode criar uma lista aninhada recuando um ou mais itens da lista abaixo de outro item. +You can create a nested list by indenting one or more list items below another item. -Para criar uma lista aninhada usando o editor web do {% data variables.product.product_name %} ou um editor de texto que usa uma fonte monoespaçada, como o [Atom](https://atom.io/), você pode alinhar sua lista visualmente. Digite caracteres de espaço na fonte do item da lista aninhada, até que o caractere de marcador da lista (`-` ou `*`) fique diretamente abaixo do primeiro caractere do texto no item acima dele. +To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [Atom](https://atom.io/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (`-` or `*`) lies directly below the first character of the text in the item above it. ```markdown -1. Primeiro item da lista - - Primeiro item de lista aninhado - - Segundo item de lista aninhada +1. First list item + - First nested list item + - Second nested list item ``` -![Lista aninhada com alinhamento destacado](/assets/images/help/writing/nested-list-alignment.png) +![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png) -![Lista com dois níveis de itens aninhados](/assets/images/help/writing/nested-list-example-1.png) +![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png) -Para criar uma lista aninhada no editor de comentários do {% data variables.product.product_name %}, que não usa uma fonte monoespaçada, você pode observar o item da lista logo acima da lista aninhada e contar o número de caracteres que aparecem antes do conteúdo do item. Em seguida, digite esse número de caracteres de espaço na fonte do item da linha aninhada. +To create a nested list in the comment editor on {% data variables.product.product_name %}, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item. -Neste exemplo, você pode adicionar um item de lista aninhada abaixo do item de lista `100. Primeiro item da lista` recuando o item da lista aninhada com no mínimo cinco espaços, uma vez que há cinco caracteres (`100.`) antes de `Primeiro item da lista`. +In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100. `) before `First list item`. ```markdown -100. Primeiro item da lista - - Primeiro item da lista aninhada +100. First list item + - First nested list item ``` -![Lista com um item de lista aninhada](/assets/images/help/writing/nested-list-example-3.png) +![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png) -Você pode criar vários níveis de listas aninhadas usando o mesmo método. Por exemplo, como o primeiro item da lista aninhada tem sete caracteres (`␣␣␣␣␣-␣`) antes do conteúdo da lista aninhada `Primeiro item da lista aninhada`, você precisaria recuar o segundo item da lista aninhada com sete espaços. +You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown -100. Primeiro item da lista - - Primeiro item da lista aninhada - - Segundo item da lista aninhada +100. First list item + - First nested list item + - Second nested list item ``` -![Lista com dois níveis de itens aninhados](/assets/images/help/writing/nested-list-example-2.png) +![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png) -Para obter mais exemplos, consulte a [Especificação de markdown em estilo GitHub](https://github.github.com/gfm/#example-265). +For more examples, see the [GitHub Flavored Markdown Spec](https://github.github.com/gfm/#example-265). -## Listas de tarefas +## Task lists {% data reusables.repositories.task-list-markdown %} -Se a descrição de um item da lista de tarefas começar com parênteses, você precisará usar a `\` para escape: +If a task list item description begins with a parenthesis, you'll need to escape it with `\`: -`- [ ] \(Optional) Abrir um problema de acompanhamento` +`- [ ] \(Optional) Open a followup issue` -Para obter mais informações, consulte "[Sobre listas de tarefas](/articles/about-task-lists)". +For more information, see "[About task lists](/articles/about-task-lists)." -## Mencionar pessoas e equipes +## Mentioning people and teams -Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando `@` mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. Para obter mais informações, sobre notificações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications)"{% endif %}." +You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing `@` plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." -`@github/suporte O que você acha dessas atualizações?` +`@github/support What do you think about these updates?` -![@menção renderizada](/assets/images/help/writing/mention-rendered.png) +![Rendered @mention](/assets/images/help/writing/mention-rendered.png) -Quando você menciona uma equipe principal, os integrantes de suas equipes secundárias também recebem notificações, simplificando a comunicação com vários grupos de pessoas. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)". +When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "[About teams](/articles/about-teams)." -Digitar um símbolo `@` chamará uma lista de pessoas ou equipes em um projeto. A lista é filtrada à medida que você digita. Portanto, assim que você achar o nome da pessoa ou da equipe que está procurando, use as teclas de seta para selecioná-lo e pressione tab ou enter para completar o nome. Para equipes, digite nome da @organização/equipe e todos os integrantes dessa equipe serão inscritos na conversa. +Typing an `@` symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation. -Os resultados do preenchimento automático são restritos aos colaboradores do repositório e qualquer outro participante no thread. +The autocomplete results are restricted to repository collaborators and any other participants on the thread. -## Fazer referências a problemas e pull requests +## Referencing issues and pull requests -Você pode trazer à tona uma lista de problemas e pull requests sugeridos no repositório digitando `#`. Digite o número ou o título do problema ou da pull request para filtrar a lista e, em seguida, pressione tab ou enter para completar o resultado destacado. +You can bring up a list of suggested issues and pull requests within the repository by typing `#`. Type the issue or pull request number or title to filter the list, and then press either tab or enter to complete the highlighted result. -Para obter mais informações, consulte "[Referências e URLs vinculados automaticamente](/articles/autolinked-references-and-urls)". +For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)." -## Fazer referência a recursos externos +## Referencing external resources {% data reusables.repositories.autolink-references %} -## Anexos de conteúdo +## Content attachments -Alguns {% data variables.product.prodname_github_apps %} fornecem informações em {% data variables.product.product_name %} para URLs vinculadas aos seus domínios registrados. O {% data variables.product.product_name %} renderiza as informações fornecidas pelo app sob o URL no texto ou comentário de um problema ou uma pull request. +Some {% data variables.product.prodname_github_apps %} provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} renders the information provided by the app under the URL in the body or comment of an issue or pull request. -![Anexo de conteúdo](/assets/images/github-apps/content_reference_attachment.png) +![Content attachment](/assets/images/github-apps/content_reference_attachment.png) -Para visualizar anexos de conteúdo, você deverá ter um {% data variables.product.prodname_github_app %} que use a API de Anexos de Conteúdo instalada no repositório.{% ifversion fpt or ghec %} Para obter mais informações, consulte "[Instalar um aplicativo na sua conta pessoal](/articles/installing-an-app-in-your-personal-account)" e "[Instalar um aplicativo na sua organização](/articles/installing-an-app-in-your-organization)".{% endif %} +To see content attachments, you must have a {% data variables.product.prodname_github_app %} that uses the Content Attachments API installed on the repository.{% ifversion fpt or ghec %} For more information, see "[Installing an app in your personal account](/articles/installing-an-app-in-your-personal-account)" and "[Installing an app in your organization](/articles/installing-an-app-in-your-organization)."{% endif %} -Os anexos de conteúdo não serão exibidos para URLs que fazem parte de um link markdown. +Content attachments will not be displayed for URLs that are part of a markdown link. -Para obter mais informações sobre como compilar um {% data variables.product.prodname_github_app %} que use anexos de conteúdo, consulte "[Usar anexos de conteúdo](/apps/using-content-attachments)". +For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)." -## Fazer upload de ativos +## Uploading assets -Você pode fazer upload de ativos como imagens, arrastando e soltando, fazendo a seleção a partir de um navegador de arquivos ou colando. É possível fazer o upload de recursos para problemas, pull requests, comentários e arquivos `.md` no seu repositório. +You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and `.md` files in your repository. -## Usar emoji +## Using emoji -Você pode adicionar emoji à sua escrita digitando `:EMOJICODE:`. +You can add emoji to your writing by typing `:EMOJICODE:`. -`@octocat :+1: Este PR parece ótimo - está pronto para o merge! :shipit:` +`@octocat :+1: This PR looks great - it's ready to merge! :shipit:` -![Emoji renderizado](/assets/images/help/writing/emoji-rendered.png) +![Rendered emoji](/assets/images/help/writing/emoji-rendered.png) -Digitar `:` trará à tona uma lista de emojis sugeridos. A lista será filtrada à medida que você digita. Portanto, assim que encontrar o emoji que estava procurando, pressione **Tab** ou **Enter** para completar o resultado destacado. +Typing `:` will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result. -Para obter uma lista completa dos emojis e códigos disponíveis, confira [a lista de emojis](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). -## Parágrafos +## Paragraphs -Você pode criar um parágrafo deixando uma linha em branco entre as linhas de texto. +You can create a new paragraph by leaving a blank line between lines of text. {% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} -## Notas de rodapé +## Footnotes -Você pode adicionar notas de rodapé ao seu conteúdo usando esta sintaxe entre colchetes: +You can add footnotes to your content by using this bracket syntax: ``` -Essa é uma simples nota de rodapé[^1]. +Here is a simple footnote[^1]. A footnote can also have multiple lines[^2]. You can also use words, to fit your writing style more closely[^note]. -[^1]: Minha referência. +[^1]: My reference. [^2]: Every new line should be prefixed with 2 spaces. This allows you to have a footnote with multiple lines. [^note]: @@ -283,9 +294,9 @@ You can also use words, to fit your writing style more closely[^note]. This footnote also has been made with a different syntax using 4 spaces for new lines. ``` -A nota de rodapé será interpretada da seguinte forma: +The footnote will render like this: -![Nota de rodapé interpretada](/assets/images/site/rendered-footnote.png) +![Rendered footnote](/assets/images/site/rendered-footnote.png) {% tip %} @@ -294,35 +305,35 @@ A nota de rodapé será interpretada da seguinte forma: {% endtip %} {% endif %} -## Ocultando o conteúdo com comentários +## Hiding content with comments -Você pode dizer a {% data variables.product.product_name %} para ocultar o conteúdo do markdown interpretado, colocando o conteúdo em um comentário HTML. +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. 
     <!-- This content will not appear in the rendered Markdown -->
    -## Ignorar formatação markdown +## Ignoring Markdown formatting -Você pode informar o {% data variables.product.product_name %} para ignorar (ou usar escape) a formatação markdown usando `\` antes do caractere markdown. +You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character. -`Vamos renomear \*our-new-project\* para \*our-old-project\*.` +`Let's rename \*our-new-project\* to \*our-old-project\*.` -![Caractere com escape renderizado](/assets/images/help/writing/escaped-character-rendered.png) +![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png) -Para obter mais informações, consulte "[Sintaxe markdown](https://daringfireball.net/projects/markdown/syntax#backslash)" de Daring Fireball. +For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)." {% ifversion fpt or ghes > 3.2 or ghae-issue-5232 or ghec %} -## Desabilitando a interpretação do Markdown +## Disabling Markdown rendering {% data reusables.repositories.disabling-markdown-rendering %} {% endif %} -## Leia mais +## Further reading -- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/) -- "[Sobre escrita e formatação no GitHub](/articles/about-writing-and-formatting-on-github)" -- "[Trabalhar com formatação avançada](/articles/working-with-advanced-formatting)" -- "[Dominar o markdown](https://guides.github.com/features/mastering-markdown/)" +- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) +- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)" +- "[Working with advanced formatting](/articles/working-with-advanced-formatting)" +- "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/)" diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md index cf99142b29..48cb432198 100644 --- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md @@ -1,6 +1,6 @@ --- -title: Trabalhar com formatação avançada -intro: 'A formatação (como tabelas, realce de sintaxe e vinculação automática) permite organizar informações complexas de forma clara em pull requests, problemas e comentários.' +title: Working with advanced formatting +intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.' redirect_from: - /articles/working-with-advanced-formatting versions: @@ -10,11 +10,12 @@ versions: ghec: '*' children: - /organizing-information-with-tables + - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet - /using-keywords-in-issues-and-pull-requests -shortTitle: Trabalhar com formatação avançada +shortTitle: Work with advanced formatting --- diff --git a/translations/pt-BR/content/graphql/guides/index.md b/translations/pt-BR/content/graphql/guides/index.md index f1dbf1c736..7311e5cf39 100644 --- a/translations/pt-BR/content/graphql/guides/index.md +++ b/translations/pt-BR/content/graphql/guides/index.md @@ -1,6 +1,6 @@ --- -title: Guias -intro: 'Saiba mais sobre como começar com o GraphQL, migrando da REST para o GraphQL e como usar a API do GraphQL do GitHub para uma variedade de tarefas.' +title: Guides +intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.' redirect_from: - /v4/guides versions: @@ -18,5 +18,6 @@ children: - /using-the-explorer - /managing-enterprise-accounts - /using-the-graphql-api-for-discussions + - /migrating-graphql-global-node-ids --- diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md deleted file mode 100644 index 669dce5a6d..0000000000 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ /dev/null @@ -1,753 +0,0 @@ ---- -title: Reviewing the audit log for your organization -intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /articles/reviewing-the-audit-log-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Review audit log ---- - -## Accessing the audit log - -The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Only owners can access an organization's audit log. - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} - -## Searching the audit log - -{% data reusables.audit_log.audit-log-search %} - -### Search based on the action performed - -To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: - -| Category name | Description -|------------------|-------------------{% ifversion fpt or ghec %} -| [`account`](#account-category-actions) | Contains all activities related to your organization account. -| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. -| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} -| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." -| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization. -| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." -| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %} -| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} -| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. -| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %} -| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %} -| [`hook`](#hook-category-actions) | Contains all activities related to webhooks. -| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | -| [`ip_allow_list`](#ip_allow_list) | Contains activitites related to enabling or disabling the IP allow list for an organization. -| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. -| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% ifversion fpt or ghec %} -| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} -| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion fpt or ghec %} -| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} -| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes > 3.0 or ghec %} -| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %} -| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. -| [`project`](#project-category-actions) | Contains all activities related to project boards. -| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. -| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %} -| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %} -| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %} -| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts.{% endif %}{% ifversion ghec %} -| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %} -| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% ifversion fpt or ghec %} -| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} -| [`team`](#team-category-actions) | Contains all activities related to teams in your organization. -| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization. - -You can search for specific sets of actions using these terms. For example: - - * `action:team` finds all events grouped within the team category. - * `-action:hook` excludes all events in the webhook category. - -Each category has a set of associated actions that you can filter on. For example: - - * `action:team.create` finds all events where a team was created. - * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. - -### Search based on time of action - -Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} - -{% data reusables.search.date_gt_lt %} - -For example: - - * `created:2014-07-08` finds all events that occurred on July 8th, 2014. - * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. - * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. - * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. - - -{% note %} - -**Note**: The audit log contains data for the current month and every day of the previous six months. - -{% endnote %} - -### Search based on location - -Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example: - - * `country:de` finds all events that occurred in Germany. - * `country:Mexico` finds all events that occurred in Mexico. - * `country:"United States"` all finds events that occurred in the United States. - -{% ifversion fpt or ghec %} -## Exporting the audit log - -{% data reusables.audit_log.export-log %} -{% data reusables.audit_log.exported-log-keys-and-values %} -{% endif %} - -## Using the audit log API - -You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}. - -{% ifversion fpt or ghec %} -The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} - -### Using the GraphQL API - -{% endif %} - -{% note %} - -**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} - -{% endnote %} - -To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: -{% data reusables.audit_log.audit-log-api-info %} - -{% ifversion fpt or ghec %} -Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)." -{% endif %} - -The GraphQL response can include data for up to 90 to 120 days. - -For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)." - -{% ifversion fpt or ghec %} - -### Using the REST API - -{% note %} - -**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. - -{% endnote %} - -To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: -{% data reusables.audit_log.audited-data-list %} - -{% data reusables.audit_log.audit-log-git-events-retention %} - -For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." - -{% endif %} - -## Audit log actions - -An overview of some of the most common actions that are recorded as events in the audit log. - -{% ifversion fpt or ghec %} -### `account` category actions - -| Action | Description -|------------------|------------------- -| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes. -| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes. -| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). -| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). -{% endif %} - -{% ifversion fpt or ghec %} -### `advisory_credit` category actions - -| Action | Description -|------------------|------------------- -| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." -| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. -| `decline` | Triggered when someone declines credit for a security advisory. -| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. -{% endif %} - -{% ifversion fpt or ghec %} -### `billing` category actions - -| Action | Description -|------------------|------------------- -| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). -| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. -{% endif %} - -### `business` category actions - -| Action | Description -|------------------|-------------------{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %} -| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %} - -{% ifversion fpt or ghec %} -### `codespaces` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace). -| `resume` | Triggered when a user resumes a suspended codespace. -| `delete` | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace). -| `create_an_org_secret` | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) -| `update_an_org_secret` | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). -| `remove_an_org_secret` | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). -| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). -{% endif %} - -{% ifversion fpt or ghec or ghes > 3.2 %} -### `dependabot_alerts` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. - -### `dependabot_alerts_new_repos` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. - -### `dependabot_security_updates` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. - -### `dependabot_security_updates_new_repos` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. -{% endif %} - -{% ifversion fpt or ghec %} -### `dependency_graph` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories. - -### `dependency_graph_new_repos` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. -{% endif %} - -### `discussion_post` category actions - -| Action | Description -|------------------|------------------- -| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). -| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). - -### `discussion_post_reply` category actions - -| Action | Description -|------------------|------------------- -| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). -| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). - -{% ifversion fpt or ghes or ghec %} -### `enterprise` category actions - -{% data reusables.actions.actions-audit-events-for-enterprise %} - -{% endif %} - -{% ifversion fpt or ghec %} -### `environment` category actions - -| Action | Description -|------------------|------------------- -| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." -| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." -| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." -| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." -{% endif %} - -{% ifversion fpt or ghec %} -### `git` category actions - -{% note %} - -**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." - -{% endnote %} - -{% data reusables.audit_log.audit-log-git-events-retention %} - -| Action | Description -|---------|---------------------------- -| `clone` | Triggered when a repository is cloned. -| `fetch` | Triggered when changes are fetched from a repository. -| `push` | Triggered when changes are pushed to a repository. - -{% endif %} - -### `hook` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization. -| `config_changed` | Triggered when an existing hook has its configuration altered. -| `destroy` | Triggered when an existing hook was removed from a repository. -| `events_changed` | Triggered when the events on a hook have been altered. - -### `integration_installation_request` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. -| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. - -### `ip_allow_list` category actions - -| Action | Description -|------------------|------------------- -| `enable` | Triggered when an IP allow list was enabled for an organization. -| `disable` | Triggered when an IP allow list was disabled for an organization. -| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. -| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. - -### `ip_allow_list_entry` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when an IP address was added to an IP allow list. -| `update` | Triggered when an IP address or its description was changed. -| `destroy` | Triggered when an IP address was deleted from an IP allow list. - -### `issue` category actions - -| Action | Description -|------------------|------------------- -| `destroy` | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository. - -{% ifversion fpt or ghec %} - -### `marketplace_agreement_signature` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. - -### `marketplace_listing` category actions - -| Action | Description -|------------------|------------------- -| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. -| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. -| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. -| `redraft` | Triggered when your listing is sent back to draft state. -| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. - -{% endif %} - -{% ifversion fpt or ghes > 3.0 or ghec %} - -### `members_can_create_pages` category actions - -For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." - -| Action | Description | -| :- | :- | -| `enable` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | -| `disable` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | - -{% endif %} - -### `org` category actions - -| Action | Description -|------------------|------------------- -| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} -| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %} -| `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. -| `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). -| `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% ifversion fpt or ghes or ghec %} -| `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} {% ifversion fpt or ghec %} -| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. -| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} -| `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} -| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} -| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization. -| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %} -| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} -| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} -| `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). -| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). -| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization. -| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %} -| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." -| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt or ghec %} -| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %} -| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.| -| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. | -| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion fpt or ghec %} -| `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." -| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." {% endif %} -| `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." -| `runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." -| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." -| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). -| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." -| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} -| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."{% endif %} -| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."{% endif %}{% ifversion fpt or ghec %} -| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %} -| `update_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %} -| `update_new_repository_default_branch_setting` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." -| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members. -| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner. -| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% ifversion fpt or ghec %} -| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. -| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} - -{% ifversion fpt or ghec %} -### `org_credential_authorization` category actions - -| Action | Description -|------------------|------------------- -| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). -| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). -| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). - -{% endif %} - -{% ifversion fpt or ghes or ghae or ghec %} -### `organization_label` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a default label is created. -| `update` | Triggered when a default label is edited. -| `destroy` | Triggered when a default label is deleted. - -{% endif %} - -### `oauth_application` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. -| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. -| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. -| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. -| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. - -{% ifversion fpt or ghes > 3.0 or ghec %} -### `packages` category actions - -| Action | Description | -|--------|-------------| -| `package_version_published` | Triggered when a package version is published. | -| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." -| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." -| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." -| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." - -{% endif %} - -{% ifversion fpt or ghec %} - -### `payment_method` category actions - -| Action | Description -|------------------|------------------- -| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method). -| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. -| `update` | Triggered when an existing payment method is updated. - -{% endif %} - -### `profile_picture` category actions -| Action | Description -|------------------|------------------- -| update | Triggered when you set or update your organization's profile picture. - -### `project` category actions - -| Action | Description -|--------------------|--------------------- -| `create` | Triggered when a project board is created. -| `link` | Triggered when a repository is linked to a project board. -| `rename` | Triggered when a project board is renamed. -| `update` | Triggered when a project board is updated. -| `delete` | Triggered when a project board is deleted. -| `unlink` | Triggered when a repository is unlinked from a project board. -| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. | -| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | -| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.| - -### `protected_branch` category actions - -| Action | Description -|--------------------|--------------------- -| `create ` | Triggered when branch protection is enabled on a branch. -| `destroy` | Triggered when branch protection is disabled on a branch. -| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators. -| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch. -| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch. -| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch. -| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. -| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. -| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. -| `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} -| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. -| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. -| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} - -### `pull_request` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a pull request is created. -| `close` | Triggered when a pull request is closed without being merged. -| `reopen` | Triggered when a pull request is reopened after previously being closed. -| `merge` | Triggered when a pull request is merged. -| `indirect_merge` | Triggered when a pull request is considered merged because its commits were merged into the target branch. -| `ready_for_review` | Triggered when a pull request is marked as ready for review. -| `converted_to_draft` | Triggered when a pull request is converted to a draft. -| `create_review_request` | Triggered when a review is requested. -| `remove_review_request` | Triggered when a review request is removed. - -### `pull_request_review` category actions - -| Action | Description -|------------------|------------------- -| `submit` | Triggered when a review is submitted. -| `dismiss` | Triggered when a review is dismissed. -| `delete` | Triggered when a review is deleted. - -### `pull_request_review_comment` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a review comment is added. -| `update` | Triggered when a review comment is changed. -| `delete` | Triggered when a review comment is deleted. - -{% endif %} - -### `repo` category actions - -| Action | Description -|------------------|------------------- -| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. -| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." -| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." -| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".{% endif %} -| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %} -| `create_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} -| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %} -| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %} -| `enable` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes or ghec %} -| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %} -| `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). -| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." -| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." -| `remove_topic` | Triggered when a repository admin removes a topic from a repository. -| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 or ghec %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} -| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %} -| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} -| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). -| `transfer_start` | Triggered when a repository transfer is about to occur. -| `unarchived` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes or ghec %} -| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %} - -{% ifversion fpt or ghec %} - -### `repository_advisory` category actions - -| Action | Description -|------------------|------------------- -| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. -| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. -| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. -| `open` | Triggered when someone opens a draft security advisory. -| `publish` | Triggered when someone publishes a security advisory. -| `reopen` | Triggered when someone reopens as draft security advisory. -| `update` | Triggered when someone edits a draft or published security advisory. - -### `repository_content_analysis` category actions - -| Action | Description -|------------------|------------------- -| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). -| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). - -{% endif %}{% ifversion fpt or ghec %} - -### `repository_dependency_graph` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. - -{% endif %} -### `repository_secret_scanning` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. - -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -### `repository_vulnerability_alert` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when {% data variables.product.product_name %} creates a {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." -| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. -| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. - -{% endif %}{% ifversion fpt or ghec %} -### `repository_vulnerability_alerts` category actions - -| Action | Description -|------------------|------------------- -| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. -| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}. - -{% endif %}{% ifversion ghec %} -### `role` category actions -| Action | Description -|------------------|------------------- -|`create` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." -|`destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." -|`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." - -{% endif %} - -### `secret_scanning` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. - -### `secret_scanning_new_repos` category actions - -| Action | Description -|------------------|------------------- -| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. - -{% ifversion fpt or ghec %} -### `sponsors` category actions - -| Action | Description -|------------------|------------------- -| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") -| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") -| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") -| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") -| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled -| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state -| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") -| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") -| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") -| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") -{% endif %} - -### `team` category actions - -| Action | Description -|------------------|------------------- -| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). -| `add_repository` | Triggered when a team is given control of a repository. -| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). -| `change_privacy` | Triggered when a team's privacy level is changed. -| `create` | Triggered when a new team is created. -| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." -| `destroy` | Triggered when a team is deleted from the organization. -| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." -| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). -| `remove_repository` | Triggered when a repository is no longer under a team's control. - -### `team_discussions` category actions - -| Action | Description -|---|---| -| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." -| `enable` | Triggered when an organization owner enables team discussions for an organization. - -### `workflows` category actions - -{% data reusables.actions.actions-audit-events-workflow %} - -## Further reading - -- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %} -- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index 70d0101646..4b2252d181 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Desabilitar ou limitar o GitHub Actions para sua organização -intro: 'Os proprietários da organização podem desabilitar, habilitar e limitar o GitHub Actions para uma organização.' +title: Disabling or limiting GitHub Actions for your organization +intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization versions: @@ -11,59 +11,60 @@ versions: topics: - Organizations - Teams -shortTitle: Desativar ou limitar ações +shortTitle: Disable or limit actions --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Sobre as permissões de {% data variables.product.prodname_actions %} para a sua organização +## About {% data variables.product.prodname_actions %} permissions for your organization -{% data reusables.github-actions.disabling-github-actions %} Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." +{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." -Você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.disabled-actions-description %} +You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %} -Como alternativa, você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios na sua organização e limitar as ações que um fluxo de trabalho pode executar. {% data reusables.github-actions.enabled-local-github-actions %} +Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %} -## Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização +## Managing {% data variables.product.prodname_actions %} permissions for your organization -Você pode desabilitar todos os fluxos de trabalho para uma organização ou definir uma política que configura quais ações podem ser usadas em uma organização. +You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization. {% data reusables.actions.actions-use-policy-settings %} {% note %} -**Observação:** Talvez você não consiga gerenciar essas configurações se a sua organização for gerenciada por uma empresa que tem uma política de substituição. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)". +**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)." {% endnote %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Em **Políticas**, selecione uma opção. ![Definir política de ações para esta organização](/assets/images/help/organizations/actions-policy.png) -1. Clique em **Salvar**. +1. Under **Policies**, select an option. + ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png) +1. Click **Save**. -## Permitir a execução de ações específicas +## Allowing specific actions to run {% data reusables.actions.allow-specific-actions-intro %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. - {%- ifversion ghes %} - ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes > 3.0 %} + ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) {%- else %} - ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) {%- endif %} -1. Clique em **Salvar**. +1. Click **Save**. {% ifversion fpt or ghec %} -## Configurar a aprovação necessária para fluxos de trabalho de bifurcações públicas +## Configuring required approval for workflows from public forks {% data reusables.actions.workflow-run-approve-public-fork %} -Você pode configurar esse comportamento para uma organização seguindo o procedimento abaixo. A modificação desta configuração substitui a configuração definida no nível corporativo. +You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -74,11 +75,11 @@ Você pode configurar esse comportamento para uma organização seguindo o proce {% endif %} {% ifversion fpt or ghes or ghec %} -## Habilitar fluxos de trabalho para bifurcações privadas do repositório +## Enabling workflows for private repository forks {% data reusables.github-actions.private-repository-forks-overview %} -### Configurar a política de bifurcação privada para uma organização +### Configuring the private fork policy for an organization {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -87,24 +88,21 @@ Você pode configurar esse comportamento para uma organização seguindo o proce {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Definindo as permissões do `GITHUB_TOKEN` para a sua organização +## Setting the permissions of the `GITHUB_TOKEN` for your organization {% data reusables.github-actions.workflow-permissions-intro %} -Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para a sua organização ou repositórios. Se você escolher a opção restrita como padrão nas configurações da sua organização, a mesma opção será selecionada automaticamente nas configurações dos repositórios na organização, e a opção permissiva ficará desabilitada. Se sua organização pertence a uma conta {% data variables.product.prodname_enterprise %} e o padrão mais restrito foi selecionado nas configurações corporativas, você não poderá de escolher o padrão mais permissivo nas configurações da organização. +You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you choose the restricted option as the default in your organization settings, the same option is auto-selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and the more restricted default has been selected in the enterprise settings, you won't be able to choose the more permissive default in your organization settings. {% data reusables.github-actions.workflow-permissions-modifying %} -### Configurar as permissões padrão do `GITHUB_TOKEN` +### Configuring the default `GITHUB_TOKEN` permissions {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Em **permissões do fluxo de trabalho**, escolha se você quer que o `GITHUB_TOKEN` tenha acesso de leitura e gravação para todos os escopos, ou apenas acesso de leitura para o escopo do     conteúdo. -Definir permissões do GITHUB_TOKEN para esta organização

    -

  • Clique em Salvar para aplicar as configurações. -

    - -

    {% endif %}

    • - +1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. + ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization.png) +1. Click **Save** to apply the settings. +{% endif %} diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md deleted file mode 100644 index 3d5084344c..0000000000 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Sobre equipes -intro: As equipes são grupos de integrantes da organização que refletem sua empresa ou a estrutura do grupo com permissões de acesso em cascata e menções. -redirect_from: - - /articles/about-teams - - /github/setting-up-and-managing-organizations-and-teams/about-teams -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams ---- - -![Lista de equipes em uma organização](/assets/images/help/teams/org-list-of-teams.png) - -Os proprietários da organização e os mantenedores de equipe podem dar às equipes acesso de administrador, leitura ou gravação aos repositórios da organização. Os integrantes da organização podem enviar uma notificação a uma equipe inteira mencionando o nome da equipe. Os integrantes da organização também podem enviar uma notificação a uma equipe inteira solicitando uma revisão dessa equipe. Os integrantes da organização podem solicitar revisões de equipes específicas com acesso de leitura ao repositório onde a pull request está aberta. As equipes podem ser designadas como proprietários de determinados tipos de área de código em um arquivo CODEOWNERS. - -Para obter mais informações, consulte: -- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)" -- "[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" -- "[Sobre proprietários do código](/articles/about-code-owners/)" - -![Imagem de uma menção de equipe](/assets/images/help/teams/team-mention.png) - -{% ifversion ghes %} - -Você também pode usar a sincronização LDAP para sincronizar os integrantes e funções da equipe da {% data variables.product.product_location %} com os grupos LDAP estabelecidos. Isso permite estabelecer o controle de acesso baseado em função para usuários do servidor LDAP em vez de manualmente na {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar a Sincronização LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". - -{% endif %} - -{% data reusables.organizations.team-synchronization %} - -## Visibilidade da equipe - -{% data reusables.organizations.types-of-team-visibility %} - -You can view all the teams you belong to on your personal dashboard. Para obter mais informações, consulte "[Sobre seu painel pessoal](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)". - -## Páginas da equipe - -Cada equipe tem sua própria página em uma organização. Na página de uma equipe, é possível exibir integrantes da equipe, equipes secundárias e os repositórios da equipe. Os proprietários da organização e os mantenedores de equipe podem acessar as configurações da equipe, bem como atualizar a descrição e a foto de perfil da equipe na página da equipe. - -Os integrantes da organização podem criar e participar de discussões com a equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)". - -![Página da equipe listando integrantes e discussões da equipe](/assets/images/help/organizations/team-page-discussions-tab.png) - -## Equipes aninhadas - -Você pode refletir seu grupo ou a hierarquia da empresa na sua organização do {% data variables.product.product_name %} com vários níveis de equipes aninhadas. Uma equipe principal pode ter várias equipes secundárias, enquanto cada equipe secundária tem apenas uma equipe principal. Não é possível aninhar equipes secretas. - -As equipes secundárias herdam as permissões de acesso da principal, simplificando o gerenciamento de permissões para grandes grupos. Os integrantes das equipes secundárias também recebem notificações quando a equipe principal é @mencionada, simplificando a comunicação com vários grupos de pessoas. - -Por exemplo, se a estrutura da sua equipe for Funcionários > Engenharia > Engenharia de aplicativos > Identidade, conceder à Engenharia acesso de gravação a um repositório significa que a Engenharia de aplicativos e a Identidade também obterão esse acesso. Se você @mencionar a Equipe Identidade ou qualquer equipe na parte inferior da hierarquia da organização, elas serão as únicas que receberão uma notificação. - -![Página das equipes com uma equipe principal e equipes secundárias](/assets/images/help/teams/nested-teams-eng-example.png) - -Para entender facilmente quem compartilha permissões da equipe principal e faz menção, você pode ver todos os integrantes das equipes secundárias de uma equipe principal na guia Members (Integrantes) da página da equipe principal. Os integrantes de uma equipe secundária não são integrantes diretos da equipe principal. - -![Página da equipe principal com todos os integrantes das equipes secundárias](/assets/images/help/teams/team-and-subteam-members.png) - -Você pode escolher uma principal quando criar a equipe ou pode mover uma equipe na hierarquia da organização posteriormente. Para obter mais informações, consulte "[Mover uma equipe na hierarquia da sua organização](/articles/moving-a-team-in-your-organization-s-hierarchy)". - -{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} - -## Preparar para aninhar equipes em sua organização - -Se a sua organização já tiver equipes, você deverá auditar as permissões de acesso ao repositório de cada equipe antes de aninhar equipes acima ou abaixo dela. Também é preciso considerar a nova estrutura que deseja implementar para a organização. - -No topo da hierarquia da equipe, você deve fornecer às equipes principais permissões de acesso ao repositório que sejam seguras para cada integrante da equipe principal e suas equipes secundárias. À medida que desce pela hierarquia, você pode conceder às equipes secundárias adicionais, acesso mais granular a repositórios mais confidenciais. - -1. Remova todos os integrantes das equipes existentes -2. Audite e ajuste as permissões de acesso ao repositório de cada equipe e forneça a cada equipe uma equipe principal -3. Crie qualquer equipe nova que desejar, escolha uma principal para cada equipe nova e forneça a ela acesso ao repositório -4. Adicione pessoas diretamente às equipes - -## Leia mais - -- "[Criar uma equipe](/articles/creating-a-team)" -- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md deleted file mode 100644 index e943d0e1b7..0000000000 --- a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Introdução aos GitHub Packages -intro: '{% data variables.product.prodname_registry %} é um serviço de hospedagem de pacotes de software que permite que você hospede seus pacotes de software de forma privada{% ifversion ghae %} para usuários especificados ou internamente para a empresa{% else %}ou publicamente{% endif %} e use pacotes como dependências dos seus projetos.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/about-github-package-registry - - /github/managing-packages-with-github-package-registry/about-github-package-registry - - /github/managing-packages-with-github-packages/about-github-packages - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/learn-github-packages/about-github-packages - - /packages/learn-github-packages/core-concepts-for-github-packages - - /packages/guides/about-github-container-registry -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: Introdução ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -## Sobre o {% data variables.product.prodname_registry %} - -{% data variables.product.prodname_registry %} is a package hosting service, fully integrated with {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combina seu código-fonte e pacotes em um só lugar para fornecer gerenciamento integrado de permissões{% ifversion not ghae %} e faturamento{% endif %}, para que você possa centralizar o desenvolvimento do seu software em {% data variables.product.product_name %}. - -You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. - -{% data variables.product.prodname_registry %} oferece registros de pacotes diferentes para gerentes de pacotes comumente usados, como npm, RubyGems, Apache Maven, Gradle, Docker e NuGet. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} {% data variables.product.prodname_container_registry %} é otimizado para contêineres e é compatível com imagens do Docker e OCI.{% endif %} Para obter mais informações sobre os diferentes registros de pacotes com os quais {% data variables.product.prodname_registry %} é compatível, consulte "[Trabalhando com um registro de {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)." - -{% ifversion fpt or ghec %} - -![Diagrama que mostra pacotes de compatibilidade para registro de contêiner, RubyGems, npm, Apache Maven, NuGet e Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png) - -{% else %} - -![Diagrama que mostra compatibilidade para pacotes do registro Docker, RubyGems, npm, Apache Maven, Gradle, NuGet e Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png) - -{% endif %} - -Você pode visualizar o LEIAME de um pacote, bem como os metadados como licenciamento, estatísticas de download, histórico de versão e muito mais em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Visualizar pacotes](/packages/manage-packages/viewing-packages)". - -### Visão geral das permissões e visibilidade do pacote - -| | | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | -| Permissões | | -| {% ifversion fpt or ghec %}As permissões para um pacote são herdadas do repositório em que o pacote está hospedado ou, para pacotes em {% data variables.product.prodname_container_registry %}, eles podem ser definidos para contas específicas de usuário ou organização. Para obter mais informações, consulte "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)". {% else %}Cada pacote herda as permissões do repositório em que o pacote está hospedado.

    Por exemplo, qualquer pessoa com permissões de leitura para um repositório pode instalar um pacote como uma dependência em um projeto, e qualquer pessoa com permissões de gravação pode publicar uma nova versão de pacote.{% endif %} | | -| | | -| Visibilidade | {% data reusables.package_registry.public-or-private-packages %} - -Para obter mais informações, consulte "[Sobre permissões para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)". - -{% ifversion fpt or ghec %} -## Sobre a cobrança do {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)". - -{% endif %} - -## Clientes e formatos compatíveis - - -O {% data variables.product.prodname_registry %} usa os comandos nativos de ferramentas de pacotes com os quais você já está familiarizado para publicar e instalar versões de pacote. -### Suporte para registros de pacotes - -| Linguagem | Descrição | Formato do pacote | Cliente do pacote | -| ---------- | --------------------------------------------------------------------- | ------------------------------------ | ----------------- | -| JavaScript | Gerenciador de pacotes de nó | `package.json` | `npm` | -| Ruby | Gerenciador de pacotes de RubyGems | `Gemfile` | `gem` | -| Java | Ferramenta de gerenciamento de projetos e compreensão do Apache Maven | `pom.xml` | `mvn` | -| Java | Ferramenta de automação do build Gradle para Java | `build.gradle` ou `build.gradle.kts` | `gradle` | -| .NET | Gerenciamento de pacotes NuGet para .NET | `nupkg` | `dotnet` CLI | -| N/A | Gerenciamento do contêiner do Docker | `arquivo Docker` | `Docker` | - -{% ifversion ghes %} -{% note %} - -**Observação:** O Docker não é compatível quando o isolamento de subdomínio está desativado. - -{% endnote %} - -Para obter mais informações sobre o isolamento de subdomínio, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". - -{% endif %} - -Para obter mais informações sobre a configuração do seu pacote para uso com {% data variables.product.prodname_registry %}, consulte "[Trabalhar com um registro de {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)". - -{% ifversion fpt or ghec %} -Para obter mais informações sobre o Docker e o {% data variables.product.prodname_container_registry %}, consulte "[Trabalhando com o registro do contêiner](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)". -{% endif %} -## Autenticar-se no {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% data reusables.package_registry.authenticate-packages-github-token %} - -## Gerenciar pacotes - -{% ifversion fpt or ghec %} -You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} user interface or using the REST API. Para obter mais informações, consulte o "[API de {% data variables.product.prodname_registry %}](/rest/reference/packages)". -{% endif %} - -{% ifversion ghes > 3.0 %} -Você pode excluir um pacote privado ou público na interface de usuário do {% data variables.product.product_name %}. Ou para pacotes com escopo de repositório, você pode excluir uma versão de um pacote privado usando o GraphQL. -{% endif %} - -{% ifversion ghes < 3.1 %} -Você pode excluir uma versão de um pacote privado na interface de usuário de {% data variables.product.product_name %} ou usando a API do GraphQL. -{% endif %} - -{% ifversion ghae %} -Você pode excluir uma versão de um pacote na interface de usuário {% data variables.product.product_name %} ou usando a API do GraphQL. -{% endif %} - -Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "{% ifversion fpt or ghes > 3.0 or ghec %}[Excluindo e restaurando um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}}[Excluindo um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}" e"[Realizando chamadas com o GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql)". - -Você pode configurar webhooks para assinar eventos relacionados aos pacotes, como quando um pacote é publicado ou atualizado. Para obter mais informações, consulte o evento de webhook de "[`pacote`](/webhooks/event-payloads/#package)". - -## Entrar em contato com o suporte - -{% ifversion fpt or ghec %} -Se você tiver comentários ou solicitações de recursos para {% data variables.product.prodname_registry %}, use o [formulário de feedback para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). - -Entre em contato com {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando o [nosso formulário de contato](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) se: - -* Você encontrar qualquer coisa que contradiga a documentação -* Você encontra erros vagos ou pouco claros -* Seu pacote publicado contém dados confidenciais, como violações do RGPD, chaves API ou informações de identificação pessoal - -{% else %} -Se você precisar de suporte para {% data variables.product.prodname_registry %}, entre em contato com os administradores do seu site. - -{% endif %} diff --git a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md deleted file mode 100644 index 61c3d66c1e..0000000000 --- a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Publicar um pacote -intro: 'Você pode publicar um pacote no {% data variables.product.prodname_registry %} para disponibilizar o pacote para que outros façam download e reutilizem.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /github/managing-packages-with-github-packages/publishing-a-package - - /packages/publishing-and-managing-packages/publishing-a-package -permissions: Anyone with write permissions for a repository can publish a package to that repository. -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -## Sobre os pacotes publicados - -Você pode ajudar as pessoas a entender e usar seu pacote fornecendo uma descrição e outros detalhes como, por exemplo, a instalação e instruções de uso na página do pacote. GitHub provides metadata for each version, such as the publication date, download activity, and recent versions. Para uma página de pacote de exemplo, veja [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). - -{% data reusables.package_registry.public-or-private-packages %} Um repositório pode ser conectado a mais de um pacote. Para evitar confusão, certifique-se de que o README e a descrição fornecem informações claras sobre cada pacote. - -{% ifversion fpt or ghec %} -Se uma nova versão de um pacote corrigir uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. -{% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." -{% endif %} - -## Publicar um pacote - -You can publish a package to {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. - -1. Crie ou use um token de acesso existente com os escopos apropriados para a tarefa que você deseja realizar. Para obter mais informações, consulte "[Sobre permissões para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)". -2. Efetue a autenticação em {% data variables.product.prodname_registry %} usando seu token de acesso e as instruções para seu cliente do pacote. -3. Publique o pacote usando as instruções do seu cliente de pacote. - -Para obter instruções específicas para o seu cliente de pacotes, consulte "[Trabalhar com um registro de pacotes do GitHub](/packages/working-with-a-github-packages-registry)". - -Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Visualizar pacotes](/packages/learn-github-packages/viewing-packages)". diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md deleted file mode 100644 index aa1d5f828e..0000000000 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: Trabalhando com o registro do Apache Maven -intro: 'Você pode configurar o Apache Maven para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto Java.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-apache-maven-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages - - /packages/guides/configuring-apache-maven-for-use-with-github-packages -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: Registro do Apache Maven ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. - -## Autenticar-se no {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% data reusables.package_registry.authenticate-packages-github-token %} - -### Efetuando a autenticação com um token de acesso pessoal - -{% data reusables.package_registry.required-scopes %} - -Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o Apache Maven editando seu arquivo *~/.m2/settings.xml* para incluir seu token de acesso pessoal. Criar um novo arquivo *~/.m2/settings.xml*, caso não exista um. - -Na etiqueta `servidores`, adicione uma etiqueta `servidor` secundário com um `Id`, substituindo *USERNAME* pelo o seu nome de usuário {% data variables.product.prodname_dotcom %} e *Token* pelo seu token de acesso pessoal. - -Na etiqueta `repositórios`, configure um repositório mapeando o `id` do repositório com o `id` que você adicionou na etiqueta `servidor` que contém as suas credenciais. Substitua {% ifversion ghes or ghae %}*HOSTNAME* pelo nome do host de {% data variables.product.product_location %} e{% endif %} *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. - -Se desejar interagir com vários repositórios, você poderá adicionar cada repositório para separar os `repositório` secundários na etiqueta `repositórios`, mapeando o `ID` de cada um com as credenciais na etiqueta `servidores`. - -{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio habilitado: -{% endif %} - -```xml - - - - github - - - - - github - - - central - https://repo1.maven.org/maven2 - - - github - https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY - - true - - - - - - - - - github - USERNAME - TOKEN - - - -``` - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio desabilitado: - -```xml - - - - github - - - - - github - - - central - https://repo1.maven.org/maven2 - - - github - HOSTNAME/_registry/maven/OWNER/REPOSITORY - - true - - - - - - - - - github - USERNAME - TOKEN - - - -``` -{% endif %} - -## Publicar um pacote - -O {% data reusables.package_registry.default-name %} por exemplo, o {% data variables.product.prodname_dotcom %} publicará um pacote denominado `com.example:test` em um repositório denominado`OWNER/test`. - -Caso queira publicar vários pacotes no mesmo repositório, você poderá incluir a URL do repositório no `` elemento do arquivo *pom.xml*. O {% data variables.product.prodname_dotcom %} fará a correspondência do repositório com base nesse campo. Como o nome do repositório também faz parte do elemento `distributionManagement`, não há etapas adicionais para publicar vários pacotes no mesmo repositório. - -Para obter mais informações sobre como criar um pacote, consulte a [documentação maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). - -1. Edite o elemento `distributionManagement` do arquivo pom.xml     *localizado no diretório do pacote, substituindo {% ifversion ghes or ghae %}*HOSTNAME* pelo nome de host de {% data variables.product.product_location %}, {% endif %}`OWNER` pelo nome da conta do usuário ou organização que possui o repositório e `REPOSITORY` pelo nome do repositório que contém o seu projeto.{% ifversion ghes %}

    - - Se sua instância tiver o isolamento de subdomínio habilitado:{% endif %} - ```xml - - - github - GitHub OWNER Apache Maven Packages - https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY - - - ```{% ifversion ghes %} - If your instance has subdomain isolation disabled: - ```xml - - - github - GitHub OWNER Apache Maven Packages - https://HOSTNAME/_registry/maven/OWNER/REPOSITORY - - - ```{% endif %} -{% data reusables.package_registry.checksum-maven-plugin %} -1. Publique o pacote. - ```shell - $ mvn deploy - ``` - - -{% data reusables.package_registry.viewing-packages %} - -## Instalar um pacote - -Para instalar um pacote de Apache Maven a partir do {% data variables.product.prodname_registry %}, edite o arquivo *pom.xml* para incluir o pacote como uma dependência. Se você desejar instalar pacotes de mais de um repositório, adicione uma etiqueta de `repositório` para cada um. Para obter mais informações sobre como usar o arquivo *pom.xml* no seu projeto, consulte "[Introdução a POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" na documentação do Apache Maven. - -{% data reusables.package_registry.authenticate-step %} -2. Adicione as dependências do pacote ao elemento `dependências` do arquivo *pom.xml* do seu projeto, substituindo `com.exemplo:test` pelo seu pacote. - - ```xml - - - com.example - test - 1.0.0-SNAPSHOT - - - ``` -{% data reusables.package_registry.checksum-maven-plugin %} -3. Instale o pacote. - - ```shell - $ mvn install - ``` - -## Leia mais - -- "[Trabalhando com o registro do Gradle](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)" -- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md deleted file mode 100644 index 41d3bbc42e..0000000000 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md +++ /dev/null @@ -1,269 +0,0 @@ ---- -title: Trabalhando com o registro do Docker -intro: '{% ifversion fpt or ghec %}The Docker registry has now been replaced by the {% data variables.product.prodname_container_registry %}.{% else %}You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.{% endif %}' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-docker-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages - - /packages/guides/configuring-docker-for-use-with-github-packages -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: Registro Docker ---- - - -{% ifversion fpt or ghec %} - -O registro do Docker d e{% data variables.product.prodname_dotcom %} (que usou o namespace `docker.pkg.github.com`) foi substituído por {% data variables.product.prodname_container_registry %} (que usa o namespace `https://ghcr.io`). O {% data variables.product.prodname_container_registry %} oferece benefícios como, por exemplo, permissões granulares e otimização de armazenamento para imagens Docker. - -As imagens do Docker armazenadas anteriormente no registro do Docker estão sendo automaticamente transferidas para {% data variables.product.prodname_container_registry %}. Para obter mais informações, consulte "[Fazendo a migração {% data variables.product.prodname_container_registry %} a partir do registro Docker](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)" e "[Trabalhando com o {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)". - -{% else %} - - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. - -## Sobre o suporte ao Docker - -Ao instalar ou publicar uma imagem do Docker, o registro do Docker atualmente não é compatível com camadas externas como, por exemplo, as imagens do Windows. - -## Autenticar-se no {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% data reusables.package_registry.authenticate-packages-github-token %} - -### Efetuando a autenticação com um token de acesso pessoal - -{% data reusables.package_registry.required-scopes %} - -Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} usando o comando de login do `docker`. - -Para manter suas credenciais seguras, recomendamos que você salve seu token de acesso pessoal em um arquivo local no seu computador e use o sinalizador `--password-stdin` do Docker que lê o seu token a partir de um arquivo local. - -{% ifversion fpt or ghec %} -{% raw %} - ```shell - $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin - ``` -{% endraw %} -{% endif %} - -{% ifversion ghes or ghae %} -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio habilitado: -{% endif %} -{% raw %} - ```shell - $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin -``` -{% endraw %} -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio desabilitado: - -{% raw %} - ```shell - $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin -``` -{% endraw %} -{% endif %} - -{% endif %} - -To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% ifversion ghes or ghae %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. - -Para obter mais informações, consulte "[Login do Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)". - -## Publicar uma imagem - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -{% note %} - -**Observação:** Os nomes de imagem devem usar apenas letras minúsculas. - -{% endnote %} - -O {% data variables.product.prodname_registry %} aceita várias imagens do Docker de nível superior por repositório. Um repositório pode ter qualquer número de tags de imagem. Você poderá conhecer uma publicação de serviço degradada ou instalar imagens do Docker com tamanho superior a 10 GB. As camadas são limitadas em 5 GB cada. Para obter mais informações, consulte "[Tag do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação Docker. - -{% data reusables.package_registry.viewing-packages %} - -1. Determine o nome da imagem e o ID da sua imagem do docker usando `imagens do docker`. - ```shell - $ docker images - > < > - > REPOSITORY TAG IMAGE ID CREATED SIZE - > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB - ``` -2. Ao usar o ID de imagem Docker, marque a imagem do docker, substituindo *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITORY* pelo nome do repositório que contém o seu projeto, *IMAGE_NAME* pelo nome do pacote ou imagem,{% ifversion ghes or ghae %} *HOSTNAME* pelo nome do host de {% data variables.product.product_location %}{% endif %} e *VERSION* pela versão do pacote no momento da compilação. - {% ifversion fpt or ghec %} - ```shell - $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% else %} - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio habilitado: - {% endif %} - ```shell - $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio desabilitado: - ```shell - $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% endif %} - {% endif %} -3. Se você ainda não criou uma imagem d docker para o pacote, crie a imagem, substituindo *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* com o nome do repositório que contém o seu projeto, *IMAGE_NAME* com o nome do pacote ou imagem, *VERSÃO* com a versão do pacote na hora da compilação,{% ifversion ghes or ghae %} *HOSTNAME* com o nome do host de {% data variables.product.product_location %},{% endif %} e *PATH* para a imagem se não estiver no diretório de trabalho atual. - {% ifversion fpt or ghec %} - ```shell - $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH - ``` - {% else %} - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio habilitado: - {% endif %} - ```shell - $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH - ``` - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio desabilitado: - ```shell - $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH - ``` - {% endif %} - {% endif %} -4. Publicar a imagem no {% data variables.product.prodname_registry %}. - {% ifversion fpt or ghec %} - ```shell - $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% else %} - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio habilitado: - {% endif %} - ```shell - $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio desabilitado: - ```shell - $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% endif %} - {% endif %} - {% note %} - - **Observação:** Você deve enviar sua imagem usando `IMAGE_NAME:VERSION` e não `IMAGE_NAME:SHA`. - - {% endnote %} - -### Exemplo de publicação de uma imagem do Docker - -{% ifversion ghes %} -Esses exemplos assumem que sua instância tem o isolamento de subdomínio habilitado. -{% endif %} - -Você pode publicar a versão 1.0 da imagem de `monalisa` para o repositório `octocat/octo-app` usando um ID de imagem. - -{% ifversion fpt or ghec %} -```shell -$ docker images - -> REPOSITORY TAG IMAGE ID CREATED SIZE -> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB - -# Tag the image with OWNER/REPO/IMAGE_NAME -$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 -``` - -{% else %} - -```shell -$ docker images - -> REPOSITORY TAG IMAGE ID CREATED SIZE -> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB - -# Tag the image with OWNER/REPO/IMAGE_NAME -$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 -``` - -{% endif %} - -Você pode publicar uma nova imagem do Docker pela primeira vez e nomeá-la como `monalisa`. - -{% ifversion fpt or ghec %} -```shell -# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION -# Assumes Dockerfile resides in the current working directory (.) -$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . -$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . - -# Faça push da imagem no {% data variables.product.prodname_registry %} -$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 -``` - -{% else %} -```shell -# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION -# Assumes Dockerfile resides in the current working directory (.) -$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 -``` -{% endif %} - -## Fazer o download de uma imagem - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -Você pode usar o comando `docker pull` para instalar uma imagem do docker a partir de {% data variables.product.prodname_registry %}, substituindo *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* pelo nome do repositório que contém seu projeto, *IMAGE_NAME* pelo nome do pacote ou da imagem, {% ifversion ghes or ghae %} *HOSTNAME* pelo nome do host {% data variables.product.product_location %}, {% endif %} e *TAG_NAME* éla tag para a imagem que você deseja instalar. - -{% ifversion fpt or ghec %} -```shell -$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME -``` -{% else %} - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio habilitado: -{% endif %} -```shell -$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME -``` -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio desabilitado: -```shell -$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME -``` -{% endif %} -{% endif %} - -{% note %} - -**Nota:** Você deve fazer pull da imagem usando `IMAGE_NAME:VERSION` e não usar `IMAGE_NAME:SHA`. - -{% endnote %} - -## Leia mais - -- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" - -{% endif %} diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md deleted file mode 100644 index 1e6980fd7c..0000000000 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Trabalhando com o registro do Gradle -intro: 'Você pode configurar o Gradle para publicar pacotes no registro do Gradle de {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências de um projeto Java.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-gradle-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages - - /packages/guides/configuring-gradle-for-use-with-github-packages -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: Registro do Gradle ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. - -## Autenticar-se no {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% data reusables.package_registry.authenticate-packages-github-token %} Para obter mais informações sobre como usar `GITHUB_TOKEN` com Gradle, consulte "[Publicar pacotes Java com o Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)". - -### Efetuando a autenticação com um token de acesso pessoal - -{% data reusables.package_registry.required-scopes %} - -Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com Gradle usando Gradle Groovy ou Kotlin DSL e editando o seu arquivo *build.gradle* (Gradle Groovy) ou o arquivo *build.gradle.kts* (Kotlin DSL) para incluir seu token de acesso pessoal. Também é possível configurar o Gradle Groovy e o Kotlin DSL para reconhecer um único pacote ou vários pacotes em um repositório. - -{% ifversion ghes %} -Substitua *REGISTRY-URL* pela URL do registro do Maven para a sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `maven.HOSTNAME`. Se sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/maven`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %}. -{% elsif ghae %} -Substitua *URL REGISTRA-* pela URL para o registro Maven da sua empresa, `maven.HOSTNAME`. Substitua *HOSTNAME* pelo nome do host de {% data variables.product.product_location %}. -{% endif %} - -Substitua *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %} *TOKEN* pelo seu token de acesso pessoal, *REPOSITÓRIO* pelo nome do repositório que contém o pacote que você deseja publicar, e *PROPRIETÁRIO* pelo nome do usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. - -{% note %} - -**Observação:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Por exemplo, consulte "[Configuraro Apache Maven para uso com {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)". - -{% endnote %} - -#### Exemplo de uso do Gradle Groovy para um único pacote em um repositório - -```shell -plugins { - id("maven-publish") -} -publishing { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") - } - } - } - publications { - gpr(MavenPublication) { - from(components.java) - } - } -} -``` - -#### Exemplo de uso do Gradle Groovy para vários pacotes no mesmo repositório - -```shell -plugins { - id("maven-publish") apply false -} -subprojects { - apply plugin: "maven-publish" - publishing { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") - } - } - } - publications { - gpr(MavenPublication) { - from(components.java) - } - } - } -} -``` - -#### Exemplo de uso do Kotlin DSL para um único pacote no mesmo repositório - -```shell -plugins { - `maven-publish` -} -publishing { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - publications { - register<MavenPublication>("gpr") { - from(components["java"]) - } - } -} -``` - -#### Exemplo de uso do Kotlin DSL para vários pacotes no mesmo repositório - -```shell -plugins { - `maven-publish` apply false -} -subprojects { - apply(plugin = "maven-publish") - configure<PublishingExtension> { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - publications { - register<MavenPublication>("gpr") { - from(components["java"]) - } - } - } -} -``` - -## Publicar um pacote - -{% data reusables.package_registry.default-name %} Por exemplo, {% data variables.product.prodname_dotcom %} publicará um pacote denominado `com.example.test` no repositório `OWNER/test` {% data variables.product.prodname_registry %}. - -{% data reusables.package_registry.viewing-packages %} - -{% data reusables.package_registry.authenticate-step %} -2. Depois de criar seu pacote, você poderá publicá-lo. - - ```shell - $ gradle publish - ``` - -## Usando um pacote publicado - -Para usar um pacote publicado a partir de {% data variables.product.prodname_registry %}, adicione o pacote como uma dependência e adicione o repositório ao seu projeto. Para obter mais informações, consulte "[Declarar dependências](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" na documentação do Gradle. - -{% data reusables.package_registry.authenticate-step %} -2. Adicione as dependências do pacote ao seu arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (arquivo de Kotlin DSL). - - Exemplo do uso do Gradle Groovy: - ```shell - dependencies { - implementation 'com.example:package' - } - ``` - Exemplo de uso do Kotlin DSL: - ```shell - dependencies { - implementation("com.example:package") - } - ``` - -3. Adicione o repositório ao seu arquivo *build.gradle* (Gradle Groovy) ou *build.gradle.kts* (arquivo Kotlin DSL). - - Exemplo do uso do Gradle Groovy: - ```shell - repositories { - maven { - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") - } - } - } - ``` - Exemplo de uso do Kotlin DSL: - ```shell - repositories { - maven { - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - ``` - -## Leia mais - -- "[Trabalhando com o registro Apache Maven](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)" -- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md deleted file mode 100644 index e25669b7a5..0000000000 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -title: Trabalhando com o registro npm -intro: 'Você pode configurar o npm para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto npm.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-npm-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/guides/configuring-npm-for-use-with-github-packages -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: Registro de npm ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. - -## Limites para versões publicadas do npm - -Se você publicar mais de 1.000 versões de pacote de npm até {% data variables.product.prodname_registry %}, você poderá ver problemas de performance e tempo-limite que ocorrem durante o uso. - -No futuro, para melhorar o desempenho do serviço, você não será capaz de publicar mais de 1.000 versões de um pacote em {% data variables.product.prodname_dotcom %}. Todas as versões publicadas antes de atingir esse limite serão legíveis. - -Se você atingir este limite, considere excluir versões de pacote ou entre em contato com o suporte para obter ajuda. Quando este limite for aplicado, a nossa documentação será atualizada com uma forma de contornar este limite. Para obter mais informações, consulte "{% ifversion fpt or ghes > 3.0 or ghec %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}" ou "[Entrar em contato com o suporte](/packages/learn-github-packages/about-github-packages#contacting-support)." - -## Autenticar-se no {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% data reusables.package_registry.authenticate-packages-github-token %} - -### Efetuando a autenticação com um token de acesso pessoal - -{% data reusables.package_registry.required-scopes %} - -Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o npm editando seu arquivo *~/.npmrc* por usuário para incluir o seu token de acesso pessoal ou fazer o login no npm na linha de comando usando seu nome de usuário e token de acesso pessoal. - -Para efetuar a autenticação adicionando seu token de acesso pessoal ao seu arquivo *~/.npmrc*, edite o arquivo *~/.npmrc* para que o seu projeto inclua a linha a seguir, substituindo {% ifversion ghes or ghae %}*HOSTNAME* pelo nome do host {% data variables.product.product_location %} e {% endif %}*TOKEN* pelo seu token de acesso pessoal. Crie um novo arquivo *~/.npmrc* se um não existir. - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio habilitado: -{% endif %} - -```shell -//{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN -``` - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio desabilitado: - -```shell -$ npm login --registry=https://npm.pkg.github.com -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS -``` -{% endif %} - -Para efetuar a autenticação conectado no npm, use o comando `npm login` , substituindo o *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, o *TOKEN* pelo seu token de acesso pessoal e *PUBLIC-EMAIL-ADDRESS* pelo seu endereço de e-mail. - -Se {% data variables.product.prodname_registry %} não é seu registro de pacote padrão para usar npm e você deseja usar o comando `npm audit` , recomendamos que você use o sinalizador `--scope` com o proprietário do pacote quando você efetuar a autenticação no {% data variables.product.prodname_registry %}. - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio habilitado: -{% endif %} - -```shell -$ npm login --scope=@OWNER --registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} - -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS -``` - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio desabilitado: - -```shell -$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS -``` -{% endif %} - -## Publicar um pacote - -{% note %} - -**Nota:** Os nomes dos pacotes e escopos só devem usar letras minúsculas. - -{% endnote %} - -Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório {% data variables.product.prodname_dotcom %} que você especificar no campo nome do arquivo *package.json*. Por exemplo, você publicaria um pacote denominado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Você pode adicionar um resumo da página de listagem do pacote incluindo um arquivo *README.md* no diretório do seu pacote. Para obter mais informações, consulte "[Trabalhando com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" e "[Como criar Módulos de Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" na documentação do npm. - -Você pode publicar vários pacotes no mesmo repositório do {% data variables.product.prodname_dotcom %} incluindo um campo de `URL` no arquivo *package.json*. Para obter mais informações, consulte "[Publicar vários pacotes no mesmo repositório](#publishing-multiple-packages-to-the-same-repository)". - -É possível definir o mapeamento do escopo para o seu projeto usando um arquivo local *.npmrc* no projeto ou usando a opção `publishConfig` em *package.json*. {% data variables.product.prodname_registry %} só é compatível com pacotes npm com escopo definido. Pacotes com escopo têm nomes no formato `@owner/name`. Os pacotes com escopo sempre começam pelo símbolo `@`. Talvez seja necessário atualizar o nome no *package.json* para usar o nome com escopo. Por exemplo, `"name": "@codertocat/hello-world-npm"`. - -{% data reusables.package_registry.viewing-packages %} - -### Publicar um pacote usando o arquivo *.npmrc* local - -Você pode usar um arquivo *.npmrc* para configurar o mapeamento do escopo para o seu projeto. No arquivo *.npmrc*, use a URL e o proprietário da conta de {% data variables.product.prodname_registry %} para que {% data variables.product.prodname_registry %} saiba onde rotear as solicitações de pacotes. O uso de um arquivo *.npmrc* impede que outros desenvolvedores publiquem acidentalmente o pacote no npmjs.org em vez de {% data variables.product.prodname_registry %}. - -{% data reusables.package_registry.authenticate-step %} -{% data reusables.package_registry.create-npmrc-owner-step %} -{% data reusables.package_registry.add-npmrc-to-repo-step %} -1. Verifique o nome do pacote no *package.json* do seu projeto. O campo `name` (nome) deve conter o escopo e o nome do pacote. Por exemplo, se o pacote for chamado de "test" e você estiver publicando na organização "My-org" do {% data variables.product.prodname_dotcom %}, o campo `name` (nome) do seu *package.json* deverá ser `@my-org/test`. -{% data reusables.package_registry.verify_repository_field %} -{% data reusables.package_registry.publish_package %} - -### Publicar um pacote usando o `publishConfig` no arquivo *package.json* - -Você pode usar o elemento `publishConfig` no arquivo *package.json* para especificar o registro onde você quer o pacote publicado. Para obter mais informações, consulte "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação npm. - -1. Edite o arquivo *package.json* do seu pacote e inclua uma entrada `publishConfig`. - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio habilitado: - {% endif %} - ```shell - "publishConfig": { - "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" - }, - ``` - {% ifversion ghes %} - Se sua instância tem o isolamento de subdomínio desabilitado: - ```shell - "publishConfig": { - "registry":"https://HOSTNAME/_registry/npm/" - }, - ``` - {% endif %} -{% data reusables.package_registry.verify_repository_field %} -{% data reusables.package_registry.publish_package %} - -## Publicar vários pacotes no mesmo repositório - -Para publicar vários pacotes no mesmo repositório, você pode incluir a URL do repositório do {% data variables.product.prodname_dotcom %} no campo `repositório` do arquivo *package.json* para cada pacote. - -Para garantir que a URL do repositório esteja correta, substitua REPOSITÓRIO pelo nome do repositório que contém o pacote que você deseja publicar, e o PROPRIETÁRIO pelo nome de usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. - -O {% data variables.product.prodname_registry %} corresponderá ao repositório baseado na URL, em vez de ser baseado no nome do pacote. - -```shell -"repository":"https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", -``` - -## Instalar um pacote - -Você pode instalar pacotes do {% data variables.product.prodname_registry %} adicionando os pacotes como dependências no arquivo *package.json* para o seu projeto. Para obter mais informações sobre como usar um pacote *package.json* no projeto, consulte "[Trabalhar com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" na documentação npm. - -Por padrão, você pode adicionar pacotes a partir de uma organização. Para obter mais informações, consulte [Instalar pacotes de outras organizações](#installing-packages-from-other-organizations)." - -Você também precisa adicionar o arquivo *.npmrc* ao seu projeto para que todos os pedidos de instalação de pacotes {% ifversion ghae %}sejam encaminhados para{% else %}passando por{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes or ghec %}Ao encaminhar todos os pedidos de pacote através de de {% data variables.product.prodname_registry %}, você pode usar pacotes com escopo e sem escopo de *npmjs.org*. Para obter mais informações, consulte "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação do npm.{% endif %} - -{% ifversion ghae %} -Por padrão, você só pode usar pacotes do npm hospedados na sua empresa e você não poderá usar pacotes sem escopo. Para obter mais informações sobre o escopo de pacotes, consulte "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação do npm. Se necessário, o suporte de {% data variables.product.prodname_dotcom %} pode habilitar um proxy de upstream para npmjs.org. Uma vez habilitado um proxy upstream, se um pacote solicitado não for encontrado na sua empresa, {% data variables.product.prodname_registry %} fará uma solicitação de proxy para npmjs.org. -{% endif %} - -{% data reusables.package_registry.authenticate-step %} -{% data reusables.package_registry.create-npmrc-owner-step %} -{% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Configure *package.json* no seu projeto para usar o pacote que você está instalando. Para adicionar as suas dependências de pacote ao arquivo *package.json* para {% data variables.product.prodname_registry %}, especifique o nome do pacote com escopo completo, como, por exemplo, `@my-org/server`. Para pacotes do *npmjs.com*, especifique o nome completo, como `@babel/core` ou `@lodash`. Por exemplo, o arquivo *package.json* a seguir usa o pacote `@octo-org/octo-app` como uma dependência. - - ```json - { - "name": "@my-org/server", - "version": "1.0.0", - "description": "Server app that uses the @octo-org/octo-app package", - "main": "index.js", - "author": "", - "license": "MIT", - "dependencies": { - "@octo-org/octo-app": "1.0.0" - } - } - ``` -5. Instale o pacote. - - ```shell - $ npm install - ``` - -### Instalar pacotes de outras organizações - -Por padrão, você só pode usar pacotes do {% data variables.product.prodname_registry %} de uma organização. Se você deseja encaminhar solicitações de pacotes para várias organizações e usuários, você pode adicionar linhas adicionais ao seu arquivo *.npmrc* substituindo {% ifversion ghes or ghae %}*HOSTNAME* pelo nome do host {% data variables.product.product_location %} e {% endif %}*OWNER* pelo nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto. - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio habilitado: -{% endif %} - -```shell -@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %} -@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %} -``` - -{% ifversion ghes %} -Se sua instância tem o isolamento de subdomínio desabilitado: - -```shell -@OWNER:registry=https://HOSTNAME/_registry/npm -@OWNER:registry=https://HOSTNAME/_registry/npm -``` -{% endif %} - -{% ifversion ghes %} -## Usando o registro oficial do NPM - -{% data variables.product.prodname_registry %} permite que você acesse o registro oficial do NPM no `registry.npmjs.com`, caso seu administrador de {% data variables.product.prodname_ghe_server %} tenha habilitado esta funcionalidade. Para obter mais informações, consulte [Conectar ao registro oficial do NPM](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). -{% endif %} - -## Leia mais - -- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md deleted file mode 100644 index 347a099de3..0000000000 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -title: Working with the NuGet registry -intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-nuget-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages - - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages - - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: NuGet registry ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -{% data reusables.package_registry.admins-can-configure-package-types %} - -## Authenticating to {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %} - -Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository: - -```shell -dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" -``` - -{% data reusables.package_registry.authenticate-packages-github-token %} - -### Authenticating with a personal access token - -{% data reusables.package_registry.required-scopes %} - -To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. - -You must replace: -- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}. -- `TOKEN` with your personal access token. -- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes or ghae %} -- `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %} - -{% ifversion ghes %}If your instance has subdomain isolation enabled: -{% endif %} - -```xml - - - - - - - - - - - - - -``` - -{% ifversion ghes %} -If your instance has subdomain isolation disabled: - -```xml - - - - - - - - - - - - - -``` -{% endif %} - -## Publishing a package - -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT). - -### Publishing a package using a GitHub PAT as your API key - -If you don't already have a PAT to use for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - -1. Create a new project. - ```shell - dotnet new console --name OctocatApp - ``` -2. Package the project. - ```shell - dotnet pack --configuration Release - ``` - -3. Publish the package using your PAT as the API key. - ```shell - dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" - ``` - -{% data reusables.package_registry.viewing-packages %} - - -### Publishing a package using a *nuget.config* file - -When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. - -{% data reusables.package_registry.authenticate-step %} -2. Create a new project. - ```shell - dotnet new console --name OctocatApp - ``` -3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: - - `OWNER` with the name of the user or organization account that owns the repository containing your project. - - `REPOSITORY` with the name of the repository containing the package you want to publish. - - `1.0.0` with the version number of the package.{% ifversion ghes or ghae %} - - `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %} - ``` xml - - - - Exe - netcoreapp3.0 - OctocatApp - 1.0.0 - Octocat - GitHub - This package adds an Octocat! - https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY - - - - ``` -4. Package the project. - ```shell - dotnet pack --configuration Release - ``` - -5. Publish the package using the `key` you specified in the *nuget.config* file. - ```shell - dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" - ``` - -{% data reusables.package_registry.viewing-packages %} - -## Publishing multiple packages to the same repository - -To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. - -For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: - -``` xml - - - - Exe - netcoreapp3.0 - OctodogApp - 1.0.0 - Octodog - GitHub - This package adds an Octodog! - https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs - - - -``` - -``` xml - - - - Exe - netcoreapp3.0 - OctocatApp - 1.0.0 - Octocat - GitHub - This package adds an Octocat! - https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs - - - -``` - -## Installing a package - -Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. - -{% data reusables.package_registry.authenticate-step %} - -2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use: - ``` xml - - - - Exe - netcoreapp3.0 - OctocatApp - 1.0.0 - Octocat - GitHub - This package adds an Octocat! - https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY - - - - - - - - ``` - -3. Install the packages with the `restore` command. - ```shell - dotnet restore - ``` - -## Troubleshooting - -Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository . - -## Further reading - -- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md deleted file mode 100644 index 750df6513f..0000000000 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: Trabalhando com o registro do RubyGems -intro: 'Você pode configurar RubyGems para publicar um pacote em {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências em um projeto Ruby com o Bundler.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-rubygems-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages - - /packages/guides/configuring-rubygems-for-use-with-github-packages -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -shortTitle: Registro do Rubygems ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} -{% data reusables.package_registry.packages-ghae-release-stage %} - -**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. - -## Pré-requisitos - -- Você deve ter o rubygems 2.4.1 ou superior. Para encontrar sua versão do rubygems: - - ```shell - $ gem --version - ``` - -- Você deve ter o bundler 1.6.4 ou superior. Para encontrar sua versão do Bundler: - - ```shell - $ bundle --version - Bundler version 1.13.7 - ``` - -- Instale o keycutter para gerenciar várias credenciais. Para instalar o keycutter: - - ```shell - $ gem install keycutter - ``` - -## Autenticar-se no {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% data reusables.package_registry.authenticate-packages-github-token %} - -### Efetuando a autenticação com um token de acesso pessoal - -{% data reusables.package_registry.required-scopes %} - -Você pode efetuar a autenticação em {% data variables.product.prodname_registry %} com o RubyGems editando o arquivo *~/.gem/credentials* para publicação de gems, editando o arquivo *~/.gemrc* para instalar um único gem, ou usando o Bundler para rastrear e instalar um ou mais gems. - -Para publicar novos gems, você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} com RubyGems, editando seu arquivo *~/.gem/credentials* para incluir seu token de acesso pessoal. Crie um novo arquivo *~/.gem/credentials* se este arquivo não existir. - -Por exemplo, você criaria ou editaria um arquivo *~/.gem/credentials* para incluir o indicado a seguir, substituindo *TOKEN* pelo seu token de acesso pessoal. - -```shell -gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" } -``` - -To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Você deve substituir: - - `NOME DE USUÁRIO` pelo seu nome de usuário no {% data variables.product.prodname_dotcom %}. - - `TOKEN` pelo seu token de acesso pessoal. - - `PROPRIETÁRIO` com o nome da conta do usuário ou da organização que é proprietário do repositório que contém o seu projeto.{% ifversion ghes %} - - `URL` com a URL para o registro do Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %}. -{% elsif ghae %} - - `REGISTRY-URL` com a URL para o registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}. -{% endif %} - -Se você não tiver um arquivo *~/.gemrc*, crie um arquivo *~/.gemrc* usando este exemplo. - -```shell ---- -:backtrace: false -:bulk_threshold: 1000 -:sources: -- https://rubygems.org/ -- https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ -:update_sources: true -:verbose: true - -``` - -Para autenticar com o bundler, configure o Bundler para usar o seu token de acesso pessoal, substituindo *USERNAME* com seu {% data variables.product.prodname_dotcom %} nome de usuário, *TOKEN* com seu token de acesso pessoal, e *OWNER* com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto.{% ifversion ghes %} Substitua `URL REGISTRO` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %}.{% elsif ghae %}Substitua `REGISTRY-URL` pela URL do registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %} - -```shell -$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN -``` - -## Publicar um pacote - -{% data reusables.package_registry.default-name %} Por exemplo, ao publicar `octo-gem` na organização `octo-org` , {% data variables.product.prodname_registry %} publicará o gem no repositório `octo-org/octo-gem`. Para obter mais informações sobre como criar seu gem, consulte "[Criar seu próprio gem](http://guides.rubygems.org/make-your-own-gem/)" na documentação do RubyGems. - -{% data reusables.package_registry.viewing-packages %} - -{% data reusables.package_registry.authenticate-step %} -2. Crie o pacote da *gemspec* para criar o pacote *.gem*. - ```shell - gem build OCTO-GEM.gemspec - ``` -3. Publicar um pacote em {% data variables.product.prodname_registry %}, substituindo o `OWNER` pelo nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto e `OCTO-GEM` pelo nome do seu pacote de gemas.{% ifversion ghes %} substitui `REGISTRY-URL` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %}.{% elsif ghae %} Substitua `REGISTRY-URL` pela URL do registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %} - - ```shell - $ gem push --key github \ - --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ - OCTO-GEM-0.0.1.gem - ``` - -## Publicar vários pacotes no mesmo repositório - -Para publicar vários gems no mesmo repositório, você pode incluir a URL no repositório de {% data variables.product.prodname_dotcom %} no campo `github_repo` em `gem.metadata`. Se você incluir este campo, {% data variables.product.prodname_dotcom %} corresponderá ao repositório baseado neste valor, ao invés de usar o nome do gem.{% ifversion ghes or ghae %} Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %} - -```ruby -gem.metadata = { "github_repo" => "ssh://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } -``` - -## Instalar um pacote - -É possível usar gems do {% data variables.product.prodname_registry %} assim como você usa gems de *rubygems.org*. Você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} adicionando o seu usuário ou organização {% data variables.product.prodname_dotcom %} como uma fonte no arquivo *~/.gemrc* ou utilizando Bundler e editando seu *Gemfile*. - -{% data reusables.package_registry.authenticate-step %} -1. Para o Bundler, adicione seu usuário ou organização {% data variables.product.prodname_dotcom %} como uma fonte no seu *Gemfile* para buscar gems a partir desta nova fonte. Por exemplo, você pode adicionar um novo bloco de     fonte `ao seu Gemfile que usa {% data variables.product.prodname_registry %} apenas para os pacotes que você especificar, substituindo GEM NAME pelo pacote que você deseja instalar {% data variables.product.prodname_registry %} e OWNER pelo usuário ou organização que possui o repositório que contém o gem que você deseja instalar.{% ifversion ghes %} substitua REGISTRY-URL-` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %}.{% elsif ghae %} Substitua `REGISTRY-URL` pela URL do registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %} - - ```ruby - source "https://rubygems.org" - - gem "rails" - - source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do - gem "GEM NAME" - end - ``` - -3. Para versões do Bundler anteriores à 1.7.0, você deve adicionar uma nova `fonte` global. Para obter mais informações sobre como usar o Bundler, consulte a [documentação bundler.io](http://bundler.io/v1.5/gemfile.html). - - ```ruby - source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" - source "https://rubygems.org" - - gem "rails" - gem "GEM NAME" - ``` - -4. Instale o pacote: - ```shell - $ gem install octo-gem --version "0.1.1" - ``` - -## Leia mais - -- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md index c6e8326563..c2529a41aa 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md @@ -1,6 +1,6 @@ --- -title: Resolver um conflito de merge no GitHub -intro: Você pode resolver conflitos de merge simples que envolvem alterações concorrentes na linha usando o editor de conflitos. +title: Resolving a merge conflict on GitHub +intro: 'You can resolve simple merge conflicts that involve competing line changes on GitHub, using the conflict editor.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github - /articles/resolving-a-merge-conflict-on-github @@ -14,47 +14,51 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Resolver conflitos de merge +shortTitle: Resolve merge conflicts --- - -Você só pode resolver conflitos de merge no {% data variables.product.product_name %} causados por alterações concorrentes na linha, como quando as pessoas fazem alterações diferentes na mesma linha do mesmo arquivo em diferentes branches no seu repositório Git. Para todos os outros tipos de conflito de merge, você deve resolver o conflito localmente na linha de comando. Para obter mais informações, consulte "[Resolver um conflito de merge usando a linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line/)". +You can only resolve merge conflicts on {% data variables.product.product_name %} that are caused by competing line changes, such as when people make different changes to the same line of the same file on different branches in your Git repository. For all other types of merge conflicts, you must resolve the conflict locally on the command line. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)." {% ifversion ghes or ghae %} -Se um administrador do site desabilitar o editor de conflitos de merge para pull requests entre repositórios, você não poderá usar o editor de conflitos no {% data variables.product.product_name %} e deverá resolver os conflitos de merge na linha de comando. Por exemplo, se o editor de conflitos de merge estiver desabilitado, você não poderá usá-lo em uma pull request entre uma bifurcação e um repositório upstream. +If a site administrator disables the merge conflict editor for pull requests between repositories, you cannot use the conflict editor on {% data variables.product.product_name %} and must resolve merge conflicts on the command line. For example, if the merge conflict editor is disabled, you cannot use it on a pull request between a fork and upstream repository. {% endif %} {% warning %} -**Aviso:** Quando você resolve um conflito de merge no {% data variables.product.product_name %}, todo o [branch base](/github/getting-started-with-github/github-glossary#base-branch) da sua pull request é mesclada ao [branch head](/github/getting-started-with-github/github-glossary#head-branch). Verifique se você deseja realmente fazer commit para esse branch. Se o branch do cabeçalho for o branch-padrão do seu repositório, você terá a opção de criar um novo branch para servir como o branch do cabeçalho para o seu pull request. Se o branch head estiver protegido, você não será capaz de mesclar sua resolução de conflitos nele, então você será solicitado a criar um novo branch head. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". +**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %}, the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch). Make sure you really want to commit to this branch. If the head branch is the default branch of your repository, you'll be given the option of creating a new branch to serve as the head branch for your pull request. If the head branch is protected you won't be able to merge your conflict resolution into it, so you'll be prompted to create a new head branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." {% endwarning %} {% data reusables.repositories.sidebar-pr %} -1. Na lista "Pull Requests", clique na pull request que tem um conflito de merge que você deseja resolver. -1. Próximo à parte inferior da pull request, clique em **Resolve conflicts** (Resolver conflitos). ![Botão de resolução de conflitos de merge](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png) +1. In the "Pull Requests" list, click the pull request with a merge conflict that you'd like to resolve. +1. Near the bottom of your pull request, click **Resolve conflicts**. +![Resolve merge conflicts button](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png) {% tip %} - **Dica:** se o botão **Resolve conflicts** (Resolver conflitos) estiver desativado, o conflito de merge da pull request é muito complexo para ser resolvido no {% data variables.product.product_name %}{% ifversion ghes or ghae %} ou o administrador do site desabilitou o editor de conflitos para pull requests entre repositórios{% endif %}. Você deve resolver o conflito de merge usando um cliente Git alternativo, ou usando o Git na linha de comando. For more information see "\[Resolving a merge conflict using the command line\](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line." + **Tip:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)." {% endtip %} {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} - ![Exemplo de exibição de conflito de merge com marcadores de conflito](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png) -1. Se houver mais de um conflito de merge no arquivo, role para baixo até o próximo conjunto de marcadores de conflito e repita as etapas quatro e cinco para resolver o conflito de merge. -1. Depois de resolver todos os conflitos do arquivo, clique em **Mark as resolved** (Marcar como resolvido). ![Clique no botão marcar como resolvido](/assets/images/help/pull_requests/mark-as-resolved-button.png) -1. Se você tiver mais de um arquivo com um conflito, selecione o próximo arquivo que deseja editar no lado esquerdo da página abaixo de "conflicting files" (arquivos conflitantes) e repita as etapas de quatro a sete até resolver todos os conflitos de merge da pull request. ![Selecione o próximo arquivo conflitante, se aplicável](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png) -1. Depois de resolver todos os conflitos de merge, clique em **Commit merge** (Fazer commit do merge). Isso incorpora todo o branch base ao branch head. ![Botão de resolução de conflitos de merge](/assets/images/help/pull_requests/merge-conflict-commit-changes.png) -1. Se solicitado, revise o branch presente no commit. + ![View merge conflict example with conflict markers](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png) +1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict. +1. Once you've resolved all the conflicts in the file, click **Mark as resolved**. + ![Click mark as resolved button](/assets/images/help/pull_requests/mark-as-resolved-button.png) +1. If you have more than one file with a conflict, select the next file you want to edit on the left side of the page under "conflicting files" and repeat steps four through seven until you've resolved all of your pull request's merge conflicts. + ![Select next conflicting file if applicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png) +1. Once you've resolved all your merge conflicts, click **Commit merge**. This merges the entire base branch into your head branch. + ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png) +1. If prompted, review the branch that you are committing to. - Se o branch head for o branch padrão do repositório, você pode escolher atualizar este branch com as mudanças que você fez para resolver o conflito, ou criar um novo branch e usar isso como o branch head da pull request. ![Solicitar a revisão do branch que será atualizado](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png) + If the head branch is the default branch of the repository, you can choose either to update this branch with the changes you made to resolve the conflict, or to create a new branch and use this as the head branch of the pull request. + ![Prompt to review the branch that will be updated](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png) - Se você escolher criar um novo branch, digite um nome para o branch. + If you choose to create a new branch, enter a name for the branch. - Se o branch head de sua pull request estiver protegido, você deve criar um novo branch. Você não terá a opção de atualizar o branch protegido. + If the head branch of your pull request is protected you must create a new branch. You won't get the option to update the protected branch. - Clique em **Criar branch e atualizar meu pull request** ou **Eu entendi, continuar atualizando _BRANCH_**. O texto do botão corresponde à ação que você está executando. -1. Para fazer merge da pull request, clique em **Merge pull request** (Fazer merge da pull request). Para obter mais informações sobre outras opções de merge da pull request, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request/)". + Click **Create branch and update my pull request** or **I understand, continue updating _BRANCH_**. The button text corresponds to the action you are performing. +1. To merge your pull request, click **Merge pull request**. For more information about other pull request merge options, see "[Merging a pull request](/articles/merging-a-pull-request/)." -## Leia mais +## Further reading -- "[Sobre merges de pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)" +- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md index 90a7d54f83..9f460d5bbc 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md @@ -1,13 +1,13 @@ --- title: Adding a pull request to the merge queue -intro: 'If merge queues are enabled for the repository, you can add your pull requests to the merge queue once all the required checks have passed. {% data variables.product.product_name %} will merge the pull requests for you.' +intro: If merge queues are enabled for the repository, you can add your pull requests to the merge queue once all the required checks have passed. {% data variables.product.product_name %} will merge the pull requests for you. versions: fpt: '*' ghec: '*' topics: - Pull requests shortTitle: Add PR to merge queue -redirect_from: +redirect_from: - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue --- @@ -25,9 +25,10 @@ redirect_from: 1. In the "Pull Requests" list, click the pull request you'd like to add to the merge queue. 1. Click **Add to merge queue** to add your pull request to the merge queue. This enables the default **Queue and merge in a group** option. Alternatively, you can: - Add your pull request to the front of the queue by selecting the **Add to merge queue** drop down menu, and clicking **Jump the queue** (only available to repository maintainers and administrators). - - Directly merge your pull request by selecting the **Add to merge queue** drop down menu, and clicking **Directly merge** (only available to repository administrators). ![Merge queue options](/assets/images/help/pull_requests/merge-queue-options.png) + - Directly merge your pull request by selecting the **Add to merge queue** drop down menu, and clicking **Directly merge** (only available to repository administrators). + ![Merge queue options](/assets/images/help/pull_requests/merge-queue-options.png) - {% tip %} + {% tip %} **Tip:** The **Add to merge queue** button is only enabled once the pull request meets all the review/approval and status check requirements. @@ -56,5 +57,5 @@ The merge queue view shows the pull requests that are currently in the queue, wi ![Merge queue view](/assets/images/help/pull_requests/merge-queue-view.png) ## Handling pull requests removed from the merge queue - + {% data reusables.pull_requests.merge-queue-reject %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md index b6b29c8b03..0a76534207 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md @@ -1,6 +1,6 @@ --- -title: Fazer merge automático de um pull request -intro: Você pode aumentar a velocidade de desenvolvimento permitindo o merge automático de um pull request para que o pull request seja mesclado automaticamente quando todos os requisitos de merge forem atendidos. +title: Automatically merging a pull request +intro: You can increase development velocity by enabling auto-merge for a pull request so that the pull request will merge automatically when all merge requirements are met. product: '{% data reusables.gated-features.auto-merge %}' versions: fpt: '*' @@ -13,38 +13,43 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request - /github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request -shortTitle: Fazer merge do PR automaticamente + +shortTitle: Merge PR automatically --- +## About auto-merge -## Sobre o merge automático +If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. -Se você habilitar o merge automático para um pull request, este será mesclado automaticamente quando todas as revisões necessárias forem atendidas e as verificações de status forem aprovadas. O merge automático impede que você espere que os sejam atendidos para que você possa passar para outras tarefas. +Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} -Antes de usar o merge automático com um pull request, o merge automático deve ser habilitado para o repositório. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} -Depois que você ativar o merge automático para uma pull request, se alguém que não tiver permissões de gravação no repositório fizer push de novas alterações no branch principal ou alterar o branch de base do pull request, o merge automático será desabilitado. Por exemplo, se um mantenedor permitir o merge automático para um pull request a partir de uma bifurcação, o merge automático será desabilitado depois que um colaborador fizer push de novas alterações no pull request.{% endif %} +You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). -Você pode fornecer feedback sobre o merge automático [entrando em contato conosco](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). - -## Habilitar merge automático +## Enabling auto-merge {% data reusables.pull_requests.auto-merge-requires-branch-protection %} -Pessoas com permissões de gravação em um repositório podem habilitar o merge automático em um pull request. +People with write permissions to a repository can enable auto-merge for a pull request. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -1. Na lista "Pull Requests", clique no pull request para o qual você deseja fazer o merge automático. -1. Opcionalmente, para escolher um método de merge, selecione o menu suspenso **Habilitar merge automático** e, em seguida, clique em um método de merge. Para obter mais informações, consulte "[Sobre merges da pull request](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)". ![Menu suspenso "Habilitar merge automático"](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png) -1. Clique **Habilitar merge automático**. ![Botão para habilitar merge automático](/assets/images/help/pull_requests/enable-auto-merge-button.png) -1. Se você escolheu os métodos de merge ou combinação por squash, digite uma mensagem de commit e a descrição e escolha o endereço de e-mail que você deseja criar o commimt de merge.![Campos para inserir mensagem de commit e descrição e escolher o e-mail do autor do commit](/assets/images/help/pull_requests/pull-request-information-fields.png) -1. Clique em **Confirmar merge automático**. ![Botão para confirmar o merge automático](/assets/images/help/pull_requests/confirm-auto-merge-button.png) +1. In the "Pull Requests" list, click the pull request you'd like to auto-merge. +1. Optionally, to choose a merge method, select the **Enable auto-merge** drop-down menu, then click a merge method. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." + !["Enable auto-merge" drop-down menu](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png) +1. Click **Enable auto-merge**. + ![Button to enable auto-merge](/assets/images/help/pull_requests/enable-auto-merge-button.png) +1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit. + ![Fields to enter commit message and description and choose commit author email](/assets/images/help/pull_requests/pull-request-information-fields.png) +1. Click **Confirm auto-merge**. + ![Button to confirm auto-merge](/assets/images/help/pull_requests/confirm-auto-merge-button.png) -## Desabilitar o merge automático +## Disabling auto-merge -As pessoas com permissões de gravação em um repositório e autores de pull request podem desabilitar o merge automático em um pull request. +People with write permissions to a repository and pull request authors can disable auto-merge for a pull request. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -1. Na lista "Pull Requests", clique no pull request para o qual você deseja desabilitar o merge automático. -1. Na caixa de merge, clique em **Desabilitar o merge automático**. ![Botão para desabilitar o merge automático](/assets/images/help/pull_requests/disable-auto-merge-button.png) +1. In the "Pull Requests" list, click the pull request you'd like to disable auto-merge for. +1. In the merge box, click **Disable auto-merge**. + ![Button to disable auto-merge](/assets/images/help/pull_requests/disable-auto-merge-button.png) diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md index 627993c36f..b14dec6166 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md @@ -1,6 +1,6 @@ --- -title: Sobre branches -intro: Use um branch para isolar o trabalho de desenvolvimento sem afetar outros branches no repositório. Cada repositório tem um branch padrão e pode ter vários outros branches. Você pode fazer merge de um branch em outro branch usando uma pull request. +title: About branches +intro: 'Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches - /articles/working-with-protected-branches/ @@ -15,20 +15,19 @@ versions: topics: - Pull requests --- +## About branches -## Sobre branches +Branches allow you to develop features, fix bugs, or safely experiment with new ideas in a contained area of your repository. -Os branches permitem que você desenvolva recursos, corrija erros ou experimente com segurança novas ideias em uma área contida do seu repositório. +You always create a branch from an existing branch. Typically, you might create a new branch from the default branch of your repository. You can then work on this new branch in isolation from changes that other people are making to the repository. A branch you create to build a feature is commonly referred to as a feature branch or topic branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository/)." -Você sempre cria um branch a partir de um branch existente. Normalmente, você pode criar um novo branch a partir do branch-padrão do seu repositório. Você então poderá trabalhar nesse novo branch isolado das mudanças que outras pessoas estão fazendo no repositório. Um branch que você cria para produzir um recurso é comumente referido como um branch de recurso ou branch de tópico. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/articles/creating-and-deleting-branches-within-your-repository/)". +You can also use a branch to publish a {% data variables.product.prodname_pages %} site. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/what-is-github-pages)." -Também é possível usar um branch para publicar um site do {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/what-is-github-pages)". +You must have write access to a repository to create a branch, open a pull request, or delete and restore branches in a pull request. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)." -Você deve ter acesso de gravação em um repositório para criar um branch, abrir uma pull request ou excluir e restaurar branches em uma pull request. Para obter mais informações, consulte "[Permissões de acesso em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)." +## About the default branch -## Sobre o branch-padrão - -{% data reusables.branches.new-repo-default-branch %} O branch-padrão é o branch que {% data variables.product.prodname_dotcom %} exibe quando alguém visita o seu repositório. O branch padrão é também o branch inicial que o Git verifica localmente quando alguém clona o repositório. {% data reusables.branches.default-branch-automatically-base-branch %} +{% data reusables.branches.new-repo-default-branch %} The default branch is the branch that {% data variables.product.prodname_dotcom %} displays when anyone visits your repository. The default branch is also the initial branch that Git checks out locally when someone clones the repository. {% data reusables.branches.default-branch-automatically-base-branch %} By default, {% data variables.product.product_name %} names the default branch `main` in any new repository. @@ -36,48 +35,48 @@ By default, {% data variables.product.product_name %} names the default branch ` {% data reusables.branches.set-default-branch %} -## Trabalhando com branches +## Working with branches -Quando estiver satisfeito com seu trabalho, você poderá abrir uma pull request para fazer merge das alterações do branch atual (o branch *head*) com outro branch (o branch *base*). Para obter mais informações, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)". +Once you're satisfied with your work, you can open a pull request to merge the changes in the current branch (the *head* branch) into another branch (the *base* branch). For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Depois que uma pull request tiver sido mesclada ou fechada, você poderá excluir o branch head, já que isso não é mais necessário. Você deve ter permissão de gravação no repositório para excluir branches. Não é possível excluir branches associados diretamente a pull requests abertas. Para obter mais informações, consulte "[Excluindo e recuperando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)". +After a pull request has been merged, or closed, you can delete the head branch as this is no longer needed. You must have write access in the repository to delete branches. You can't delete branches that are directly associated with open pull requests. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" {% data reusables.pull_requests.retargeted-on-branch-deletion %} -Os seguintes diagramas ilustram isso. +The following diagrams illustrate this. - Here someone has created a branch called `feature1` from the `main` branch, and you've then created a branch called `feature2` from `feature1`. Existem pull requests abertas para ambos os branches. As setas indicam o branch base atual para cada pull request. Neste ponto, `feature1` é o branch base para `feature2`. Se a pull request para `feature2` for mesclada agora, o branch `feature2` será mesclado no `feature1`. + Here someone has created a branch called `feature1` from the `main` branch, and you've then created a branch called `feature2` from `feature1`. There are open pull requests for both branches. The arrows indicate the current base branch for each pull request. At this point, `feature1` is the base branch for `feature2`. If the pull request for `feature2` is merged now, the `feature2` branch will be merged into `feature1`. - ![botão-merge-pull-request](/assets/images/help/branches/pr-retargeting-diagram1.png) + ![merge-pull-request-button](/assets/images/help/branches/pr-retargeting-diagram1.png) In the next diagram, someone has merged the pull request for `feature1` into the `main` branch, and they have deleted the `feature1` branch. As a result, {% data variables.product.prodname_dotcom %} has automatically retargeted the pull request for `feature2` so that its base branch is now `main`. - ![botão-merge-pull-request](/assets/images/help/branches/pr-retargeting-diagram2.png) + ![merge-pull-request-button](/assets/images/help/branches/pr-retargeting-diagram2.png) Now when you merge the `feature2` pull request, it'll be merged into the `main` branch. -## Trabalhar com branches protegidos +## Working with protected branches -Os administradores de repositório podem habilitar proteções em um branch. Se estiver trabalhando em um branch que é protegido, não será possível excluir nem forçar o push no branch. Os administradores do repositório podem habilitar, de modo adicional, várias outras configurações de branch protegido para aplicar vários fluxos de trabalho antes que um branch passe por um merge. +Repository administrators can enable protections on a branch. If you're working on a branch that's protected, you won't be able to delete or force push to the branch. Repository administrators can additionally enable several other protected branch settings to enforce various workflows before a branch can be merged. {% note %} -**Observação:** se você for administrador de um repositório, será possível fazer merge de pull requests em branches com proteções de branch habilitadas, mesmo se a pull request não atender aos requisitos; a não ser que as proteções de branch tenham sido definidas para "Include administrators" (Incluir administradores). +**Note:** If you're a repository administrator, you can merge pull requests on branches with branch protections enabled even if the pull request does not meet the requirements, unless branch protections have been set to "Include administrators." {% endnote %} -Para verificar se é possível fazer merge de uma pull request, observe a caixa de merge na parte inferior da guia **Conversation (Conversa)** da pull request. Para obter mais informações, consulte "[Sobre branches protegidos](/articles/about-protected-branches)". +To see if your pull request can be merged, look in the merge box at the bottom of the pull request's **Conversation** tab. For more information, see "[About protected branches](/articles/about-protected-branches)." -Quando um branch estiver protegido: +When a branch is protected: -- Você não poderá excluir nem fazer um push forçado no branch. -- Se as verificações de status obrigatórias forem habilitadas no branch, não será possível fazer merge das alterações no branch até que todos os testes de CI obrigatórios sejam aprovados. Para obter mais informações, consulte "[Sobre verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)". -- Se as revisões obrigatórias de pull request forem habilitadas no branch, não será possível fazer merge de alterações no branch até que todos os requisitos na política da revisão de pull request tenham sido atendidos. Para obter mais informações, consulte "[Fazer merge de uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". -- Se a revisão obrigatória de um proprietário do código for habilitada em um branch, e uma pull request modificar o código que tem um proprietário, um proprietário do código deverá aprovar a pull request para que ela possa passar por merge. Para obter mais informações, consulte "[Sobre proprietários do código](/articles/about-code-owners)". -- Se a assinatura de commit obrigatória for habilitada em um branch, não será possível fazer push de qualquer commit no branch que não esteja assinado e verificado. Para obter mais informações, consulte "[Sobre verificação de assinatura de commit](/articles/about-commit-signature-verification)" e "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits). -- Se você usar o editor de conflitos do {% data variables.product.prodname_dotcom %}para corrigir conflitos para uma solicitação de pull request que você criou a partir de um branch protegido, {% data variables.product.prodname_dotcom %} ajudará você a criar um branch alternativo para a solicitação de pull request, para que a resolução dos conflitos possa ser mesclada. Para obter mais informações, consulte "[Resolvendo um conflito de merge no {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)". +- You won't be able to delete or force push to the branch. +- If required status checks are enabled on the branch, you won't be able to merge changes into the branch until all of the required CI tests pass. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." +- If required pull request reviews are enabled on the branch, you won't be able to merge changes into the branch until all requirements in the pull request review policy have been met. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." +- If required review from a code owner is enabled on a branch, and a pull request modifies code that has an owner, a code owner must approve the pull request before it can be merged. For more information, see "[About code owners](/articles/about-code-owners)." +- If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)." +- If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. For more information, see "[Resolving a merge conflict on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)." -## Leia mais +## Further reading -- "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" -- "[Branch](/articles/github-glossary/#branch)" no glossário do {% data variables.product.prodname_dotcom %} -- "[Branches em um Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" na documentação do Git +- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" +- "[Branch](/articles/github-glossary/#branch)" in the {% data variables.product.prodname_dotcom %} glossary +- "[Branches in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" in the Git documentation diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md index 42d8653ec8..bb13e13a07 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Sobre como comparar branches nas pull requests -intro: As pull requests exibem diffs para comparar as alterações feitas no branch de tópico com o branch base com o qual você deseja fazer merge. +title: About comparing branches in pull requests +intro: Pull requests display diffs to compare the changes you made in your topic branch against the base branch that you want to merge your changes into. redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests - /articles/about-comparing-branches-in-pull-requests @@ -13,60 +13,60 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Comparar branches +shortTitle: Compare branches --- - {% note %} -**Observação:** ao criar a pull request, é possível alterar o branch base com o qual você está comparando suas alterações. Para obter mais informações, consulte "[Criar uma pull request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)". +**Note:** When creating your pull request, you can change the base branch that you're comparing your changes against. For more information, see "[Creating a pull request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)." {% endnote %} -You can view proposed changes in a pull request in the Files changed tab. ![Guia Files changed (Arquivos alterados) da pull request](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) +You can view proposed changes in a pull request in the Files changed tab. +![Pull Request Files changed tab](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) -Em vez de exibir os commits em si, você pode ver as alterações propostas como elas aparecerão nos arquivos assim que a pull request passar pelo merge. Os arquivos aparecem em ordem alfabética na guia Files changed (Arquivos alterados). As adições aos arquivos aparecem em verde e são precedidas por um sinal de `+`, enquanto o conteúdo que foi removido aparece em vermelho e é precedido por um sinal de `-`. +Rather than viewing the commits themselves, you can view the proposed changes as they'll appear in the files once the pull request is merged. The files appear in alphabetical order within the Files changed tab. Additions to the files appear in green and are prefaced by a `+` sign while content that has been removed appears in red and is prefaced by a `-` sign. -## Opções de exibição de diff +## Diff view options {% tip %} -**Dica:** se estiver com dificuldades para entender o contexto de uma alteração, você poderá clicar em **View** (Exibir) na guia Files changed (Arquivos alterados) para ver o arquivo todo com as alterações propostas. +**Tip:** If you're having a hard time understanding the context of a change, you can click **View** in the Files changed tab to view the whole file with the proposed changes. {% endtip %} -Há várias opções de exibição de um diff: -- A exibição unificada mostra conteúdo atualizado e existente juntos em uma exibição linear. -- A exibição dividida mostra conteúdo antigo em um lado e novo conteúdo do outro lado. -- A exibição de diff avançado mostra uma visualização da aparência das alterações depois que a pull request passar por merge. -- A exibição da origem mostra as alterações na origem sem a formatação da exibição de diff avançado. +You have several options for viewing a diff: +- The unified view shows updated and existing content together in a linear view. +- The split view shows old content on one side and new content on the other side. +- The rich diff view shows a preview of how the changes will look once the pull request is merged. +- The source view shows the changes in source without the formatting of the rich diff view. -Também é possível optar por ignorar alterações de espaço em branco para obter uma exibição mais precisa das alterações importantes em uma pull request. +You can also choose to ignore whitespace changes to get a more accurate view of the substantial changes in a pull request. -![Menu de opções para exibição de diff](/assets/images/help/pull_requests/diff-settings-menu.png) +![Diff viewing options menu](/assets/images/help/pull_requests/diff-settings-menu.png) -Para simplificar a revisão das alterações em um pull request extenso, é possível filtrar o diff para mostrar apenas os tipos de arquivo selecionados, mostrar arquivos dos quais você é CODEOWNER, ocultar arquivos que você já visualizou ou ocultar arquivos excluídos. Para obter mais informações, consulte "[Filtrar aquivos em uma pull request por tipo de arquivo](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)". +To simplify reviewing changes in a large pull request, you can filter the diff to only show selected file types, show files you are a CODEOWNER of, hide files you have already viewed, or hide deleted files. For more information, see "[Filtering files in a pull request by file type](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - ![Menu suspenso File filter (Filtro de arquivo)](/assets/images/help/pull_requests/file-filter-menu.png) + ![File filter drop-down menu](/assets/images/help/pull_requests/file-filter-menu.png) -## Comparações de diff do Git de três pontos e dois pontos +## Three-dot and two-dot Git diff comparisons -Por padrão, as pull requests no {% data variables.product.prodname_dotcom %} mostram um diff de três pontos ou uma comparação entre a versão mais recente do branch de tópico e o commit onde o branch de tópico foi sincronizado pela última vez com o branch base. +By default, pull requests on {% data variables.product.prodname_dotcom %} show a three-dot diff, or a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch. -Para ver duas referências de committish em uma comparação de diff de dois pontos no {% data variables.product.prodname_dotcom %}, você pode editar o URL da página "Comparing changes" (Comparar alterações) do seu repositório. Para obter mais informações, consulte [Glossário do Git para "committish"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) no book site do _Pro Git_. +To see two committish references in a two-dot diff comparison on {% data variables.product.prodname_dotcom %}, you can edit the URL of your repository's "Comparing changes" page. For more information, see the [Git Glossary for "committish"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) from the _Pro Git_ book site. {% data reusables.repositories.two-dot-diff-comparison-example-urls %} -Um diff de dois pontos compara duas referências de committish do Git, como SHAs ou IDs de objeto (OIDs, Object IDs), diretamente entre si. No {% data variables.product.prodname_dotcom %}, as referências de committish do Git em uma comparação de diff de dois pontos devem ser enviadas por push ao mesmo repositório ou para suas bifurcações. +A two-dot diff compares two Git committish references, such as SHAs or OIDs (Object IDs), directly with each other. On {% data variables.product.prodname_dotcom %}, the Git committish references in a two-dot diff comparison must be pushed to the same repository or its forks. -Se desejar simular um diff de dois pontos em uma pull request e ver uma comparação entre as versões mais recentes de cada branch, você poderá fazer merge do branch base no branch de tópico, o que atualiza o último ancestral comum entre seus branches. +If you want to simulate a two-dot diff in a pull request and see a comparison between the most recent versions of each branch, you can merge the base branch into your topic branch, which updates the last common ancestor between your branches. -Para obter mais informações sobre os comandos do Git para comparar alterações, consulte "[Opções de diff do Git](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" no site do livro do _Pro Git_. +For more information about Git commands to compare changes, see "[Git diff options](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" from the _Pro Git_ book site. -## Motivos pelos quais os diffs não serão exibidos -- Você excedeu o limite total de arquivos ou de determinados tipos de arquivo. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#limits-for-viewing-content-and-diffs-in-a-repository)". -- Seu arquivo corresponde a uma regra no arquivo *.gitattributes* do repositório para impedir esse arquivo de ser exibido por padrão. Para obter mais informações, consulte "[Personalizar como os arquivos alterados aparecem no GitHub](/articles/customizing-how-changed-files-appear-on-github)". +## Reasons diffs will not display +- You've exceeded the total limit of files or certain file types. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#limits-for-viewing-content-and-diffs-in-a-repository)." +- Your file matches a rule in the repository's *.gitattributes* file to block that file from displaying by default. For more information, see "[Customizing how changed files appear on GitHub](/articles/customizing-how-changed-files-appear-on-github)." -## Leia mais +## Further reading -- "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" -- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" +- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)" +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index da44e557f8..04002cc4a8 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Sobre pull requests -intro: 'As pull requests permitem que você informe outras pessoas sobre as alterações das quais você fez push para um branch em um repositório no {% data variables.product.product_name %}. Depois que uma pull request é aberta, você pode discutir e revisar as possíveis alterações com colaboradores e adicionar commits de acompanhamento antes que as alterações sofram merge no branch base.' +title: About pull requests +intro: 'Pull requests let you tell others about changes you''ve pushed to a branch in a repository on {% data variables.product.product_name %}. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests - /articles/using-pull-requests/ @@ -15,30 +15,29 @@ versions: topics: - Pull requests --- - -## Sobre pull requests +## About pull requests {% note %} -**Observação:** ao trabalhar com pull requests, lembre-se do seguinte: -* Se estiver trabalhando no [modo de repositório compartilhado](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), é recomendável usar um branch de tópico para sua pull request. Embora você possa enviar pull requests de qualquer branch ou commit, com um branch de tópico, é possível fazer push de commits de acompanhamento caso seja preciso atualizar as alterações propostas. -* Ao fazer push de commits para uma pull request, não force o push. O push forçado pode corromper a pull request. +**Note:** When working with pull requests, keep the following in mind: +* If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes. +* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} -Você pode criar pull requests no {% data variables.product.prodname_dotcom_the_website %}, com {% data variables.product.prodname_desktop %}, em {% data variables.product.prodname_codespaces %}, em {% data variables.product.prodname_mobile %} e ao usar a CLI do GitHub. +You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI. -Após inicialização de uma pull request, você verá uma página de revisão que mostra uma visão geral de alto nível das alterações entre seu branch (o branch de comparação) e o branch base do repositório. É possível adicionar um resumo das alterações propostas, revisar as alterações feitas pelos commits, adicionar etiquetas, marcos e responsáveis, bem como fazer @menção a contribuidores individuais ou equipes. Para obter mais informações, consulte "[Criar uma pull request](/articles/creating-a-pull-request)". +After initializing a pull request, you'll see a review page that shows a high-level overview of the changes between your branch (the compare branch) and the repository's base branch. You can add a summary of the proposed changes, review the changes made by commits, add labels, milestones, and assignees, and @mention individual contributors or teams. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)." -Depois que tiver criado uma pull request, você poderá fazer push dos commits do branch de tópico para adicioná-los à sua pull request existente. Esses commits aparecerão em ordem cronológica na pull request e as alterações estarão visíveis na guia "Files chenged" (Arquivos alterados). +Once you've created a pull request, you can push commits from your topic branch to add them to your existing pull request. These commits will appear in chronological order within your pull request and the changes will be visible in the "Files changed" tab. -Outros contribuidores podem revisar as alterações propostas, adicionar comentários de revisão, contribuir com a discussão da pull request e, até mesmo, adicionar commits à pull request. +Other contributors can review your proposed changes, add review comments, contribute to the pull request discussion, and even add commits to the pull request. {% ifversion fpt or ghec %} -Você pode ver as informações sobre o status da implantação atual do branch e atividades passadas de implantação na guia "Conversa". Para obter mais informações, consulte "[Exibir atividade de implantação para um repositório](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)". +You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. For more information, see "[Viewing deployment activity for a repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)." {% endif %} -Quando estiver satisfeito com as alterações propostas, você poderá fazer merge da pull request. Se você está trabalhando em um modelo de repositório compartilhado, você cria uma pull request e, você ou outra pessoa, fará a mesclagem de suas alterações do seu branch de recurso no branch base que você especificar na sua pull request. Para obter mais informações, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request)". +After you're happy with the proposed changes, you can merge the pull request. If you're working in a shared repository model, you create a pull request and you, or someone else, will merge your changes from your feature branch into the base branch you specify in your pull request. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)." {% data reusables.pull_requests.required-checks-must-pass-to-merge %} @@ -46,32 +45,32 @@ Quando estiver satisfeito com as alterações propostas, você poderá fazer mer {% tip %} -**Dicas:** -- Para alternar entre as opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request, mantenha pressionados opçãoAltAlt e clique em **Mostrar desatualizados** ou **Ocultar desatualizados**. Para ver mais atalhos, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts)". -- Você pode combinar commits por squash ao fazer merge de uma pull request para obter uma exibição mais simplificada das alterações. Para obter mais informações, consulte "[Sobre merges da pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)". +**Tips:** +- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down optionAltAlt and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)." +- You can squash commits when merging a pull request to gain a more streamlined view of changes. For more information, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." {% endtip %} -É possível acessar seu painel a fim de encontrar rapidamente links para pull requests recentemente atualizadas nas quais você está trabalhando ou nas quais está inscrito. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)". +You can visit your dashboard to quickly find links to recently updated pull requests you're working on or subscribed to. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." -## Pull requests de rascunho +## Draft pull requests {% data reusables.gated-features.draft-prs %} -Ao criar uma pull request, você pode optar por criar uma que já está pronta para revisão ou uma pull request de rascunho. Não é possível fazer merge das pull requests, e os proprietários do código não são solicitados automaticamente a revisar pull requests de rascunho. Para obter mais informações sobre como criar uma pull request de rascunho, consulte "[Criar uma pull request](/articles/creating-a-pull-request)" e "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)". +When you create a pull request, you can choose to create a pull request that is ready for review or a draft pull request. Draft pull requests cannot be merged, and code owners are not automatically requested to review draft pull requests. For more information about creating a draft pull request, see "[Creating a pull request](/articles/creating-a-pull-request)" and "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)." -{% data reusables.pull_requests.mark-ready-review %} Você pode converter uma pull request em rascunho a qualquer momento. Para obter mais informações, consulte "[Alterar o stage de um pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)". +{% data reusables.pull_requests.mark-ready-review %} You can convert a pull request to a draft at any time. For more information, see "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." -## Diferenças entre commits em páginas de comparação e pull request +## Differences between commits on compare and pull request pages -As páginas de comparação e pull request usam métodos diferentes para calcular o diff para os arquivos alterados: +The compare and pull request pages use different methods to calculate the diff for changed files: -- As páginas de comparação mostram a diferença entre a ponta do ref principal e o ancestral comum atual (ou seja, a base de merge) do ref principal e de base. -- As páginas de pull request mostram a diferença entre a ponta do ref principal e o ancestral comum do ref principal e de base no momento em que o pull request foi criado. Consequentemente, a base de merge utilizada para a comparação pode ser diferente. +- Compare pages show the diff between the tip of the head ref and the current common ancestor (that is, the merge base) of the head and base ref. +- Pull request pages show the diff between the tip of the head ref and the common ancestor of the head and base ref at the time when the pull request was created. Consequently, the merge base used for the comparison might be different. -## Leia mais +## Further reading -- "[pull request](/articles/github-glossary/#pull-request)" no glossário do {% data variables.product.prodname_dotcom %} +- "[Pull request](/articles/github-glossary/#pull-request)" in the {% data variables.product.prodname_dotcom %} glossary - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)" -- "[Comentando em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" -- "[Fechar uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)" +- "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" +- "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index b1b1494429..f3bf58b413 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -1,6 +1,6 @@ --- -title: Criar e excluir branches no repositório -intro: 'Você pode criar ou excluir branches diretamente no {% data variables.product.product_name %}.' +title: Creating and deleting branches within your repository +intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository - /articles/deleting-branches-in-a-pull-request/ @@ -13,38 +13,41 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Criar & excluir branches +shortTitle: Create & delete branches --- - -## Criar um branch +## Creating a branch {% data reusables.repositories.navigate-to-repo %} -1. Opcionalmente, se quiser criar um novo branch a partir de um branch diferente do branch padrão para o repositório, clique em {% octicon "git-branch" aria-label="The branch icon" %} **NUMBER branches** e escolha outro branch: ![Link de branches numa página de visão geral](/assets/images/help/branches/branches-link.png) -1. Clique no menu seletor de branch. ![menu seletor de branch](/assets/images/help/branch/branch-selection-dropdown.png) -1. Digite um nome exclusivo para o novo branch e selecione **Create branch** (Criar branch). ![caixa de texto de criação de branch](/assets/images/help/branch/branch-creation-text-box.png) +1. Optionally, if you want to create your new branch from a branch other than the default branch for the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **NUMBER branches** then choose another branch: + ![Branches link on overview page](/assets/images/help/branches/branches-link.png) +1. Click the branch selector menu. + ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png) +1. Type a unique name for your new branch, then select **Create branch**. + ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png) -## Excluir um branch +## Deleting a branch {% data reusables.pull_requests.automatically-delete-branches %} {% note %} -**Observação:** Se o branch que você deseja excluir for o branch padrão do repositório, você deverá escolher um novo branch padrão antes de excluir o branch. For more information, see "[Setting the default branch](/github/administering-a-repository/setting-the-default-branch)." +**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." {% endnote %} -Se o branch que você deseja excluir estiver associado a um pull request aberto, você deverá fazer o merge ou fechar o pull request antes de excluir o branch. Para obter mais informações, consulte "[Fazer merge de um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" ou "[Fechar um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)". +If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" or "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} -1. Role até o branch que deseja excluir e clique em {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![excluir o branch](/assets/images/help/branches/branches-delete.png) +1. Scroll to the branch that you want to delete, then click {% octicon "trash" aria-label="The trash icon to delete the branch" %}. + ![delete the branch](/assets/images/help/branches/branches-delete.png) {% data reusables.pull_requests.retargeted-on-branch-deletion %} -Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)". +For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)." -## Leia mais +## Further reading - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)" -- "[Exibir branches no repositório](/github/administering-a-repository/viewing-branches-in-your-repository)" -- "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" +- "[Viewing branches in your repository](/github/administering-a-repository/viewing-branches-in-your-repository)" +- "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index 9eab7cd121..4bca185ea4 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -1,6 +1,6 @@ --- -title: Sobre bifurcações -intro: Uma bifurcação é uma cópia de um repositório que você gerencia. As bifurcações permitem fazer alterações em um projeto sem afetar o repositório original. Você pode fazer fetch de atualizações no repositório ou enviar alterações ao repositório original com pull requests. +title: About forks +intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks - /articles/about-forks @@ -14,33 +14,32 @@ versions: topics: - Pull requests --- +Forking a repository is similar to copying a repository, with two major differences: -Bifurcar um repositório é semelhante a copiar um repositório, com duas grandes diferenças: - -* Você pode usar uma pull request para sugerir alterações da sua bifurcação user-owned para o repositório original, também conhecido como o repositório *upstream*. -* Você pode transmitir alterações do repositório upstream para a sua bifurcação local sincronizando a bifurcação com o repositório upstream. +* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository. +* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository. {% data reusables.repositories.you-can-fork %} {% ifversion fpt or ghec %} -Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, existem outras restrições nos repositórios que você pode bifurcar. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} {% data reusables.repositories.desktop-fork %} -Excluir uma bifurcação não exclui o repositório upstream original. Você pode fazer quaisquer alterações que quiser em sua bifurcação — adicionar colaboradores, renomear arquivos, gerar {% data variables.product.prodname_pages %}— sem efeito no original.{% ifversion fpt or ghec %} Você não pode restaurar um repositório bifurcado excluído. Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %} +Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} -Em projetos de código aberto, as bifurcações são usadas com frequência para iterar ideias ou alterações antes que elas sejam oferecidas de volta ao repositório upstream. Ao fazer alterações em sua bifurcação user-owned e abrir uma pull request que compara seu trabalho com o repositório upstream, você pode dar a qualquer pessoa com acesso push ao repositório upstream permissão para fazer push das alterações no seu branch de pull requests. Isso agiliza a colaboração ao permitir que os mantenedores de repositório façam commits ou executem testes localmente em seu branch de pull requests a partir de uma bifurcação de propriedade do usuário antes de fazer merge. Você não pode dar permissões de push a uma bifurcação de propriedade de uma organização. +In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch. This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. {% data reusables.repositories.private_forks_inherit_permissions %} -Se você desejar criar um novo repositório a partir do conteúdo de um repositório existente, mas não desejar mesclar suas alterações a montante no futuro, Você pode duplicar o repositório ou, se o repositório for um modelo, você poderá usar o repositório como um modelo. Para obter mais informações, consulte "[Duplicando um repositório](/articles/duplicating-a-repository)" e "[Criando um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". +If you want to create a new repository from the contents of an existing repository but don't want to merge your changes upstream in the future, you can duplicate the repository or, if the repository is a template, use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)". -## Leia mais +## Further reading -- "[Sobre modelos de desenvolvimento colaborativo](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)" -- "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)" -- [Guias de código aberto](https://opensource.guide/){% ifversion fpt or ghec %} +- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)" +- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)" +- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index fef8ad3791..d71fb84226 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -1,6 +1,6 @@ --- -title: O que acontece com as bifurcações quando um repositório é excluído ou muda de visibilidade? -intro: A exclusão do repositório ou a mudança na visibilidade dele afeta as bifurcações desse repositório. +title: What happens to forks when a repository is deleted or changes visibility? +intro: Deleting your repository or changing its visibility affects that repository's forks. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility - /articles/changing-the-visibility-of-a-network/ @@ -14,75 +14,74 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Visibilidade excluída ou alterada +shortTitle: Deleted or changes visibility --- - {% data reusables.repositories.deleted_forks_from_private_repositories_warning %} -## Excluir um repositório privado +## Deleting a private repository -Quando você exclui um repositório privado, todas as bifurcações privadas dele também são excluídas. +When you delete a private repository, all of its private forks are also deleted. {% ifversion fpt or ghes or ghec %} -## Excluir um repositório público +## Deleting a public repository -Quando você exclui um repositório público, uma das bifurcações públicas existentes é escolhida para ser o novo repositório principal. Todos os outros repositórios são bifurcados a partir desse principal e as pull request subsequentes vão para ele também. +When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent. {% endif %} -## Permissões e bifurcações privadas +## Private forks and permissions {% data reusables.repositories.private_forks_inherit_permissions %} {% ifversion fpt or ghes or ghec %} -## Mudar de repositório público para repositório privado +## Changing a public repository to a private repository -Se um repositório público passa a ser privado, as bifurcações públicas dele são divididas em uma nova rede. Assim como na exclusão de um repositório público, uma das bifurcações públicas existentes é escolhida para ser o novo repositório principal, todos os outros repositórios são bifurcados a partir dele e as pull requests subsequentes vão para esse repositório também. +If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent. -Ou seja, as bifurcações de um repositório público permanecerão públicas na própria rede de repositório separada, mesmo depois que o repositório principal se tornar privado. Isso permite que os proprietários da bifurcação continuem trabalhando e colaborando sem interrupção. Se as bifurcações públicas não tiverem sido movidas para uma rede separada dessa forma, os proprietários dessas bifurcações precisarão obter as [permissões de acesso](/articles/access-permissions-on-github) apropriadas para fazer pull de alterações do repositório principal (agora privado) e enviar pull requests para ele, ainda que antes não precisassem dessas permissões. +In other words, a public repository's forks will remain public in their own separate repository network even after the parent repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate [access permissions](/articles/access-permissions-on-github) to pull changes from and submit pull requests to the (now private) parent repository—even though they didn't need those permissions before. {% ifversion ghes or ghae %} -Se um repositório público tiver acesso de leitura anônimo do Git habilitado e o repositório passar a ser privado, todas as bifurcações do repositório perderão o acesso de leitura anônimo do Git e retornarão à configuração padrão desabilitada. Se um repositório bifurcado passar a ser público, os administradores dele poderão reabilitar o acesso de leitura anônimo do Git. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". +If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." {% endif %} -### Excluir o repositório privado +### Deleting the private repository -Se um repositório público passa ser privado e depois é excluído, as bifurcações públicas dele continuam existindo em uma rede separada. +If a public repository is made private and then deleted, its public forks will continue to exist in a separate network. -## Mudar de repositório privado para repositório público +## Changing a private repository to a public repository -Se um repositório privado passa a ser público, cada uma das bifurcações privadas dele é transformada em um repositório privado autônomo e se torna o principal da própria rede de repositório nova. As bifurcações privadas nunca são transformadas em públicas de forma automática porque podem conter commits confidenciais que não devem ser expostos publicamente. +If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the parent of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly. -### Excluir o repositório público +### Deleting the public repository -Se um repositório privado passa a ser público e depois é excluído, as bifurcações privadas dele continuam existindo como repositórios privados autônomos em redes separadas. +If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks. {% endif %} {% ifversion fpt or ghae or ghes or ghec %} -## Alterar a visibilidade de um repositório interno +## Changing the visibility of an internal repository {% note %} -**Observação:** {% data reusables.gated-features.internal-repos %} +**Note:** {% data reusables.gated-features.internal-repos %} {% endnote %} -Se a política para a sua empresa permitir a bifurcação, qualquer bifurcação de um repositório interno será privado. Se você alterar a visibilidade de um repositório interno, qualquer bifurcação pertencente a uma organização ou conta de usuário continuará sendo privada. +If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private. -### Excluir o repositório interno +### Deleting the internal repository -Se você alterar a visibilidade de um repositório interno e, em seguida, excluir o repositório, as bifurcações continuarão a existir em uma rede separada. +If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network. {% endif %} -## Leia mais +## Further reading -- "[Definir a visibilidade de um repositório](/articles/setting-repository-visibility)" -- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" -- "[Gerenciando a política de bifurcação de seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- "[Gerenciar a política de bifurcação para sua organização](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" +- "[Setting repository visibility](/articles/setting-repository-visibility)" +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" +- "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories)" diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md index 2aa4896666..75eca09a64 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md @@ -1,8 +1,6 @@ --- -title: Criar um commit com vários autores -intro: |- - Você pode atribuir um commit a mais de um autor adicionando um ou mais trailers "Co-authored-by" à mensagem do commit. Os commits coautorados podem ser vistos no {% data variables.product.product_name %}{% ifversion ghes or ghae %} e podem ser incluídos no gráfico de contribuições de perfil e nas estatísticas - do repositório{% endif %}. +title: Creating a commit with multiple authors +intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% ifversion ghes or ghae %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.' redirect_from: - /articles/creating-a-commit-with-multiple-authors - /github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors @@ -12,40 +10,39 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Com vários autores +shortTitle: With multiple authors --- +## Required co-author information -## Informações obrigatórias do coautor - -Para poder adicionar um coautor a um commit, você deve saber o e-mail adequado a ser usado para cada coautor. For the co-author's commit to count as a contribution, you must use the email associated with their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. {% ifversion fpt or ghec %} -Se uma pessoa optar por manter o respectivo endereço de e-mail privado, você deverá usar o e-mail `no-reply` dela fornecido pelo {% data variables.product.product_name %} para proteger a privacidade. Caso contrário, o e-mail do coautor estará disponível para o público na mensagem do commit. Se desejar manter seu e-mail privado, você poderá usar um e-mail `no-reply` fornecido pelo {% data variables.product.product_name %} para operações de Git e pedir que outros coautores listem seu e-mail `no-reply` nos trailers de commit. +If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers. -Para obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)." +For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." {% tip %} - **Dica:** você pode ajudar um coautor a encontrar o endereço de e-mail de preferência dele compartilhando essas informações: - - Para encontrar o e-mail `no-reply` fornecido pelo {% data variables.product.product_name %}, navegue até a página de configurações do e-mail em "Keep my email address private" (Manter meu endereço de e-mail privado). - - Para encontrar o e-mail usado para configurar o Git no seu computador, execute `git config user.email` na linha de comando. + **Tip:** You can help a co-author find their preferred email address by sharing this information: + - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private." + - To find the email you used to configure Git on your computer, run `git config user.email` on the command line. {% endtip %} {% endif %} -## Criar commits coautorados usando o {% data variables.product.prodname_desktop %} +## Creating co-authored commits using {% data variables.product.prodname_desktop %} -Você pode usar o {% data variables.product.prodname_desktop %} para criar um commit com um coautor. Para obter mais informações, consulte "[Escrever uma mensagem do commit e fazer push das alterações](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" e [{% data variables.product.prodname_desktop %}](https://desktop.github.com). +You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com). -![Adicionar um coautor à mensagem do commit](/assets/images/help/desktop/co-authors-demo-hq.gif) +![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif) -## Criar commits coautorados na linha de comando +## Creating co-authored commits on the command line {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias. +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. ```shell $ git commit -m "Refactor usability tests. > @@ -53,13 +50,13 @@ Você pode usar o {% data variables.product.prodname_desktop %} para criar um co ``` {% tip %} - **Dica:** Se estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, certifique-se de que existam duas novas linhas entre o final da sua descrição de commit e o indicador `Co-authored-by:`. + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer. {% endtip %} -3. Na próxima linha da mensagem do commit, digite `Co-authored-by: name ` com informações específicas para cada coautor. Depois das informações do coautor, adicione aspas de fechamento. +3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. - Se estiver adicionando vários coautores, dê a cada um a própria linha e o trailer de commit `Co-authored-by:`. + If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. ```shell $ git commit -m "Refactor usability tests. > @@ -68,25 +65,26 @@ Você pode usar o {% data variables.product.prodname_desktop %} para criar um co Co-authored-by: another-name <another-name@example.com>" ``` -O novo commit e a mensagem aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. Para obter mais informações, consulte "[Fazer push das alterações em um repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)". +The new commit and message will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)." -## Criar commits coautorados no {% data variables.product.product_name %} +## Creating co-authored commits on {% data variables.product.product_name %} -Depois que fizer alterações em um arquivo usando o editor web no {% data variables.product.product_name %}, você poderá criar um commit coautorado adicionando um trailer `Co-authored-by:` à mensagem do commit. +After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message. {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -2. Depois de fazer as alterações juntos, na parte inferior da página, digite uma mensagem de commit curta e significativa que descreve as alterações feitas. ![Mensagem do commit para sua alteração](/assets/images/help/repository/write-commit-message-quick-pull.png) -3. Na caixa de texto abaixo da mensagem do commit, adicione `Co-authored-by: name ` com informações específicas para cada coautor. Se estiver adicionando vários coautores, dê a cada um a própria linha e o trailer de commit `Co-authored-by:`. +2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. + ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) +3. In the text box below your commit message, add `Co-authored-by: name ` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. - ![Exemplo de trailer de coautor da mensagem do commit na segunda caixa de texto da mensagem do commit](/assets/images/help/repository/write-commit-message-co-author-trailer.png) -4. Clique em **Commit changes** (Fazer commit de alterações) ou **Propose changes** (Propor alterações). + ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png) +4. Click **Commit changes** or **Propose changes**. -O novo commit e a mensagem aparecerão no {% data variables.product.product_location %}. +The new commit and message will appear on {% data variables.product.product_location %}. -## Leia mais +## Further reading {% ifversion ghes or ghae %} -- "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)" -- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} -- "[Exibir contribuidores de um projeto](/articles/viewing-a-projects-contributors)" -- "[Alterar uma mensagem do commit](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" -- "[Fazer commit e revisar alterações no seu projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" na documentação do {% data variables.product.prodname_desktop %} +- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" +- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} +- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)" +- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" +- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md index 8568265329..613caee543 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md @@ -1,6 +1,6 @@ --- -title: 'O commit aparece no GitHub, mas não no meu clone local' -intro: 'Às vezes, um commit poderá ser visto no {% data variables.product.product_name %}, mas não existirá no clone local do repositório.' +title: Commit exists on GitHub but not in my local clone +intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.' redirect_from: - /articles/commit-exists-on-github-but-not-in-my-local-clone - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone @@ -10,73 +10,83 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Commit ausente no clone local +shortTitle: Commit missing in local clone --- +When you use `git show` to view a specific commit on the command line, you may get a fatal error. -Quando você usa `git show` para exibir um commit específico na linha de comando, é possível que veja um erro fatal. - -Por exemplo, talvez você receba um erro de `bad object` no local: +For example, you may receive a `bad object` error locally: ```shell $ git show 1095ff3d0153115e75b7bca2c09e5136845b5592 > fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592 ``` -No entanto, ao exibir o commit no {% data variables.product.product_location %}, você poderá vê-lo sem qualquer problema: +However, when you view the commit on {% data variables.product.product_location %}, you'll be able to see it without any problems: `github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592` -Há várias explicações possíveis: +There are several possible explanations: -* O repositório local está desatualizado. -* O branch que contém o commit foi excluído, de modo que o commit não é mais referenciado. -* Alguém fez push forçado no commit. +* The local repository is out of date. +* The branch that contains the commit was deleted, so the commit is no longer referenced. +* Someone force pushed over the commit. -## O repositório local está desatualizado +## The local repository is out of date -O repositório local pode não ter o commit ainda. Para levar informações de seu repositório remote para o clone local, use `git fetch`: +Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`: ```shell $ git fetch remote ``` -Isso copia informações com segurança do repositório remote para o clone local sem fazer alterações nos arquivos em que você fez checkout. É possível usar `git fetch upstream` para obter informações de um repositório bifurcado ou `git fetch origin` para obter informações de um repositório que você apenas clonou. +This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out. +You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned. {% tip %} -**Dica**: para obter mais informações, leia sobre [como gerenciar remotes e fazer fetch de dados](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) no livro [Pro Git](https://git-scm.com/book). +**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book. {% endtip %} -## O branch que continha o commit foi excluído +## The branch that contained the commit was deleted -Se um colaborador no repositório tiver excluído o brach contendo o commit ou tiver forçado o push no branch, o commit ausente poderá ter ficado órfão (isto é, não poderá ser alcançado de qualquer referência) e, portanto, o fetch dele não poderá ser feito no clone local. +If a collaborator on the repository has deleted the branch containing the commit +or has force pushed over the branch, the missing commit may have been orphaned +(i.e. it cannot be reached from any reference) and therefore will not be fetched +into your local clone. -Felizmente, se algum colaborador tiver um clone local do repositório com o commit ausente, ele poderá fazer push dele de volta no {% data variables.product.product_name %}. Ele precisa ter certeza de que o commit é referenciado por um branch local e, em seguida, fazer push dele como um novo branch para o {% data variables.product.product_name %}. +Fortunately, if any collaborator has a local clone of the repository with the +missing commit, they can push it back to {% data variables.product.product_name %}. They need to make sure the commit +is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}. -Vamos dizer que a pessoa ainda tem um branch local (chame-o de `B`) que contém o commit. Isso pode estar rastreando o branch que teve push forçado ou excluído e ele simplesmente ainda não foi atualizado. Para preservar o commit, ele pode fazer push desse branch local em um novo branch (chame-o de `recover-B`) no {% data variables.product.product_name %}. Para este exemplo, vamos supor que ele tenha um remote chamado `upstream` pelo qual ele tem acesso push a `github.com/$account/$repository`. +Let's say that the person still has a local branch (call it `B`) that contains +the commit. This might be tracking the branch that was force pushed or deleted +and they simply haven't updated yet. To preserve the commit, they can push that +local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}. For this example, +let's assume they have a remote named `upstream` via which they have push access +to `github.com/$account/$repository`. -A outra pessoa executa: +The other person runs: ```shell $ git branch recover-B B -# Criar um branch local fazendo referência ao commit +# Create a new local branch referencing the commit $ git push upstream B:recover-B -# Fazer push do local B para o novo branch upstream, criando referência ao commit +# Push local B to new upstream branch, creating new reference to commit ``` -Agora, *você* pode executar: +Now, *you* can run: ```shell $ git fetch upstream recover-B -# Fazer fetch de commit no repositório local. +# Fetch commit into your local repository. ``` -## Evitar pushes forçados +## Avoid force pushes -Evite o push forçado em um repositório, a menos que seja absolutamente necessário. Isso se aplica especialmente quando mais de uma pessoa pode fazer push no repositório. +Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests. -## Leia mais +## Further reading -- ["Trabalhar com remotes" no livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) -- ["Recuperação de dados" no livro _Pro Git_](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) +- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index 6a6c47bd6e..5bc13e0a96 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -1,57 +1,58 @@ --- -title: Por que meus commits estão vinculados ao usuário errado? +title: Why are my commits linked to the wrong user? redirect_from: - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/ - /articles/why-are-my-commits-linked-to-the-wrong-user - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user - /github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user -intro: 'O {% data variables.product.product_name %} usa o endereço de e-mail no header do commit para vincular o commit a um usuário do GitHub. Se seus commits estão sendo vinculados a outro usuário, ou não vinculados a um usuário, você pode precisar alterar suas configurações locais de configuração do Git, {% ifversion not ghae %}, adicionar um endereço de e-mail nas configurações de e-mail da sua conta ou fazer ambas as coisas{% endif %}.' +intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -shortTitle: Vinculado ao usuário incorreto +shortTitle: Linked to wrong user --- - {% tip %} -**Observação**: se os commits estiverem vinculados a outro usuário, não significa que o usuário possa acessar o repositório pertencente a você. Um usuário só poderá acessar um repositório seu se você adicioná-lo como colaborador ou incluí-lo em uma equipe que tenha acesso ao repositório. +**Note**: If your commits are linked to another user, that does not mean the user can access your repository. A user can only access a repository you own if you add them as a collaborator or add them to a team that has access to the repository. {% endtip %} -## Commits vinculados a outro usuário +## Commits are linked to another user -Se seus commits estiverem vinculados a outro usuário, isso significa que o endereço de e-mail nas configurações locais do Git está conectado à conta desse usuário em {% data variables.product.product_name %}. Neste caso, você pode alterar o e-mail nas configurações locais do Git, {% ifversion ghae %} ao endereço associado à sua conta em {% data variables.product.product_name %} para vincular seus commits futuros. Os commits antigos não serão vinculados. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} account to link future commits to your account. +If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% ifversion ghae %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} account to link future commits to your account. -1. Para alterar o endereço de e-mail na sua configuração Git local, siga os passos em "[Definir o seu endereço de e-mail de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Se você trabalha em várias máquinas, precisa alterar essa configuração em cada uma deles. -2. Adicione o endereço de e-mail da etapa 2 às configurações da sua conta seguindo os passos em "[Adicionar um endereço de e-mail à sua conta GitHub](/articles/adding-an-email-address-to-your-github-account)".{% endif %} +1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one. +2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %} -Os commits criados a partir daí serão vinculados à sua conta. +Commits you make from this point forward will be linked to your account. -## Commits não vinculados a nenhum usuário +## Commits are not linked to any user -Se seus commits não estiverem vinculados a nenhum usuário, o nome do autor do commit não será exibido como um link para o perfil de um usuário. +If your commits are not linked to any user, the commit author's name will not be rendered as a link to a user profile. -Para verificar o endereço de e-mail usado para esses commits e conectar commits à sua conta, siga estas etapas: +To check the email address used for those commits and connect commits to your account, take the following steps: -1. Navegue até o commit clicando no link da mensagem do commit. ![Link da mensagem do commit](/assets/images/help/commits/commit-msg-link.png) -2. Para ler uma mensagem sobre o motivo do commit não estar vinculado, passe o mouse sobre o {% octicon "question" aria-label="Question mark" %} azul à direita do nome de usuário. ![Mensagem do commit exibida ao passar o mouse](/assets/images/help/commits/commit-hover-msg.png) +1. Navigate to the commit by clicking the commit message link. +![Commit message link](/assets/images/help/commits/commit-msg-link.png) +2. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username. +![Commit hover message](/assets/images/help/commits/commit-hover-msg.png) - - **Autor não reconhecido (com endereço de e-mail)** Se você vir esta mensagem com um endereço de e-mail, o endereço que você usou para criar o commit não estará conectado à sua conta em {% data variables.product.product_name %}. {% ifversion not ghae %}Para vincular seus commits, [adicione o endereço de e-mail às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account).{% endif %} Se o endereço de e-mail tiver um Gravatar associado, o Gravatar será exibido ao lado do commit, em vez do Octoact cinza padrão. - - **Autor não reconhecido (sem endereço de e-mail)** Se você vir esta mensagem sem um endereço de e-mail. significa que você usou um endereço de e-mail genérico que não pode ser conectado à sua conta em {% data variables.product.product_name %}.{% ifversion not ghae %} Você deverá [definir seu endereço de e-mail no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %} - - **E-mail inválido** O endereço de e-mail nas configurações locais do Git está em branco ou não está formatado como um endereço de e-mail.{% ifversion not ghae %} Você deverá [definir seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %} + - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% ifversion not ghae %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat. + - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} + - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} {% ifversion ghae %} -Você pode alterar o e-mail nas configurações locais do Git para o endereço associado à sua conta para vincular seus futuros commits. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Configurar o endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". +You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)." {% endif %} {% warning %} -Caso a configuração local do Git contenha um endereço de e-mail genérico ou um endereço de e-mail já anexado à conta de outro usuário, os commits anteriores não serão vinculados à sua conta. Embora o Git permita que você altere o endereço de e-mail usado para commits anteriores, é recomendável evitar isso, principalmente em um repositório compartilhado. +If your local Git configuration contained a generic email address, or an email address that was already attached to another user's account, then your previous commits will not be linked to your account. While Git does allow you to change the email address used for previous commits, we strongly discourage this, especially in a shared repository. {% endwarning %} -## Leia mais +## Further reading -* "[Pesquisar commits](/search-github/searching-on-github/searching-commits)" +* "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md index f1f775c4cb..b8d5a45fc7 100644 --- a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -1,6 +1,6 @@ --- -title: Arquivar repositórios -intro: Você pode arquivar um repositório a fim de torná-lo somente leitura para todos os usuários e indicar que ele não está mais sendo mantido ativamente. Também é possível desarquivar repositórios que foram arquivados. +title: Archiving repositories +intro: You can archive a repository to make it read-only for all users and indicate that it's no longer actively maintained. You can also unarchive repositories that have been archived. redirect_from: - /articles/archiving-repositories - /github/creating-cloning-and-archiving-repositories/archiving-repositories @@ -17,31 +17,33 @@ topics: - Repositories --- -## Sobre o arquivamento do repositório +## About repository archival {% ifversion fpt or ghec %} {% note %} -**Observação:** se você tiver um plano de cobrança por repositório herdado, será feita a cobrança pelo seu repositório arquivado. Se não desejar ser cobrado por um repositório arquivado, será preciso atualizar para um novo produto. Para obter mais informações, consulte os "[Produtos da {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". +**Note:** If you have a legacy per-repository billing plan, you will still be charged for your archived repository. If you don't want to be charged for an archived repository, you must upgrade to a new product. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)." {% endnote %} {% endif %} {% data reusables.repositories.archiving-repositories-recommendation %} -Depois que um repositório é arquivado, não é possível adicionar nem remover colaboradores ou equipes. Os contribuidores com acesso ao repositório podem apenas bifurcar ou marcar com estrela seu projeto. +Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project. -Quando um repositório é arquivado, seus problemas, pull requests, código, etiquetas, marcos, projetos, wiki, versões, commits, tags, branches, reações, alertas de varredura de código e comentários tornam-se somente leitura. Para fazer alterações em um repositório arquivado, você deve desarquivar o repositório primeiro. +When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first. -É possível pesquisar repositórios arquivados. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de repositórios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". +You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)." -## Arquivar um repositório +## Archiving a repository {% data reusables.repositories.archiving-repositories-recommendation %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em "Danger Zone" (Zona de perigo), clique em **Archive this repository** (Arquivar este repositório) ou em **Unarchive this repository** (Desarquivar este repositório). ![Botão Archive this repository (Arquivar este repositório)](/assets/images/help/repository/archive-repository.png) -4. Leia os avisos. -5. Digite o nome do repositório que deseja arquivar ou desarquivar. ![Avisos de arquivamento de repositório](/assets/images/help/repository/archive-repository-warnings.png) -6. Clique em **I understand the consequences, archive this repository** (Entendo as consequências, arquive este repositório). +3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**. + ![Archive this repository button](/assets/images/help/repository/archive-repository.png) +4. Read the warnings. +5. Type the name of the repository you want to archive or unarchive. + ![Archive repository warnings](/assets/images/help/repository/archive-repository-warnings.png) +6. Click **I understand the consequences, archive this repository**. diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index 1f807713af..6353932fb4 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -1,6 +1,6 @@ --- -title: Sobre branches protegidos -intro: 'Você pode proteger branches importantes definindo regras de proteção de branch, que definem se os colaboradores podem excluir ou forçar push para o branch e definem os requisitos para todos os pushes para o branch, tais como verificações de status de passagem ou um histórico linear de commits.' +title: About protected branches +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches @@ -25,118 +25,113 @@ versions: topics: - Repositories --- +## About branch protection rules -## Sobre as regras de proteção do branch +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -É possível aplicar certos fluxos de trabalho ou requisitos antes que um colaborador possa fazer push de alterações em um branch no repositório, incluindo o merge de um pull request no branch, criando uma regra de proteção de branch. +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -Por padrão, cada regra de proteção de branch desabilita push forçado para os branches correspondentes e impede que os branches correspondentes sejam excluídos. Você pode, opcionalmente, desabilitar essas restrições e habilitar configurações adicionais de proteção de branches. +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. -Por padrão, as restrições de uma regra de proteção de branch não se aplicam a pessoas com permissões de administrador para o repositório. Opcionalmente, você também pode escolher incluir administradores. - -{% data reusables.repositories.branch-rules-example %} Para obter mais informações sobre os padrões de nomes do branch, consulte "[Gerenciar uma regra de proteção de branch](/github/administering-a-repository/managing-a-branch-protection-rule)". +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -## Sobre as configurações de proteção do branch +## About branch protection settings -Para cada regra de proteção do branch, você pode escolher habilitar ou desabilitar as seguintes configurações. -- [Exigir revisões de pull request antes do merge](#require-pull-request-reviews-before-merging) -- [Exigir verificações de status antes do merge](#require-status-checks-before-merging) +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) {% ifversion fpt or ghes > 3.1 or ghae-issue-4382 or ghec %} -- [Exigir resolução de conversas antes do merge](#require-conversation-resolution-before-merging){% endif %} -- [Exigir commits assinados](#require-signed-commits) -- [Exigir histórico linear](#require-linear-history) +- [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %} +- [Require signed commits](#require-signed-commits) +- [Require linear history](#require-linear-history) {% ifversion fpt or ghec %} - [Require merge queue](#require-merge-queue) {% endif %} -- [Incluir administradores](#include-administrators) -- [Restringir quem pode fazer push para branches correspondentes](#restrict-who-can-push-to-matching-branches) -- [Permitir push forçado](#allow-force-pushes) -- [Permitir exclusões](#allow-deletions) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) -Para obter mais informações sobre como configurar a proteção de branches, consulte "[Gerenciar uma regra de proteção de branch](/github/administering-a-repository/managing-a-branch-protection-rule)". +For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." -### Exigir revisões de pull request antes do merge +### Require pull request reviews before merging {% data reusables.pull_requests.required-reviews-for-prs-summary %} -Se você habilitar as revisões necessárias, os colaboradores só podem fazer push das alterações em um branch protegido por meio de um pull request aprovado pelo número necessário de revisores com permissões de gravação. +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. -Se uma pessoa com permissões de administrador escolher a opção **Solicitar alterações** em uma revisão, essa pessoa deverá aprovar o pull request antes que o merge possa ser efetuado. Se um revisor que solicita alterações em um pull request não estiver disponível, qualquer pessoa com permissões de gravação no repositório poderá ignorar a revisão de bloqueio. +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. {% data reusables.repositories.review-policy-overlapping-commits %} -Se um colaborador tentar fazer merge de um pull request com revisões pendentes ou rejeitadas no branch protegido, o colaborador receberá uma mensagem de erro. +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. ```shell remote: error: GH006: Protected branch update failed for refs/heads/main. remote: error: Changes have been requested. ``` -Opcionalmente, você pode escolher ignorar as aprovações de pull request obsoletas quando commits são enviados por push. Se alguém fizer push de um commit que modifica código para um pull request aprovado, a aprovação será ignorada e o pull request não poderá ser mesclado. Isso não se aplica se o colaborador fizer push de commits que não modificam código, como mesclar o branch de base no branch do pull request. Para obter mais informações sobre branch base, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)". +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Opcionalmente, você pode restringir a capacidade de ignorar comentários de pull request para pessoas ou equipes específicas. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." -Opcionalmente, você pode optar por exigir análises dos proprietários do código. Se você o fizer, qualquer pull request que afeta código com o proprietário do código deverá ser aprovado pelo proprietário desse código antes que o pull request possa ser mesclada no branch protegido. +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. -### Exigir verificações de status antes do merge +### Require status checks before merging -As verificações de status obrigatórias garantem que todos os testes de CI sejam aprovados antes que os colaboradores possam fazer alterações em um branch protegido. Para obter mais informações, consulte "[Configurar branches protegidos](/articles/configuring-protected-branches/)" e "[Habilitar verificações de status obrigatórias](/articles/enabling-required-status-checks)". Para obter mais informações, consulte "[Sobre verificações de status](/github/collaborating-with-issues-and-pull-requests/about-status-checks)". +Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." -Antes de habilitar as verificações de status necessárias, é necessário configurar o repositório para usar a API de status. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#statuses)" na documentação do REST. +Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. -Depois de habilitar a verificação de status obrigatória, todas as verificações de status necessárias deverão passar para que os colaboradores possam fazer merge das alterações no branch protegido. Depois que todas as verificações de status necessárias passarem, quaisquer commits devem ser enviados por push para outro branch e, em seguida, mesclados ou enviados por push diretamente para o branch protegido. +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch. -{% note %} +Any person or integration with write permissions to a repository can set the state of any status check in the repository, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates. If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box. -**Observação:** Qualquer pessoa ou integração com permissões de gravação em um repositório pode configurar o estado de qualquer verificação de status no repositório. O {% data variables.product.company_short %} não analisa se o autor de uma verificação está autorizado a criar uma verificação com um determinado nome ou modificar um status existente. Antes de realizar o merge de uma pull request, você deve verificar se o autor de cada status, listado na caixa de merge, é esperado. +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging. -{% endnote %} +| Type of required status check | Setting | Merge requirements | Considerations | +| --- | --- | --- | --- | +| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.| +| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. -Você pode configurar as verificações de status obrigatórias como "flexível" ou "rígida". O tipo de verificação de status obrigatória que você escolher determinará se o branch precisará ser atualizado com o branch base antes do merge. - -| Tipo de verificação de status obrigatória | Configuração | Requisitos de merge | Considerações | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Rígida** | A caixa de seleção **Exigir a atualização dos branches antes de fazer merge** fica marcada. | O branch **precisa** ser atualizado no branch base antes do merge. | Este é o comportamento padrão para verificações de status obrigatórias. Podem ser necessárias mais compilações, já que você precisará atualizar o branch head depois que outros colaboradores fizerem merge de pull requests no branch base protegido. | -| **Flexível** | A caixa de seleção **Exigir a atualização dos branches antes de fazer merge** **não** fica marcada. | O branch **não precisa** ser atualizado no branch base antes do merge. | Serão necessárias menos compilações, já que você não precisará atualizar o branch head depois que outros colaboradores fizerem merge de pull requests. As verificações de status poderão falhar depois que você fizer merge do branch, caso haja alterações incompatíveis com o branch base. | -| **Desabilitada** | A caixa de seleção **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge) **não** fica marcada. | O branch não tem restrições de merge. | Se as verificações de status obrigatórias não estiverem habilitadas, os colaboradores poderão fazer merge do branch a qualquer momento, estando ou não atualizados com o branch base. Isso aumenta a possibilidade de alterações incompatíveis. | - -Para obter informações sobre a solução de problemas, consulte "[Solucionar problemas para as verificações de status obrigatórias](/github/administering-a-repository/troubleshooting-required-status-checks)". +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." {% ifversion fpt or ghes > 3.1 or ghae-issue-4382 or ghec %} -### Exigir resolução de conversa antes de merge +### Require conversation resolution before merging -Exige que todos os comentários no pull request sejam resolvidos antes de poder fazer merge em um branch protegido. Isso garante que todos os comentários sejam resolvidos ou reconhecidos antes do merge. +Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge. {% endif %} -### Exigir commits assinados +### Require signed commits -Ao habilitar a assinatura de commit obrigatória em um branch, os contribuidores {% ifversion fpt or ghec %}e bots{% endif %} só podem fazer push de commits que foram assinados e verificados no branch. Para obter mais informações, consulte "[Sobre verificação de assinatura commit](/articles/about-commit-signature-verification)". +When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)." {% note %} {% ifversion fpt or ghec %} -**Notas:** +**Notes:** -* Se você habilitou o modo vigilante, que indica que seus commits serão sempre assinados, todos os commits que {% data variables.product.prodname_dotcom %} indentificar como "parcialmente verificado" serão permitidos em branches que exijam commits assinados. Para obter mais informações sobre o modo vigilante, consulte "[Exibir status de verificação para todos os seus commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)". -* Se um colaborador fizer push de um commit não assinado para um branch que exige assinaturas de commit, o colaborador deverá fazer rebase do commit para incluir uma assinatura verificada e, em seguida, fazer push forçado no commit reescrito para o branch. +* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)." +* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. {% else %} -**Observação:** Se um colaborador fizer push de um commit não assinado para um branch que exige assinaturas de commit, o colaborador deverá fazer rebase do commit para incluir uma assinatura verificada e, em seguida, fazer push forçado no commit reescrito para o branch. +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. {% endif %} {% endnote %} -Você sempre pode fazer push de commits locais para o branch se os commits forem assinados e verificados. {% ifversion fpt or ghec %}Você também pode mesclar commits assinados e verificados no branch usando uma pull request no {% data variables.product.product_name %}. No entanto, você não pode combinar por squash e fazer o merge de uma pull request no branch em {% data variables.product.product_name %}, a menos que você seja o autor da pull request.{% else %} No entanto, você não pode mesclar as pull requests no branch no {% data variables.product.product_name %}.{% endif %} Você pode {% ifversion fpt or ghec %}combinar por squash e {% endif %}merge pull requests localmente. Para obter mais informações, consulte "[Fazer checkout de pull requests localmente](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)". +You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)." -{% ifversion fpt or ghec %} Para obter mais informações sobre métodos de merge, consulte "[Sobre métodos de merge em {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github){% endif %} +{% ifversion fpt or ghec %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} -### Exigir histórico linear +### Require linear history -Aplicar o histórico linear de commit impede que os colaboradores façam push de commits de merge no branch. Isto significa que quaisquer pull requests mesclada no branch protegido devem usar um merge squash ou um merge rebase. Um histórico de commit estritamente linear pode ajudar as equipes a reverter alterações mais facilmente. Para obter mais informações sobre métodos de merge, consulte "[Sobre merges de pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)". +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." -Antes de exigir um histórico de commit linear, seu repositório deve permitir merge squash ou merge rebase. Para obter mais informações, consulte "[Configurando merges da pull request](/github/administering-a-repository/configuring-pull-request-merges)". +Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)." {% ifversion fpt or ghec %} ### Require merge queue @@ -146,30 +141,30 @@ Antes de exigir um histórico de commit linear, seu repositório deve permitir m {% data reusables.pull_requests.merge-queue-references %} {% endif %} -### Incluir administradores +### Include administrators -Por padrão, as regras de branch protegidos não se aplicam a pessoas com permissões de administrador em um repositório. Você pode habilitar essa configuração para incluir administradores em suas regras de branch protegido. +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. -### Restringir quem pode fazer push para branches correspondentes +### Restrict who can push to matching branches {% ifversion fpt or ghec %} -Você pode habilitar as restrições do branch se seu repositório for propriedade de uma organização que usa {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. +You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% endif %} -Ao habilitar as restrições de branches, apenas usuários, equipes ou aplicativos com permissão podem fazer push para o branch protegido. Você pode visualizar e editar usuários, equipes ou aplicativos com acesso de push a um branch protegido nas configurações do branch protegido. +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. -Você só pode dar acesso de push a um branch protegido a usuários, equipes ou {% data variables.product.prodname_github_apps %} instalados com acesso de gravação a um repositório. As pessoas e os aplicativos com permissões de administrador em um repositório sempre conseguem fazer push em um branch protegido. +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. -### Permitir push forçado +### Allow force pushes -Por padrão, os blocks do {% data variables.product.product_name %} fazem push forçado em todos os branches protegidos. Quando você habilitar push forçado em um branch protegido, qualquer pessoa com, pelo menos, permissões de gravação no repositório pode forçar o push ao branch, incluindo aqueles com permissões de administrador. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests. -Habilitar push forçado não irá substituir quaisquer outras regras de proteção de branch. Por exemplo, se um branch exigir um histórico de commit linear, você não poderá forçar commits a mesclar commits para esse branch. +Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. -{% ifversion ghes or ghae %}Você não pode habilitar pushes forçados para um branch protegido se um administrador do site bloquear push forçados para todos os branches do seu repositório. Para obter mais informações, consulte "[Bloqueando push forçado para repositórios de propriedade de uma conta de usuário ou organização](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." +{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." -Se um administrador do site bloquear pushes forçados apenas para o branch padrão, você ainda pode habilitar pushes forçados para qualquer outro branch protegido.{% endif %} +If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} -### Permitir exclusões +### Allow deletions -Por padrão, você não pode excluir um branch protegido. Ao habilitar a exclusão de um branch protegido, qualquer pessoa com permissão de gravação no repositório pode excluir o branch. +By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 1440d7e425..af1d2efaca 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -1,6 +1,6 @@ --- -title: Gerenciar uma regra de proteção de branch -intro: 'Você pode criar uma regra de proteção de branch para aplicar certos fluxos de trabalho para um ou mais branches, como exigir uma revisão de aprovação ou verificações de status de aprovação para todos os pull requests mesclados no branch protegido.' +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/configuring-protected-branches @@ -26,26 +26,25 @@ versions: permissions: People with admin permissions to a repository can manage branch protection rules. topics: - Repositories -shortTitle: Regra de proteção de branch +shortTitle: Branch protection rule --- - -## Sobre as regras de proteção do branch +## About branch protection rules {% data reusables.repositories.branch-rules-example %} -É possível criar uma regra para todos os branches atuais e futuros no repositório com a sintaxe curinga `*`. Pelo fato de o {% data variables.product.company_short %} usar o sinalizador `File::FNM_PATHNAME` para a sintaxe `File.fnmatch`, o curinga não corresponde aos separadores de diretório (`/`). Por exemplo, `qa/*` pode fazer correspondência com todos os branches que começam com `qa/` e contêm uma única barra. Você pode incluir várias barras com `qa/**/*` e você pode estender a string `qa` com `qa**/**/*` para tornar a regra mais inclusiva. Para obter mais informações sobre opções de sintaxe para regras de branch, consulte a [documentação de fnmatch](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). -Se um repositório tiver várias regras de branch protegido que afetem os mesmos branches, as regras que incluírem um nome de branch específico terão a prioridade mais alta. Se houver mais de uma regra de branch protegido que faça referência ao mesmo nome de branch específico, a regra de branch criada primeiro terá a prioridade mais alta. +If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority. -As regras de branch protegido que mencionam um caractere especial, como `*`, `?` ou `]`, são aplicadas na ordem em que foram criadas, de modo que as regras mais antigas com esses caracteres têm uma prioridade mais alta. +Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority. -Para criar uma exceção a uma regra de branch existente, você pode criar outra regra de proteção de branch que tenha prioridade superior, como uma regra para um nome de branch específico. +To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name. -Para obter mais informações sobre cada uma das configurações de proteção de branch disponíveis, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." -## Criar uma regra de proteção de branch +## Creating a branch protection rule -Ao criar uma regra de branch, o branch que você especificar ainda não existe no repositório. +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -53,53 +52,79 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n {% data reusables.repositories.add-branch-protection-rules %} {% ifversion fpt or ghec %} 1. Optionally, enable required pull requests. - - Under "Protect matching branches", select **Require a pull request before merging**. ![Caixa de seleção Pull request review restriction (Restrição de revisão de pull request)](/assets/images/help/repository/PR-reviews-required-updated.png) - - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch. ![Menu suspenso para selecionar o número de revisões de aprovação obrigatórias](/assets/images/help/repository/number-of-required-review-approvals-updated.png) + - Under "Protect matching branches", select **Require a pull request before merging**. + ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png) + - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch. + ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png) {% else %} -1. Opcionalmente, habilite as revisões obrigatórias de de pull request. - - Em "Proteger os branches correspondentes", selecione **Exigir revisões de pull request antes do merge**. ![Caixa de seleção Pull request review restriction (Restrição de revisão de pull request)](/assets/images/help/repository/PR-reviews-required.png) - - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. ![Menu suspenso para selecionar o número de revisões de aprovação obrigatórias](/assets/images/help/repository/number-of-required-review-approvals.png) +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. + ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. + ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png) {% endif %} - - Opcionalmente, para ignorar uma revisão de aprovação de pull request quando um commit de modificação de código for enviado por push para o branch, selecione **Ignorar aprovações obsoletas de pull request quando novos commits forem enviados por push**. ![Caixa de seleção Dismiss stale pull request approvals when new commits are pushed (Ignorar aprovações de pull requests obsoletas ao fazer push de novos commits)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - - Opcionalmente, para exigir a revisão de um proprietário do código quando o pull request afeta o código que tem um proprietário designado, selecione **Exigir revisão de Proprietários do Código**. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". ![Require review from code owners (Exigir revisão de proprietários de código)](/assets/images/help/repository/PR-review-required-code-owner.png) - - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Em seguida, procure e selecione as pessoas ou equipes que têm permissão para ignorar as revisões de pull request. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Caixa de seleção Restrict who can dismiss pull request reviews (Restringir quem pode ignorar revisões de pull request)](/assets/images/help/repository/PR-review-required-dismissals.png) -1. Opcionalmente, habilite as verificações de status obrigatórias. - - Selecione **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge). ![Opção Required status checks (Verificações de status obrigatórias)](/assets/images/help/repository/required-status-checks.png) - - Opcionalmente, para garantir que os pull requests sejam testados com o código mais recente no branch protegido, selecione **Exigir que os branches estejam atualizados antes do merge**. ![Caixa de seleção Status obrigatório rígido ou flexível](/assets/images/help/repository/protecting-branch-loose-status.png) - - Na lista de verificações de status disponíveis, selecione as verificações que você deseja tornar obrigatórias.![Lista de verificações de status disponíveis](/assets/images/help/repository/required-statuses-list.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. + ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." + ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) +{% ifversion fpt or ghec %} + - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. + ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) +{% endif %} + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." + ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + - Select **Require status checks to pass before merging**. + ![Required status checks option](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. + ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png) + - Search for status checks, selecting the checks you want to require. + ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png) {%- ifversion fpt or ghes > 3.1 or ghae-issue-4382 %} -1. Opcionalmente, selecione **Exige resolução de conversas antes de fazer merge**. ![Exigir resolução de conversas antes de fazer o merge](/assets/images/help/repository/require-conversation-resolution.png) +1. Optionally, select **Require conversation resolution before merging**. + ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png) {%- endif %} -1. Opcionalmente, selecione **Exigir commits assinados**. ![Opção Require signed commits (Exigir commits assinados)](/assets/images/help/repository/require-signed-commits.png) -1. Opcionalmente, selecione **Exigir histórico linear**. ![Opção de histórico linear necessária](/assets/images/help/repository/required-linear-history.png) +1. Optionally, select **Require signed commits**. + ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. + ![Required linear history option](/assets/images/help/repository/required-linear-history.png) {%- ifversion fpt or ghec %} -1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png) +1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} + ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png) {% tip %} **Tip:** The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup). {% endtip %} {%- endif %} -1. Outra opção é selecionar **Include administrators** (Incluir administradores). ![Caixa de seleção Include administrators (Incluir administradores)](/assets/images/help/repository/include-admins-protected-branches.png) -1. Opcionalmente, {% ifversion fpt or ghec %} se o repositório pertencer a uma organização que usa {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %},{% endif %} habilitar as restrições de branches. - - Selecione **Restringir quem pode fazer push para os branches correspondentes**. ![Caixa de seleção Branch restriction (Restrição de branch)](/assets/images/help/repository/restrict-branch.png) - - Procurar e selecionar pessoas, equipes ou aplicativos que tenham permissão para fazer push para o branch protegido. ![Pesquisa de restrição de branch](/assets/images/help/repository/restrict-branch-search.png) -1. Opcionalmente, em "Regras aplicadas a todos incluindo administradores", selecione **Permitir pushes forçados**. ![Permitir opção push forçado](/assets/images/help/repository/allow-force-pushes.png) -1. Opcionalmente, selecione **Permitir exclusões**. ![Permitir a opção de exclusão de branch](/assets/images/help/repository/allow-branch-deletions.png) -1. Clique em **Criar**. +1. Optionally, select **Include administrators**. +![Include administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% ifversion fpt or ghec %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. + ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png) + - Search for and select the people, teams, or apps who will have permission to push to the protected branch. + ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png) +2. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)." + ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. + ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png) +1. Click **Create**. -## Editar uma regra de proteção de branch +## Editing a branch protection rule {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. À direita da regra de proteção de branch que você deseja editar, clique em **Editar**. ![Botão editar](/assets/images/help/repository/edit-branch-protection-rule.png) -1. Faça as alterações desejadas na regra de proteção do branch. -1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/help/repository/save-branch-protection-rule.png) +1. To the right of the branch protection rule you want to edit, click **Edit**. + ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. Click **Save changes**. + ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png) -## Excluir as regras de proteção do branch +## Deleting a branch protection rule {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. À direita da regra de proteção do branch que você deseja excluir, clique em **Excluir**. ![Botão excluir](/assets/images/help/repository/delete-branch-protection-rule.png) +1. To the right of the branch protection rule you want to delete, click **Delete**. + ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png) diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index f019aa08a9..671b0e2809 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -1,6 +1,6 @@ --- -title: Solução de problemas de verificações de status necessárias -intro: Você pode verificar erros comuns e resolver problemas com as verificações de status necessárias. +title: Troubleshooting required status checks +intro: You can check for common errors and resolve issues with required status checks. product: '{% data reusables.gated-features.protected-branches %}' versions: fpt: '*' @@ -12,20 +12,19 @@ topics: redirect_from: - /github/administering-a-repository/troubleshooting-required-status-checks - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks -shortTitle: Verificações de status necessárias +shortTitle: Required status checks --- +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)." -Se você tiver uma verificação e um status com o mesmo nome e selecionar esse nome como uma verificação de status obrigatória, a verificação e o status serão obrigatórios. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)". - -Depois que você habilitar as verificações de status solicitadas, seu branch pode precisar estar atualizado com o branch de base antes da ação de merge. Isso garante que o branch foi testado com o código mais recente do branch base. Se o branch estiver desatualizado, você precisará fazer merge do branch base no seu branch. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." {% note %} -**Observação:** também é possível atualizar o seu branch com o branch base usando o rebase do Git. Para obter mais informações, consulte "[Rebase no Git](/github/getting-started-with-github/about-git-rebase)". +**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)." {% endnote %} -Não será possível fazer push de alterações locais em um branch protegido enquanto todas as verificações de status obrigatórias não forem aprovadas. Sendo assim, você receberá uma mensagem de erro semelhante a esta. +You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following. ```shell remote: error: GH006: Protected branch update failed for refs/heads/main. @@ -33,13 +32,19 @@ remote: error: Required status check "ci-build" is failing ``` {% note %} -**Observação:** as pull requests que são atualizadas e passam nas verificações de status obrigatórias podem sofrer merge localmente e enviadas por push para o branch protegido. Isso pode ser feito sem verificações de status em execução no próprio commit de merge. +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. This can be done without status checks running on the merge commit itself. {% endnote %} {% ifversion fpt or ghae or ghes or ghec %} -Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. Se o commit de merge de testes tem status, o commit de merge de testes deve passar. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. Para obter mais informações sobre commits de merge de teste, consulte "[Pulls](/rest/reference/pulls#get-a-pull-request)". +Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." -![Branch com commits de mescla conflitantes](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} + +It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app. + +``` +Required status check "build" was not set by the expected {% data variables.product.prodname_github_app %}. +``` 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 55d0790bd5..651ec1b4dd 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 @@ -1,6 +1,6 @@ --- -title: Transferir um repositório -intro: É possível transferir repositórios para outros usuários ou contas da organização. +title: Transferring a repository +intro: You can transfer repositories to other users or organization accounts. redirect_from: - /articles/about-repository-transfers/ - /move-a-repo/ @@ -22,60 +22,60 @@ versions: topics: - Repositories --- +## About repository transfers -## Sobre transferências de repositório +When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings. -Quando você transfere um repositório para um novo proprietário, ele pode administrar imediatamente o conteúdo do repositório, além de problemas, pull requests, versões, quadros de projeto e configurações. +Prerequisites for repository transfers: +- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %} +- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization. +- The target account must not have a repository with the same name, or a fork in the same network. +- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %} +- Internal repositories can't be transferred.{% endif %} +- Private forks can't be transferred. -Prerequisites for repository transfers: -- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. Se o novo proprietário não aceitar a transferência em um dia, o convite vai expirar.{% endif %} -- Para transferir um repositório que você possui para uma organização, é preciso ter permissão para criar um repositório na organização de destino. -- A conta de destino não deve ter um repositório com o mesmo nome ou uma bifurcação na mesma rede. -- O proprietário original do repositório é adicionado como colaborador no repositório transferido. Os outros colaboradores do repositório transferido permanecem intactos. -- Bifurcações privadas não podem ser transferidas. +{% ifversion fpt or ghec %}If you transfer a private repository to a {% data variables.product.prodname_free_user %} user or organization account, the repository will lose access to features like protected branches and {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %} -{% ifversion fpt or ghec %}Se você transferir um repositório privado para uma conta de usuário ou organização {% data variables.product.prodname_free_user %}, o repositório perderá o acesso a recursos como branches protegidos e {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %} +### What's transferred with a repository? -### O que é transferido com um repositório? +When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition: -Quando você transfere um repositório, também são transferidos problemas, pull requests, wiki, estrelas e inspetores dele. Se o repositório transferido contiver webhooks, serviços, segredos ou chaves de implantação, eles continuarão associados mesmo depois que a transferência for concluída. Informações do Git sobre commits, inclusive contribuições, são preservadas. Além disso: - -- Se o repositório transferido for uma bifurcação, continuará associado ao repositório upstream. -- Se o repositório transferido tiver alguma bifurcação, ela permanecerá associada ao repositório depois que a transferência for concluída. -- Se o repositório transferido usar {% data variables.large_files.product_name_long %}, todos os objetos {% data variables.large_files.product_name_short %} serão automaticamente movidos. This transfer occurs in the background, so if you have a large number of {% data variables.large_files.product_name_short %} objects or if the {% data variables.large_files.product_name_short %} objects themselves are large, it may take some time for the transfer to occur.{% ifversion fpt or ghec %} Before you transfer a repository that uses {% data variables.large_files.product_name_short %}, make sure the receiving account has enough data packs to store the {% data variables.large_files.product_name_short %} objects you'll be moving over. Para obter mais informações sobre como adicionar armazenamento para contas de usuário, consulte "[Atualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)".{% endif %} -- Quando um repositório é transferido entre duas contas de usuário, as atribuições de problemas são mantidas intactas. Quando você transfere um repositório de uma conta de usuário para uma organização, os problemas atribuídos a integrantes da organização permanecem intactos, e todos os outros responsáveis por problemas são destituídos. Somente proprietários da organização têm permissão para criar novas atribuições de problemas. Quando você transfere um repositório de uma organização para uma conta de usuário, são mantidos somente os problemas atribuídos ao proprietário do repositório. Todos os outros responsáveis por problemas são removidos. -- Se o repositório transferido contiver um site do {% data variables.product.prodname_pages %}, os links para o repositório do Git na web e por meio de atividade do Git serão redirecionados. No entanto, não redirecionamos o {% data variables.product.prodname_pages %} associado ao repositório. -- Todos os links para o local do repositório anterior são automaticamente redirecionados para o novo local. Quando você usar `git clone`, `git fetch` ou `git push` em um repositório transferido, esses comandos serão redirecionados para a nova URL ou local do repositório. No entanto, para evitar confusão, recomendamos que qualquer clone local seja atualizado para apontar para a nova URL do repositório. Use `git remote` na linha de comando para fazer isso: +- If the transferred repository is a fork, then it remains associated with the upstream repository. +- If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete. +- If the transferred repository uses {% data variables.large_files.product_name_long %}, all {% data variables.large_files.product_name_short %} objects are automatically moved. This transfer occurs in the background, so if you have a large number of {% data variables.large_files.product_name_short %} objects or if the {% data variables.large_files.product_name_short %} objects themselves are large, it may take some time for the transfer to occur.{% ifversion fpt or ghec %} Before you transfer a repository that uses {% data variables.large_files.product_name_short %}, make sure the receiving account has enough data packs to store the {% data variables.large_files.product_name_short %} objects you'll be moving over. For more information on adding storage for user accounts, see "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)."{% endif %} +- When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed. +- If the transferred repository contains a {% data variables.product.prodname_pages %} site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect {% data variables.product.prodname_pages %} associated with the repository. +- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line: ```shell $ git remote set-url origin new_url ``` -- Quando você transfere um repositório de uma organização para uma conta de usuário, os colaboradores somente leitura do repositório não serão transferidos. Isso acontece porque os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta de usuário. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -### Transferências de repositório e organizações +### Repository transfers and organizations -Para transferir repositórios para uma organização, é preciso ter permissões de criação de repositórios na organização recebedora. Se os proprietários da organização tiverem desabilitado a criação de repositórios por integrantes da organização, somente proprietários da organização poderão transferir repositórios dentro ou fora da organização. +To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization. -Depois que um repositório for transferido para uma organização, os privilégios de associação padrão e as configurações padrão de permissão de repositório da organização se aplicarão ao repositório transferido. +Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository. -## Transferir um repositório pertencente à sua conta de usuário +## Transferring a repository owned by your user account -É possível transferir seu repositório para qualquer conta de usuário que aceite transferência de repositório. Quando um repositório é transferido entre duas contas de usuário, o proprietário e os colaboradores do repositório original são automaticamente adicionados como colaboradores ao novo repositório. +You can transfer your repository to any user account that accepts your repository transfer. When a repository is transferred between two user accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository. -{% ifversion fpt or ghec %}If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, before transferring the repository, you may want to remove or update your DNS records to avoid the risk of a domain takeover. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} +{% ifversion fpt or ghec %}If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, before transferring the repository, you may want to remove or update your DNS records to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.transfer-repository-steps %} -## Transferir um repositório pertencente à organização +## Transferring a repository owned by your organization -Se você tiver permissões de proprietário em uma organização ou permissões de administrador para um dos repositórios dela, será possível transferir um repositório pertencente à organização para sua conta de usuário ou para outra organização. +If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your user account or to another organization. -1. Entre na sua conta de usuário que tem permissões de proprietário ou de administrador na organização proprietária do repositório. +1. Sign into your user account that has admin or owner permissions in the organization that owns the repository. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.transfer-repository-steps %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 52bd17dd28..be05049a7c 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -1,6 +1,6 @@ --- -title: Sobre proprietários do código -intro: Você pode usar um arquivo CODEOWNERS para definir indivíduos ou equipes que são responsáveis pelo código em um repositório. +title: About code owners +intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository. redirect_from: - /articles/about-codeowners/ - /articles/about-code-owners @@ -15,62 +15,61 @@ versions: topics: - Repositories --- +People with admin or owner permissions can set up a CODEOWNERS file in a repository. -As pessoas com permissões de administrador ou proprietário podem configurar um arquivo CODEOWNERS em um repositório. +The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. -As pessoas que você escolhe como proprietários do código devem ter permissões de gravação para o repositório. Quando o proprietário do código é uma equipe, essa equipe deverá ser visível e ter permissões de gravação, ainda que todos os membros individuais da equipe já tenham permissões de gravação diretamente, por meio da associação da organização ou por meio de outra associação à equipe. +## About code owners -## Sobre proprietários do código +Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)." -Solicita-se automaticamente que os proprietários do código revisem quando alguém abre um pull request que modifica o código que possuem. Solicita-se automaticamente que os proprietários do código revejam os rascunhos de pull requests. Para obter mais informações sobre pull requests em rascunho, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Solicita-se automaticamente que os proprietários do código revejam os rascunhos de pull requests. Se você converter um pull request em rascunho, as pessoas que já assinaram as notificações não terão suas assinaturas canceladas automaticamente. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)". +When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -Quando alguém com permissões de administrador ou proprietário tiver habilitado revisões obrigatórias, se desejar, ele também poderá exigir aprovação de um proprietário do código para que o autor possa fazer merge de uma pull request no repositório. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". +If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}. -Se um arquivo tiver um proprietário do código, você poderá ver quem é o proprietário do código antes de abrir um pull request. No repositório, é possível pesquisar o arquivo e passar o mouse sobre o {% octicon "shield-lock" aria-label="The edit icon" %}. +![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png) -![Proprietário do código para um arquivo em um repositório](/assets/images/help/repository/code-owner-for-a-file.png) +## CODEOWNERS file location -## Local do arquivo CODEOWNERS +To use a CODEOWNERS file, create a new file called `CODEOWNERS` in the root, `docs/`, or `.github/` directory of the repository, in the branch where you'd like to add the code owners. -Para usar um arquivo CODEOWNERS, crie um novo arquivo denominado `CODEOWNERS` na raiz, `docs/` ou no diretório `.github/` do repositório, no branch em que deseja adicionar os proprietários do código. +Each CODEOWNERS file assigns the code owners for a single branch in the repository. Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch. -Cada arquivo CODEOWNERS atribui os proprietários do código para um único branch no repositório. Dessa forma, você pode atribuir diferentes proprietários de códigos para diferentes branches, como `@octo-org/codeowners-team` para uma base de código no branch-padrão e `@octocat` para um site do {% data variables.product.prodname_pages %} no branch de `gh-pages`. - -Para que os proprietários do código recebam solicitações de revisão, o arquivo CODEOWNERS deve estar no branch base da pull request. Por exemplo, se você atribuir `@octocat` como o proprietário do código para arquivos *.js* no branch `gh-pages` do seu repositório, `@octocat` receberá solicitações de revisão quando uma pull request com alterações nos arquivos *.js* for aberta entre o branch head e `gh-pages`. +For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`. {% ifversion fpt or ghae or ghes > 3.2 or ghec %} -## Tamanho do arquivo CODEOWNERS +## CODEOWNERS file size -Os arquivos CODEOWNERS devem ter menos de 3 MB. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. +CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. -Para reduzir o tamanho do seu arquivo CODEOWNERS, considere o uso de padrões curinga para consolidar múltiplas entradas em uma única entrada. +To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. {% endif %} -## Sintaxe de CODEOWNERS +## CODEOWNERS syntax -Um arquivo CODEOWNERS usa um padrão que segue a maioria das mesmas regras usadas nos arquivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), com [algumas exceções](#syntax-exceptions). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Os usuários devem ter acessso de `leitura` ao repositório e as equipes devem ter acesso explícito de `gravação`, mesmo que os integrantes da equipe já tenham acesso. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. +A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. -Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões. -### Exemplo de um arquivo CODEOWNERS +If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. +### Example of a CODEOWNERS file ``` -# Este é um comentário. -# Cada linha é um padrão de arquivo seguido por um ou mais proprietários. +# This is a comment. +# Each line is a file pattern followed by one or more owners. -# Esses proprietários serão os proprietários padrão para tudo no -# repositório. A menos que uma correspondência posterior tenha precedência, -# @global-owner1 e @global-owner2 serão solicitados para -# revisão quando alguém abrir uma pull request. +# These owners will be the default owners for everything in +# the repo. Unless a later match takes precedence, +# @global-owner1 and @global-owner2 will be requested for +# review when someone opens a pull request. * @global-owner1 @global-owner2 -# A ordem é importante; o último padrão de correspondência tem -# prioridade. Quando alguém abre uma pull request que -# modifica apenas arquivos JS, somente @js-owner, e não o(s) -# proprietário(s) global(is), será solicitado para uma revisão. +# Order is important; the last matching pattern takes the most +# precedence. When someone opens a pull request that only +# modifies JS files, only @js-owner and not the global +# owner(s) will be requested for a review. *.js @js-owner -# Você também pode usar endereços de e-mail se preferir. Eles serão -# usados para procurar usuários assim como fazemos com e-mails do -# autor do commit. +# You can also use email addresses if you prefer. They'll be +# used to look up users just like we do for commit author +# emails. *.go docs@example.com # Teams can be specified as code owners as well. Teams should @@ -84,13 +83,13 @@ Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o ar # subdirectories. /build/logs/ @doctocat -# O padrão `docs/*` corresponderá a arquivos como -# `docs/getting-started.md`, mas a nenhum outro arquivo aninhado como +# The `docs/*` pattern will match files like +# `docs/getting-started.md` but not further nested files like # `docs/build-app/troubleshooting.md`. docs/* docs@example.com -# Neste exemplo, @octocat tem qualquer arquivo no diretório apps -# em qualquer lugar do seu repositório. +# In this example, @octocat owns any file in an apps directory +# anywhere in your repository. apps/ @octocat # In this example, @doctocat owns any file in the `/docs` @@ -104,16 +103,16 @@ apps/ @octocat /apps/ @octocat /apps/github ``` -### Exceções de sintaxe -Existem algumas regras de sintaxe para arquivos gitignore que não funcionam em arquivos CODEOWNERS: -- Fugir de um padrão que começa com `#` usando `\` para que seja tratado como um padrão e não como um comentário -- Usar `!` para negar um padrão -- Usar `[ ]` para definir um intervalo de caracteres +### Syntax exceptions +There are some syntax rules for gitignore files that do not work in CODEOWNERS files: +- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment +- Using `!` to negate a pattern +- Using `[ ]` to define a character range -## Proteção de branch e de CODEOWNERS -Os proprietários do repositório podem adicionar regras de proteção de branch para garantir que o código alterado seja revisado pelos proprietários dos arquivos alterados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." +## CODEOWNERS and branch protection +Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." -### Exemplo de um arquivo CODEOWNERS +### Example of a CODEOWNERS file ``` # In this example, any change inside the `/apps` directory # will require approval from @doctocat. @@ -125,18 +124,14 @@ Os proprietários do repositório podem adicionar regras de proteção de branch # In this example, any change inside the `/apps` directory # will require approval from a member of the @example-org/content team. -# If a member of @example-org/content opens a pull request -# with a change inside the `/apps` directory, their approval is implicit. -# The team is still added as a reviewer but not a required reviewer. -# Anyone can approve the changes. /apps/ @example-org/content-team ``` -## Leia mais +## Further reading -- "[Criar arquivos](/articles/creating-new-files)" -- "[Convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)" -- "[Gerenciar o acesso de um indivíduo a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)" -- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)" -- "[Exibir uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)" +- "[Creating new files](/articles/creating-new-files)" +- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)" +- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)" +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)" diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md deleted file mode 100644 index ba6705582b..0000000000 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -title: Gerenciando as configurações do GitHub Actions para um repositório -intro: 'Você pode desabilitar ou configurar {% data variables.product.prodname_actions %} para um repositório específico.' -redirect_from: - - /github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository - - /github/administering-a-repository/managing-repository-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository - - /github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository - - /github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: how_to -topics: - - Actions - - Permissions - - Pull requests -shortTitle: Gerenciar configurações do GitHub Actions ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -## Sobre as permissões do {% data variables.product.prodname_actions %} para o seu repositório - -{% data reusables.github-actions.disabling-github-actions %} Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." - -É possível habilitar o {% data variables.product.prodname_actions %} para seu repositório. {% data reusables.github-actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para o seu repositório completamente. {% data reusables.github-actions.disabled-actions-description %} - -Como alternativa, você pode habilitar o {% data variables.product.prodname_actions %} em seu repositório, mas limitar as ações que um fluxo de trabalho pode ser executado. {% data reusables.github-actions.enabled-local-github-actions %} - -## Gerenciando as permissões do {% data variables.product.prodname_actions %} para o seu repositório - -É possível desabilitar todos os fluxos de trabalho para um repositório ou definir uma política que configura quais ações podem ser usadas em um repositório. - -{% data reusables.actions.actions-use-policy-settings %} - -{% note %} - -**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)." - -{% endnote %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -1. Em **Permissões de ações**, selecione uma opção. ![Definir política de ações para esta organização](/assets/images/help/repository/actions-policy.png) -1. Clique em **Salvar**. - -## Permitir a execução de ações específicas - -{% data reusables.actions.allow-specific-actions-intro %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -1. Em **Permissões de ações**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. - {%- ifversion ghes %} - ![Adicionar ações para permitir lista](/assets/images/help/repository/actions-policy-allow-list.png) - {%- else %} - ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) - {%- endif %} -2. Clique em **Salvar**. - -{% ifversion fpt or ghec %} -## Configurar a aprovação necessária para fluxos de trabalho de bifurcações públicas - -{% data reusables.actions.workflow-run-approve-public-fork %} - -Você pode configurar esse comportamento para um repositório seguindo o procedimento abaixo. A modificação desta configuração substitui a configuração definida no nível da organização ou empresa. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -{% data reusables.github-actions.workflows-from-public-fork-setting %} - -{% data reusables.actions.workflow-run-approve-link %} -{% endif %} - -## Habilitar fluxos de trabalho para bifurcações privadas do repositório - -{% data reusables.github-actions.private-repository-forks-overview %} - -### Configurar a política de bifurcação privada para um repositório - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -{% data reusables.github-actions.private-repository-forks-configure %} - -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -## Definir as permissões do `GITHUB_TOKEN` para o seu repositório - -{% data reusables.github-actions.workflow-permissions-intro %} - -As permissões padrão também podem ser configuradas nas configurações da organização. Se o padrão mais restrito foi selecionado nas configurações da organização, a mesma opção será selecionada automaticamente nas configurações do repositório e a opção permissiva estará desabilitada. - -{% data reusables.github-actions.workflow-permissions-modifying %} - -### Configurar as permissões padrão do `GITHUB_TOKEN` - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -1. Em **permissões do fluxo de trabalho**, escolha se você quer que o `GITHUB_TOKEN` tenha acesso de leitura e gravação para todos os escopos, ou apenas acesso de leitura para o escopo do conteúdo. -Definir permissões do GITHUB_TOKEN para este repositório

    -

  • Clique em Salvar para aplicar as configurações. -

    - -

    {% endif %}

    • - - -

    {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}

    - -

    Permitindo o acesso a componentes em um repositório interno

    - -

    {% note %}

    - -

    Observação: {% data reusables.gated-features.internal-repos %}

    - -

    {% endnote %}

    - -

    Os integrantes da sua empresa podem usar repositórios internos para trabalhar em projetos sem compartilhar informações publicamente. Para obter informações, consulte "Sobre repositórios".

    - -

    Para configurar se os fluxos de trabalho em um repositório interno podem ser acessados de fora do repositório:

    - -
      -
    1. No {% data variables.product.prodname_dotcom %}, acesse a página principal do repositório interno.
      2. -

    2. No nome do repositório, clique em {% octicon "gear" aria-label="The gear icon" %} Configurações. -

      - -

      {% data reusables.repositories.settings-sidebar-actions %}

      3. -

    3. Em Acesso, escolha uma das configurações de acesso: -Defina o acesso aos componentes das Ações

      4. -
    - -
      -
    • Não acessível - Os fluxos de trabalho em outros repositórios não podem usar fluxos de trabalho neste repositório.
      • -
    • Acessível por qualquer repositório na organização - Fluxos de trabalho em outros repositórios podem usar fluxos de trabalho neste repositório, desde que façam parte da mesma organização.
      • -
    • Acessível por qualquer repositório na empresa - Os luxos de trabalho em outros repositórios podem usar fluxos de trabalho nesse repositório, desde que façam parte da mesma empresa. - -
        -

      1. Clique em Salvar para aplicar as configurações. -

        - -

        {% endif %}

        2. -
      • -
    - -

    Configurar o período de retenção para artefatos e registros de{% data variables.product.prodname_actions %} no seu repositório

    - -

    Você pode configurar o período de retenção para artefatos e registros de {% data variables.product.prodname_actions %} no seu repositório.

    - -

    {% data reusables.actions.about-artifact-log-retention %}

    - -

    Você também pode definir um período de retenção personalizado para um artefato específico criado por um fluxo de trabalho. Para obter mais informações, consulte "Definir o período de retenção para um artefato".

    - -

    Definir o período de retenção para um repositório

    - -

    {% data reusables.repositories.navigate-to-repo %}

    - -

    -

    - -

    {% data reusables.repositories.sidebar-settings %}

    - -

    -

    - -

    {% data reusables.repositories.settings-sidebar-actions %}

    - -

    -

    - -

    {% data reusables.github-actions.change-retention-period-for-artifacts-logs %}

    diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md deleted file mode 100644 index 82b190a683..0000000000 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Sobre notificações de e-mail para pushes no seu repositório -intro: Você pode optar por enviar notificações por email automaticamente para um endereço de email específico quando alguém fizer push para o repositório. -permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository. -redirect_from: - - /articles/managing-notifications-for-pushes-to-a-repository/ - - /articles/receiving-email-notifications-for-pushes-to-a-repository/ - - /articles/about-email-notifications-for-pushes-to-your-repository/ - - /github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository - - /github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository - - /github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Repositories -shortTitle: Notificações de e-mail para pushes ---- - -{% data reusables.notifications.outbound_email_tip %} - -Cada notificação de e-mail para um push no repositório lista os novos commits e os vincula a um diff contendo apenas esses commits. Na notificação de e-mail, você verá: - -- O nome do repositório onde o commit foi feito -- O branch em que um commit foi feito -- O SHA1 do commit, incluindo um link para o diff no {% data variables.product.product_name %} -- O autor do commit -- A data em que o commit foi feito -- Os arquivos que foram alterados como parte do commit -- A mensagem do commit; - -É possível filtrar notificações de e-mail que você recebe para pushes em um repositório. Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Sobre e-mails de notificação](/github/receiving-notifications-about-activity-on-github/about-email-notifications)"." Você também pode desativar notificações por email para pushes. Para obter mais informações, consulte " -[Escolher o método de entrega das suas notificações](/enterprise/{{ page.version }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}".

    - - - -## Habilitando notificações de e-mail para pushes no seu repositório - -{% data reusables.repositories.navigate-to-repo %} - - - -{% data reusables.repositories.sidebar-settings %} - - - -{% data reusables.repositories.sidebar-notifications %} - -5. Digite até dois endereços de e-mail, separados por um espaço, para os quais deseja enviar as notificações. Se desejar enviar e-mails a mais de duas contas, defina um dos endereços para um endereço de e-mail de grupo. ![Caixa de texto de endereço de e-mail](/assets/images/help/settings/email_services_addresses.png) - -1. Se você operar o seu próprio servidor, você poderá verificar a integridade dos e-mails através do **Cabeçalho aprovado**. O **Cabeçalho aprovado** é um token ou segredo que você digita nesse campo e enviado com o e-mail. Se o cabeçalho `Aprovado` de um e-mail corresponder ao token, você poderá confiar que o e-mail é de {% data variables.product.product_name %}. ![Caixa de texto do cabeçalho do e-mail aprovado](/assets/images/help/settings/email_services_approved_header.png) - -7. Clique em **Configurar notificações**. ![Botão para configurar notificações](/assets/images/help/settings/setup_notifications_settings.png) - - - -## Leia mais - -{% ifversion fpt or ghae or ghes or ghec %} - -- "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - - {% else %} - -- "[Sobre notificações](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - -- "[Escolhendo o método de entrega de suas notificações](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" -- "[Sobre notificações por e-mail](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[Sobre notificações web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md index f882e10b4b..54bb112651 100644 --- a/translations/pt-BR/content/rest/overview/api-previews.md +++ b/translations/pt-BR/content/rest/overview/api-previews.md @@ -1,6 +1,6 @@ --- -title: Pré-visualizações da API -intro: Você pode usar pré-visualizações da API para testar novos recursos e fornecer feedback antes que estes recursos se tornem oficiais. +title: API previews +intro: You can use API previews to try out new features and provide feedback before these features become official. redirect_from: - /v3/previews versions: @@ -13,208 +13,230 @@ topics: --- -Pré-visualizações da API permitem que você experimente novas APIs e alterações nos métodos de API existentes antes de se tornarem parte da API oficial do GitHub. +API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API. -Durante o período de pré-visualização, poderemos alterar alguns recursos com base no feedback do desenvolvedor. Se fizermos alterações, iremos anunciá-las no [blogue do desenvolvedor](https://developer.github.com/changes/) sem aviso prévio. +During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -Para acessar uma pré-visualização da API, você precisará fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar` para suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido. +To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% ifversion ghes < 3.3 %} -## Implementações aprimoradas +## Enhanced deployments -Exerça um maior controle sobre as [implantações](/rest/reference/repos#deployments) com mais informações e uma granularidade mais precisa. +Exercise greater control over [deployments](/rest/reference/repos#deployments) with more information and finer granularity. -**Tipo de mídia personalizada:** `ant-man-preview` **Anunciado em:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +**Custom media type:** `ant-man-preview` +**Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) {% endif %} {% ifversion ghes < 3.3 %} -## Reações +## Reactions -Gerencie as [reações](/rest/reference/reactions) de commits, problemas e comentários. +Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. -**Tipo de mídia personalizado:** `squirrel-girl-preview` **Anunciado en:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Atualizado em:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +**Custom media type:** `squirrel-girl-preview` +**Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) +**Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) {% endif %} {% ifversion ghes < 3.3 %} -## Linha do tempo +## Timeline -Obter uma [lista de eventos](/rest/reference/issues#timeline) para um problema ou pull request. +Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. -**Tipo de mídia personalizada:** `mockingbird-preview` **Anunciado em:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +**Custom media type:** `mockingbird-preview` +**Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) {% endif %} {% ifversion ghes %} -## Ambientes pre-receive +## Pre-receive environments -Cria, lista, atualiza e exclui ambientes para hooks pre-receive. +Create, list, update, and delete environments for pre-receive hooks. -**Tipo de mídia personalizada:** `eye-scream-preview` **Anunciado em:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) +**Custom media type:** `eye-scream-preview` +**Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} {% ifversion ghes < 3.3 %} -## Projetos +## Projects -Gerencie [projetos](/rest/reference/projects). +Manage [projects](/rest/reference/projects). -**Tipo de mídia personalizado:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Atualizado em:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +**Custom media type:** `inertia-preview` +**Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) +**Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) {% endif %} {% ifversion ghes < 3.3 %} -## Pesquisa de commit +## Commit search -[Pesquisa commits](/rest/reference/search). +[Search commits](/rest/reference/search). -**Tipo de mídia personalizada:** `cloak-preview` **Anunciado em:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) +**Custom media type:** `cloak-preview` +**Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% endif %} {% ifversion ghes < 3.3 %} -## Tópicos do repositório +## Repository topics -Ver uma lista dos [tópicos do repositório](/articles/about-topics/) em [chamadas](/rest/reference/repos) que retornam resultados do repositório. +View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. -**Tipo de mídia personalizada:** `mercy-preview` **Anunciado em:** [2017-01-31](https://github.com/blog/2309-introducing-topics) +**Custom media type:** `mercy-preview` +**Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) {% endif %} {% ifversion ghes < 3.3 %} -## Códigos de conduta +## Codes of conduct -Veja todos os [códigos de conduta](/rest/reference/codes-of-conduct) ou obtenha qual código de conduta um repositório tem atualmente. +View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. -**Tipo de mídia personalizado:** `scarlet-witch-preview` +**Custom media type:** `scarlet-witch-preview` {% endif %} {% ifversion ghae or ghes %} -## Webhooks globais +## Global webhooks -Habilita [webhooks globais](/rest/reference/enterprise-admin#global-webhooks/) para [organizações](/webhooks/event-payloads/#organization) e tipos de evento do [usuário](/webhooks/event-payloads/#user). Esta visualização da API só está disponível para {% data variables.product.prodname_ghe_server %}. +Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for [organization](/webhooks/event-payloads/#organization) and [user](/webhooks/event-payloads/#user) event types. This API preview is only available for {% data variables.product.prodname_ghe_server %}. -**Tipo de mídia personalizada:** `superpro-preview` **Anunciado em:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks) +**Custom media type:** `superpro-preview` +**Announced:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks) {% endif %} {% ifversion ghes < 3.3 %} -## Exigir commits assinados +## Require signed commits -Agora você pode usar a API para gerenciar a configuração para [exigir commits assinados em branches protegidos](/rest/reference/repos#branches). +You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches). -**Tipo de mídia personalizada:** `zzzax-preview` **Anunciado em:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +**Custom media type:** `zzzax-preview` +**Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) {% endif %} {% ifversion ghes < 3.3 %} -## Exigir múltiplas revisões de aprovação +## Require multiple approving reviews -Agora você pode [exigir múltiplas revisões de aprovação](/rest/reference/repos#branches) para um pull request usando a API. +You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. -**Tipo de mídia personalizada:** `luke-cage-preview` **Anunciado em:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +**Custom media type:** `luke-cage-preview` +**Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) {% endif %} {% ifversion ghes %} -## Acesso de Git anônimo aos repositórios +## Anonymous Git access to repositories -Quando uma instância do {% data variables.product.prodname_ghe_server %} estiver em modo privado, os administradores do site e do repositório podem habilitar o acesso anônimo ao Git para um repositório público. +When a {% data variables.product.prodname_ghe_server %} instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository. -**Tipo de mídia personalizada:** `x ray-preview` **Anunciado:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) +**Custom media type:** `x-ray-preview` +**Announced:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) {% endif %} {% ifversion ghes < 3.3 %} -## Detalhes do cartão de projeto +## Project card details -As respostas da API REST para [eventos de problemas](/rest/reference/issues#events) e [eventos da linha do tempo de problemas](/rest/reference/issues#timeline) agora retornam o campo `project_card` para eventos relacionados ao projeto. +The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events. -**Tipo de mídia personalizada:** `starfox-preview` **Anunciado:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) +**Custom media type:** `starfox-preview` +**Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) {% endif %} {% ifversion fpt or ghec %} -## Manifestoes do aplicativo GitHub +## GitHub App Manifests -Os manifestos do aplicativo GitHub permitem que pessoas criem aplicativos GitHub pré-configurados. Veja "[Criar aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obter mais inoformações. +GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" for more details. -**Tipo de mídia personalizada:** `fury-preview` +**Custom media type:** `fury-preview` {% endif %} {% ifversion ghes < 3.3 %} -## Status da implantação +## Deployment statuses -Agora você pode atualizar o ambiente `` de um [status de implantação](/rest/reference/repos#create-a-deployment-status) e usar os estados `in_progress` e `na fila`. Ao criar o status da implantação, agora você pode usar o parâmetro `auto_inactive` para marcar implantações de `produção` antigas como `inativa`. +You can now update the `environment` of a [deployment status](/rest/reference/repos#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`. -**Tipo de mídia personalizada:** `flash-preview` **Anunciado:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +**Custom media type:** `flash-preview` +**Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) {% endif %} {% ifversion ghes < 3.3 %} -## Permissões de criação de repositório +## Repository creation permissions -Agora você pode configurar se os integrantes da organização podem criar repositórios e que tipos de repositórios podem criar. Consulte "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" para obter mais informações. +You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. -**Tipos de mídia personalizada:** `surtur-preview` **Anunciado:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +**Custom media types:** `surtur-preview` +**Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} -## Anexos de conteúdo +## Content attachments -Agora você pode fornecer mais informações no GitHub para URLs vinculadas a domínios registrados usando a API de {% data variables.product.prodname_unfurls %}. Consulte "[Usar anexos de conteúdo](/apps/using-content-attachments/)" para obter mais informações. +You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details. -**Tipos de mídia personalizada:** `corsair-preview` **Anunciado:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +**Custom media types:** `corsair-preview` +**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) -{% ifversion ghes < 3.3 %} +{% ifversion ghae or ghes < 3.3 %} -## Habilitar e desabilitar páginas +## Enable and disable Pages -Você pode usar os novos pontos de extremidade no [API de páginas](/rest/reference/repos#pages) para habilitar ou desabilitar páginas. Para saber mais sobre páginas, consulte "[Princípios básicos do GitHub Pages](/categories/github-pages-basics)". +You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)". -**Tipos de mídia personalizada:** `switcheroo-preview` **Anunciado:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +**Custom media types:** `switcheroo-preview` +**Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) {% endif %} {% ifversion ghes < 3.3 %} -## Listar branches ou pull requests para um commit +## List branches or pull requests for a commit -Você pode usar dois novos pontos de extremidade na [API de commits](/rest/reference/repos#commits) para listar branches ou pull requests para um commit. +You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit. -**Tipos de mídia personalizada:** `groot-preview` **Anunciado:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) +**Custom media types:** `groot-preview` +**Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) {% endif %} {% ifversion ghes < 3.3 %} -## Atualizar um branch de pull request +## Update a pull request branch -Você pode usar um novo ponto de extremidade para [atualizar um branch de pull request](/rest/reference/pulls#update-a-pull-request-branch) com alterações do HEAD do branch upstream. +You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch. -**Tipos de mídia personalizada:** `lidian-preview` **Anunciado:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) +**Custom media types:** `lydian-preview` +**Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) {% endif %} {% ifversion ghes < 3.3 %} -## Criar e usar modelos de repositório +## Create and use repository templates -Você pode usar um novo ponto de extremidade para [Criar um repositório usando um modelo](/rest/reference/repos#create-a-repository-using-a-template) e [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) que é um repositório de modelo, definindo o parâmetro `is_template` como `verdadeiro`. [Obter um repositório](/rest/reference/repos#get-a-repository) para verificar se ele é definido como um repositório de modelo usando a chave `is_template`. +You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key. -**Tipos de mídia personalizada:** `baptiste-preview` **Anunciado:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) +**Custom media types:** `baptiste-preview` +**Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% endif %} {% ifversion ghes < 3.3 %} -## Novo parâmetro de visibilidade para a API de repositórios +## New visibility parameter for the Repositories API -Você pode definir e recuperar a visibilidade de um repositório na [API de repositórios](/rest/reference/repos). +You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). -**Tipos de mídia personalizada:** `nebula-preview` **Anunciado:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +**Custom media types:** `nebula-preview` +**Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/pt-BR/content/rest/reference/activity.md b/translations/pt-BR/content/rest/reference/activity.md deleted file mode 100644 index a2aaac3fb5..0000000000 --- a/translations/pt-BR/content/rest/reference/activity.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -title: Atividade -intro: 'The Activity API allows you to list events and feeds and manage notifications, starring, and watching for the authenticated user.' -redirect_from: - - /v3/activity -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - API -miniTocMaxHeadingLevel: 3 ---- - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Eventos - -A API de eventos é uma API somente leitura para os eventos de {% data variables.product.prodname_dotcom %}. Esses eventos alimentam os vários fluxos de atividades no site. - -A API de eventos pode retornar diferentes tipos de eventos acionados por atividade em {% data variables.product.product_name %}. The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{{ site.data.variables.product.prodname_dotcom }} Event types](/developers/webhooks-and-events/github-event-types)." Para obter mais informações, consulte a "[API de Eventos de problema](/rest/reference/issues#events)". - -Os eventos são otimizados para sondagem a com o cabeçalho "ETag". Se nenhum novo evento for iniciado, você verá uma resposta "304 Not Modified" e seu limite de taxa atual não será alterado. Há também um cabeçalho "X-Poll-Interval" que especifica quantas vezes (em segundos) você pode fazer uma sondagem. Em tempos de alta carga do servidor, o tempo pode aumentar. Obedeça o cabeçalho. - -``` shell -$ curl -I {% data variables.product.api_url_pre %}/users/tater/events -> HTTP/2 200 -> X-Poll-Interval: 60 -> ETag: "a18c3bded88eb5dbb5c849a489412bf3" - -# The quotes around the ETag value are important -$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \ -$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"' -> HTTP/2 304 -> X-Poll-Interval: 60 -``` - -Apenas eventos criados nos últimos 90 dias serão incluídos nas linhas de tempo. Eventos mais antigos que 90 dias não serão incluídos (mesmo que o número total de eventos na linha do tempo seja inferior a 300). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Feeds - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %} -{% endfor %} - -### Exemplo de como obter um feed do Atom - -Para obter um feed no formato Atom você deve especificar o tipo `application/atom+xml` no cabeçalho `Aceitar`. Por exemplo, para obter o feed do Atom para consultorias de segurança do GitHub: - - curl -H "Accept: application/atom+xml" https://github.com/security-advisories - -#### Resposta - -```shell -HTTP/2 200 -``` - -```xml - - - tag:github.com,2008:/security-advisories - - GitHub Security Advisory Feed - - GitHub - - 2019-01-14T19:34:52Z - - tag:github.com,2008:GHSA-abcd-12ab-23cd - 2018-07-26T15:14:52Z - 2019-01-14T19:34:52Z - [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp - - - <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p> - <p><strong>Affected Packages</strong></p> - - <dl> - <dt>Octoapp</dt> - <dd>Ecosystem: npm</dd> - <dd>Severity: moderate</dd> - <dd>Versions: &lt; 4.17.5</dd> - <dd>Fixed in: 4.17.5</dd> - </dl> - - <p><strong>References</strong></p> - - <ul> - <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li> - </ul> - - - - -``` - -## Notificações - -Os usuários recebem notificações de conversas em repositórios que inspecionam, incluindo: - -* Problemas e seus comentários -* Pull Requests e seus comentários -* Comentários em quaisquer commits - -As notificações também são enviadas para conversas em repositórios não inspecionados quando o usuário está envolvido, incluindo: - -* **@mentions** -* Tarefas de problemas -* Commits que o usuário cria ou faz commit -* Qualquer discussão de que o usuário participa ativamente - -Todas as chamadas de notificação da API requerem escopos da API para `notificações` ou `repositórios`. Fazer isto dará acesso somente-leitura a algum problema e fará commit do conteúdo. Você ainda precisará do escopo de `repositório` para acessar problemas e commits de seus respectivos pontos de extremidade. - -Notificações retornam como "correntes". Uma corrente contém informações sobre a discussão atual de um problema, pull request ou commit. - -As notificações são otimizadas para sondagem com o cabeçalho `Last-Modified`. Se não houver novas notificações, você verá uma resposta `304 Not Modified`, deixando a sua taxa de limite atual inalterada. Há um cabeçalho `X-Poll-Interval` que especifica com que frequência (em segundos) que você pode fazer a sondagem. Em tempos de alta carga do servidor, o tempo pode aumentar. Obedeça o cabeçalho. - -``` shell -# Add authentication to your requests -$ curl -I {% data variables.product.api_url_pre %}/notifications -HTTP/2 200 -Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT -X-Poll-Interval: 60 - -# Pass the Last-Modified header exactly -$ curl -I {% data variables.product.api_url_pre %}/notifications -$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" -> HTTP/2 304 -> X-Poll-Interval: 60 -``` - -### Motivos de notificação - -Ao recuperar respostas da API de Notificações, cada carga tem uma carga denominada `drazão`. Estas correspondem a eventos que ativam uma notificação. - -Aqui está uma lista da potencial `razão` para receber uma notificação: - -| Nome da razão | Descrição | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `assign` | O problema foi atribuído a você. | -| `autor` | Você criou a corrente. | -| `comentário` | Você comentou na corrente. | -| `ci_activity` | A execução de um fluxo de trabalho {% data variables.product.prodname_actions %} que você acionou foi concluída. | -| `convite` | Você aceitou um convite para contribuir com o repositório. | -| `manual` | Você assinou a corrente (por meio de um problema ou pull request). | -| `menção` | Você foi especificamente **@mentioned** no conteúdo. | -| `review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %} -| `security_alert` | O {% data variables.product.prodname_dotcom %} descobriu uma [vulnerabilidade de segurança](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) no seu repositório.{% endif %} -| `state_change` | Você alterou o estado da corrente (por exemplo, fechando um problema ou mesclando um pull request). | -| `assinado` | Você está inspecionando o repositório. | -| `team_mention` | Você estava em uma equipe que foi mencionada. | - -Observe que a `razão` é modificada em uma base de corrente e pode mudar se a `razão` em uma notificação posterior for diferente. - -Por exemplo, se você é o autor de um problema, as notificações subsequentes sobre essa problema terão uma `razão` do `autor`. Portanto, se você for **@mentioned** no mesmo problema, as notificações que você buscar subsequentemente terão uma `razão` a `mencionar`. A `razão` permanece como `menção`, independentemente se você já foi mencionado novamente. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Marcar com uma estrela - -Marcar o repositório como uma estrela é uma funcionalidade que permite aos usuários favoritar os repositórios. As estrelas são exibidas ao lado dos repositórios para mostrar um nível de interesse aproximado. As estrelas não têm efeito nas notificações ou no feed da atividade. - -### Marcar como estrela vs. Inspecionar - -Em agosto de 2012, [mudamos a forma como a inspeção funciona](https://github.com/blog/1204-notifications-stars) em {% data variables.product.prodname_dotcom %}. Muitas aplicações de cliente da API podem estar usando os pontos de extremidade originais de "inspetor" para acessar estes dados. Agora você pode começar a usar os pontos de extremidade "estrela" (descritos abaixo). Para obter mais informações, consulte a [Post de alteração da API de Inspeção](https://developer.github.com/changes/2012-09-05-watcher-api/) e a [API de Inspeção do repositório](/rest/reference/activity#watching)". - -### Tipos de mídia personalizados para marcar como estrela - -Existe um tipo de mídia personalizado com suporte para a API REST estrelada. Ao usar este tipo de mídia personalizada, você receberá uma resposta com a propriedade do registro de tempo `starred_at`, que indica o tempo que a estrela foi criada. A resposta também tem uma segunda propriedade que inclui o recurso retornado quando o tipo de mídia personalizado não está incluído. A propriedade que contém o recurso será `usuário` ou `repositório`. - - application/vnd.github.v3.star+json - -Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Inspecionando - -Inspecionar um repositório registra o usuário para receber notificações de novas discussões, bem como eventos no feed de atividade do usuário. Para favoritar um repositório de forma simples, consulte "[Marcar repositórios com uma estrela](/rest/reference/activity#starring)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md deleted file mode 100644 index d8512c1e8d..0000000000 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ /dev/null @@ -1,329 +0,0 @@ ---- -title: GitHub Enterprise administration -intro: You can use these endpoints to administer your enterprise. Among the tasks you can perform with this API are many relating to GitHub Actions. -allowTitleToDifferFromFilename: true -redirect_from: - - /v3/enterprise-admin - - /v3/enterprise -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - API -miniTocMaxHeadingLevel: 3 -shortTitle: Enterprise administration ---- - -{% ifversion fpt or ghec %} - -{% note %} - -**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu. - -{% endnote %} - -{% endif %} - -### Endpoint URLs - -REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: - -```shell -{% data variables.product.api_url_pre %} -``` - -{% ifversion ghes %} -[Management Console](#management-console) API endpoints are only prefixed with a hostname: - -```shell -http(s)://hostname/ -``` -{% endif %} -{% ifversion ghae or ghes %} -### Authentication - -Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} -OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %} - -Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. - -{% endif %} - -{% ifversion ghae or ghes %} -### Version information - -The current version of your enterprise is returned in the response header of every API: -`X-GitHub-Enterprise-Version: {{currentVersion}}.0` -You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -{% endif %} - -{% ifversion fpt or ghec or ghes > 3.2 %} - -## Audit log - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion fpt or ghec %} -## Billing - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -## GitHub Actions - -{% data reusables.actions.ae-beta %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} -{% endfor %} - - -{% ifversion ghae or ghes %} -## Admin stats - -The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghae or ghes > 2.22 %} - -## Announcements - -The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghae or ghes %} - -## Global webhooks - -Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types. - -*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghes %} - -## LDAP - -You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization. - -With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghae or ghes %} -## License - -The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghes %} - -## Management console - -The Management Console API helps you manage your {% data variables.product.product_name %} installation. - -{% tip %} - -You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. - -If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects. - -You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/). - -{% endtip %} - -### Authentication - -You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license). - -Use the `api_key` parameter to send this token with each request. For example: - -```shell -$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password' -``` - -You can also use standard HTTP authentication to send this token. For example: - -```shell -$ curl -L 'https://api_key:your-amazing-password@hostname:admin_port/setup/api' -``` - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghae or ghes %} -## Organizations - -The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghes %} -## Organization pre-receive hooks - -The Organization Pre-receive Hooks API allows you to view and modify -enforcement of the pre-receive hooks that are available to an organization. - -### Object attributes - -| Name | Type | Description | -|----------------------------------|-----------|-----------------------------------------------------------| -| `name` | `string` | The name of the hook. | -| `enforcement` | `string` | The state of enforcement for the hook on this repository. | -| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. | -| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | - -Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject -any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. - -`configuration_url` may be a link to this endpoint or this hook's global -configuration. Only site admins are able to access the global configuration. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghes %} - -## Pre-receive environments - -The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. - -### Object attributes - -#### Pre-receive Environment - -| Name | Type | Description | -|-----------------------|-----------|----------------------------------------------------------------------------| -| `name` | `string` | The name of the environment as displayed in the UI. | -| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. | -| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. | -| `download` | `object` | This environment's download status. | -| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. | - -#### Pre-receive Environment Download - -| Name | Type | Description | -|-----------------|----------|---------------------------------------------------------| -| `state` | `string` | The state of the most recent download. | -| `downloaded_at` | `string` | The time when the most recent download started. | -| `message` | `string` | On failure, this will have any error messages produced. | - -Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghes %} -## Pre-receive hooks - -The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to -[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. - -### Object attributes - -#### Pre-receive Hook - -| Name | Type | Description | -|----------------------------------|-----------|-----------------------------------------------------------------| -| `name` | `string` | The name of the hook. | -| `script` | `string` | The script that the hook runs. | -| `script_repository` | `object` | The GitHub repository where the script is kept. | -| `environment` | `object` | The pre-receive environment where the script is executed. | -| `enforcement` | `string` | The state of enforcement for this hook. | -| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. | - -Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject -any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghes %} - -## Repository pre-receive hooks - -The Repository Pre-receive Hooks API allows you to view and modify -enforcement of the pre-receive hooks that are available to a repository. - -### Object attributes - -| Name | Type | Description | -|---------------------|----------|-----------------------------------------------------------| -| `name` | `string` | The name of the hook. | -| `enforcement` | `string` | The state of enforcement for the hook on this repository. | -| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | - -Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. - -`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% ifversion ghae or ghes %} -## Users - -The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md index 1041fe3483..a8142804dc 100644 --- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md @@ -1,6 +1,6 @@ --- -title: Permissões necessárias para os aplicativos GitHub -intro: 'Você pode encontrar as permissões necessárias para cada ponto de extremidade compatível com {% data variables.product.prodname_github_app %}.' +title: Permissions required for GitHub Apps +intro: 'You can find the required permissions for each {% data variables.product.prodname_github_app %}-compatible endpoint.' redirect_from: - /v3/apps/permissions versions: @@ -11,16 +11,16 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -shortTitle: Permissões do aplicativo GitHub +shortTitle: GitHub App permissions --- -### Sobre as permissões de {% data variables.product.prodname_github_app %} +### About {% data variables.product.prodname_github_app %} permissions -{% data variables.product.prodname_github_apps %} são criadas com um conjunto de permissões. As permissões definem quais recursos o {% data variables.product.prodname_github_app %} pode acessar através da API. Para obter mais informações, consulte "[Configurações de permissões para os aplicativos GitHub](/apps/building-github-apps/setting-permissions-for-github-apps/)". +{% data variables.product.prodname_github_apps %} are created with a set of permissions. Permissions define what resources the {% data variables.product.prodname_github_app %} can access via the API. For more information, see "[Setting permissions for GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)." -### Permissões de metadados +### Metadata permissions -Os aplicativos GitHub têm a permissão de metadados `Read-only` por padrão. A permissão de metadados fornece acesso a uma coleção de pontos de extremidade somente leitura com metadados para vários recursos. Esses pontos de extremidade não vazam informações privadas sobre repositórios. +GitHub Apps have the `Read-only` metadata permission by default. The metadata permission provides access to a collection of read-only endpoints with metadata for various resources. These endpoints do not leak sensitive private repository information. {% data reusables.apps.metadata-permissions %} @@ -72,17 +72,17 @@ Os aplicativos GitHub têm a permissão de metadados `Read-only` por padrão. A - [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) -_Colaboradores_ +_Collaborators_ - [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) - [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) -_Comentários de commit_ +_Commit comments_ - [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) - [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) - [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) - [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) -_Eventos_ +_Events_ - [`GET /events`](/rest/reference/activity#list-public-events) - [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories) - [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events) @@ -95,16 +95,16 @@ _Git_ - [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) - [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) -_Chaves_ +_Keys_ - [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) -_Integrantes da organização_ +_Organization members_ - [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) - [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) - [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members) - [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user) -_Pesquisar_ +_Search_ - [`GET /search/code`](/rest/reference/search#search-code) - [`GET /search/commits`](/rest/reference/search#search-commits) - [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests) @@ -114,7 +114,7 @@ _Pesquisar_ - [`GET /search/users`](/rest/reference/search#search-users) {% ifversion fpt or ghes or ghec %} -### Permissão em "ações" +### Permission on "actions" - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) @@ -138,7 +138,7 @@ _Pesquisar_ - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) {% endif %} -### Permissão em "administração" +### Permission on "administration" - [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) - [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) @@ -147,6 +147,11 @@ _Pesquisar_ - [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) - [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) - [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository) (:write) +- [`PUT /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository) (:write) {% ifversion fpt or ghes -%} - [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) - [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write) @@ -218,28 +223,28 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) {% endif %} -_Colaboradores_ +_Collaborators_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) - [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) -_Convites_ +_Invitations_ - [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) - [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) - [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) -_Chaves_ +_Keys_ - [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) - [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) - [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) - [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) -_Equipes_ +_Teams_ - [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) - [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) {% ifversion fpt or ghec %} -_Tráfego_ +_Traffic_ - [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) - [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) - [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) @@ -247,7 +252,7 @@ _Tráfego_ {% endif %} {% ifversion fpt or ghec %} -### Permissão em "bloqueio" +### Permission on "blocking" - [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) - [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) @@ -255,7 +260,7 @@ _Tráfego_ - [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) {% endif %} -### Permissão em "verificações" +### Permission on "checks" - [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) - [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) @@ -269,7 +274,7 @@ _Tráfego_ - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) -### Permissão em "conteúdo" +### Permission on "contents" - [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) {% ifversion fpt -%} @@ -366,7 +371,7 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) {% endif %} -_Comentários de commit_ +_Commit comments_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) - [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) - [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) @@ -388,7 +393,7 @@ _Git_ - [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) {% ifversion fpt or ghec %} -_importar_ +_Import_ - [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (:read) - [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (:write) - [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (:write) @@ -399,7 +404,7 @@ _importar_ - [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) {% endif %} -_Reações_ +_Reactions_ {% ifversion fpt or ghes or ghae -%} - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) @@ -415,7 +420,7 @@ _Reações_ - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write) {% endif %} -_Versões_ +_Releases_ - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) - [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (:write) - [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (:read) @@ -428,7 +433,7 @@ _Versões_ - [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (:read) - [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (:read) -### Permissão em "implantações" +### Permission on "deployments" - [`GET /repos/:owner/:repo/deployments`](/rest/reference/repos#list-deployments) (:read) - [`POST /repos/:owner/:repo/deployments`](/rest/reference/repos#create-a-deployment) (:write) @@ -441,7 +446,7 @@ _Versões_ - [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/repos#get-a-deployment-status) (:read) {% ifversion fpt or ghes or ghec %} -### Permissão em "e-mails" +### Permission on "emails" {% ifversion fpt -%} - [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) @@ -452,7 +457,7 @@ _Versões_ - [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) {% endif %} -### Permissão em "seguidores" +### Permission on "followers" - [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) - [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) @@ -460,7 +465,7 @@ _Versões_ - [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) - [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) -### Permissão em "chaves gpg" +### Permission on "gpg keys" - [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) - [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) @@ -468,16 +473,16 @@ _Versões_ - [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) {% ifversion fpt or ghec %} -### Permissão em "limites de interação" +### Permission on "interaction limits" - [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (:read) - [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (:write) - [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (:write) {% endif %} -### Permissão em "problemas" +### Permission on "issues" -Problemas e pull requests estão estreitamente relacionados. Para obter mais informações, consulte "[Lista de problemas atribuídos ao usuário autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)". Se seu aplicativo GitHub tiver permissões em problemas e não em pull requests, esses pontos de extremidade irão limitar-se a problemas. Pontos de extremidade que retornam problemas e pull requests serão filtrados. Os pontos de extremidade que permitem operações em ambos problemas e pull requests estarão restritos a problemas. +Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues. - [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) - [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) @@ -497,17 +502,17 @@ Problemas e pull requests estão estreitamente relacionados. Para obter mais inf - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) -_Responsáveis_ +_Assignees_ - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) -_Eventos_ +_Events_ - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) -_Etiquetas_ +_Labels_ - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) @@ -519,7 +524,7 @@ _Etiquetas_ - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) -_Marcos_ +_Milestones_ - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) @@ -527,7 +532,7 @@ _Marcos_ - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) -_Reações_ +_Reactions_ - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) - [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) @@ -544,15 +549,15 @@ _Reações_ - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write) {% endif %} -### Permissão em "chaves" +### Permission on "keys" -_Chaves_ +_Keys_ - [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) - [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) - [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) - [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) -### Permissão em "integrantes" +### Permission on "members" {% ifversion fpt -%} - [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) @@ -587,14 +592,14 @@ _Chaves_ {% endif %} {% ifversion fpt or ghec %} -_Convites_ +_Invitations_ - [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) - [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) - [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) - [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) {% endif %} -_Integrantes da organização_ +_Organization members_ - [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) - [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) - [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) @@ -605,13 +610,13 @@ _Integrantes da organização_ - [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) - [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) -_Integrantes da equipe_ +_Team members_ - [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) - [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) - [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) - [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) -_Equipes_ +_Teams_ - [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) - [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) - [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) @@ -629,7 +634,7 @@ _Equipes_ - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) - [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) -### Permissão em "administração da organização" +### Permission on "organization administration" - [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) {% ifversion fpt -%} @@ -642,11 +647,11 @@ _Equipes_ - [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) {% endif %} -### Permissão em "eventos de organização" +### Permission on "organization events" - [`GET /users/:username/events/orgs/:org`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (:read) -### Permissão em "hooks da organização" +### Permission on "organization hooks" - [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (:read) - [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (:write) @@ -655,11 +660,11 @@ _Equipes_ - [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (:write) - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) -_Equipes_ +_Teams_ - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% ifversion ghes %} -### Permissão em "hooks pre-receive da organização" +### Permission on "organization pre receive hooks" - [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read) - [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read) @@ -667,7 +672,7 @@ _Equipes_ - [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write) {% endif %} -### Permissão em "projetos da organização" +### Permission on "organization projects" - [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) @@ -688,7 +693,7 @@ _Equipes_ - [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) {% ifversion fpt or ghec %} -### Permissão em "bloqueio de usuários da organização" +### Permission on "organization user blocking" - [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) - [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) @@ -696,7 +701,7 @@ _Equipes_ - [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) {% endif %} -### Permissão em "páginas" +### Permission on "pages" - [`GET /repos/:owner/:repo/pages`](/rest/reference/repos#get-a-github-pages-site) (:read) - [`POST /repos/:owner/:repo/pages`](/rest/reference/repos#create-a-github-pages-site) (:write) @@ -710,9 +715,9 @@ _Equipes_ - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write) {% endif %} -### Permissão em "pull requests" +### Permission on "pull requests" -Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Os pontos de extremidade que retornam pull requests e problemas serão filtrados. Os pontos de extremidade que permitem operações em pull requests e problemas serão restritos a pull requests. +Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests. - [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) - [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) @@ -738,18 +743,18 @@ Pull requests and issues are closely related. If your GitHub App has permissions - [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) -_Responsáveis_ +_Assignees_ - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) -_Eventos_ +_Events_ - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) -_Etiquetas_ +_Labels_ - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) @@ -761,7 +766,7 @@ _Etiquetas_ - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) -_Marcos_ +_Milestones_ - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) @@ -769,7 +774,7 @@ _Marcos_ - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) -_Reações_ +_Reactions_ - [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) @@ -787,12 +792,12 @@ _Reações_ - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write) {% endif %} -_Revisores solicitados_ +_Requested reviewers_ - [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) - [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) - [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) -_Revisões_ +_Reviews_ - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) @@ -801,11 +806,11 @@ _Revisões_ - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) -### Permissão em "perfil" +### Permission on "profile" - [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write) -### Permissão em "hooks de repositório" +### Permission on "repository hooks" - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) - [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) @@ -824,7 +829,7 @@ _Revisões_ - [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) (:write) {% endif %} -### Permissão em "projetos de repositório" +### Permission on "repository projects" - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) - [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) @@ -845,11 +850,11 @@ _Revisões_ - [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) - [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) -_Equipes_ +_Teams_ - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) {% ifversion fpt or ghec %} -### Permissão em "segredos" +### Permission on "secrets" - [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) - [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) @@ -868,14 +873,14 @@ _Equipes_ {% endif %} {% ifversion fpt or ghes > 3.0 or ghec %} -### Permissão em "alertas de varredura de segredo" +### Permission on "secret scanning alerts" - [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) - [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) {% endif %} -### Permissão em "eventos de segurança" +### Permission on "security events" - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) @@ -896,34 +901,39 @@ _Equipes_ {% endif -%} {% ifversion fpt or ghes or ghec %} -### Permissão em "executores auto-hospedados" +### Permission on "self-hosted runners" - [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) - [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) - [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) - [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) - [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) - [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) +- [`GET /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization) (:write) +- [`PUT /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (:write) {% endif %} -### Permissão em "arquivo único" +### Permission on "single file" - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) - [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) - [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) -### Permissão em "marcar com uma estrela" +### Permission on "starring" - [`GET /user/starred/:owner/:repo`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) (:read) - [`PUT /user/starred/:owner/:repo`](/rest/reference/activity#star-a-repository-for-the-authenticated-user) (:write) - [`DELETE /user/starred/:owner/:repo`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) (:write) -### Permissão em "status" +### Permission on "statuses" - [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) - [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) - [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) -### Permissão em "discussões em equipe" +### Permission on "team discussions" - [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) - [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md index 9c871074b2..99d4a14e4f 100644 --- a/translations/pt-BR/content/rest/reference/search.md +++ b/translations/pt-BR/content/rest/reference/search.md @@ -1,6 +1,6 @@ --- -title: Pesquisar -intro: 'A API de pesquisa de {% data variables.product.product_name %} permite que você procure o item específico de forma eficiente.' +title: Search +intro: 'The {% data variables.product.product_name %} Search API lets you to search for the specific item efficiently.' redirect_from: - /v3/search versions: @@ -13,109 +13,125 @@ topics: miniTocMaxHeadingLevel: 3 --- -A API de pesquisa ajuda a pesquisar o item específico que você deseja encontrar. Por exemplo, você pode encontrar um usuário ou um arquivo específico em um repositório. Pense nisso da mesma forma que você pensa em realizar uma pesquisa no Google. Ele é projetado para ajudá-lo a encontrar o resultado que você está procurando (ou talvez os poucos resultados que você está procurando). Assim como pesquisar no Google, às vezes, você quer ver algumas páginas com resultados de pesquisa para que você possa encontrar o item que melhor atenda às suas necessidades. Para atender a essa necessidade, a API de pesquisa do {% data variables.product.product_name %} fornece **até 1.000 resultados para cada pesquisa**. +The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**. -Você pode restringir sua pesquisa usando as consultas. Para saber mais sobre a sintaxe de consultas de pesquisa, consulte "[Criar uma consulta de pesquisa](/rest/reference/search#constructing-a-search-query)". +You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." -### Resultados da pesquisa de classificação +### Ranking search results -A menos que outra opção de ordenamento seja fornecida como um parâmetro de consulta, os resultados são ordenados pela melhor correspondência e em ordem decrescente. Vários fatores são combinados para impulsionar o item mais relevante para a parte superior da lista de resultados. +Unless another sort option is provided as a query parameter, results are sorted by best match in descending order. Multiple factors are combined to boost the most relevant item to the top of the result list. -### Limite de taxa +### Rate limit -A API de pesquisa tem um limite de taxa personalizado. Para solicitações que usam a [Autenticação Básica](/rest#authentication)[OAuth ](/rest#authentication) ou [ID e segredo do cliente e](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), você pode fazer até 30 solicitações por minuto. Para solicitações não autenticadas, o limite de taxa permite que você faça até 10 solicitações por minuto. +The Search API has a custom rate limit. For requests using [Basic +Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client +ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to +30 requests per minute. For unauthenticated requests, the rate limit allows you +to make up to 10 requests per minute. {% data reusables.enterprise.rate_limit %} -Veja a [documentação do limite de taxa](/rest/reference/rate-limit) para obter informações sobre a determinação do seu status atual de limite de taxa. +See the [rate limit documentation](/rest/reference/rate-limit) for details on +determining your current rate limit status. -### Criar uma consulta de pesquisa +### Constructing a search query -Cada ponto de extremidade na API de Pesquisa usa [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para realizar pesquisas no {% data variables.product.product_name %}. Veja o ponto de extremidade individual na API de pesquisa para obter um exemplo que inclui o ponto de extremidade de parâmetros de consulta. +Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org/wiki/Query_string) to perform searches on {% data variables.product.product_name %}. See the individual endpoint in the Search API for an example that includes the endpoint and query parameters. -Uma consulta pode conter qualquer combinação de qualificadores de pesquisa compatíveis em {% data variables.product.product_name %}. O formato da consulta de pesquisa é: +A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is: ``` SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N ``` -Por exemplo, se você quisesse pesquisar todos os _repositórios_ de propriedade de `defunkt` que continham a palavra `GitHub` e `Octocat` no arquivo README, você usaria a consulta seguinte com o ponto de extremidade _pesquisar repositórios_: +For example, if you wanted to search for all _repositories_ owned by `defunkt` that +contained the word `GitHub` and `Octocat` in the README file, you would use the +following query with the _search repositories_ endpoint: ``` GitHub Octocat in:readme user:defunkt ``` -**Observação:** Certifique-se de usar o codificador HTML preferido do seu idioma para construir suas strings de consulta. Por exemplo: +**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. For example: ```javascript // JavaScript const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -Veja "[Pesquisar no GitHub](/articles/searching-on-github/)" para obter uma lista completa de qualificadores disponíveis, seu formato e um exemplo de como usá-los. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)". +See "[Searching on GitHub](/articles/searching-on-github/)" +for a complete list of available qualifiers, their format, and an example of +how to use them. For information about how to use operators to match specific +quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." -### Limitações no tamanho da consulta +### Limitations on query length -A API de pesquisa não é compatível com consultas que: -- têm tamanho superior a 256 caracteres (não incluindo operadores ou qualificadores). -- têm mais de cinco operadores de `E`, `OU` ou `NÃO` operadores. +The Search API does not support queries that: +- are longer than 256 characters (not including operators or qualifiers). +- have more than five `AND`, `OR`, or `NOT` operators. -Estas consultas de pesquisa irão retornar uma mensagem de erro "Ocorreu uma falha na validação". +These search queries will return a "Validation failed" error message. -### Tempo esgotado e resultados incompletos +### Timeouts and incomplete results -Para manter a API de pesquisa rápida para todos, limitamos quanto tempo todas as consulta individual podem ser executadas. Para consultas que [excedem o tempo limite](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), a API retorna as correspondências que já foram encontradas antes do tempo limite, e a resposta tem a propriedade `incomplete_results` definida como `verdadeiro`. +To keep the Search API fast for everyone, we limit how long any individual query +can run. For queries that [exceed the time limit](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), +the API returns the matches that were already found prior to the timeout, and +the response has the `incomplete_results` property set to `true`. -Atingir um tempo limite não significa necessariamente que os resultados da pesquisa estão incompletos. É possível que mais resultados tenham sido, mas também é possível que não. +Reaching a timeout does not necessarily mean that search results are incomplete. +More results might have been found, but also might not. -### Erros de acesso ou resultados de pesquisa ausentes +### Access errors or missing search results -Você precisa efetuar a autenticação com sucesso e ter acesso aos repositórios nas consultas de pesquisa. Caso contrário, você verá um erro 422 Unprocessible Entry` com uma mensagem "Falha na validação". Por exemplo, sua pesquisa irá falhar se sua consulta incluir qualificadores repo:`, `user:` ou `org:` que solicitam recursos aos quais você não tem acesso ao efetuar login em {% data variables.product.prodname_dotcom %}. +You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}. -Quando sua consulta de pesquisa solicitar vários recursos, a resposta só conterá os recursos aos quais você tem acesso e **não** fornecerá uma mensagem de erro listando os recursos que não foram retornados. +When your search query requests multiple resources, the response will only contain the resources that you have access to and will **not** provide an error message listing the resources that were not returned. -Por exemplo, se sua consulta de pesquisa pesquisar os repositórios `octocat/test` e `codertocat/test`, mas você só tem acesso a `octocat/test`, a sua resposta mostrará resultados de pesquisa para `octocat/test` e nenhum resultado para `codertocat/teste`. Este comportamento imita como a pesquisa que funciona no {% data variables.product.prodname_dotcom %}. +For example, if your search query searches for the `octocat/test` and `codertocat/test` repositories, but you only have access to `octocat/test`, your response will show search results for `octocat/test` and nothing for `codertocat/test`. This behavior mimics how search works on {% data variables.product.prodname_dotcom %}. {% include rest_operations_at_current_path %} -### Metadados da correspondência de texto +### Text match metadata -No GitHub, você pode usar o contexto fornecido por trechos de código e destaques nos resultados de pesquisa. A API de pesquisa oferece metadados adicionais que permitem que você destaque os termos de pesquisa correspondentes ao exibir resultados de busca. +On GitHub, you can use the context provided by code snippets and highlights in search results. The Search API offers additional metadata that allows you to highlight the matching search terms when displaying search results. ![code-snippet-highlighting](/assets/images/text-match-search-api.png) -As solicitações podem optar por receber esses fragmentos de texto na resposta, e cada fragmento é acompanhado de ajustes numéricos que identificam a localização exata de cada termo de pesquisa correspondente. +Requests can opt to receive those text fragments in the response, and every fragment is accompanied by numeric offsets identifying the exact location of each matching search term. -Para obter esses metadados nos resultados da sua pesquisa, especifique o tipo de mídia de `text-match` no seu cabeçalho `Aceitar`. +To get this metadata in your search results, specify the `text-match` media type in your `Accept` header. ```shell application/vnd.github.v3.text-match+json ``` -Ao fornecer o tipo de mídia `text-match`, você receberá uma chave extra na carga do JSON denominada `text_matches`, que fornece informações sobre a posição dos seus termos de pesquisa dentro do texto e da `propriedade` que inclui o termo de pesquisa. Dentro do array `text_match`, cada objeto inclui os atributos a seguir: +When you provide the `text-match` media type, you will receive an extra key in the JSON payload called `text_matches` that provides information about the position of your search terms within the text and the `property` that includes the search term. Inside the `text_matches` array, each object includes +the following attributes: -| Nome | Descrição | -| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `object_url` | A URL para o recurso que contém uma propriedade de string que corresponde a um dos termos de pesquisa. | -| `object_type` | O nome para o tipo de recurso que existe em determinado `object_url`. | -| `propriedade` | O nome de uma propriedade do recurso que existe em `object_url`. Esta propriedade é uma string que corresponde a um dos termos de pesquisa. (No JSON retornado a partir de `object_url`, o conteúdo completo do `fragmento` será encontrado na propriedade com este nome.) | -| `fragmento` | Um subconjunto do valor de `propriedade`. Este é o fragmento de texto que corresponde a um ou mais dos termos de pesquisa. | -| `matches` | Um array de um ou mais termos de pesquisa que estão presentes no `fragmento`. Os índices (ou seja, "ajustes") são relativos ao fragmento. (Eles não são relativos ao conteúdo _completo_ de `propriedade`.) | +Name | Description +-----|-----------| +`object_url` | The URL for the resource that contains a string property matching one of the search terms. +`object_type` | The name for the type of resource that exists at the given `object_url`. +`property` | The name of a property of the resource that exists at `object_url`. That property is a string that matches one of the search terms. (In the JSON returned from `object_url`, the full content for the `fragment` will be found in the property with this name.) +`fragment` | A subset of the value of `property`. This is the text fragment that matches one or more of the search terms. +`matches` | An array of one or more search terms that are present in `fragment`. The indices (i.e., "offsets") are relative to the fragment. (They are not relative to the _full_ content of `property`.) -#### Exemplo +#### Example -Se usarmos cURL e o [exemplo de pesquisa de problemas](#search-issues-and-pull-requests) acima, nossa solicitação de API seria da seguinte forma: +Using cURL, and the [example issue search](#search-issues-and-pull-requests) above, our API +request would look like this: ``` shell curl -H 'Accept: application/vnd.github.v3.text-match+json' \ '{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc' ``` -A resposta incluirá um array `text_matches` para cada resultado de pesquisa. No JSON abaixo, temos dois objetos no array `text_matches`. +The response will include a `text_matches` array for each search result. In the JSON below, we have two objects in the `text_matches` array. -A primeira correspondência de texto ocorreu na propriedade do `texto` do problema. Vemos um fragmento de texto a partir do texto do problema. O termo da pesquisa (`windows`) aparece duas vezes dentro desse fragmento, e temos os índices para cada ocorrência. +The first text match occurred in the `body` property of the issue. We see a fragment of text from the issue body. The search term (`windows`) appears twice within that fragment, and we have the indices for each occurrence. -A segunda correspondência de texto ocorreu na propriedade do `texto` de um dos comentários do problema. Nós temos a URL do comentário do problema. E, evidentemente, vemos um fragmento de texto do comentário. O termo de pesquisa (`windows`) aparece uma vez dentro desse fragmento. +The second text match occurred in the `body` property of one of the issue's comments. We have the URL for the issue comment. And of course, we see a fragment of text from the comment body. The search term (`windows`) appears once within that fragment. ```json { diff --git a/translations/pt-BR/content/rest/reference/secret-scanning.md b/translations/pt-BR/content/rest/reference/secret-scanning.md index ea4c976060..d3fd555101 100644 --- a/translations/pt-BR/content/rest/reference/secret-scanning.md +++ b/translations/pt-BR/content/rest/reference/secret-scanning.md @@ -1,6 +1,6 @@ --- -title: Varredura secreta -intro: 'Para recuperar e atualizar os alertas secretos de um repositório privado, você pode usar a API de digitalização secreta.' +title: Secret scanning +intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.' versions: fpt: '*' ghes: '>=3.1' @@ -11,6 +11,12 @@ miniTocMaxHeadingLevel: 3 {% data reusables.secret-scanning.api-beta %} -A API de {% data variables.product.prodname_secret_scanning %} permite recuperar e atualizar alertas de varredura de segredo de um repositório {% ifversion fpt or ghec %}privado {% endif %}. Para obter mais informações sobre a varredura de segredo, consulte "[Sobre o varredura de secredo](/code-security/secret-security/about-secret-scanning)". +The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}: + +- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. +- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below. +{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %} + +For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." {% include rest_operations_at_current_path %} diff --git a/translations/pt-BR/data/learning-tracks/actions.yml b/translations/pt-BR/data/learning-tracks/actions.yml index 505b49e936..1e96bf7290 100644 --- a/translations/pt-BR/data/learning-tracks/actions.yml +++ b/translations/pt-BR/data/learning-tracks/actions.yml @@ -37,6 +37,17 @@ deploy_to_the_cloud: - /actions/deployment/deploying-to-amazon-elastic-container-service - /actions/deployment/deploying-to-azure-app-service - /actions/deployment/deploying-to-google-kubernetes-engine +adopting_github_actions_for_your_enterprise: + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.' + guides: + - /actions/learn-github-actions/understanding-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae + - /actions/security-guides/security-hardening-for-github-actions hosting_your_own_runners: title: 'Hospede seus próprios executores' description: 'Você pode criar executores auto-hospedados para executar fluxos de trabalho em um ambiente altamente personalizável.' diff --git a/translations/pt-BR/data/learning-tracks/admin.yml b/translations/pt-BR/data/learning-tracks/admin.yml index 3e1002d74e..5b8ae75a75 100644 --- a/translations/pt-BR/data/learning-tracks/admin.yml +++ b/translations/pt-BR/data/learning-tracks/admin.yml @@ -2,6 +2,9 @@ get_started_with_github_ae: title: 'Primeiros passos com {% data variables.product.prodname_ghe_managed %}' description: 'Aprenda sobre {% data variables.product.prodname_ghe_managed %} e realize a configuração inicial de uma nova empresa.' + featured_track: true + versions: + ghae: '*' guides: - /admin/overview/about-github-ae - /admin/overview/about-data-residency @@ -12,6 +15,8 @@ deploy_an_instance: title: 'Implantar instância' description: 'Instalar {% data variables.product.prodname_ghe_server %} na sua plataforma de escolha e configurar a autenticação SAML.' featured_track: true + versions: + ghes: '*' guides: - /admin/overview/system-overview - /admin/installation @@ -22,6 +27,8 @@ deploy_an_instance: upgrade_your_instance: title: 'Atualizar sua instância' description: 'Teste as atualizações no treinamento, notifique os usuários de manutenção e atualize sua instância para os recursos mais recentes e atualizações de segurança.' + versions: + ghes: '*' guides: - /admin/enterprise-management/enabling-automatic-update-checks - /admin/installation/setting-up-a-staging-instance @@ -29,9 +36,22 @@ upgrade_your_instance: - /admin/user-management/customizing-user-messages-for-your-enterprise - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/enterprise-management/upgrading-github-enterprise-server +adopting_github_actions_for_your_enterprise: + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.' + guides: + - /actions/learn-github-actions/understanding-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server + - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae + - /actions/security-guides/security-hardening-for-github-actions increase_fault_tolerance: title: 'Aumente a tolerância de falha da instância' description: "Faça backup do código de seus desenvolvedores e configure alta disponibilidade (HA) para garantir a confiabilidade do {% data variables.product.prodname_ghe_server %} no seu ambiente." + versions: + ghes: '*' guides: - /admin/configuration/accessing-the-administrative-shell-ssh - /admin/configuration/configuring-backups-on-your-appliance @@ -41,6 +61,8 @@ increase_fault_tolerance: improve_security_of_your_instance: title: 'Melhore a segurança da sua instância' description: "Revise a configuração de rede e as funcionalidades de segurança e reforce a instância em {% data variables.product.prodname_ghe_server %} para proteger os dados da sua empresa." + versions: + ghes: '*' guides: - /admin/configuration/enabling-private-mode - /admin/guides/installation/configuring-tls @@ -54,6 +76,8 @@ improve_security_of_your_instance: configure_github_actions: title: 'Configurar {% data variables.product.prodname_actions %}' description: 'Permitir que seus desenvolvedores criem, automatizem, personalizem e executem poderosos fluxos de trabalho de desenvolvimento de software em {% data variables.product.product_location %} com {% data variables.product.prodname_actions %}.' + versions: + ghes: '*' guides: - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise @@ -64,6 +88,8 @@ configure_github_actions: configure_github_advanced_security: title: 'Configurar {% data variables.product.prodname_GH_advanced_security %}' description: "Melhore a qualidade e a segurança do código do seu desenvolvedor com {% data variables.product.prodname_GH_advanced_security %}." + versions: + ghes: '*' guides: - /admin/advanced-security/about-licensing-for-github-advanced-security - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise @@ -73,6 +99,9 @@ configure_github_advanced_security: get_started_with_your_enterprise_account: title: 'Get started with your enterprise account' description: 'Get started with your enterprise account to centrally manage multiple organizations on {% data variables.product.product_name %}.' + versions: + ghes: '*' + ghec: '*' guides: - /admin/overview/about-enterprise-accounts - /billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml index efef5c6697..f9463e073f 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml @@ -8,6 +8,7 @@ sections: - 'As contagens dos trabalhadores de Resque foram exibidas incorretamente no modo de manutenção. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - 'A memória memorizada memcached poderia ser zero no modo de clustering. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - 'Corrige versões {% data variables.product.prodname_pages %} para que elas levem em conta a configuração NO_PROXY do aparelho. Isto é relevante para os aparelhos configurados apenas com um proxy HTTP. (atualização 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml new file mode 100644 index 0000000000..ca1ccd136e --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml @@ -0,0 +1,22 @@ +--- +date: '2021-11-23' +sections: + security_fixes: + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - Pre-receive hooks would fail due to undefined `PATH`. + - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. + - Some critical services may not have been available on backend nodes in GHES Cluster. + changes: + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. + - Upgraded collectd to version 5.12.0. + - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + known_issues: + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - Quando um nó de réplica está off-line em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó off-line, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml new file mode 100644 index 0000000000..4262a53361 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml @@ -0,0 +1,25 @@ +--- +date: '2021-11-23' +sections: + security_fixes: + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. + - Pre-receive hooks would fail due to undefined `PATH`. + - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' + - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. + - Some critical services may not have been available on backend nodes in GHES Cluster. + changes: + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. + - Upgraded collectd to version 5.12.0. + - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + known_issues: + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - Se o {% data variables.product.prodname_actions %} estiver habilitado para {% data variables.product.prodname_ghe_server %}, a desmontagem de um nó de réplica com `ghe-repl-teardown` será bem-sucedida, mas poderá retornar `ERROR:Running migrations`. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml index de692d4953..2cbedda704 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml @@ -9,6 +9,7 @@ sections: - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' - 'Corrige versões {% data variables.product.prodname_pages %} para que elas levem em conta a configuração NO_PROXY do aparelho. Isto é relevante para os aparelhos configurados apenas com um proxy HTTP. (atualização 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' known_issues: - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml new file mode 100644 index 0000000000..a2787ae224 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml @@ -0,0 +1,29 @@ +--- +date: '2021-11-23' +sections: + security_fixes: + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. + - Pre-receive hooks would fail due to undefined `PATH`. + - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' + - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' + - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. + - Some critical services may not have been available on backend nodes in GHES Cluster. + - The repository permissions to the user returned by the `/repos` API would not return the full list. + - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. + - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. + - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. + changes: + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. + - Upgraded collectd to version 5.12.0. + - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + known_issues: + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. diff --git a/translations/pt-BR/data/reusables/actions/about-actions.md b/translations/pt-BR/data/reusables/actions/about-actions.md new file mode 100644 index 0000000000..04b25d13f2 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/about-actions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} helps you automate tasks within your software development life cycle. diff --git a/translations/pt-BR/data/reusables/actions/about-runners.md b/translations/pt-BR/data/reusables/actions/about-runners.md new file mode 100644 index 0000000000..08beb8c611 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/about-runners.md @@ -0,0 +1 @@ +Um executor é um servidor que tem o[aplicativo do executor de {% data variables.product.prodname_actions %}](https://github.com/actions/runner) instalado. Você pode usar um executor hospedado em {% data variables.product.prodname_dotcom %} ou você pode hospedar seu próprio. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/access-actions-on-dotcom.md b/translations/pt-BR/data/reusables/actions/access-actions-on-dotcom.md new file mode 100644 index 0000000000..d783080fb4 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/access-actions-on-dotcom.md @@ -0,0 +1 @@ +Se os usuários da sua empresa precisam de acesso a outras ações a partir de {% data variables.product.prodname_dotcom_the_website %} ou {% data variables.product.prodname_marketplace %}, há algumas opções de configuração. diff --git a/translations/pt-BR/data/reusables/actions/actions-bundled-with-ghes.md b/translations/pt-BR/data/reusables/actions/actions-bundled-with-ghes.md new file mode 100644 index 0000000000..19459efbf4 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/actions-bundled-with-ghes.md @@ -0,0 +1 @@ +A maioria das ações oficiais de autoria de {% data variables.product.prodname_dotcom %} são automaticamente agrupadas com {% data variables.product.product_name %} e são capturadas em um momento a partir do {% data variables.product.prodname_marketplace %}. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/general-security-hardening.md b/translations/pt-BR/data/reusables/actions/general-security-hardening.md new file mode 100644 index 0000000000..0cd70cd6f9 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/general-security-hardening.md @@ -0,0 +1,3 @@ +## Fortalecimento geral de segurança para {% data variables.product.prodname_actions %} + +Se você quiser saber mais sobre as práticas de segurança para {% data variables.product.prodname_actions %}, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/introducing-enterprise.md b/translations/pt-BR/data/reusables/actions/introducing-enterprise.md new file mode 100644 index 0000000000..b7e8b0856c --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/introducing-enterprise.md @@ -0,0 +1 @@ +Before you get started, you should make a plan for how you'll introduce {% data variables.product.prodname_actions %} to your enterprise. For more information, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/migrating-enterprise.md b/translations/pt-BR/data/reusables/actions/migrating-enterprise.md new file mode 100644 index 0000000000..9876b13360 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/migrating-enterprise.md @@ -0,0 +1 @@ +If you're migrating your enterprise to {% data variables.product.prodname_actions %} from another provider, there are additional considerations. For more information, see "[Migrating your enterprise to {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md new file mode 100644 index 0000000000..486bb3838a --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -0,0 +1,3 @@ +{% ifversion ghes or ghae %} +The connection between self-hosted runners and {% data variables.product.product_name %} is over HTTP (port 80) and HTTPS (port 443). +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/secret-scanning/api-beta.md b/translations/pt-BR/data/reusables/secret-scanning/api-beta.md index 7368c80c93..2aa4737698 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/api-beta.md +++ b/translations/pt-BR/data/reusables/secret-scanning/api-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghes > 3.0 %} +{% ifversion ghes > 3.0 or ghae-next %} {% note %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 45f71de946..4b07ccfaa8 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -140,7 +140,11 @@ Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} -Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token Shopify | Shopify Private App Password | shopify_private_app_password Slack | Slack API Token | slack_api_token Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url SSLMate | SSLMate API Key | sslmate_api_key SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret Stripe | Stripe API Key | stripe_api_key +Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token Shopify | Shopify Private App Password | shopify_private_app_password Slack | Slack API Token | slack_api_token Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url +{%- ifversion fpt or ghec or ghes > 3.3 %} +Square | Square Production Application Secret | square_production_application_secret{% endif %} +{%- ifversion fpt or ghec or ghes > 3.3 %} +Square | Square Sandbox Application Secret | square_sandbox_application_secret{% endif %} SSLMate | SSLMate API Key | sslmate_api_key SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret Stripe | Stripe API Key | stripe_api_key {%- ifversion fpt or ghec or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.0 or ghae %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 09e735a1bf..34b598c265 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -75,6 +75,8 @@ | Samsara | Token de API de Samsara | | Samsara | Token de acesso de OAuth de Samsara | | SendGrid | SendGrid API Key | +| Sendinblue | Sendinblue API Key | +| Sendinblue | Sendinblue SMTP Key | | Shopify | Segredo compartilhado do aplicativo Shopify | | Shopify | Token de acesso de Shopify | | Shopify | Token de acesso do aplicativo personalizado Shopify | @@ -91,4 +93,5 @@ | Tencent Cloud | ID de segredot de Tencent Cloud | | Twilio | Identificador de string de conta de Twilio | | Twilio | Chave da API de Twilio | +| Typeform | Typeform Personal Access Token | | Valour | Valour Access Token | diff --git a/translations/pt-BR/data/reusables/webhooks/workflow_job_properties.md b/translations/pt-BR/data/reusables/webhooks/workflow_job_properties.md index 087fbaf0ae..6203a0b1d7 100644 --- a/translations/pt-BR/data/reusables/webhooks/workflow_job_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/workflow_job_properties.md @@ -1,4 +1,10 @@ -| Tecla | Tipo | Descrição | -| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser uma das ações a seguir:
    • `queued` - A new job was created.
    • `in_progress` - The job has started processing on the runner.
    • `completed` - The `status` of the job is `completed`.
    | -| `workflow_job` | `objeto` | The workflow job. Many `workflow_job` keys, such as `head_sha`, `conclusion`, and `started_at` are the same as those in a [`check_run`](#check_run) object. | +| Tecla | Tipo | Descrição | +| --------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Ação` | `string` | A ação realizada. Pode ser uma das ações a seguir:
    • `queued` - A new job was created.
    • `in_progress` - The job has started processing on the runner.
    • `completed` - The `status` of the job is `completed`.
    | +| `workflow_job` | `objeto` | The workflow job. Many `workflow_job` keys, such as `head_sha`, `conclusion`, and `started_at` are the same as those in a [`check_run`](#check_run) object. | +| `workflow_job[status]` | `string` | Status atual do trabalho. Pode ser `queued`, `in_progress` ou `completed`. | +| `workflow_job[labels]` | `array` | Custom labels for the job. Specified by the [`"runs-on"` attribute](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on) in the workflow YAML. | +| `workflow_job[runner_id]` | `inteiro` | The ID of the runner that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`. | +| `workflow_job[runner_name]` | `string` | The name of the runner that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`. | +| `workflow_job[runner_group_id]` | `inteiro` | The ID of the runner group that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`. | +| `workflow_job[runner_group_name]` | `string` | The name of the runner group that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`. | diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index c6c523e7ad..8afb7b3796 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -151,7 +151,7 @@ prodname_arctic_vault: 'Cofre de Código do Ártico' prodname_copilot: 'GitHub Copilot' prodname_copilot_short: 'Copilot' #Command Palette -prodname_command_palette: 'GitHub Command Palette' +prodname_command_palette: 'Paleta de comando do GitHub' #Links product_url: >- {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index 9d49dc02a9..6ba64d8d33 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -1,6 +1,6 @@ --- -title: 管理用户帐户设置 -intro: 您可以更改个人帐户的多项设置，包括更改用户名和删除帐户。 +title: Managing user account settings +intro: 'You can change several settings for your personal account, including changing your username and deleting your account.' redirect_from: - /categories/29/articles/ - /categories/user-accounts/ @@ -23,12 +23,13 @@ children: - /deleting-your-user-account - /permission-levels-for-a-user-account-repository - /permission-levels-for-user-owned-project-boards + - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - /managing-security-and-analysis-settings-for-your-user-account - /managing-access-to-your-user-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do -shortTitle: 用户帐户设置 +shortTitle: User account settings --- diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/index.md b/translations/zh-CN/content/actions/deployment/about-deployments/index.md index f038c974df..3267edb591 100644 --- a/translations/zh-CN/content/actions/deployment/about-deployments/index.md +++ b/translations/zh-CN/content/actions/deployment/about-deployments/index.md @@ -10,4 +10,3 @@ children: - /about-continuous-deployment - /deploying-with-github-actions --- - diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md index a43a4570ce..463324f7b7 100644 --- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md +++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md @@ -11,4 +11,3 @@ children: - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine --- - diff --git a/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md b/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md index 01e2784d0d..7aea761e3a 100644 --- a/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md +++ b/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md @@ -9,4 +9,3 @@ versions: children: - /viewing-deployment-history --- - diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md index 0272c0839a..ce25ef4811 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md @@ -15,4 +15,3 @@ children: - /configuring-openid-connect-in-cloud-providers - /using-openid-connect-with-reusable-workflows --- - diff --git a/translations/zh-CN/content/actions/guides.md b/translations/zh-CN/content/actions/guides.md index 83baa6d656..7ac00d9b29 100644 --- a/translations/zh-CN/content/actions/guides.md +++ b/translations/zh-CN/content/actions/guides.md @@ -1,6 +1,6 @@ --- title: Guides for GitHub Actions -intro: '{% data variables.product.prodname_actions %} 的这些指南包含具体的使用案例和示例来帮助您配置工作流程。' +intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -13,6 +13,7 @@ learningTracks: - continuous_integration - continuous_deployment - deploy_to_the_cloud + - '{% ifversion ghec or ghes or ghae %}adopting_github_actions_for_your_enterprise{% endif %}' - hosting_your_own_runners - create_actions includeGuides: diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md index 437a5b1cb7..d92f270477 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: 配置企业 -intro: '在 {% data variables.product.product_name %} 启动并运行后，您可以配置企业适应组织需求。' +title: Configuring your enterprise +intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.' redirect_from: - /enterprise/admin/guides/installation/basic-configuration/ - /enterprise/admin/guides/installation/administrative-tools/ @@ -34,6 +34,7 @@ children: - /restricting-network-traffic-to-your-enterprise - /configuring-github-pages-for-your-enterprise - /configuring-the-referrer-policy-for-your-enterprise -shortTitle: 配置企业 + - /configuring-custom-footers +shortTitle: Configure your enterprise --- diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md deleted file mode 100644 index 0217eac360..0000000000 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: GitHub Actions for GitHub Enterprise Server 使用入门 -shortTitle: GitHub Actions 使用入门 -intro: '了解首次在 {% data variables.product.prodname_ghe_server %} 上启用和配置 {% data variables.product.prodname_actions %}。' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -redirect_from: - - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/enabling-github-actions-and-configuring-storage - - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server -versions: - ghes: '*' -type: how_to -topics: - - Actions - - Enterprise ---- - -{% data reusables.actions.enterprise-beta %} - -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% ifversion ghes %} - -本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_server %} 来使用 {% data variables.product.prodname_actions %}。 它涵盖了硬件和软件需求、存储选项以及安全管理策略。 - -{% endif %} - -## 查看硬件注意事项 - -{% ifversion ghes = 3.0 %} - -{% note %} - -**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)。” - -{% endnote %} - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -{% data variables.product.product_location %} 可用的 CPU 和内存资源决定了 {% data variables.product.prodname_actions %} 的最大作业吞吐量。 - -{% data variables.product.company_short %} 的内部测试展示了具有系列 CPU 和内存配置的 {% data variables.product.prodname_ghe_server %} 实例的以下最大吞吐量。 您可能会看到不同的吞吐量，具体取决于实例的总体活动水平。 - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -可用于 {% data variables.product.product_location %} 的 CPU 和内存资源可确定可同时运行且不造成绩效损失的工作数量。 - -在没有性能损失的情况下并行工作的高峰数量取决于作业持续时间限、构件使用、运行操作的仓库数量，以及实例所做的与操作无关的其他工作量等。 GitHub 的内部测试在一系列 CPU 和内存配置中证明了 GitHub Enterprise Server 的以下性能目标： - -{% endif %} - -{%- ifversion ghes < 3.2 %} - -| vCPU | 内存 | 最大作业吞吐量 | -|:---- |:------ |:------- | -| 4 | 32 GB | 演示或轻量测试 | -| 8 | 64 GB | 25 个作业 | -| 16 | 160 GB | 35 个作业 | -| 32 | 256 GB | 100 个作业 | - -{%- endif %} - -{%- ifversion ghes > 3.1 %} - -| vCPU | 内存 | 最大并行数* | -|:---- |:------ |:-------- | -| 32 | 128 GB | 1500 个作业 | -| 64 | 256 GB | 1900 个作业 | -| 96 | 384 GB | 2200 个作业 | - -*最大并行数使用多个仓库、约 10 分钟的作业持续时间以及 10 MB 构件上传测得。 您可能会经历不同的性能，具体取决于实例的总体活动水平。 - -{%- endif %} - -If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. 有关监控 {% data variables.product.prodname_ghe_server %} 容量和性能的更多信息，请参阅“[监控您的设备](/admin/enterprise-management/monitoring-your-appliance)”。 - -有关 {% data variables.product.product_location %} 的最低硬件要求的更多信息，请参阅实例平台的硬件考虑因素。 - -- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) -- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) -- [Google Cloud 平台](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) -- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) -- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) -- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %} -- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %} - -{% data reusables.enterprise_installation.about-adjusting-resources %} - -## 外部存储要求 - -要在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %}，您必须有权访问外部 Blob 存储。 - -{% data variables.product.prodname_actions %} 使用 Blob 存储来存储工作流程运行生成的构件，如工作流程日志和用户上传的构建构件。 所需存储量取决于您使用 {% data variables.product.prodname_actions %} 的情况。 仅支持单个外部存储配置，不能同时使用多个存储提供程序。 - -{% data variables.product.prodname_actions %} 支持以下存储提供商： - -* Azure Blob 存储 -* Amazon S3 -* S3 兼容的 MinIO Gateway for NAS - -{% note %} - -**注：**只有这些是 {% data variables.product.company_short %} 支持并可以提供帮助的存储提供程序。 由于 S3 API 的差异，其他 S3 API 兼容的存储提供程序难以正常工作。 [联系我们](https://support.github.com/contact) 以请求支持额外的存储提供程序。 - -{% endnote %} - -## 网络考虑因素 - -{% data reusables.actions.proxy-considerations %} 有关使用 {% data variables.product.prodname_ghe_server %} 代理的更多信息，请参阅“[配置出站网络代理服务器](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)”。 - -{% ifversion ghes %} - -## 使用您的存储提供程序启用 {% data variables.product.prodname_actions %} - -请按照以下过程之一使用所选存储提供程序启用 {% data variables.product.prodname_actions %}： - -* [使用 Azure Blob 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) -* [使用 Amazon S3 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) -* [使用 MinIO Gateway for NAS 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) - -## 管理企业中 {% data variables.product.prodname_actions %} 的访问权限 - -您可以使用策略来管理 {% data variables.product.prodname_actions %} 的访问。 更多信息请参阅“[为企业执行 GitHub Actions 策略](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)”。 - -## 添加自托管的运行器 - -{% data reusables.actions.enterprise-github-hosted-runners %} - -要运行 {% data variables.product.prodname_actions %} 工作流程，您需要添加自托管运行器。 您可以在企业、组织或仓库级别添加自托管运行器。 更多信息请参阅“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 - -## 管理哪些操作可用于您的企业 - -您可以控制允许用户在企业中使用哪些操作。 这包括设置 {% data variables.product.prodname_github_connect %} 以自动访问来自 {% data variables.product.prodname_dotcom_the_website %} 的操作，或手动同步来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。 - -更多信息请参阅“[关于使用企业中的操作](/admin/github-actions/about-using-actions-in-your-enterprise)”。 - -## {% data variables.product.prodname_actions %} 的一般安全性增强 - -如需了解有关 {% data variables.product.prodname_actions %} 安全实践的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions)”。 - -{% endif %} - -## 保留名称 - -为企业启用 {% data variables.product.prodname_actions %} 时，将创建两个组织：`github` 和 `actions`。 如果您的企业已经使用 `github` 组织名称，则将改用 `github-org` （如果 `github-org` 也在使用中，则改用 `github-github-org`）。 如果您的企业已经使用 `actions` 组织名称，则将改用 `github-actions`（如果 `github-actions` 也在使用中，则改用 `github-actions-org`）。 启用操作后，您将无法再使用这些名称。 diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 5766324a27..ee0f477635 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -1,16 +1,15 @@ --- -title: 启用 GitHub Actions for GitHub Enterprise Server -intro: '了解如何配置存储并在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %}。' +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' versions: ghes: '*' topics: - Enterprise children: - - /getting-started-with-github-actions-for-github-enterprise-server - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - /setting-up-dependabot-updates -shortTitle: 启用 GitHub Actions +shortTitle: Enable GitHub Actions --- diff --git a/translations/zh-CN/content/admin/github-actions/index.md b/translations/zh-CN/content/admin/github-actions/index.md index ed287f3097..808fdae5b0 100644 --- a/translations/zh-CN/content/admin/github-actions/index.md +++ b/translations/zh-CN/content/admin/github-actions/index.md @@ -1,19 +1,21 @@ --- -title: 管理企业的 GitHub Actions -intro: '在 {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} 上启用 {% data variables.product.prodname_actions %}，并管理 {% data variables.product.prodname_actions %} 策略和设置。' +title: Managing GitHub Actions for your enterprise +intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, and manage {% data variables.product.prodname_actions %} policies and settings.' redirect_from: - /enterprise/admin/github-actions versions: + ghec: '*' ghes: '*' ghae: '*' topics: - Enterprise children: + - /getting-started-with-github-actions-for-your-enterprise - /using-github-actions-in-github-ae - /enabling-github-actions-for-github-enterprise-server - /managing-access-to-actions-from-githubcom - /advanced-configuration-and-troubleshooting -shortTitle: 管理 GitHub Actions +shortTitle: Manage GitHub Actions --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md deleted file mode 100644 index 5d620fdd98..0000000000 --- a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: GitHub Actions for GitHub AE 使用入门 -shortTitle: GitHub Actions 使用入门 -intro: '了解在 {% data variables.product.prodname_ghe_managed %} 上配置 {% data variables.product.prodname_actions %}。' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -versions: - ghae: '*' -type: how_to -topics: - - Actions - - Enterprise -redirect_from: - - /admin/github-actions/getting-started-with-github-actions-for-github-ae ---- - -{% data reusables.actions.ae-beta %} - -本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_managed %} 来使用 {% data variables.product.prodname_actions %}。 - -## 管理企业中 {% data variables.product.prodname_actions %} 的访问权限 - -您可以使用策略来管理 {% data variables.product.prodname_actions %} 的访问。 更多信息请参阅“[为企业执行 GitHub Actions 策略](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)”。 - -## 添加运行器 - -{% note %} - -**注意：**要添加 {% data variables.actions.hosted_runner %} 到 {% data variables.product.prodname_ghe_managed %}，您需要联系 {% data variables.product.prodname_dotcom %} 支持。 - -{% endnote %} - -要运行 {% data variables.product.prodname_actions %} 工作流程，您需要添加运行器。 您可以在企业、组织或仓库级别添加运行器。 更多信息请参阅“[关于 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)”。 - - -## {% data variables.product.prodname_actions %} 的一般安全性增强 - -如需了解有关 {% data variables.product.prodname_actions %} 安全实践的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions)”。 diff --git a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md index 351bf06fbc..ed67e364c7 100644 --- a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md +++ b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md @@ -1,11 +1,10 @@ --- -title: 在 GitHub AE 中使用 GitHub Actions -intro: '了解如何在 {% data variables.product.prodname_ghe_managed %} 上配置 {% data variables.product.prodname_actions %}。' +title: Using GitHub Actions in GitHub AE +intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.' versions: ghae: '*' children: - - /getting-started-with-github-actions-for-github-ae - /using-actions-in-github-ae -shortTitle: 在 GitHub AE 中使用 Actions +shortTitle: Use Actions in GitHub AE --- diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md index dfe56e529b..6eee293a97 100644 --- a/translations/zh-CN/content/admin/guides.md +++ b/translations/zh-CN/content/admin/guides.md @@ -1,7 +1,7 @@ --- -title: GitHub Enterprise 指南 -shortTitle: 指南 -intro: '学习如何通过 {% data variables.product.product_name %} 提高开发人员的工作效率和代码质量。' +title: GitHub Enterprise guides +shortTitle: Guides +intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.' allowTitleToDifferFromFilename: true layout: product-sublanding versions: @@ -9,14 +9,15 @@ versions: ghes: '*' ghae: '*' learningTracks: + - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' - '{% ifversion ghae %}get_started_with_github_ae{% endif %}' - '{% ifversion ghes %}deploy_an_instance{% endif %}' - '{% ifversion ghes %}upgrade_your_instance{% endif %}' + - adopting_github_actions_for_your_enterprise - '{% ifversion ghes %}increase_fault_tolerance{% endif %}' - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}' - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}' - - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}' includeGuides: - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - /admin/authentication/changing-authentication-methods diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md index b44b7a6478..4341a5a61c 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -35,7 +35,7 @@ topics: 企业所有者可以完全控制企业，并可以采取所有操作，包括： - 管理管理员 -- {% ifversion ghec %}添加和删除{% elsif ghae or ghes %}管理{% endif %}{% elsif ghae or ghes %}{% endif %}企业中的组织{% ifversion ghec %}。 +- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise - 管理企业设置 - 在组织范围内强制实施政策 {% ifversion ghec %}- 管理帐单设置{% endif %} diff --git a/translations/zh-CN/content/billing/index.md b/translations/zh-CN/content/billing/index.md index fca5bb4e71..067b356ef5 100644 --- a/translations/zh-CN/content/billing/index.md +++ b/translations/zh-CN/content/billing/index.md @@ -1,15 +1,46 @@ --- -title: Billing and payments for GitHub -shortTitle: 计费和付款 -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}.{% endif %}' +title: Billing and payments on GitHub +shortTitle: Billing and payments +intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github +introLinks: + overview: '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/about-billing-on-github{% elsif ghes%}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' +featuredLinks: + guides: + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method{% endif %}' + - '{% ifversion fpt %}/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription{% endif %}' + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/setting-your-billing-email{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/about-per-user-pricing{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + popular: + - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}' + - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security{% endif %}' + - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}' + - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}' + guideCards: + - /billing/managing-your-github-billing-settings/removing-a-payment-method + - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process + - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}' + - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud{% endif %}' +layout: product-landing versions: fpt: '*' - ghec: '*' ghes: '*' ghae: '*' + ghec: '*' +topics: + - Billing children: - /managing-your-github-billing-settings - /managing-billing-for-your-github-account @@ -23,5 +54,4 @@ children: - /managing-billing-for-github-marketplace-apps - /managing-billing-for-git-large-file-storage - /setting-up-paid-organizations-for-procurement-companies ---- - +--- \ No newline at end of file diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 211ce54ec4..96dec45cdf 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -35,6 +35,24 @@ topics: To produce more detailed logging output, you can enable step debug logging. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)." +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5601 %} + +## Creating {% data variables.product.prodname_codeql %} debugging artifacts + +You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %} by setting a debug configuration flag. Modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`. + +``` +- name: Initialize CodeQL + uses: github/codeql-action/init@v1 + with: + debug: true +``` +The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. + +These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} code scanning. If you contact GitHub support, they might ask for this data. + +{% endif %} + ## Automatic build for a compiled language fails If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps. diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index bbe6c925b7..14ea4e4b20 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -59,7 +59,7 @@ You can use the dependency graph to: - Explore the repositories your code depends on{% ifversion fpt or ghec %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% ifversion fpt or ghec %} - View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} - View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes > 3.1 or ghec %} -- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."{% endif %} +- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %} ## Enabling the dependency graph diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md index e6df934439..48cb432198 100644 --- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md @@ -1,6 +1,6 @@ --- -title: 使用高级格式 -intro: 表格、语法突出显示和自动链接等格式设置可让您在拉取请求、议题和评论中清楚地布置复杂的信息。 +title: Working with advanced formatting +intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.' redirect_from: - /articles/working-with-advanced-formatting versions: @@ -10,11 +10,12 @@ versions: ghec: '*' children: - /organizing-information-with-tables + - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet - /using-keywords-in-issues-and-pull-requests -shortTitle: 使用高级格式 +shortTitle: Work with advanced formatting --- diff --git a/translations/zh-CN/content/graphql/guides/index.md b/translations/zh-CN/content/graphql/guides/index.md index 3d2fae5acc..7311e5cf39 100644 --- a/translations/zh-CN/content/graphql/guides/index.md +++ b/translations/zh-CN/content/graphql/guides/index.md @@ -1,6 +1,6 @@ --- -title: 指南 -intro: 了解如何开始使用 GraphQL、从 REST 迁移到 GraphQL 以及如何利用 GitHub GraphQL API 执行各种任务。 +title: Guides +intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.' redirect_from: - /v4/guides versions: @@ -18,5 +18,6 @@ children: - /using-the-explorer - /managing-enterprise-accounts - /using-the-graphql-api-for-discussions + - /migrating-graphql-global-node-ids ---